INTERACT FORUM
Devices => JRiver Id -- Hardware by JRiver => Topic started by: Fred H on December 21, 2022, 12:01:47 pm
-
Due to some reshuffling I've unplugged and replugged the USB from the IdPi from the DAC (Topping D30Pro) several times. Before, I had the Id set to provide all rates up to the DAC's limit (384KHz) and it worked for all.
Now I have to run everything at 48K -- and, if I choose anything else then MC crashes.
Everything in the setup has returned to what it was before the reshuffling. Any ideas on how to get back where I was?
-
Due to some reshuffling I've unplugged and replugged the USB from the IdPi from the DAC (Topping D30Pro) several times. Before, I had the Id set to provide all rates up to the DAC's limit (384KHz) and it worked for all.
Now I have to run everything at 48K -- and, if I choose anything else then MC crashes.
Everything in the setup has returned to what it was before the reshuffling. Any ideas on how to get back where I was?
Does function 10 from the menu still report that it's supporting all of rates you mentioned and in what format?
(ie S32_LE, etc)
-
Yes, it said:
Card 2, ID 'Pro', name 'D30 Pro'
Device 0, ID 'USB Audio', name 'USB Audio', 1 subdevices (1 available)
2 channels, sampling rates 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Sample formats: S32_LE, SPECIAL
-
Did you try powering everything off and back on?
-
No, doing so now...
-
I didn't reboot MC, should I have?
MC told me 44.1 wouldn't work and asked if I wanted 48. I said yes (a/k/a Change settings and continue playing) and it crashed. (Edit: So MC was rebooted anyway.)
When it came back up I changed the setting for 44.1 to 44.1, and the same thing happened again.
BTW, I sure am happy that you told me about the automatic rebooting within a minute.
-
Do you have another USB DAC you could try?
-
Yes. I hadn't thought of it, but there's another DAC attached to the IdPi -- Atom DAC+ -- and MC is perfectly happy feeding it 44.1. It was doing it when it refused to send 44.1 to the D30pro. I've actually had both of them playing while I've been corresponding with you.
Also, I've noticed on the remote desktop connection to the IdPi: After it's been playing for a while if I pause it then it crashes. All of this is new. I've had 30.0.23 installed and running for several weeks, without any such difficulty.
-
Remote desktop itself may be the problem. Try without it. Try one DAC at a time, with the other one unplugged.
-
I can't change MC's output settings on JRemote, so I'll have to move a monitor and mouse near the IdPi to connect directly. This may have to wait a day or few.
Also, I need to have it all working for Christmas. So I'll err on the side of doing nothing until after then.
Thank you for your help, and I will be back on this.
-
What device is selected in MC's audio settings?
Full name please.
-
default: CARD=Pro [ALSA]
The other DAC that's working properly is on hw:CARD=DAC,DEV=0 [ALSA]DS Labs Atom DAC+, USB Audio . Direct hardware device without any conversions
I tried changing the D30pro to: hw:CARD=Pro,DEV=0 [ALSA] D30 Pro, USB Audio. Direct hardware device without any conversions
After that it worked properly. Thank you!
Part of what I was doing before this happened was to test connecting REW to the DAC (temporarily disconnecting the IdPi). I wonder if this made a change in the DAC that caused MC to change the device to one that only accepts 48 kHz -- which is what REW demands. I'll check this when I get back to REW after the holidays.
Again, thank you.
-
default: CARD=Pro [ALSA]
The other DAC that's working properly is on hw:CARD=DAC,DEV=0 [ALSA]DS Labs Atom DAC+, USB Audio . Direct hardware device without any conversions
I tried changing the D30pro to: hw:CARD=Pro,DEV=0 [ALSA] D30 Pro, USB Audio. Direct hardware device without any conversions
After that it worked properly. Thank you!
Part of what I was doing before this happened was to test connecting REW to the DAC (temporarily disconnecting the IdPi). I wonder if this made a change in the DAC that caused MC to change the device to one that only accepts 48 kHz -- which is what REW demands. I'll check this when I get back to REW after the holidays.
Again, thank you.
Ah this pretty much explains the issue.
If you run MC without the previously selected device attached, it will switch to the default device which is usually locked by ALSA to one sample rate. 48k by default.
-
That makes sense. I'll remember that when I get back to REW. Thanks again.