Fix: Ringbuf patch release requires explicit type param

Ringbuf 0.4.2 onwards adds in a new storage type for `SharedRb`.
Unfortunately, this is handled in such a way that we fail to
compile because an explicit type parameter is required to
disambiguate the method in question.

src/input/adapters/async_adapter.rs

@@ -3,7 +3,7 @@ use async_trait::async_trait;
 use flume::{Receiver, RecvError, Sender, TryRecvError};
 use futures::{future::Either, stream::FuturesUnordered, FutureExt, StreamExt};
 use parking_lot::Mutex;
-use ringbuf::{traits::*, *};
+use ringbuf::{storage::Heap, traits::*, *};
 use std::{
     io::{
         Error as IoError,
@@ -156,7 +156,7 @@ impl AsyncAdapterStream {
     /// between the async and sync halves.
     #[must_use]
     pub fn new(stream: Box<dyn AsyncMediaSource>, buf_len: usize) -> AsyncAdapterStream {
-        let (bytes_in, bytes_out) = SharedRb::new(buf_len).split();
+        let (bytes_in, bytes_out) = SharedRb::<Heap<_>>::new(buf_len).split();
         let bytes_out = bytes_out.into();
         let (resp_tx, resp_rx) = flume::unbounded();
         let (req_tx, req_rx) = flume::unbounded();