Print

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

[tzr916]

This is new, not sure if it started when I upgraded from MC25 to MC26, or when I set up Zones (video=bitstream, audio=2ch pcm). My hardware has not changed. My OS has not changed. My video drivers have not changed. My antivirus has not changed.


When I start watching a tv show (TS file) and I press Jump forward several times rapidly, then press Jump back once or twice rapidly, MC will freeze. Video is frozen and many times the audio is just doing a half second loop/repeat. Only option is to CTRL-ALT-DEL task manager, highlight MC, choose end process. Strangely, task manager does NOT show that MC is "not responding", and CPU usage for MC is less than 5%. After restarting MC, the same file plays back fine.

95% of our tv watching is done on the MC Server and this issue is now happening once every two or three days. It has happened about 8 or 9 times now since upgrading to MC26/setting up zones. I have grown afraid of touching the jump fwd/back buttons especially while important recordings are in progress.  I used to be able to press the jump buttons like crazy and never had these freezes. The freezing has NEVER happened when just watching a show (not pressing any buttons).

Hope the attached log helps figure this out. "Previous Log" file was HUGE, so I snipped it to begin just where playback of the [frozen]show began, to the END of log.

Thank you


PS. Forgot to mention this happened once on a Client machine, but not able to grab a log from it, had to force shutdown the PC using power button on front panel because there's no keyboard/mouse on the client.

[Yaobing]

I have not seen this behavior and there have been no changes that I am aware in video playback in MC26.

I will set my recording in TS format and keep an eye on it.

[Yaobing]

If I have to guess, I would say bit stream might have something to do with it.  Try experiment with changing that setting.

[tzr916]

I'm really new to the Zone thing. Basically, before setting up Zone Switch, I had the Server set to always bitstream. The only change I made was to setup a second zone called Music. When video plays it uses the original "Player" zone that was not modified (bitstream), and when music is played it uses a new zone "Music" that is 2 channel PCM.

It's easy to see that the correct zone is being used when I'm in standard view testing, but 99.9% of the time I use theater view so I can't tell which zone is being used when the freeze happens. Is there any possibility the wrong zone is being chosen? See line in log file:

356824953: 4676: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Zone: Music (id: 10012)

[Yaobing]

Since you always used bitstream for video, and you continue to use it for video, then it is less likely the issue.  I made the suggestion on assumption that you changed the setting for video.

[tzr916]

After changing from Direct Sound to WASAPI mode, my jump fwd/rev problem has gotten much better, gone in fact. But still about once a week MC will freeze/hang requiring CTL-ALT-DEL. This time, it's right when I press Play on a tv show (ts file)- the first frame of the video comes up on the screen and freezes while audio continues to play, but MC will not respond to any remote or keyboard and I have to force MC to close using task manager.

I am the third person to see quite similar video freezing/crashing (see other two):
https://yabb.jriver.com/interact/index.php/topic,124284
https://yabb.jriver.com/interact/index.php/topic,124485

[tzr916]

Just froze again right when I pressed "play" with remote, had to kill MC using task manager again.... Log file attached, snipped previous log just prior to point where playback was being started of program called "I:\TEMP\Paranormal Emergency - S2019E105 - I Wasn't Alone.ts"


Anyone helping me?

[Yaobing]

Just froze again right when I pressed "play" with remote, had to kill MC using task manager again.... Log file attached, snipped previous log just prior to point where playback was being started of program called "I:\TEMP\Paranormal Emergency - S2019E105 - I Wasn't Alone.ts"


Anyone helping me?

The thread that built a DirectShow graph was successful in doing it.  The main thread of the program seemed to have been stuck. 

This was the last operation in the main thread:

25969062: 11100: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike\AppData\Roaming\J River\Media Center 26\Library\browser (theater view).jmd

I could not see whether that operation was successful unfortunately.  This seems to be unrelated to video playback.

[JimH]

Here's another "stuck" problem that was related to a NAS drive failure:
https://yabb.jriver.com/interact/index.php/topic,24031.msg862032.html#msg862032

[tzr916]

25969062: 11100: Database: CMediaFileIOSave::Load: Saving: C:\Users\Mike\AppData\Roaming\J River\Media Center 26\Library\browser (theater view).jmd

I could not see whether that operation was successful unfortunately.  This seems to be unrelated to video playback.

Thanks for looking 

In the original (full) log, that save operation happened 7 other times, and I do not see what a "success" should look like? Is there supposed to be a line saying "save successful" or something? Because I don't see evidence of that anywhere in those 7 other times that the save operation showed up. And MC certainly did not freeze on any of those other save operations.

[Yaobing]

Thanks for looking 

In the original (full) log, that save operation happened 7 other times, and I do not see what a "success" should look like? Is there supposed to be a line saying "save successful" or something? Because I don't see evidence of that anywhere in those 7 other times that the save operation showed up. And MC certainly did not freeze on any of those other save operations.

No, that particular line of logging has no indication of success or failure, or "Start" and "Finish" as seen in logging in many other functions.  So there is just no way to tell.  It could have been stuck inside that function, or that function could have succeeded but no other main thread activity was logged after that.

[tzr916]

Another freeze... Had just rebooted PC, started MC, was watching live tv for almost an hour, pressed stop, navigate to saved show "CBS 13 News at 10p", press play, video froze on first frame while audio continued to play. Can see by CPU usage that madvr is not processing frames. This time did not do CTL-ALT-DEL, just hit ESC, MC closed down with no error message or warning. Restart MC, collect log, start watching same CBS 13 News without issue. Log:

[Yaobing]

This time the main thread disappeared from the log again, but at a different location.  So something stalled.  The audio started running, and video did not.  I wonder if there is something not right between your video device and madVR.

[tzr916]

Thanks for checking again. Just strange that it works perfect for 10 days then craps out. Haven't touched Madvr in a long time, it still shows my AVR and display model correctly.

I went ahead and updated my GPU drivers, enabled Madvr setting "delay playback start until renderer is full", lowered CPU queue size... See what happens.

[tzr916]

...I went ahead and updated my GPU drivers, enabled Madvr setting "delay playback start until renderer is full", lowered CPU queue size... See what happens.

MC working fine until just now, freeze again, this time didn't even display the first frame of video or play any sound at all, just froze on the tv show's theater view page where I pressed play. I tried ESC a few time, mouse cursor went to spinning circle, then all white overlay, then MC shut down without any error. Restart MC, collect logs, play the same show, no problems.

Log snipped to just prior trying to play show and freeze "20_20 - The Deadly Ride 2020-04-03.ts"

[Yaobing]

I am adding some logging to function CMediaFileIOSave::Start().  I don't see why that function would hang, but twice we have seen it being the last main thread entry.

[tzr916]

Thanks, let me know if I need to change log verbose (currently set to zero).

[Yaobing]

Verbosity only affects TV logging.  This particular one is not TV specific.  So leaving it at verbosity 0 is fine.