INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: Fleckenzwerg on March 28, 2013, 01:50:50 pm
-
Hi,
my MC 18 (newest version) always crashes when I pause a track and then click the "stop" button. It cannot be restarted because the MC18 process is still running. It cannot be killed manually, only a reboot helps. (Windows 7)
Thanks
Fleck.
-
Have you recently switched to Kernel Streaming?
-
Please report the full version you're using. 18.0.158 is on the download page.
-
I use kernel streaming since I use MC 18. My version is 18.0.158. I had the same problem with a previous version of MC 18.
Thanks!
-
I did a new install (had a system drive die on me) and MC 18 crashes after about a minute or two after I start it. Below is the system log. It's complaining about LAVAudio.ax
Log Name: Application
Source: Application Error
Date: 3/29/2013 7:29:09 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Caritas
Description:
Faulting application name: Media Center 18.exe, version: 18.0.158.0, time stamp: 0x5152fde4
Faulting module name: LAVAudio.ax, version: 0.55.3.0, time stamp: 0x51179c6d
Exception code: 0xc0000005
Fault offset: 0x00008d9c
Faulting process id: 0xdbc
Faulting application start time: 0x01ce2c78ecedcb96
Faulting application path: C:\Program Files (x86)\J River\Media Center 18\Media Center 18.exe
Faulting module path: C:\Users\Matthew\AppData\Roaming\J River\Media Center 18\Plugins\lav\LAVAudio.ax
Report Id: 40b1d29b-986c-11e2-8ec1-00e081c14830
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-03-29T12:29:09.000000000Z" />
<EventRecordID>711</EventRecordID>
<Channel>Application</Channel>
<Computer>Caritas</Computer>
<Security />
</System>
<EventData>
<Data>Media Center 18.exe</Data>
<Data>18.0.158.0</Data>
<Data>5152fde4</Data>
<Data>LAVAudio.ax</Data>
<Data>0.55.3.0</Data>
<Data>51179c6d</Data>
<Data>c0000005</Data>
<Data>00008d9c</Data>
<Data>dbc</Data>
<Data>01ce2c78ecedcb96</Data>
<Data>C:\Program Files (x86)\J River\Media Center 18\Media Center 18.exe</Data>
<Data>C:\Users\Matthew\AppData\Roaming\J River\Media Center 18\Plugins\lav\LAVAudio.ax</Data>
<Data>40b1d29b-986c-11e2-8ec1-00e081c14830</Data>
</EventData>
</Event>
-
I also used Kernel Streaming for quite some time (Win-7, MC-17,18)
it worked well, but, if I ever hit "pause" instead of stop, MC would crash.
Since switching to WASAPI-Event, all has been 100% fine.
Actually, now that I think about it, I've not actually tried Kernel Streaming with MC 18, only MC-17 and prior.
Not sure if Kernel Streaming would work for me now (MC-18)
-
I tried wasapi output and the problem does not occure. Hence, the problem is kernel streaming realted but I still prefere the kernel streaming output because it sounds better than wasapi.
-
MC18 should produce a crash log if you enable logging.
Help -> Logging, and click the checkbox, then make it crash.
After restarting MC again, go to Help -> Logging again and press the "Report" button, it'll create a .zip file on your Desktop. You should upload and link it here, so the Devs can have a look.
-
In my case, I can't detect any quality hit going from Kernel Streaming to Wasapi-Event. (Audio only, FLAC/WAV high-rez, Async USB to W4S-DAC2 & Esoteric D-07X - CJ GAT, Parasound JC-1s, Magnepan 20.7)
This issue for me has been around for a couple years and was discussed way way back on a couple threads somewhere here.
I think the suggestion is that if Kernel Streaming does not work, use WASAPI.
It's my understanding they are both bit-perfect and there should be no impact playback quality using either. In my case I'd concur, but I know everyone has specific preferences.
-
I proceeded as suggested. Here is the link to the Log:
http://www.file-upload.net/download-7436927/JRiver-Log-2013-04-07-11-11-57.zip.html
@ rayooo
I know this discussion and also a lot of of people confirming the difference between wasapi and KS (a lot more differences can be heard).
The sound is influenced not only by the ones and zeroes. It is also about noise and how things are processed. If you like a good explanation go to the phasure forum and use the search function or ask some people there. They are very kind and helpfull. The "digital is just ones and zeroes and hence there should be no difference"-discussion is similar like the cable discussion. Some people deny a possible difference in cables because it is just a piece of wire. Most audiophiles and technichians know it is not as simple as one could wish.