INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC losing DAC connection over Library Server (then failure to locate)  (Read 3941 times)

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123

There is the possibility of a bug in Library Server as of late.

I'm seeing failure of playback on files I just played! Non-cue files.

I'll switch from ASIO to WASAPI, and the track I just played isn't found. I switch back it then it still isn't found.

I'm coming out of sleep (s3) sometimes, but this really just doesn't explain some of the weird phenomena I'm seeing.

Any other heavy LS user seeing any failed location errors?
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: Library Server failure to locate
« Reply #1 on: December 24, 2010, 08:05:10 am »



I'm rolling back a few builds as LS is broken here. First song can be played, but is subsequently not found afterwards.

Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: Library Server failure to locate
« Reply #2 on: January 14, 2011, 01:07:51 pm »

Support?

This is still broken.

I have the option to use local file locations disabled, and LS eventually will not be able to play a file just played.

If I toggle the option back on, and make sure my mapped drives are available on the network, it still won't find the file JUST played.

Log doesn't show much (to me).

using 172
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: Library Server failure to locate
« Reply #3 on: January 14, 2011, 01:11:14 pm »

3767299: 2728: Reader: CInternetReader::Open: Opening http://192.168.0.104:52101/eventSub
3767299: 2676: Reader: CInternetReader::Thread: Start
3767299: 2676: Reader: CInternetReader::Connect: Start
3767299: 2676: Reader: CInternetReader::Connect: Finish (0 ms)
3767299: 2676: Reader: CInternetReader::DownloadFromHTTPURL: Start
3767299: 2676: Reader: CInternetReader::DownloadFromHTTPURL: Success
3767299: 2676: Reader: CInternetReader::DownloadFromHTTPURL: Finish (0 ms)
3767299: 2676: Reader: CInternetReader::Thread: Finish (0 ms)
3767315: 2728: Reader: CInternetReader::Open: Finish (16 ms)
3767315: 2728: Reader: CInternetReader::Read: InternetReadFile returned true with zero bytes read: EOF
3767315: 2728: Reader: CInternetReader::Close: Start
3767315: 2728: Reader: CInternetReader::Close: Finish (0 ms)
3767377: 2880: General: CMainUIWnd::Resize: Start
3767409: 2880: General: CMainUIWnd::Resize: Finish (32 ms)
3767455: 2880: Playback: CPlayerZone::HandlePlaybackError: Start
3767455: 2880: Playback: CPlayerZone::HandlePlaybackError: Finish (0 ms)
3767549: 2880: Playback: CPlayerZone::Stop: Start
3767549: 2880: Playback: CPlayerZone::Stop: Checking for not loaded playback engine
3767549: 2880: Playback: CPlayerZone::Stop: Firing stop to playback engine
3767565: 2880: Playback: CMJPlayerCore::Stop: Start
3767565: 2880: Playback: CMJPlayerCore::Stop: Closing feeder thread
3767565: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Start
3767565: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Cancel
3767565: 2880: Reader: CInternetReader::Close: Start
3767580: 2880: Reader: CInternetReader::Close: Finish (15 ms)
3767580: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Stopping thread
3767580: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Deleting input source
3767580: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Unloading DLL
3767580: 2880: Playback: CMJWaveFeeder::~CMJWaveFeeder: Finish (15 ms)
3767580: 2880: Playback: CMJPlayerCore::Stop: Closing main output bin
3767580: 2880: Playback: CMJPlayerCore::Stop: Closing rights object
3767580: 2880: Playback: CMJPlayerCore::Stop: Deleting output plugin
3767580: 2880: Playback: CMJPlayerCore::Stop: Updating play state
3767580: 2880: Playback: CMJPlayerCore::Stop: Finish (15 ms)
3767596: 2880: Playback: CPlayerZone::Stop: Processing internal previous / next
3767596: 2880: Playback: CPlayerZone::Stop: Clearing display info
3767596: 2880: Playback: CPlayerZone::Stop: Updating statistics
3767596: 2880: Playback: CPlayerZone::Stop: Updating playback state
3767596: 2880: Playback: CPlayerZone::Stop: Updating UI
3767596: 2880: Playback: CPlayerZone::Stop: Applying database changes
3767611: 2880: Playback: CPlayerZone::Stop: Finish (62 ms)
3767627: 2300: Reader: CInternetReader::Open: Start
3767627: 2300: Reader: CInternetReader::Open: Opening http://192.168.0.104:52101/eventSub
3767627: 2708: Reader: CInternetReader::Thread: Start
3767627: 2708: Reader: CInternetReader::Connect: Start
3767627: 2708: Reader: CInternetReader::Connect: Finish (0 ms)
3767627: 2708: Reader: CInternetReader::DownloadFromHTTPURL: Start
3767643: 2708: Reader: CInternetReader::DownloadFromHTTPURL: Success
3767643: 2708: Reader: CInternetReader::DownloadFromHTTPURL: Finish (16 ms)
3767643: 2708: Reader: CInternetReader::Thread: Finish (16 ms)
3767643: 2300: Reader: CInternetReader::Open: Finish (16 ms)
3767643: 2300: Reader: CInternetReader::Read: InternetReadFile returned true with zero bytes read: EOF
3767643: 2300: Reader: CInternetReader::Close: Start
3767643: 2300: Reader: CInternetReader::Close: Finish (0 ms)
3767689: 2880: General: CMainUIWnd::Resize: Start
3767721: 2880: General: CMainUIWnd::Resize: Finish (32 ms)
3768891: 2764: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768891: 2764: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768891: 2764: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768891: 2764: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768891: 2816: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768891: 2816: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768891: 2816: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768891: 2816: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768891: 2472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768891: 2472: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768891: 2472: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768891: 2472: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768891: 3676: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768891: 3676: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768891: 3676: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768891: 3676: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 1180: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768906: 1180: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768906: 1180: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768906: 1180: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 3984: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768906: 3984: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768906: 3984: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768906: 3984: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 3744: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768906: 3744: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768906: 3744: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768906: 3744: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 2792: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768906: 2792: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768906: 2792: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768906: 2792: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 3596: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768906: 3596: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768906: 3596: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768906: 3596: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (0 ms)
3768906: 1252: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3768922: 1252: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.1: NOTIFY: http://239.255.255.250:1900*
3768922: 1252: Sharing Plugins: VHTTPMessage::Write: Wrote 139 bytes
3768922: 1252: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (16 ms)
3771901: 2880: General: CMCResourceHelper::GetIsModalPopupShowing: Menu showing
3774475: 2880: General: CMCResourceHelper::GetIsModalPopupShowing: Menu showing
3775645: 2712: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3775645: 2712: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.104: M-SEARCH: http://239.255.255.250:1900*
3775677: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 415 bytes
3775692: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 419 bytes
3775770: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 416 bytes
3775833: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 416 bytes
3775895: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 405 bytes
3775973: 2712: Sharing Plugins: VHTTPMessage::Write: Wrote 406 bytes
3775973: 2712: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (328 ms)
3775973: 548: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3775973: 548: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.104: M-SEARCH: http://239.255.255.250:1900*
3776004: 548: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (31 ms)
3776004: 2060: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3776004: 2060: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.104: M-SEARCH: http://239.255.255.250:1900*
3776020: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 415 bytes
3776035: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 419 bytes
3776113: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 416 bytes
3776160: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 416 bytes
3776176: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 405 bytes
3776176: 2060: Sharing Plugins: VHTTPMessage::Write: Wrote 406 bytes
3776176: 2060: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (172 ms)
3776176: 924: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
3776176: 924: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 192.168.0.104: M-SEARCH: http://239.255.255.250:1900*
3776191: 924: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (15 ms)
3776301: 2880: General: CMCResourceHelper::GetIsModalPopupShowing: Main window disabled
3777517: 2880: General: RunProgram: Start
3777517: 2880: General: RunProgram: Filename: C:\Users\JCC\AppData\Roaming\J River\Media Center 15\Log.txt / Parameters:
3777517: 2880: General: RunProgram: Performing ShellExecute...
3777783: 2880: General: RunProgram: Running process...
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: Library Server failure to locate
« Reply #4 on: January 19, 2011, 07:55:48 am »

Anyone out there?

I have tried both options: Always Decode/Never decode

...and I'm experiencing a major problem with library server.

Not sure if this is a problem with corrupt FLAC files, or an issue that has crept into LS when using WASAPI [event].

My DAC will drop connection, and MC keeps playing. But then MC won't be able to play the file again, after I hit stop. I get a File can't be found error.

So I 'm hopeful this is a not a hardware issue with the Antelope Zodiac+ DAC. Yesterday, upon experiencing this failure, I switched to Always Decode, and I could then play the file which MC was reporting as "Unable to Locate File". Eventually, it occurred again though.

The is a potential serious instability, and I'd like to hear from other Library Server users, who are using USB (WASAPI, either mode), or from JR staff so we can begin troubleshooting.

The only change to my system since the introduction of [event] mode WASAPI has been recent upgrades to .172 and last few earlier builds.

I can roll back both my server and client to an old build and try for a few days.

Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #5 on: January 19, 2011, 08:13:59 am »

I'm testing the same version of MC, using WASAPI [event], from work using my EMU USB 0202.

The only difference will be that I will have it set to High Quality Mp3 Stream (but still using Always Convert).

At home, I use Uncompressed Stream, no memory playback, 100-250ms, 6 second pre-buffer.

Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #6 on: January 20, 2011, 09:41:25 pm »

The last time a stuck with a problem, dug for more users with the same problem, it directly led to WASAPI [Event] mode.

I'm not even worthy of Jim telling me my mahcine is fragged any more....wow ::)

Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #7 on: January 20, 2011, 09:45:08 pm »

*whistling
Logged

DarkPenguin

  • Citizen of the Universe
  • *****
  • Posts: 1921
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #8 on: January 20, 2011, 10:46:58 pm »

Perhaps it is your antivirus.
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #9 on: January 20, 2011, 10:53:50 pm »

No, leave that disabled on the client. and never had a problem running NOD32 on the server for the last 5 years.
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #10 on: January 22, 2011, 01:26:50 pm »

Well, installed .173 all around and things became notably worse.

Using the same sample rate, with 1second crossfade, MC would now hang about 30-40 between manual track changes to different albums. On the same album it was okay. Switched to native sample rate and same thing, MC becomes unresponsive and will cache your next button and stop hits for minutes and just lag.

I looked at the log but nothing obvious.

I rolled back to Summer 2010 with .108 and WASAPI (normal) works 100% client/server. Let it play for about 40 minutes with no issues.

I can try to roll up tho the build with WASAPI [event] introduced mode later.
Logged

HiFiTubes

  • Citizen of the Universe
  • *****
  • Posts: 1123
Re: MC losing DAC connection over Library Server (then failure to locate)
« Reply #11 on: January 29, 2011, 08:41:06 pm »

.136 if anyone wants to test.
Logged
Pages: [1]   Go Up