INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Windows => Topic started by: mattkhan on July 29, 2020, 06:12:25 am
-
bringing this longstanding issue fwd into MC26 - https://yabb.jriver.com/interact/index.php/topic,116500.msg805197.html (from MC24) and https://yabb.jriver.com/interact/index.php/topic,112027.0.html (from MC23 days)
I still get this on a regular basis and it becomes more of an issue as use of streaming services (and hence WDM driver) increases
to recap, issue is directly attributable to the WDM driver as simply stopping the WDM driver is sufficient to release the memory without any further intervention.
A nuclear option would be to upgrade to windows 10 but to my mind, it's only worth considering that if there is some material difference in how the WDM driver is implemented in Win10 vs Win8.1. Is there?
-
We've never been able to reproduce this issue on any system we tried it on. I use the WDM driver a bunch myself. Can't fix what I can't see. And it seems oddly isolated to... just you? I don't remember any other reports of such issues.
I don't remember if you have ever re-installed the system in the time that you've been experiencing the issue, but considering how isolated it appears to be, doing that, or switching to Windows 10 seems like the best attempts to me.
-
Yes that's correct, unfortunately though it probably means I have to give up using MC for this and find some other app that can do the DSP. Not ideal so thought I would raise it back up.
Is there a difference in how wdm is implemented or interacts with MC on Windows 10?
-
Could the leak be in the driver for the audio device? Try Direct Sound.
What is the driver?
If this were a problem with WDM, I think we'd see a lot of complaints.
-
it has occurred with 3 different ASIO drivers (from motu, focusrite & RME) so I doubt it is the driver
directsound isn't an option
as per previous posts/threads, the only constant in all this is the WDM driver. For sure there is some specific behaviour here that mean I suffer the problem but working out what that is is another Q.
-
Directsound as an experiment to try to separate where the problem is. Or WASAPI.
The quality of ASIO drivers is more uneven.
-
RME drivers are known to be amongst the best around
Motu drivers have been rock solid for me also
If it were the driver then I would get this at other times but I don't, it has literally never happened, only when wdm is in use.
-
One thing I do make regular use of is MCWS/v1/Playback/StopAll
I have previously wondered if this unhinges something internally
-
Try not using it.
-
Just to close this thread out. This problem has been persistent (i.e. multiple forced restarts required per day) up until the last week or so when I appear to have fixed it.... I'm not sure I can class this as a solution though as that involved building a new PC and migrating to Windows 10 (with the same physical hardware attached & the same MCWS calls being made). At least it is solved from my perspective but I guess it will remain a mystery forever as to what caused the leak!
-
Just to close this thread out.
spoke too soon, still happens on the new machine