I'd *really a lot* like to get some good pictures (not screen grabs; I want the TV bezels visible) for this section, illustrating the combinations in question. No flash; you'll have to use a tripod.
--04:30, 29 January 2006 (UTC)
- I'm a moron. I actually meant to link to Aspect ratio, which I had already written; I guess we'd better merge them.
--Baylink 01:49, 31 January 2006 (UTC)
- Okay, after seeing no dispute, I have carried out the merger. --Gregturn 18:39, 13 February 2006 (UTC)
- Thanks for doing that Greg. I was a little too close to my own writeup to be able to figure out how best to glue the other guy's into it. --Baylink 20:46, 13 February 2006 (UTC)
- perhaps some more info on configuration in MythTV which is why people are here after all -Paul
So, about those black bars when having a true 4:3 show on 16:9. Is it possible to configure MythTV to display grey bars and not black?
- Those are sent by the station, so not without cropping and replacing.--Steve Adeff 15:38, 22 August 2006 (UTC)
- No, not those. Correct me if I am wrong, but I get a 4:3 picture from the network, and "MythTV" adds the black padding/borders on each side to fit my 16:9 layout. In "Standard" mode, ffmpeg is used, and in "mpeg2" mode libmpeg2 is used, am I correct? So if ffmpeg is used, the API should support changing the color (padcolor) of the stream, right? I might be way of now :-) --Hazze 20:08, 27 August 2006 (UTC)
- You can set the color of the bars added by MythTV to black/gray (at least in 0.21-fixes)
--Dekarl 10:22, 8 October 2008 (UTC)
MythTV's aspect ratio override options
Could someone explain exactly what all the mythtv aspect ratio options do? This article does a good job of explaining what the tv can do, but skips over MythTV's options. What I would like to do is force MythTV to stretch any video to full screen, so that I can use the settings on my tv to correct the aspect ratio. --Turpie 01:54, 9 October 2006 (UTC)
Problem with incorrect aspect ratio playback
I have some 1920x1080 recordings on my backend. I can play these recordings fine with mplayer on my frontend, no re-scaling, on my 1920x1200 monitor. 1:1 play is correct aspect ratio, not quite as tall as my monitor. I have spent about an hour trying to hack mythtv playback to mimic this behavior. Default play squishes the 16:9 recording to 4:3, and no mythtv zoom mode/ aspect ratio settings seem to get the recording back to the original aspect ratio.
Any tips on what I can do?
I also changed the mythtv gui to 1920x1080, tv-size to match gui... same problem.
Is the backend transcoding the stored mpg file to something wrong? Playing the .mpg file on the frontend with mplayer works correctly. beautiful, 16:9 picture at 1920x1080 resolution, 1:1 pixel display to recording
My settings table has no
value = 'XineramaMonitorAspectRatio'
rows. So that does not work. I tried the mplayer command defined in VideoDefaultPlayer, and it works fine on the .mpg file. I note that I only see mythfrontend.read eating CPU on the frontend while playing video. The backend only shows significant activity on mythbackend. How does it decide how to display/resample/transcode? I cannot immagine that mythbackend is transcoding, at a CPU load of around 1%.
--Mr.What 17:26, 21 February 2009 (UTC)
AR and AFD seem to be mixed up in some places. AR contained in the signal is about the transmitted frame. AFD is about the relevant content contained within the frame. e.g. a 4:3(AFD) movie within a 16:9(AR) stream to be displayed on a 4:3 screen. Myth could automagically display a full screen picture instead of a framed one. More about AFD at Wikipedia. See SMPTE for what can go wrong / right with AR/AFD/bar data, etc. --Dekarl 10:30, 8 October 2008 (UTC)
mention ATSC bar data
According to Wikipedia there is some bar data to be transmitted on ATSC channels when broadcasting wider then 16:9 content. This could be used to crop/resize the video in a windowed player to occupy as little screen space with black bars. Also useful for cropping recordings when transcoding to mkv and the like. --Dekarl 10:30, 8 October 2008 (UTC)