INTERACT FORUM
Windows => JRiver Media Center 33 for Windows => Topic started by: pete74 on March 23, 2025, 11:15:09 am
-
Hi... I've recently upgraded to jrmc 33.0.71 64 bit. After importing a new flac file to my library I always analyze the file. Since upgrading to the new version, it seems to crash when analyzing mono files quite often.
As I'm writing this, I was playing back one of the files it crashed analyzing, it also crashed during playback. That said, these are .flac's I've created myself (recording from vinyl) using izotope rx6 as I have done for years. Did not see this issue until upgrading to jrmc 33
Any advice?
-
Have attached windows event log snips...the first is from analyzing, the second, playing back
-
Are you using any sort of antivirus app? Bitdefender, perhaps?
-
Are you using any sort of antivirus app? Bitdefender, perhaps?
Just the 'windows defender' built into win10 pro.
update - I've just disabled defender and tried again, same thing.
All my flac's are 24/96 and the ONLY ones MC seems to crash on are mono.
-
Check to make sure that "Mono" flac file contains 2 channels.
-
The logging message points to ntdll.dll as a problem.
Try a Google search for ntdll.dll + crash.
-
Awesome Donkey from 2017: https://yabb.jriver.com/interact/index.php/topic,112547.msg778527.html#msg778527
-
Have gone back and checked/tried many things.....
1) windows safe mode - no difference
2) added windows defender exceptions to jrmc's .exe's AND my folder containing the music.
2) all my mono flac files are single channel
3) jrmc 23 does not have this issue (is still installed on machine after buying/installing 33)
4) audacity, vlc, izotope rx6, AND jrmc 23 have no issues playing the same files. Issue only occurs when either playing or analyzing a mono 24/96 flac file in jrmc 33.
5) running jrmc 33 as Administrator changes behaviour..... app hangs (not crash) when analyzing file (no windows event details written)
6) Have converted to 24/96 wav with same results
-
Is it always reproducible with specific files? Could you upload a couple different samples?
-
Is it always reproducible with specific files? Could you upload a couple different samples?
Seems to be, yes.
Upload here on forum as attachments?
-
Probably too big to be attached to the forum. But I'd recommend uploading them (in a zip file) to Google Drive or Dropbox or Mega or one of those sites.
-
https://drive.proton.me/urls/CBHMCCNZ00#V3AafBI6wuJu (https://drive.proton.me/urls/CBHMCCNZ00#V3AafBI6wuJu)
-
It appears to be indeed a single/mono channel 24/96 file (in the log MC reports it as 2 channel). Strangely enough while it did originally import and play in MC for me, it does eventually crash MC, usually on stop. Even better, after enabling logging and attempting playback again, it crashed immediately. So log attached.
Hey Matt, this one's probably for you.
-
It appears to be indeed a single/mono channel 24/96 file (in the log MC reports it as 2 channel). Strangely enough while it did originally import and play in MC for me, it does eventually crash MC, usually on stop. Even better, after enabling logging and attempting playback again, it crashed immediately. So log attached.
Hey Matt, this one's probably for you.
That's odd because I've got 6 24/96 Tracks that were ripped with dbpowerAmp and they all have 2 channels but the DSP Studio Analyser is showing that the right and left channel are identical.
-
That's odd because I've got 6 24/96 Tracks that were ripped with dbpowerAmp and they all have 2 channels but the DSP Studio Analyser is showing that the right and left channel are identical.
I use Audacity to create the file. Simply select 1 Recording Channel (Mono) from the options.
-
Try recreating it using 2 channels and then in MC when it's playing open the DSP Studio Analyzer Panel and check to see if it's mono, left and right channels in he same place, or stereo, left and right channel lines not on top of each other.
-
dBpoweramp reports it as a single/mono channel file here. That's likely the crux of the issue here.
(https://i.imgur.com/FDPN69R.png)
-
dBpoweramp reports it as a single/mono channel file here. That's likely the crux of the issue here.
(https://i.imgur.com/FDPN69R.png)
So, I've been creating these for probably 10 years and have a few thousand MONO/single channel files. Plus, MC 23 reads em just fine and always did.
-
So, I've been creating these for probably 10 years and have a few thousand MONO/single channel files. Plus, MC 23 reads em just fine and always did.
Why are you making mono files?
-
Why are you making mono files?
Their sources are analog mono recordings.
-
Their sources are analog mono recordings.
Are you absolutely certain about that because Discogs has it listed as STEREO
-
The issue with the file crashing should be resolved in MC34.
-
Are you absolutely certain about that because Discogs has it listed as STEREO
Why debate an irrelevant point sir? I've already stated I have thousands (as do many audiophiles) of mono recordings and you're totally focused on the wrong point.
Earlier versions of MC work fine with these files as do every other audio app I've tried. The particular file I shared was simply recorded while troubleshooting this issue.
-
The issue with the file crashing should be resolved in MC34.
@Hendrik, thank you for the information. As my master license was purchased this month it is for mc34. I will await that version to be available.