Sub-millisecond differences in latency are inconsequential in audio applications.Latency can play a major role here.
Sub-millisecond differences in latency are inconsequential in audio applications.Latency can play a major role here.
A one millisecond frequency is an octave below a two millisecond frequency. Nicht Wahr? Or is this the wrong context?Sub-millisecond differences in latency are inconsequential in audio applications.
Wrong context I think - this is latency in network packet arrival, and unless MiniDSP have done something very unusual with the MPD configuration, its buffers will be much bigger than required to cover that.A one millisecond frequency is an octave below a two millisecond frequency. Nicht Wahr? Or is this the wrong context?
Right. The time required to transmit a maximum-size (1500 bytes) Ethernet frame at 100 Mbps is 0.12 ms. That's not enough to matter for audio streaming.Wrong context I think - this is latency in network packet arrival, and unless MiniDSP have done something very unusual with the MPD configuration, its buffers will be much bigger than required to cover that.
Thanks for that. Trouble is: can you bring this down to my level. 'network packet' and MiniDSP mean nothing to me.Wrong context I think - this is latency in network packet arrival, and unless MiniDSP have done something very unusual with the MPD configuration, its buffers will be much bigger than required to cover that.
I'll have a go. If you follow the quotes back up the thread you'll see mansr and Gradius were discussing an issue in the network streaming part of the MiniDSP SHD DAC and streamer. Networks transfer small chunks of data known as packets, and some variation in when they arrive is to be expected as that's how networks work. Streaming audio requires the data to be split into these packets, sent, then reassembled by the receiving end, which keeps a buffer to cover the maximum expected delay in the network. As I understand it the receiving application used by MiniDSP in the SHD is called MPD, and by default keeps a buffer big enough for several seconds of audio. Packets would have to be delayed by long enough for the data in the buffer to run out before the DAC would see any difference, so sub-millisecond changes in packet arrival are invisible to the DAC.Thanks for that. Trouble is: can you bring this down to my level. 'network packet' and MiniDSP mean nothing to me.
Those letter segments are the pits. Certainly doesn't provide confidence in the business. I don't own any of its products and I don't think I ever will.Let me be clear: I think PS Audio products are shown to be poor, and Paul McGowan appears to be a bullshitter.
is there something you specifically don't comprehend?Uh-huh.
Before all the sceptics start quoting digital is just 0's and 1's, it's time for them to understand there is very little difference between the way analog and digital signals travel through cables. In fact the main difference is analog is sine wave, while digital is square wave. If you accept that shielding is necessary so that sine waves are not contaminated, then there is no reason to suggest square waves are any different. If EMI and RFI did not exist even at miniscule levels, there would be no need for shielding.
Perhaps I should have explained the square wave isn't audio but digital and in the respect it is a switch; on/off which represents 0's and 1's.
I am certain the I²S cable has better shielding than the USB cable, particularly as those with high throughput require a superior level of shielding to achieve their rating.
Before all the sceptics start quoting digital is just 0's and 1's, it's time for them to understand there is very little difference between the way analog and digital signals travel through cables. In fact the main difference is analog is sine wave, while digital is square wave. If you accept that shielding is necessary so that sine waves are not contaminated, then there is no reason to suggest square waves are any different. If EMI and RFI did not exist even at miniscule levels, there would be no need for shielding.
is there something you specifically don't comprehend?
What is an I2S cable? There is no such official thing. I2S is an internal bus to sane people. If you mean an HDMI cable carrying LVDS pairs of the I2S signals, then fine... but it's an HDMI cable.
I2S is slow. USB 3.x SS 5Gbps and SS+ 10Gbps are real things, you know. As is Thunderbolt and DP Alt Mode over USB cables. HDMI cables might be theoretically better but the difference manifests itself at incredibly high rates, nothing that will impact the integrity of this janky I2S connection.
In any case, it has little to do with their shield construction...