Could be - except that power-cycling the dCS fixed the problem.
I’m suspecting that the issue is related to the dCS not properly handling different sample rates.
I’m deeply aware of this kind of problem as we see a similar issue with people who use our software (plugin host for performing musicians) at the same time as another product where one is configured at 44.1k and the other is at 48k. In that scenario, the pitch is off by about 1 semitone.
The Tidal sources were at 44.1k with MQA but the Qobuz source (same piece of music) was at 96k and it was after I switched back to the Tidal source that the problem occurred. The 96k is just a bit over double that of the 44.1k and misinterpreting the sample rate would absolutely cause this issue.
Given the history of dCS as well as their contribution to the protocols for the distribution of hi-res music data I think that this is unlikely. Ben’s linked history of his similar problem supports my expectation that this will turn out be some kind of network problem. Maybe @Anupc ( see Ben’s second link) will contribute to this thread when the time in his zone is suitable.
I had a similar situation and the music was playing twice as fast. Resetting Bartók with the switch on the back helped. I use Minimserver on Qnap NAS and Mosaic to select music. I was not able to repeat this problem. I wonder if this has nothing to do with the upsampling mode. The problem occurred after switching from DSD to DXD upsampling.
FYI, similar to your issue, I once had an issue with Qobuz music playing too fast on a non-dCS DAC through Roon and USB. Just restarted everything and problem solved. I’ve only seen this issue the one time.
Between the two incidents, my assumption is that it’s a streaming issue, or a hiccup with the services/app chain (and possibly devices).
Hmm, I read through it - it doesn’t really support that theory.
I’m not aware of any network mechanism that would explain how just one piece of music can play at twice the rate and an octave (or so) higher while everything else plays properly whereas I can easily imagine how a cached stream of data could get interpreted wrong if the system doesn’t have the correct sample rate for that cached stream. (I’m not saying that’s the issue, just noting a more likely possibiity — Occam’s Razor and all that!)
If same the piece continued to be played wrong after resetting everything then I would suspect that wrong meta data was being received (therefore an issue with the provider) but it played perfectly fine after a reset.
Yeah, I have 40 years of software experience as well but somehow bugs still manage to get into my software!
I know exactly what you’re referring to, and as others have said, it’s highly likely to be network-related. I had several UPNP players before my dCS and they all eventually encountered an issue like you describe, requiring a reboot of the player. Rest assured, it’s not you or your Bartok.
The player will perform a new network discovery upon reboot, something it doesn’t routinely perform once established.
I must apologize, I completely glossed over your second bullet point. I don’t see how that can be network related. But the 1st one can and almost always is.
Though I did not have exactly this kind of problem but had different kind of network issues in my setup and then I found somewhere that disabling IPV6 in Internet would help. I did that and since then my setup runs smooth.
Yes, I understand that, but if you request uPNP and there’s nothing there (although not clear why something wasn’t there!), it should retry network discovery at that point. Hence I view this as, if not a bug, then a missing “feature”
My fault - I should have reported these separately.
No idea but probably shouldn’t be too concerned unless it is a recurring problem. Once you get Roon you’ll most likely be so happy you’ll forget any of this ever happened.
David, almost universally, problems associated with UPnP Server/Client visibility has do with the home network not properly passing Multicast traffic. Even when the Bartok is working properly, if your network occasionally gobbles-up multicast packets, things won’t work properly, so, you might want to double check your Ethernet Switch configuration to be sure it’s not filtering out multicast packets (usually based on IGMP Snooping or Proxying).
Agreed. Your double-speed playback problem is highly unlikely to be (home) network associated. A quick Google search seems to show others with non-dCS DACs having the exact same problem. Tidal seems to be a common factor in most cases, even via Roon, here’s an example;
A Bartok reboot “solving” the problem doesn’t automatically point to a problem with Bartok (especially considering some of us have had the Bartok for over 2 years without ever encountering this problem ).
Hmm, I’m using TrendNet 24-Port Gigabit switches but IGMP is disabled. I have quite a few zero-conf devices on my LAN. I’ll keep an eye on this though. On the other hand, it would be nice if the Bartok would let me manually define the IP address for a media server so that it doesn’t have to rely on uPnP to find it.
It doesn’t definitely prove it — but presumably the Bartok (and other streamers) have to know how to decode incoming data from Tidal. If the problem was due to a faulty Tidal stream, then I would not expect rebooting the Bartok to fix the problem as the incoming data stream would presumably still be faulty.
Obviously I don’t know why it happened - nor is it my responsibility to debug the problem - I simply don’t want to experience it!
Which model if I may ask? (By the way, TRENDNet is not Trend Micro - two very separate companies ).
Generally I would say you’re right. That said, there’s a significant amount of “chatter” that goes on between the Streaming services and the DAC, it’s very easy for things to go haywire occasionally.
ps: I just noticed you used the plural;
Are your Bartok and UPnP Server on different LAN segments?
Also, the “quality” of your internet connection plays a significant part in this as well. Albeit, the chatter between the Streaming services and Bartok are completely stateless, so, problems occurring should be rare.
And by the way, it’s not without precedent for Tidal to do stuff that adversely affects the DAC playback. For example; MPEG and not MQA - #41 by PAR
The reason behind this is that Tidal have unilaterally changed how they are identifying Tidal Master files. So the cause does not lie with Mosaic but that the change by Tidal has resulted in this outcome.
Ultimately, there could be a whole host of reasons for your double-speed playback incident, maybe best to just report it separately if you encounter it again.
As for Tidal, I’m not going to keep it — I have been trialing Tidal vs Qubuz and I’ve decided to keep Qubuz. So hopefully I won’t have this problem again.
).
