INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Windows => Topic started by: MarSies on May 13, 2019, 02:39:44 pm
-
Some of the older versions worked fine but I kept upgrading in the hope that it would solve the problems I face. And I have had similar problems with multiple PC's throughout the years
The last thing that I have tried was to remove Bitdefender, use the built in Windows virus scanner, and I upgraded to MC25.
Removing Bitdefender reduced the amount of hang ups and crashes with maybe 20%. Or because I avoid the crash situations it is less.
- Sending music to my Astell & Kern player is a true drama. If I send about 200 songs to the player it mostly goes well. As soon as the number is about 1000 songs MC can just crash without a sign of it being crashed. (also happens when using a folder on my PC as a handheld).
- It does not rip or plays CD's anymore but shows the contents. Windows Media Player works just fine with the same CD's.
- Why can't I just use a folder on my MicroSD on my android phone as a device.
- Why does MC appear to hang when I start ripping 2 CD's simultaneously.
- How come the screen freezes (mouse keeps moving) for multiple seconds when MC is busy.
I don't use the newest features of MC. I just rip CD's, store the contents on my PC, transfer music to multiple players and that's it. NO other fancy stuff or plugins but it fails to work.
-
Please post a log after a crash.
https://wiki.jriver.com/index.php/Logging
-
HI Matt
The log file is too big so that's why I added a link. System became un responsive and the list of files being converted and send to my handheld was gone,. Either this happens or MC crashes silently.
https://we.tl/t-ZBWtXvNUgh
-
You can set the logfile to a 5mb maximum.
-
Do you ever get a crash dump? That would make the job of figuring it out lots easier. Thanks.
-
Sending music to my Astell & Kern player is a true drama. If I send about 200 songs to the player it mostly goes well. As soon as the number is about 1000 songs MC can just crash without a sign of it being crashed. (also happens when using a folder on my PC as a handheld).
That one may be a problem with the player.
Just in case you're using an older version of MC, please read this:
https://yabb.jriver.com/interact/index.php/topic,120376.0.html
-
@Matt
When MC has silently crashed it sometimes warns me to possibly reinstall MC, library etc etc. I will look into that if I can find a crash dump. On the other hand I can also make a log try to rip a CD or play it and then send that log to you.
@JimH
I have read that post and would love to see you guys fix these issues. It is not the A&K, because when I use a folder on my PC as a handheld it does the same. And even if it was the player why should MC crash?
Tomorrow I will hook up my A&K, send files to it and upload a possible crash dump or log.
But truly, some parts of MC have not been upgraded for a very long time. Small textual example, why should there still be a warning with using ape in the highest compression mode. All devices nowadays have a huge CPU capacity.
-
Matt,
In this log I started MC25. Tried to play a CD for which it displays the contents. Then I tried to rip the CD.
Playing and ripping didn't work.
-
Another crash, just like that when only playing a song.
No conversions to my Astell and Kerns ..
-
From your log:
0029360: 13316: TV: CTVRecordingManager::Process: returning because TV device list has not been initialized, and there are no recording actions
Try disabling TV. Options > General > Features
-
And after a fresh restart it happens again.
Will disable the tv. I don't have one connected. But I never configured it !!
-
To analyze crashes, we need the "(Previous) Crash.dmp" files that MC generates. Logs don't help much. Sorry.
-
JimH, disabling tv didn't help.
Hendrik, here is the requested file. Just happened when converting music to my A&K SP1000.
-
Did anyone have a chance to go through my crashdump file ..
-
Did anyone have a chance to go through my crashdump file ..
I did and it isn't clear to me what is going on, it just died in creating output.
Can you get it to happen again and attach another dump to see if it's dying in the same place?
Also, the associated log file combined with that dump can be helpful.