INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: Matias on February 16, 2015, 07:11:50 am
-
Version 20.0.70 is crashing in_dsd.dll when analyzing my library during a library import. Ideas?
-
Can you isolate what DSD file causes the crash, and then provide a copy to matt at jriver dot com? Thanks.
-
Very strange. I did not try to analyze now, just to show the Dynamic Range 128 column in the Artist default view. Click one CD, shows the info. Click another, show too. Keep scrolling and they all show DR 128 column until one point when in_dsd.dll freezes. Aha, so I mark which CD it was, close JRiver, open again. Click artist view, show DR 128 column, click the CD.... and it works ok. Keep scrolling until it hangs in another place!
Tried selecting all albums in Artist view, click tools - analyze audio. Hangs somewhere. Decrease simultaneous threads from 4 to 1 (using an i5 2500k here), hangs too. Enter advanced options, input plugins, DSD, change from auto to 1 thread too. Hangs. Instead of running it manually, checked the option during library import. Hangs.
:-\
-
Very strange. I did not try to analyze now, just to show the Dynamic Range 128 column in the Artist default view. Click one CD, shows the info. Click another, show too. Keep scrolling and they all show DR 128 column until one point when in_dsd.dll freezes. Aha, so I mark which CD it was, close JRiver, open again. Click artist view, show DR 128 column, click the CD.... and it works ok. Keep scrolling until it hangs in another place!
Tried selecting all albums in Artist view, click tools - analyze audio. Hangs somewhere. Decrease simultaneous threads from 4 to 1 (using an i5 2500k here), hangs too. Enter advanced options, input plugins, DSD, change from auto to 1 thread too. Hangs. Instead of running it manually, checked the option during library import. Hangs.
:-\
So can you send me one of the files it hangs on? I'm matt at jriver dot com.
Thanks.
-
Problem is that it hangs in different places.
But now I figured it maybe scanning in the background with that analyze audio option turned on. Maybe that was the reason it was hanging when I was browsing without analyzing myself.
Turned off analyze while importing. Now running it accross the library manually, let's see if it hangs and where.
When I find out which one is causing it I will send you the file.
-
Hi Matt
I see the same behavior: several crashes in in_dsd.dll and version 20.0.0.70 (and 62 + 63).
I've posted my logs and description here: http://yabb.jriver.com/interact/index.php?topic=95617.0
Beside random unprovoked crashes, I'm able to provoke the crash if I'm analyzing a specific sacd.iso file.
I'm currently uploading it and will send you a link when it is ready (approx 4.5GB).
-
Matt, I found one particular SACD ISO that hangs every time I try to analyze it, but it is over a gig and I can't email it to you to test.
I reboot, do nothing else other than open MC, select that album only, hit Analyze and hangs. Always in_dsd.dll, and after finished analyzing and is saving tag.
If it helps, I have DSD input set up as Permissive, 1 Thread, without +6dB increase.
-
I had the same problem. It would crash when I imported a directory. On further examination, it was on a specific video file which was "bad" as it would not play properly. Once deleted, the import worked fine.
Dave
-
If you find a file like that, please save it. We'd like to see it.
-
I fixed a DSD related crash for an upcoming version. Please provide crash reports if you encounter any other crashes.
-
Matt, I found one particular SACD ISO that hangs every time I try to analyze it, but it is over a gig and I can't email it to you to test.
I reboot, do nothing else other than open MC, select that album only, hit Analyze and hangs. Always in_dsd.dll, and after finished analyzing and is saving tag.
If it helps, I have DSD input set up as Permissive, 1 Thread, without +6dB increase.
Can you upload it to Dropbox or similar? Thanks.
-
Jim, I sent Matt an email. Hope it helps you finding what is wrong.
-
73 skips the error track, and if you analyze many files at once, after a given number of errors is reached it stops analyzing with a "clean" error message.
Not sure if this is the best intended behavior. Sure, doesn't crash anymore, it is a lot better. Still I don't know what files caused it and what is the error so that I can try to fix it.