Mine just did it again.
I am making a reel 2 reel tape tonight ready for the show. Streaming, went from a normal res track to hi res and it did it again.
Mine is definitely getting more frequent
1 Like
Hi @Dunc
When it happens is it always at the start of a track?
If so then is it at a sample rate change or have you had it happen between tracks of the same sample rate?
If you stick to all 44kHz based (so 44.1, 88.2, 176.4) tracks then does it still happen? Same with 48kHz based (48, 96, 192)?
P
Hi Phil
Always happens at the start of the track.
I think its when the sample rate changes, well it was last night, but i can’t 100% say.
That i don’t know, sorry.
OK … let me start digging and see what we can find.
How long does it take before you get this to happen?
It would be really handy if you could do a listening session with only 44.1kHz (and - more difficult I know - another session with only 48k) based audio and see if you can get the same issue.
All the controls on the DAC still work when it does this don’t they (volume, menu buttons etc)?
Is the DAC still showing the correct input format coming from the Upsampler?
P
Most of these problems can be resolved by 2s long press switch off and reboot. Most units will remain fine for a few days afterwards.
My complete stack was completely turned off for 3 weeks, at the beginning of September. It hasn’t made a difference, as its happened a few tines since.
Plus over the last year, that this had been happening, my vivaldi kit has been switched off many times
Mine would crash whenever I switched between USB and Ethernet input with different resolutions. DSD files are amongst the very worst culprits. The crash would manifest as skipping, 2X playback speed, front panel timer stopped counting for a few seconds then skipped to the correct time and stopped again. Usually the system will reboot by itself. After the reboot Mosaic will not show clock lock (showing “–” only) but front panel will show W1/W2 locked correctly. I have to power cycle the master clock to correct this problem.
I have gotten used to such problems which can usually be resolved by rebooting. Except on one occasion when the front panel power switch could only induce certain circuit board relay clicking sound but the unit remained switched on with music still playing.
1 Like
This seems different from the issue reported by @Dunc . As he is is a dialogue with support I will leave it to them . Phil requested some information from him a couple of days ago.
Your issue with Mosaic crashing sounds like a problem with your network and/or its settings. You may wish to contact support for guidance .
1 Like
Thanks Pete.
Little update.
Been sent a file to upload to the upsampler, this i have just done, and will see how i get on.
Thanks to Phil, and the team at dCS for being very helpful, quick, etc, at trying to sort this issue out.
2 Likes
Phil
Is it possible that this file that I have downloaded could effect the sound?
As I could be fooling myself, easily done. But things seem to be slightly clearer?
I noticed that the file I loaded looked to be a complete reflash of the hole upsampler, rather than a update.
I just hope it has sorted it and I keep on thinking it sounds better for it. Maybe mine was a bit ill all the time for some reason, and at times very bad. I am sure you know much more than me on this, and like I said probably all in my head.
Cheers dunc
If nothing has changed sound wise then I am officially going mad.
More importantly its working fine so far.
1 Like
Hi @Dunc
There shouldn’t be any change in how it sounds … but in this world madness is always very closeby.
Phil
I had upgraded from Bartok APEX to Rossini APEX, and both have similar problems. Pete is probably right, that the problem is external because two different DACs have similar issues.
I am currently using Mosaic with M4 MacBook Pro. Router is Asus BQ16 mesh WiFi (everything is connected together with ethernet cables, even the satellite nodes are hardwired to the master node).
Ah! Mesh wi-fi. A factor in many similar issues posted here. I expect that @Phil will be able to help you on this.
1 Like
I have used two versions of Netgears Orbi mesh set-ups over the past 8 years and “once past” the initial set all has been rock solid. So blaming mesh to me is just an easy answer.
I concur. I’ve used 2 different versions of TP-Link DECO mesh wif-fi systems, nary a problem with my Rossini APEX.
BUT. There can be only one boss in a local network, so I’ve set up the DECO network in AP (Access Point) mode, so IP address allocation is handled by the router supplied by my network provider. No double NAT-ing, no two different DHCP servers handing out IP addresses.
Most mesh systems want to be routers by default, that is usually a bad idea. Best leave all routing to the box you get from your provider.
Sorry Dunc for sidetracking the thread.
One other thing I have noticed, is that when I am running Mosaic on a MacBook, everything seems to be more stable if Mosaic always remains the frontmost window (kind of like “currently running window”). Connection between Mosaic and Rossini is rock solid if left this way.
Most of the time, however, I am browsing the web on Safari. Mosaic becomes running in the background. This may lead to disconnection between Mosaic and Rossini.
I discovered such disconnections when sometimes I close Safari, Mosaic has to reconnect to Rossini. This rarely happens when Mosaic always stays as the frontmost window.
I am not sure if this will affect playback stability.
So, network discussions …
Yes, I know it seems to be a cop out when I/we go “I think it’s a network issue” and usually the reply I’ll get is “But my computer and phone work fine on my network” however…
…doing support you get a handle on what things are LIKELY to be (there are always exceptions that make life more interesting) but on the whole you get a feeling pretty quickly on whether you’re looking for an issue inside or outside the unit … this is why usually the first thing that I’ll ask for is the unit to be connected directly back to the router and any additional wireless access points or network extenders turned off and then test the setup again.
One issue that does pop up quite frequently with mesh networks and wireless network extenders / Ethernet over mains devices is their handling of UDP / IGMP and that’s what is used for autodiscovery of dCS devices from the app which can then cause the app to be unable to connect.
Often in that case rebooting the streamer (which makes it then rebroadcast its presence on the network) often kicks things back into life but that can very easily be taken as a problem with the streamer rather than with the network …
I guess what I’m trying to say is when we/I say “I think you have a network issue” that isn’t a get out or a passing of the buck - we do try to get things resolved even if it is a network problem.
Phil
6 Likes