INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: parisphoto on March 08, 2013, 02:09:49 pm
-
I still can't use JRiver for any length of time, because it always stalls / freezes.
I just upgraded to 18.0.144, and the problem exists.
Here's the link to my thread on the Media Center 17 Forum.
http://yabb.jriver.com/interact/index.php?topic=78290.msg533117#msg533117
JRiver logs to follow.
Thanks.
-
Hi,
I looked at the other thread for MC17. One thing I didn't understand was how you played your music. You seemed to say that you were using an outboard dac via usb and the Realtek audio at the same time, but I may be misunderstanding you; as far as I know, that can't be done.
Ok, having said that, what is the dac you are using that is connected to the usb output of your computer? Your problem seems to lie there somewhere. Some dacs require particular settings in the music playing software.
If you're using the on board audio (Realtec) you should be using either the analog or digital outs, not the usb out, unless there's something going on I've not heard about.
Chris
-
Sorry for any confusion. Realtek is not being used. My audio path is PC--SPDIF Converter--DAC.
All info is in MC 17 Thread.
I just emailed the first MC 18 log.
I'm ready to go to the Bose Store !
-
What is your converter and dac? I didn't see it in the other thread.
Have you tried all the settings like 24 bits in a 32 bit...? I ask because I've had similar problems and settings made a difference.
As to Bose, I hear you, as to hearing them/it, well.... Although a long time ago a friend had the 901s and they sounded great; I remember being so envious.
-
I have two dacs. A Musical Fidelity M-1 which is both USB and Coaxial, and a Musical Fidelity kw DM25, which is just coaxial.
Two SPDIF converters as well. M2 Tech HiFace and HIFace Evo with external clock and Battery supply.
The problem occurs no matter what combination is used, even straight USB to the M-1 dac.
All the settings have been tried. I have no idea what else I can do.
Hopefully JRiver can deduce something from the log that I just emailed.
-
You might try, if you haven't already, to run your dac from a powered usb hub. Just to see if uneven power from the pc usb could be an issue.
I've had the same hanging issue with MC18 as you seem to have, and still do to a lesser degree (less frequently). It became much less frequent when I changed from kernel streaming to Wasapi. It also was better in earlier iterations of MC18 and nonexistent for me in MC17. Have you tried MC17 in your new computer? If not, I would.
-
I'm confused regarding your suggestion.
Both dacs are powered via AC.
When you say run my dac from a powered USB hub do you mean that I should have a powered USB hub connected to the PC, and run the USB out from the hub to the dac / SPDIF converter?
I've tried tried the various combinations of Wasapi, Kernel Streaming, MC 17 and MC 18 on both PCs.
-
When you say run my dac from a powered USB hub do you mean that I should have a powered USB hub connected to the PC, and run the USB out from the hub to the dac / SPDIF converter?
Yes, not normally suggested and probably won't matter, but, hey.
-
Thanks.I'll give it a shot.
-
The OS, multiple drivers, MC and the usb port/controller in your computer are the common denominators.
You need to logically isolate the problem.
Try foobar2000 using the same methods for play back be it wasapi or directsound.
If it still fails i would think there is a usb problem or driver issues on your machine.
-
Have you been through the "Weird Problems" thread in my signature?
I didn't read the entire thread or the old one, but from your initial description, it sounds like MC is waiting for data. Or it's waiting for the audio device to request data.
A virus checker could do it. A drive spun down.
If you have a way to test your motherboard sound, that might provide a clue.