Topic: [bugs] with Theatre View (Read 4160 times)

dean70 · « **on:** August 12, 2012, 05:48:21 pm »

1 - On startup in Theatre View having an issue with application error in mc17.exe that occurs after the audio device has been changed in the previous session. When the crash is about to occur (usually a few seconds after the theatre view display shows), there is no background image displayed (using Rapier Fusion skin). If you quickly switch to standard view, then back to theatre view, the crash does not occur.

2 - When starting a movie, there is no video showing (just blank screen), but the audio plays. Stopping the movie and restarting will bring back the video display. This has only started since 17.0.182 (or thereabouts).

3 - Starting a DVD from disc in Theatre View will sometimes display in a windowed view. You have to manually select Display View to get it back to full screen. This seems to occur after playing multiple discs.

Currently running v17.0.183

dean70 · « **Reply #1 on:** August 18, 2012, 03:45:52 am »

I have gone through the process of uninstalling MC17.0.184 and re-installing the latest stable release 17.0.182. Item 1 has been resolved - was an issue with the Rapier Fusion skin - now using Blue Puzzle without this issue.

Items 2 & 3 still occur. Item 2 (the blank screen issue can be worked around by changing the view to Standard (Ctrl+1) or Theatre View (Ctrl+4), then back to Display (Ctrl+3) while the move is playing to get the video display back (BTW changed to Red October Standard as well) - this is repeatable 100% of the time.

As this is a purchased product, I would expect such fundamental issues be resolved and not be ignored or swept under the carpet.

JimH · « **Reply #2 on:** August 18, 2012, 06:26:08 am »

If nobody answers, it often means nobody knows. I don't know.

Are you using Red October Std or HQ? Try the other.

It could be a video driver problem.

dean70 · « **Reply #3 on:** August 18, 2012, 07:17:47 pm »

This has only started within the last few updates of MC >17.0.180. I have been using MC since v17.0.99 and this is only a fairly recent occurrence. MC is the only software that is updated - things like drivers, etc have not been changed since the HTPC was built. Edit: All the drivers are still at the latest version.

This will occur with both Red October HQ and Red October Standard. It is not a case of I don't know - something has changed in the software to cause this to happen. The Video option 'Switch on play to Display View' is also set. If this is disabled and I manually switch it is ok.

So there are 3 scenarios:

1 - Stop and restart the movie to get it to show
2 - Switch to standard view (Ctrl+1) or Theatre view (Ctrl+4), then back to Display view (Ctrl+3) to get the video to display
3 - Change the Video option 'Switch on play to Display View'

Video will quite happily play first time in any configuration other than Display View. As this is a HTPC hooked up to a 1080p Projector, I expect to be able to watch a movie full screen without having to fiddle around with different views to get it to work. It was that way right up to about MC v17.0.180.

dean70 · « **Reply #4 on:** August 26, 2012, 05:18:38 pm »

Noticed that Display View doesnt always take full screen focus. I can sometimes see the Windows Task Bar along the bottom of screen (Task Bar set to auto-hide). Clicking on the display window will bring it back to foreground.

When switching using scenario 2 above to Standard View then back to Display View, after watching movie MC returns to Standard View, but switching to Theatre View again will cause MC to hang. You have to right click on taskbar and select close & get the Application has stopped responding... message in Windows. I am able to launch MC again into Theatre View without issue.

The blank screen issue only affects DVD from disc and mt2s BluRay copies played from the hard disc for the first video played after startup. If you switch to Display View (Ctrl+3) before anything is played so the MC logo displays, then switch back to Theatre, it will play correctly. It does not affect TV mode.

MrHaugen · « **Reply #5 on:** August 27, 2012, 04:53:17 am »

Even though you've not changed any other software (or hardware), this might still be driver related issues. Especially when it only happens to certain things like Display in your case. JRiver might for instance take advantage of new functions of graphic cards or the software they use, and those functions might be missing or broken in the older driver software. This is all theory, but it's worth a shot.

First, you could also try enabling or disable Hardware Acceleration and change the Red October Quality settings. If that does not work, you could try to update to the latest drivers for your graphics card. You can also update the DirectX software. Both of those are very often the culprit in display problems.

dean70 · « **Reply #6 on:** August 27, 2012, 11:20:53 pm »

Quote from: MrHaugen on August 27, 2012, 04:53:17 am

Even though you've not changed any other software (or hardware), this might still be driver related issues. Especially when it only happens to certain things like Display in your case. JRiver might for instance take advantage of new functions of graphic cards or the software they use, and those functions might be missing or broken in the older driver software. This is all theory, but it's worth a shot.

I am running on a platform (AMD A8-3850 Llano APU) that was only released Q3 2011. Hardly obsolete hardware. I did actually find a newer driver suite on AMDs web site which I am trying now. (The one listed on Asus motherboard page is still the same revision that I originally built the HTPC with). If this is a the case, I would have thought the onus would be on the developer to ensure compatibiliy with most current hardware.

Quote from: MrHaugen on August 27, 2012, 04:53:17 am

Even though you've not changed any other software (or hardware), this might still be driver related issues. Especially when it only happens to certain things like Display in your case. JRiver might for instance take advantage of new functions of graphic cards or the software they use, and those functions might be missing or broken in the older driver software. This is all theory, but it's worth a shot.

First, you could also try enabling or disable Hardware Acceleration and change the Red October Quality settings. If that does not work, you could try to update to the latest drivers for your graphics card. You can also update the DirectX software. Both of those are very often the culprit in display problems.

Looking at all the video settings - did manage to fix an unrelated auto refresh switch in the process as well.

dean70 · « **Reply #7 on:** August 29, 2012, 07:16:11 am »

It is exactly the same with the latest AMD driver suite

MrHaugen · « **Reply #8 on:** August 29, 2012, 07:24:01 am »

And DirectX is up to date?

dean70 · « **Reply #9 on:** August 29, 2012, 05:45:57 pm »

Quote from: MrHaugen on August 29, 2012, 07:24:01 am

And DirectX is up to date?

It should be - running Windows 7 SP1 with all current Windows Updates installed.

I can also get MC to lock-up without playing any video by switching from Theatre View (set to startup in this mode) to Standard view to change/check an option, then back to Theatre View will lockup completely with black screen and wait cursor. Have to terminate the process in Task Manager. I am using custom skins and theatre view and standard view.

The thing is, if you go though the process of "initialising" display view by switching first before playing anything then back again, all playback is flawless.

MrHaugen · « **Reply #10 on:** August 30, 2012, 03:19:46 am »

That should be a good clue. Perhaps Matt knows what's going on.

dean70 · « **Reply #11 on:** August 30, 2012, 05:30:50 am »

This is the skin I am using for Theater View: http://x-plain.blogspot.com.au/p/blue-puzzle.html
Also had used http://x-plain.blogspot.com.au/p/rapier-fusion-skin.html previously since v17.0.99

and using Emotiva http://yabb.jriver.com/interact/index.php?topic=73087.10 for standard view (It did not resolve anything by going back to the default skin).

JimH · « **Reply #12 on:** August 30, 2012, 07:46:19 am »

I don't think what you see is an MC bug.

dean70 · « **Reply #13 on:** August 31, 2012, 07:35:03 am »

Done some more testing with the Theatre View hang issue. If I use a standard skin & theme (Noire) it is ok. Changing just the theme setting to either Rapier Fusion or Blue Puzzle with skin still set to Noire will cause eventual hang. Changing skin to Rapier Fusion or Blue Puzzle and leaving theme either blank or default will also cause hang.

The only way to get it stable is to only use the default supplied themes and skins. Also tried setting Theatre View to Fullscreen exclusive under Options.

dean70 · « **Reply #14 on:** September 04, 2012, 10:30:53 pm »

stewart_pk · « **Reply #15 on:** September 04, 2012, 11:31:53 pm »

Hello, I use both of those skins (Rapier at the moment).

Just in case you're not, shouldn't you be setting both the Skin and the Theme settings under Theater View to both Blue Puzzle or both Raper?

http://yabb.jriver.com/interact/index.php?topic=70190.0
http://yabb.jriver.com/interact/index.php?topic=69662.0

dean70 · « **Reply #16 on:** September 05, 2012, 07:36:27 pm »

Quote from: stewart_pk on September 04, 2012, 11:31:53 pm

Hello, I use both of those skins (Rapier at the moment).

Just in case you're not, shouldn't you be setting both the Skin and the Theme settings under Theater View to both Blue Puzzle or both Raper?

http://yabb.jriver.com/interact/index.php?topic=70190.0
http://yabb.jriver.com/interact/index.php?topic=69662.0

I have both Skin and Theme set to Blue Puzzle - was trying one at a time as a test to isolate the hanging issue. Seems to have only cropped up in the last couple of releases. I was using Raiper previously since release v17.0.99, but started having issues.

stewart_pk · « **Reply #17 on:** September 06, 2012, 12:41:32 am »

I feel for ya dean, I don't have any of the problems you've mentioned.
I think the Blue Puzzle and Rapier skins add significant value to the JRiver product and probably should be officially included, thank you maker!

Anyway I use a cheap Asus AMD 6450 silent video card, cost like $50-60. I'm using Windows 7 64bit with the latest drivers.
Perhaps if you added one to your system, these problems would go away, good luck!

MrHaugen · « **Reply #18 on:** September 06, 2012, 01:56:19 am »

Dean, you should try to log some of those problems. Perhaps there can be a fix. At least for version 18. You'll find log under the Help menu. You could post a link to the file here, or post parts of it in text if you kan narrow down where the problem starts.

dean70 · « **Reply #19 on:** September 07, 2012, 07:41:42 pm »

Here is a log with the theater view hang. http://www.mediafire.com/view/?in1560mtz29qjua

As for the no video issue, I have logged it and it appears to be trying to contact a laptop on the LAN in the cases where the video doesn't show. The laptop has a trial install of JRiver (the original version of 17 that I downloaded for trial) that is not actively running, but must be running a service that is broadcasting on the network. I will uninstall & try the video again. eg:

Code: [Select]

0206343: 2232: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 10.10.10.11: M-SEARCH: http://239.255.255.250:1900*

This doesn't show up on the log with the working video display

edit: with the DLNA function disabled still getting no video on startup issue, so the ip address unrelated. I did find something interesting - section of logs below:

no video:

Code: [Select]

0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Start
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Native video size (1920, 1080)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Window client rect (l=0, t=0, r=1920, b=1080)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Original target rect (l=0, t=0, r=320, b=180)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Deflate 0.000000
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Target rect after zooming (l=-307, t=0, r=2228, b=1080)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Target rect after shifting (l=5231, t=3115, r=7766, b=4195)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Source rect after cropping (l=0, t=131, r=1920, b=949)
0038080: 2388: Unknown: CVideoZoomControl::GetVideoRectangles: Finish (0 ms)
0038080: 2388: Playback: CDXPlayerWindow::LayoutWindow: Source: 0,131,1920,949; Target: 5231,3115,7766,4195)
0038080: 2388: Playback: CDXPlayerWindow::LayoutWindow: Positioning video
0038080: 2388: Playback: CDXPlayerWindow::LayoutWindow: Success
0038080: 2388: Playback: CDXPlayerWindow::LayoutWindow: Finish (0 ms)

video:

Code: [Select]

0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Start
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Start
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Native video size (1920, 1080)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Window client rect (l=0, t=0, r=1920, b=1080)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Original target rect (l=0, t=0, r=1920, b=1080)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Deflate 0.000000
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Target rect after zooming (l=-307, t=0, r=2228, b=1080)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Target rect after shifting (l=-307, t=0, r=2228, b=1080)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Source rect after cropping (l=0, t=131, r=1920, b=949)
0021887: 3844: Unknown: CVideoZoomControl::GetVideoRectangles: Finish (0 ms)
0021887: 3844: Playback: CDXPlayerWindow::LayoutWindow: Source: 0,131,1920,949; Target: -307,0,2228,1080)
0021887: 3844: Playback: CDXPlayerWindow::LayoutWindow: Positioning video
0021887: 3844: Playback: CDXPlayerWindow::LayoutWindow: Success
0021887: 3844: Playback: CDXPlayerWindow::LayoutWindow: Finish (15 ms)

Notice the Target window coodinates in the line Playback: CDXPlayerWindow::LayoutWindow: Source: 0,131,1920,949; Target: 5231,3115,7766,4195) vs Playback: CDXPlayerWindow::LayoutWindow: Source: 0,131,1920,949; Target: -307,0,2228,1080)?

dean70 · « **Reply #20 on:** September 10, 2012, 05:03:02 pm »

InflatableMouse · « **Reply #21 on:** September 11, 2012, 01:05:16 am »

I just rebuilt my HTPC and I'm seeing the behavior that sometimes a video plays audio with a black screen, sometimes it doesn't play at all, just a black screen. I noticed that without audio, nothing else pops up on the screen when I skip forward, change volume or press info. When audio plays, search bars and volume bars are shown.

I'm using ROHQ. I have set the display frequencies to match the video source, but I had set things like 23.975 to 24 and 29/59 to 60. When I changed that to 23 and 59 things improved dramatically.

Over the weekend I had MC not return to Theater View at all, it just remained black. Alt-tab would show the preview windows but alt-tabbing to something other than MC just showed a flash of the other app, they wouldn't stay in the foreground. MC was unresponsive, Ctrl-alt-del showed the options for task manager, shutdown etc, but task manager woudn't stay op top either, things turned black again. I eventually just rebooted. This happened twice.

Another setting that I disabled may have had to do with it, in Theater View settings at the bottom there's something called exclusive mode. I had that ticked but disabled it because I wasn't sure what it did, it might have been responsible for MC not returning to Theater View after playing a video I don't know.

When I looked at the list of refresh rates, at the bottom is something like default behavior, which defaults to desktop settings. I had that set to 60hz, but then I noticed Windows/drivers preferred 59Hz. I changed that back to desktop settings and that may have improved the behavior as well.

INTERACT FORUM

Author Topic: [bugs] with Theatre View (Read 4160 times)