Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[CountryBumkin]

Sorry to report that version 211 did not solve my issue. http://yabb.jriver.com/interact/index.php?topic=81801.0 I cannot watch movie all the way through on Client. it stops/freezes after playing for a while. I thought it might be network related so I ran the same movie on two different Clients at the same time (movie: Blu-ray version of Hobbit, ripped to m2ts). The movie played okay for a while then stopped on each machine - but at different times. The one I was watching just said "Buffering" but was froze and then returned to Theater View menu by itself. The other played for a while longer (I could hear it in the other room) when I went to check on it, it had also returned to menu.
BTW - I did play this movie all the way through on the Server. It's just the Clients that seem to have difficulties.

Obviously this is not a common problem. I'm thinking about just formatting and reinstalling from clean drive (maybe go to Win8) but if this problem is of any diagnostic value to JRiver, I'll keep working on it. If you'd rather move on with MC19 stuff - that's okay too - let me know and I'll start formatting drives.

Here is part of the log - the part where things change (it is attached):

1257368: 4056: Playback: BufferedInternetReader::FindEarliestHolePosition: number of download threads=3
1257368: 4056: Playback: BufferedInternetReader::FindEarliestHolePosition: Next hole - 3141446656
1257368: 4056: Playback: BufferedInternetReader::FindEarliestHolePosition: Finish (0 ms)
1257368: 4056: Playback: BufferedInternetReader::MonitorDownloadThread: Finish (0 ms)
1257415: 4056: Playback: BufferedInternetReader::MonitorDownloadThread: Start
1257415: 4056: Playback: BufferedInternetReader::MonitorDownloadThread: getting lock
1257415: 4056: Playback: BufferedInternetReader::FindEarliestHolePosition: Start
1257415: 4056: Playback: BufferedInternetReader::FindEarliestHolePosition: Next hole - 3141446656
1343293: 1788: Reader: CWinINetReader::Close: Finish (31 ms)
1343293: 3248: Playback: BufferedInternetReader::OnThreadEnds: Start
1343293: 3248: Playback: BufferedInternetReader::OnThreadEnds: getting lock
1343293: 3248: Playback: BufferedInternetReader::OnThreadEnds: Finish (0 ms)
1343293: 3248: Playback: BufferedInternetReader::Close: deleting threads array
1343293: 3248: Playback: BufferedInternetReader::Close: stopping monitor thread
1343325: 3248: Playback: BufferedInternetReader::Close: closing and deleting reader
1343325: 3248: TV: VSplitterReader::DeleteStaleChunks: Start
1343325: 3248: TV: VSplitterReader::DeleteStaleChunks: Finish (0 ms)
1343325: 3248: Playback: BufferedInternetReader::Close: closing and deleting writer
1343325: 3248: TV: VSplitterReader::DeleteStaleChunks: Start
1343325: 3248: TV: VSplitterReader::DeleteStaleChunks: Finish (0 ms)
1343652: 3248: Playback: BufferedInternetReader::Close: Finish (390 ms)
1343652: 3248: Playback: BufferedInternetReader::Close: Start
1343652: 3248: Playback: BufferedInternetReader::Close: getting lock
1343652: 3248: Playback: BufferedInternetReader::Close: stopping download threads and closing downloading readers
1343652: 3248: Playback: BufferedInternetReader::Close: deleting threads array
1343652: 3248: Playback: BufferedInternetReader::Close: stopping monitor thread
1343652: 3248: Playback: BufferedInternetReader::Close: closing and deleting reader
1343652: 3248: Playback: BufferedInternetReader::Close: closing and deleting writer
1343652: 3248: Playback: BufferedInternetReader::Close: Finish (0 ms)
1343652: 3248: Podcast: CDXColorControls::Clear: Start
1343652: 3248: Podcast: CDXColorControls::Clear: Finish (0 ms)
1343652: 3248: Playback: CSubtitleEngine::~CSubtitleEngine: Start
1343652: 3248: Playback: CSubtitleEngine::~CSubtitleEngine: Finish (0 ms)
1343652: 3248: Playback: CPlayerZone::Stop: Processing internal previous / next
1343652: 3248: Playback: CPlayerZone::Stop: Clearing display info
1343652: 3248: Playback: CPlayerZone::Stop: Updating statistics
1343652: 3248: Database: CDataHolder::Load: Field: Stack Top; Files: 26425; Pointer bytes: 0; Data bytes: 48; Elapsed ms: 0.251
1343652: 3248: Database: CDataHolder::Load: Field: Last Played; Files: 26425; Pointer bytes: 14756; Data bytes: 4168; Elapsed ms: 0.525
1343652: 3248: Playback: CPlayerZone::Stop: Updating playback state
1343652: 3248: Playback: CPlayerZone::Stop: Updating UI
1343652: 3248: Playback: CPlayerZone::Stop: Applying database changes
1343652: 3248: Playback: CPlayerZone::Stop: Finish (795 ms)
1343652: 2536: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Start
1343652: 2536: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Zone: Player (id: 0)
1343652: 3248: Playback: CPlayerZone::Next: Finish (795 ms)
1343652: 3248: General: CMCUICore::SetMode: Start
1343652: 3248: General: CMCUICore::SetMode: Setting UI mode: -994
1343652: 3248: Database: CMediaFileIOLoad::Load: Loading: C:\Users\user1\AppData\Roaming\J River\Media Center 18\Connected Library\browser (theater view).jmd
1343699: 3248: General: CMCUICore::UpdateScreenResolution: Start
1343699: 3248: General: CMCUICore::UpdateScreenResolution: Default fullscreen settings:
1343699: 3248: General: CMCUICore::UpdateScreenResolution: Changing monitor 65537 settings to:
1343699: 3248: General: JRMonitor::SetDisplayMode: Start
1343699: 3248: General: JRMonitor::SetDisplayMode: Mode 1920x1080x32x60 for device \\.\DISPLAY1
1344729: 3248: General: JRMonitor::SetDisplayMode: Finish (result: 1) (1030 ms)
1344791: 3248: General: CMCUICore::UpdateScreenResolution: Finish (1092 ms)
1344791: 3248: General: CMainUIWnd::Resize: Start
1344791: 3248: General: CDXCore::Initialize: Start
1344791: 3248: General: CDXCore::Initialize: Stopping previous instances
1344791: 3248: General: CDXCore::Terminate: Start
1344791: 3248: General: CDXCore::Terminate: DestroyObjects
1344791: 3248: General: CDXCore::Terminate: Release Direct3D
1344791: 3248: General: CDXCore::Terminate: Unload D3D.dll
1344791: 3248: General: CDXCore::Terminate: Clearing variables
1344791: 3248: General: CDXCore::Terminate: Finish (0 ms)

[JimH]

What about the Windows settings for sleep, screensaver, etc?  Even network cards can be set to power down.

[Hendrik]

Do you have the files mapped as a network drive and the appropriate option turned on so that MC will access the files directly, or does it stream them over its own thing?

[Yaobing]

Please try the following modified JRReader.dll

https://www.dropbox.com/s/qfwaunatzf9fzrg/JRReader.rar

[CountryBumkin]

Thanks for the attempt but the new "dll" did not fix the problem.
Still stops playing a few minutes into watching (I tried two different Blu-ray movies). At least it's not freezing - it returns to menu and I can restart where I left off. BTW, I'm playing a DVD rip (ifo/vob) now and it seems to be playing fine. It has (so far) stayed playing much longer than the blu-ray movies.

I also tried mapping the drive from the server (where the movies are stored) on the client , and I double checked that all power savings (sleep modes) are off.

 I think I'll try a fresh Windows7 install this weekend. That will (might help) rule out any odd program glitches (maybe caused by a Windows update).

[gvanbrunt]

I doubt this is related, but just in case...

I have the same thing happening instantly when I try to watch some movies in gizmo over a wan. It used to work.

I'm on the road so I can't really troubleshoot at the moment. I thought it was cliant but now I'm not so sure. ..

[glynor]

I also tried mapping the drive from the server (where the movies are stored) on the client

To be clear, if you're playing off of a LAN, MC's video support works best if you map a drive on the client using the same exact path on the clients as where the Server sees the copies.

Then, MC will (on the client end) just play the file "locally" (from the network "disk") as though it weren't connected to the Library Server at all.  But the key is, they have to have the same exact path on both the Client and the Server.  The reason this often works best is to do it the other way, the Server has to convert and stream the content to the Client.  This is useful for playing "away from your LAN", but it requires substantial horsepower to transcode on the fly, and it will probably not work well with sources with very high data rates, and those in "odd" formats.

So, there are a two main strategies for doing this:

1. You can import the files "normally" on the Server, and share out the entire root drive as a network share.  Then, mount that share on the Client machines using the same exact drive letter the server uses, and the "paths" will match.

2. If you can't do this for some reason (maybe the files are spread across many volumes, or are on your C drive), you can import the files on the Server using their UNC paths, as though they weren't local (using \\servername\sharename\path\to\files.mkv even though you are on the server).  This works just as well, and you don't have to map any drives on the client.  However, you DO have to open those network shares in Windows Explorer on the Client machine at least once (so it can cache your credentials) before playing anything, and again if you ever change your Windows login password, or it'll fall back to streaming mode.

I do both of these (number 1 at home, and number 2 at the office), and I have few-if-any troubles.  I've had mixed success using MC's video streaming capabilities.  It works if the connections at both ends are fast and trouble-free, but over WiFi or if the server is trapped behind a "slow" connection, it is flaky at best.

I say all this because I've seen the exact same "freezing" problem before using the streaming.  Even if you changed nothing, and it worked before, it could be that a neighbor changed something (if you're over WiFi).

Of course, it could just be something on that box acting weird too.  I've seen all sorts of weirdness with hosed Network card drivers...

[CountryBumkin]

Please try the following modified JRReader.dll

https://www.dropbox.com/s/qfwaunatzf9fzrg/JRReader.rar

BTW - it may be useful, or interesting, for you to know that after I installed the new jrreader.dll and restarted the computer, the first time I started MC it immediately stopped and
popped up the message "Program is not responding" and identified the fault with "ole32.dll". Then I restarted MC and it worked fine (except that my original problem remains).

I thought I mention this because I've seen some other postings mentioning problems with ole32. Maybe its all related.

[Yaobing]

Can you provide another log, using the DLL that I posted?  Just in case it gives me additional info.

[CountryBumkin]

Can you provide another log, using the DLL that I posted?  Just in case it gives me additional info.

Attached is a log from today. I cleared the existing log, started playing the BD movie and waited for it to stop on its own. Then I captured the log.
Below is a short screen shot (of my uneducated guess of where the failure occurs) - it looks like it is failing in the same place - around the time the TV thingy starts.

BTW - I tried to create a second log (but it is too big to attach) where I play a BD movie, it stops and MC went back to menu, then I selected a DVD (ifo/vob) movie which plays to the end (seems like only the BD movies have a problem), then I started playing a second BD movie which stopped but this time it stayed on the screen saying "buffering". I was able to ALT+F4 to get back to menu. So MC is not really freezing.

Code: [Select]

0820815: 3788: Playback: BufferedInternetReader::MonitorDownloadThread: Start
0820815: 3788: Playback: BufferedInternetReader::MonitorDownloadThread: Finish (0 ms)
0821033: 3124: Reader: CWinINetReader::Close: Finish (249 ms)
0821049: 3836: Playback: BufferedInternetReader::OnThreadEnds: Start
0821049: 3836: Playback: BufferedInternetReader::OnThreadEnds: Finish (0 ms)
0821049: 3836: Playback: BufferedInternetReader::Close: deleting threads array
0821049: 3836: Playback: BufferedInternetReader::Close: stopping monitor thread
0821049: 3836: Playback: BufferedInternetReader::Close: closing and deleting reader
0821049: 3836: TV: VSplitterReader::DeleteStaleChunks: Start
0821049: 3836: TV: VSplitterReader::DeleteStaleChunks: Finish (0 ms)
0821049: 3836: Playback: BufferedInternetReader::Close: closing and deleting writer
0821049: 3836: TV: VSplitterReader::DeleteStaleChunks: Start
0821049: 3836: TV: VSplitterReader::DeleteStaleChunks: Finish (0 ms)
0821283: 3836: Playback: BufferedInternetReader::Close: Finish (499 ms)
0821283: 3836: Playback: BufferedInternetReader::Close: Start
0821283: 3836: Playback: BufferedInternetReader::Close: getting lock
0821283: 3836: Playback: BufferedInternetReader::Close: stopping download threads and closing downloading readers
0821283: 3836: Playback: BufferedInternetReader::Close: deleting threads array
0821283: 3836: Playback: BufferedInternetReader::Close: stopping monitor thread
0821283: 3836: Playback: BufferedInternetReader::Close: closing and deleting reader
0821283: 3836: Playback: BufferedInternetReader::Close: closing and deleting writer
0821283: 3836: Playback: BufferedInternetReader::Close: Finish (0 ms)
0821283: 3836: Podcast: CDXColorControls::Clear: Start
0821283: 3836: Podcast: CDXColorControls::Clear: Finish (0 ms)
0821283: 3836: Playback: CSubtitleEngine::~CSubtitleEngine: Start
0821283: 3836: Playback: CSubtitleEngine::~CSubtitleEngine: Finish (0 ms)
0821283: 3836: Playback: CPlayerZone::Stop: Processing internal previous / next
0821283: 3836: Playback: CPlayerZone::Stop: Clearing display info
0821283: 3836: Playback: CPlayerZone::Stop: Updating statistics
0821283: 3836: Playback: CPlayerZone::Stop: Updating playback state
0821283: 3836: Playback: CPlayerZone::Stop: Updating UI
0821283: 3836: Playback: CPlayerZone::Stop: Applying database changes
0821283: 3836: Playback: CPlayerZone::Stop: Finish (905 ms)
0821283: 1504: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Start
0821283: 3836: Playback: CPlayerZone::Next: Finish (905 ms)
0821283: 1504: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Zone: Player (id: 0)
0821283: 3836: General: CMCUICore::SetMode: Start
0821283: 3836: General: CMCUICore::SetMode: Setting UI mode: -994
0821314: 3836: Database: CMediaFileIOLoad::Load: Loading: C:\Users\user1\AppData\Roaming\J River\Media Center 18\Connected Library\browser (theater view).jmd
0821361: 3836: General: CMCUICore::UpdateScreenResolution: Start
0821361: 3836: General: CMCUICore::UpdateScreenResolution: Default fullscreen settings:
0821361: 3836: General: CMCUICore::UpdateScreenResolution: Changing monitor 65537 settings to:
0821361: 3836: General: JRMonitor::SetDisplayMode: Start
0821361: 3836: General: JRMonitor::SetDisplayMode: Mode 1920x1080x32x60 for device \\.\DISPLAY1
0822469: 3836: General: JRMonitor::SetDisplayMode: Finish (result: 1) (1108 ms)
0822515: 3836: General: CMCUICore::UpdateScreenResolution: Finish (1154 ms)
0822515: 3836: General: CMainUIWnd::Resize: Start
0822547: 3836: General: CDXCore::Initialize: Start
0822547: 3836: General: CDXCore::Initialize: Stopping previous instances
0822547: 3836: General: CDXCore::Terminate: Start
0822547: 3836: General: CDXCore::Terminate: DestroyObjects
0822547: 3836: General: CDXCore::Terminate: Release Direct3D
0822547: 3836: General: CDXCore::Terminate: Unload D3D.dll
0822547: 3836: General: CDXCore::Terminate: Clearing variables
0822547: 3836: General: CDXCore::Terminate: Finish (0 ms)


[JimH]

Attached BTW - I tried to create a second log (but it is too big to attach) where I play a BD movie, it stops and MC went back to menu, then I selected a DVD (ifo/vob) movie which plays to the end (seems like only the BD movies have a problem), then I started playing a second BD movie which stopped but this time it stayed on the screen saying "buffering". I was able to ALT+F4 to get back to menu. So MC is not really freezing.

What happens if you wait?  Will it come back on its own?  Try it overnight if you can.  It might provide another clue.

It's possible MC is trying to download components and something like a firewall is preventing it.

An error message behind the screen is another possibility.

[CountryBumkin]

I will wait longer this next test.
Most of the time, the BD will just stop playing and return to the MC Theater View Menu within a few minutes at most. Sometimes it stops playing and immediately jumps to the menu, sometimes I wait a few minutes and it jumps to menu. This last test I waited about 15 to 20 minutes and then I did the Alt+f4 to get to the menu. I'll just leave it alone this test and see how long it takes.
The two BD movies I'm testing with are Hobbit and Lopper - but I don't think it matters. I also need to test with more DVD rips to be sure they are not affected too, but so far I have not seen any failures playing DVD rips.
Thanks for you attention on this.

[CountryBumkin]

I thought I would provide an update on this problem - incase it helps someone in the future.
I found the cause of the problem - well not the cause, but the solution.

Both of my client machines have small (60GB) SSDs, each with a larger 1TB drive for recordings. What I found was happening is that the small drives were "filling up" with the Temp files during playback. My MC settings (which have never been changed) have the Temp files at C:\Users\user1\AppData\Roaming\J River\Media Center 18\Temp\. As the C:drive is at 35GB normally, playing a BD would fill the C: drive after about 30 minutes of playback and cause the BD playback to stop.

What is also interesting is that as the C: drive became low on space the program "MsMpEng.exe" (Antimalware Service Executable) began to consume more CPU cycles. I was watching the resource monitor showing  MediaCenter 18.exe between 40 to 45% of CPU load and MsMpEng.exe using 45-50% of CPU. Once CPU load hit 100% the playback would stop. I spent some time thinking the problem was due to MsMpEng, but when I moved the MC "Temp" file off the C: drive the CPU load dropped to under 40% (with MsMpEng around 10 to 12% max).

I don't know if a Windows update or a MC update that started the behavior, but I now have the Temp files on both clients using the other drives (not C:) and I have not seen a problem since.