More > JRiver Media Center 23 for Windows

MC doesn't behave nicely doing resource intensive tasks

<< < (13/13)

JimH:

--- Quote from: Awesome Donkey on October 25, 2019, 01:01:18 pm ---If it only happens with files loaded over the network, and not when testing local files located on the machine itself, the issue is probably related to the network which might be too slow to handle it in a timely manner. I think you said 150Mbps is your network speed, but these days that's not really that much when 1Gbps networks have become pretty commonplace. I myself use 1Gbps hardwire for my network (and NAS) and I don't have any issues with network bottlenecks.

--- End quote ---
And you can discount heavily the nominal speed.  No network does what it might do.

steff:
First - You moved back this post to MC23, but this is applicable to MC23, MC24 and MC25, since I reproduced with all of them, so please move to MC25

Second - I Never said that my network is 150 Mbps. It is based on Cisco 3850 Gbps switch for the wired and Cisco 1815 for the wireless at home.
and if you are interested, the higher the speed the more evident the problem.

Third - It is not a problem of the network. Even if it is very slow, then who cares? Should I improve the network speed to reduce the time where the problems appear?
I can wait, but MC shoud not mess up everything while while waiting.

It happen just with memory playback AND during the time where the file is loaded from the netowrk to the computer.

Moreover, have a look at this old post in the MC24 section
https://yabb.jriver.com/interact/index.php/topic,115542.0.html

I was not alone with this problem.

Maybe most of people do not care so much about this problem, but I do, because the only reason I got the MC23 license was Theatre View, then upgraded to MC24 hoping to see the problem solved, again upgraded to MC25... but nothing.
I am paying and I am not using the product. it is not a money matter... this is the proof... I spend thousand €€€ for turbtable kartdriges... why not spend few $$$ for JRiver?
But at this point I see that there is no intention to change MC behaviour, so... I give up.
I will not upgrade to MC26 and will stop spending time with JRiver.

Foobar can play from memory and while I wait my huge 384 kHz PCM FLAC to be loaded, my PC does not mess up its windows, so this is the proof that the root cause is not the network, the antivirus, the NAS, etc.

RoderickGI:
Jim, this is a real issue. It is very easily observed. There has been a lot of discussion about it from various people.

If Windows asks if you want to close MC, then the issue has happened, even if it was for a short time before the Windows message.

Mostly, the issue has been dismissed, or people have been asked to test stuff ad Infinitum. Occasionally some technical reason was given why it happened, or couldn't be fixed. But that isn't a user issue.

I do see it happen with Windows Explorer on rare occasions, but not for as long as it happens with MC, or as often.

Simply put, the MC UI should always remain responsive, even when you have asked it to do something. Or at worst, MC should show the "Working" message (which it does, for example, when loading files to view in the MC Explorer), the MC window shouldn't expand, and a user should be able to switch to another application while MC does its thing.


Sorry to hear you are giving up Steff. You get points for persistence up until now.

steff:
Thanks for your cooperation.
I suppose JRiver developers are not interested to invest time and money to work on this problem.
Also MC25 if affected, but the message has been pushed back to MC23 section, where few people look into.

Navigation

[0] Message Index

[*] Previous page