Just to update my issue.
I sent my log off and got sent a file to download to the upsampler. I believe this was an earlier version, but whatever it has been fine since doing this.
So tonight I have updated my upsampler back to the latest version. Going to see how I get on with.
But the team at dCS have been very supportive with this and obviously still on board if I get the problem reoccurring again.
Cheers dunc
It had been working faultlessly since I put it back to the latest software version. But last night playing a DSC file from my melco, it once again went a bit wrong.
This time not as bad as it can be, and a quick switch over as before solved it straight away.
Hopefully it won’t keep happening going forward and it was a small glitch, but lets see.
I feel it might have to go back, but hopefully not.
Sorry to say but my problems are back.
It’s happening again, started about a week ago, not every night, but it has just happened again tonight. I did the update last night, just for reference.
Sorry to hear this.
Reading the thread it seems that the issue occurs when different file types follow each other. Your previous post defers to it happening when you played a DSD file, I assume after a PCM one. Similarly does it happen if you change upsample rate to,say, DSDx2 ?
I am wondering if you can can hear the mute relay clicking during the change?
I went back to an earlier software and it was fine, I have since gone back to what was the latest version and last night uploaded the new version.
It played up tonight while I was streaming from qobuz, but it did it also once about 10 days ago. Was hoping it was just a once only, but it looks like it’s going back to be tested.
It’s got one more chance then that’s it
So, it isn’t related to file type changes but the Vivaldi Upsampler firmware where the two most recent versions cause the issue but the earlier firmware that Phil sent you fixed it. Is that correct?
If so this still seems to be something to refer again to dCS Support.
What? You are going to dispose of it?
No send it back to dCS
My chatbot told me that dCS engineering will conclude that there is a hardware fault in your specific Upsampler (e.g. something marginal in memory/FPGA/clock logic) and fix/replace it after bench testing.
I’ve been experiencing the same issues with my Vivaldi Apex full stack + Antipodes K41 (server only). The only way to overcome the issue is by physically rebooting each unit. Any advice other than leave the dCS units on (which I still have to test)? Thanks. F.
FRanco, it isn’t possible to judge if you are experiencing precisely the same issues as @Dunc without some detailed information, let alone finding a solution.
Duncan left this thread saying that if the fault is repeated he would be sending the unit ( or units?) back to dCS however we have Heard nothing further. In the meantime I would suggest that you contact support at dCS for their assistance ( as Duncan has):
BTW, I would also suggest that you do not switch off Vivaldi but switch it to sleep mode only. This is not connected with your issue but preserves the batteries which power the memories of the units whilst they are switched off. However ultimately they will need replacing ( I think an average life of 10 years life has been mentioned).
Mine hasn’t played up since. I know probably tempting fate.
So it doesn’t go away if you change the upsampling rate in mosaic?
If i change from DSD x 2 to another rate, it goes instantly. Or if I changed the filter map.
Thanks Pete. It happened more than once and yes I will contact dCS’ assistance next time.
I’ve always put dCS in standby when I don’t use it. Is that what you mean?
Hello Duncan, no I haven’t tried that. Are you suggesting that it has something to do with the upsampler?
Try it as like I said it sorts mine out straight away, and yes upsampler rather than dac.
yes. This part of my reply was suggested by you saying:
Just sent a new log off as it happening again.
I feel its time it came back for you guys to look at.
Dunc, I will tag @Phil to ensure that he sees your post above:
Cheers
But sent the email off to dCS support, same as last time. So they will have it.
Just need to get this sorted once and for all.
I asked my chatbot „what should Dunc do?“
<<If you want it in one sentence: grab logs during the event, send them to dCS Support, and get the Upsampler sent back in for investigation/repair.>>