Jump to content
IGNORED

USB audio transmission isn’t bit true


Recommended Posts

  • 5 weeks later...
8 hours ago, Em2016 said:

 

Somebody in another forum was commenting that error correction with USB audio is not possible:

 

"That would not make any sense to resend any audio packets when music is playing in real time."

 

Could you explain how a custom protocol could allow this? In the context of real-time music playback (like streaming Tidal for example, if the app could use this custom protocol).

 

Not that I'm at all worried about dropped USB audio packets - just very interested in the technical side.

The TCP connection to Tidal has no problem with retransmissions.

Link to comment
32 minutes ago, Em2016 said:

Noted. I meant real-time streaming of Tidal on a PC to a USB DAC (via direct USB cable connection from PC to USB DAC).

Real-time streaming from Tidal to a PC works fine with retransmissions actually happening. Why would the next hop, PC to DAC, have issues? As Peter already said, you just need a bit of buffer in the DAC and some extra bandwidth.

Link to comment
  • 3 months later...
1 hour ago, OE333 said:

So why was the Isochronous USB mode chosen for Audio transmissions ?

The reason is that USB Audio was (and is) mainly used for Pro-Audio equipment (the few Computer Audiophiles do not count). In Pro Audio the main interest is to avoid any latency - so the input buffers needed for error correction (with several ms latency) are an absolute No-No.

Latency is one reason, guaranteed bandwidth another. With bulk mode, a data burst on another device might eat into the bandwidth and cause drop-outs of indefinite length. Isochronous mode reserves bandwidth upfront that can't be used by other devices.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...