Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

MacOSX frontend & 1080i

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


gallatin at cs

Mar 12, 2007, 7:27 AM

Post #1 of 19 (3715 views)
Permalink
MacOSX frontend & 1080i

Is anybody able to play smooth, 1080i video using the MacOSX frontend?

After upgrading my Linux combined front/backend to 0.20-fixes, I
decided to try the MacOSX frontend on my 2.16GHz Core2 Duo iMac with a
Radeon x1600 (1680x1050 lcd). I'm running the MacOSX binary from
http://www.goof.com/~mmead/MythFrontend-MacOSXUniversal-0.20-fixes-20061001.dmg.bz2.

Standard def, and 720p content works flawlessly, but 1080i has
annoying jerkiness. The same 1080i files play flawlessly with vlc. I
have tried the hints in the Wiki, and have tried libmpeg2, etc, but to
no avail. The machine is 65-75% idle when playing 1080i, so I don't
*think* CPU is the issue.

One thing I've fixated on is the messages I find in the log when
I enable verbose playback. This is printed roughly 4 times per
second:

2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
doubling video frame interval to slow down.

According to -v audio,playback, the audio device seems to be setup
as 48000Hz, even though the bitrate of the AC3 audio is 384000
(log snippet below). Could this be the problem? I've left my
audio settings at their default, and don't have any passthroughs
enabled..

Thanks for any help you can offer,

Drew

PS: Here are some snippets from -v playback,audio

2007-03-12 09:52:01.236 TV: Attempting to change from None to WatchingPreRecorded
2007-03-12 09:52:01.240 RingBuf(/video/1051_20070312030500.mpg): OpenFile(/video/1051_20070312030500.mpg, 12)
2007-03-12 09:52:01.243 RingBuf(/video/1051_20070312030500.mpg): CalcReadAheadThresh(4000 KB)
-> threshhold(146 KB) min read(32 KB) blk size(64 KB)
0: start_time: 5990.753 duration: 323.573
1: start_time: 5990.729 duration: -9223372036854.775
stream: start_time: 66563.660 duration: 3595.524 bitrate=15522 kb/s
2007-03-12 09:52:01.594 AFD: Stream #0, has id 0x49 codec id MPEG2VIDEO, type Video, bitrate 45000000 at 0x0x1b28c7c0
2007-03-12 09:52:01.594 detectInterlace(Detect Scan, Interlaced Scan, 29.97, 1088) ->Interlaced Scan
2007-03-12 09:52:01.597 AFD: Looking for decoder for MPEG2VIDEO
2007-03-12 09:52:01.597 AFD: Opened codec 0x18be800, id(MPEG2VIDEO) type(Video)
2007-03-12 09:52:01.597 AFD: Stream #1, has id 0x52 codec id AC3, type Audio, bitrate 384000 at 0x0x1b28c9f0
2007-03-12 09:52:01.597 AFD: Looking for decoder for AC3
2007-03-12 09:52:01.598 AFD: Opened codec 0x18bfe00, id(AC3) type(Audio)
2007-03-12 09:52:01.598 AFD: Audio Track #1 is A/V stream #1 and has 2 channels in the English language(6647399).
2007-03-12 09:52:01.598 RingBuf(/video/1051_20070312030500.mpg): CalcReadAheadThresh(45384 KB)
-> threshhold(1662 KB) min read(32 KB) blk size(512 KB)
2007-03-12 09:52:01.598 AFD: Selected track 1: English AC3 2ch (A/V Stream #1)
2007-03-12 09:52:01.598 AFD: Initializing audio parms from audio track #1
2007-03-12 09:52:01.599 AFD: Audio format changed
from id(NONE) -1Hz -1ch 0bps ; id(NONE) -1Hz -1ch 0bps
to id( AC3) 48000Hz 2ch 16bps ; id( AC3) 48000Hz 2ch 16bps
2007-03-12 09:52:01.603 AO: Killing AudioOutputDSP
2007-03-12 09:52:01.764 AO: Audio fragment size: 0
2007-03-12 09:52:01.777 AO: Audio Stretch Factor: 1
2007-03-12 09:52:01.777 AO: Ending reconfigure
2007-03-12 09:52:01.777 Dec: Trying to select track (w/lang)
2007-03-12 09:52:01.777 Dec: Selecting first track
2007-03-12 09:52:01.778 Dec: Selected track #1 in the Unknown language(0)
2007-03-12 09:52:01.778 Resyncing position map. posmapStarted = 0 livetv(0) watchingRec(0)
2007-03-12 09:52:01.922 Position map filled from DB to: 93864
2007-03-12 09:52:01.923 SyncPositionMap prerecorded, from DB: 6459 entries
2007-03-12 09:52:01.923 SyncPositionMap, new totframes: 93864, new length: 3131, posMap size: 6459
2007-03-12 09:52:01.923 AFD: Position map found
2007-03-12 09:52:01.923 AFD: Successfully opened decoder for file: "/video/1051_20070312030500.mpg". novideo(0)
2007-03-12 09:52:01.974 VideoOutputQuartz::Init(width=1920, height=1088, aspect=1.77778, winid=14
winx=0, winy=0, winw=1680, winh=1050, WId embedid=0)
2007-03-12 09:52:01.975 Over/underscan. V: 0, H: 0, XOff: 0, YOff: 0
2007-03-12 09:52:01.975 VideoOutputQuartz::VideoAspectRatioChanged(aspect=1.77778) [was 0]
<....>
2007-03-12 09:52:05.417 NVP: Video is 3.06417 frames ahead of audio,
doubling video frame interval to slow down.
2007-03-12 09:52:05.422 AO: Broadcasting free space avail
2007-03-12 09:52:05.434 AO: Broadcasting free space avail
2007-03-12 09:52:05.446 AO: Broadcasting free space avail
2007-03-12 09:52:05.457 AO: Broadcasting free space avail
2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
doubling video frame interval to slow down.
2007-03-12 09:52:05.469 AO: Broadcasting free space avail
2007-03-12 09:52:05.481 AO: Broadcasting free space avail
2007-03-12 09:52:05.492 AO: Broadcasting free space avail
2007-03-12 09:52:05.504 AO: Broadcasting free space avail
2007-03-12 09:52:05.515 AO: Broadcasting free space avail
2007-03-12 09:52:05.527 AO: Broadcasting free space avail
2007-03-12 09:52:05.527 NVP: Video is 3.89831 frames ahead of audio,
doubling video frame interval to slow down.
2007-03-12 09:52:05.539 AO: Broadcasting free space avail
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 12, 2007, 7:49 AM

Post #2 of 19 (3604 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
>
> Is anybody able to play smooth, 1080i video using the MacOSX frontend?

1080i works well for me, on my 1.66GHz Core Duo Mac Mini + 720P DLP Display.

> After upgrading my Linux combined front/backend to 0.20-fixes, I
> decided to try the MacOSX frontend on my 2.16GHz Core2 Duo iMac with a
> Radeon x1600 (1680x1050 lcd). I'm running the MacOSX binary from
> http://www.goof.com/~mmead/MythFrontend-MacOSXUniversal-0.20-fixes-20061001.dmg.bz2.
>
> Standard def, and 720p content works flawlessly, but 1080i has
> annoying jerkiness. The same 1080i files play flawlessly with vlc. I
> have tried the hints in the Wiki, and have tried libmpeg2, etc, but to
> no avail. The machine is 65-75% idle when playing 1080i, so I don't
> *think* CPU is the issue.
>
> One thing I've fixated on is the messages I find in the log when
> I enable verbose playback. This is printed roughly 4 times per
> second:
>
> 2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
> doubling video frame interval to slow down.

Have you tried changing the video playback settings? I have "Use
video as timebase" disabled in my configuration. Maybe also try
different de-interlacing settings to see the effect.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 12, 2007, 8:23 AM

Post #3 of 19 (3603 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak [ignasiak [at] gmail] wrote:
> On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
> >
> > Is anybody able to play smooth, 1080i video using the MacOSX frontend?
>
> 1080i works well for me, on my 1.66GHz Core Duo Mac Mini + 720P DLP Display.

Cool! What output resulution do you run at?

I've always 1080i problems on my Linux box as well, and was thinking
about purchasing a Mini to use as a frontend, which is why I was
playing around on MacOSX.

> > After upgrading my Linux combined front/backend to 0.20-fixes, I
> > decided to try the MacOSX frontend on my 2.16GHz Core2 Duo iMac with a
> > Radeon x1600 (1680x1050 lcd). I'm running the MacOSX binary from
> > http://www.goof.com/~mmead/MythFrontend-MacOSXUniversal-0.20-fixes-20061001.dmg.bz2.

Do you run this same binary, or did you build it yourself..?

> > Standard def, and 720p content works flawlessly, but 1080i has
> > annoying jerkiness. The same 1080i files play flawlessly with vlc. I
> > have tried the hints in the Wiki, and have tried libmpeg2, etc, but to
> > no avail. The machine is 65-75% idle when playing 1080i, so I don't
> > *think* CPU is the issue.
> >
> > One thing I've fixated on is the messages I find in the log when
> > I enable verbose playback. This is printed roughly 4 times per
> > second:
> >
> > 2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
> > doubling video frame interval to slow down.
>
> Have you tried changing the video playback settings? I have "Use
> video as timebase" disabled in my configuration. Maybe also try
> different de-interlacing settings to see the effect.

I've tried enabling and disabling the "video as timebase", as well
as totally disabling de-interlacing. No matter what I do, I still
see the "NVP: Video is 3.x frames ahead of audio" several times
per second, corresponding to surging, or jerkiness in the video.

Can you do me a favor, and play a 1080i video with verbose audio and
playback enabled
(/Applications/MythFrontend.app/Contents/MacOS/mythfrontend -v
audio,playback > log ) and check your log for these messages? And
maybe see what the audio format of the recording is and what your
audio device gets set to? That might put my mind at ease as to
whether this audio thing is what is killing me.

Thanks,

Drew

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 12, 2007, 3:16 PM

Post #4 of 19 (3592 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
> Todd Ignasiak [ignasiak [at] gmail] wrote:
> > On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > >
> > > Is anybody able to play smooth, 1080i video using the MacOSX frontend?
> >
> > 1080i works well for me, on my 1.66GHz Core Duo Mac Mini + 720P DLP Display.
>
> Cool! What output resulution do you run at?

1280x720 @ 60FPS. My audio is AC3 passthrough via the digital audio output.

> I've always 1080i problems on my Linux box as well, and was thinking
> about purchasing a Mini to use as a frontend, which is why I was
> playing around on MacOSX.
>
> > > After upgrading my Linux combined front/backend to 0.20-fixes, I
> > > decided to try the MacOSX frontend on my 2.16GHz Core2 Duo iMac with a
> > > Radeon x1600 (1680x1050 lcd). I'm running the MacOSX binary from
> > > http://www.goof.com/~mmead/MythFrontend-MacOSXUniversal-0.20-fixes-20061001.dmg.bz2.
>
> Do you run this same binary, or did you build it yourself..?

No, I built mine, with the osx-packager.pl script.

> > > Standard def, and 720p content works flawlessly, but 1080i has
> > > annoying jerkiness. The same 1080i files play flawlessly with vlc. I
> > > have tried the hints in the Wiki, and have tried libmpeg2, etc, but to
> > > no avail. The machine is 65-75% idle when playing 1080i, so I don't
> > > *think* CPU is the issue.
> > >
> > > One thing I've fixated on is the messages I find in the log when
> > > I enable verbose playback. This is printed roughly 4 times per
> > > second:
> > >
> > > 2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
> > > doubling video frame interval to slow down.
> >
> > Have you tried changing the video playback settings? I have "Use
> > video as timebase" disabled in my configuration. Maybe also try
> > different de-interlacing settings to see the effect.
>
> I've tried enabling and disabling the "video as timebase", as well
> as totally disabling de-interlacing. No matter what I do, I still
> see the "NVP: Video is 3.x frames ahead of audio" several times
> per second, corresponding to surging, or jerkiness in the video.
>
> Can you do me a favor, and play a 1080i video with verbose audio and
> playback enabled
> (/Applications/MythFrontend.app/Contents/MacOS/mythfrontend -v
> audio,playback > log ) and check your log for these messages? And
> maybe see what the audio format of the recording is and what your
> audio device gets set to? That might put my mind at ease as to
> whether this audio thing is what is killing me.

The vast majority of the logs are of the general type:

2007-03-12 17:16:17.286 NVP: interlaced frame seen after 1 progressive frames
2007-03-12 17:16:17.294 AO: Broadcasting free space avail
2007-03-12 17:16:17.320 NVP: progressive frame seen after 1 interlaced frames
2007-03-12 17:16:17.326 AO: Broadcasting free space avail
2007-03-12 17:16:17.358 AO: Broadcasting free space avail
2007-03-12 17:16:17.370 NVP: interlaced frame seen after 1 progressive frames
2007-03-12 17:16:17.390 AO: Broadcasting free space avail
2007-03-12 17:16:17.403 NVP: progressive frame seen after 1 interlaced frames
2007-03-12 17:16:17.422 AO: Broadcasting free space avail
2007-03-12 17:16:17.453 NVP: interlaced frame seen after 1 progressive frames


I did see some messages like yours after I have the video paused then
restart it. But, after a second or so those messages go away. And,
I don't notice any problems on the video:

2007-03-12 17:20:19.034 AO: Broadcasting free space avail
2007-03-12 17:20:19.058 NVP: Video is 11.5747 frames ahead of audio,
doubling video frame interval to slow down.
2007-03-12 17:20:19.058 NVP: interlaced frame seen after 1 progressive frames
2007-03-12 17:20:19.066 AO: Broadcasting free space avail
2007-03-12 17:20:19.098 AO: Broadcasting free space avail
2007-03-12 17:20:19.125 NVP: Video is 10.8614 frames ahead of audio,
doubling video frame interval to slow down.
2007-03-12 17:20:19.125 NVP: progressive frame seen after 1 interlaced frames
2007-03-12 17:20:19.130 AO: Broadcasting free space avail
2007-03-12 17:20:19.162 AO: Broadcasting free space avail
2007-03-12 17:20:19.192 NVP: Video is 10.2065 frames ahead of audio,
doubling video frame interval to slow down.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


jessewk at gmail

Mar 12, 2007, 3:37 PM

Post #5 of 19 (3597 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

I just joined the list so I may be late to the discussion here, so
excuse me if you've already been over this...

On my Mac Mini 1.66 Ghz w/ 1 GB RAM, 1080i playback is also jerky *if*
I have 'scale video as necessary' enabled. If I uncheck the box, the
content will play smoothly and it looks great on my 1080p display.
The difference I notice is that WindowServer sits at 30% CPU when
scaling is enabled and it's around 3% when it's not enabled. Of
course, no scaling should be necessary at all given my display
resolution.

Unchecking scaling it's not really a good solution since it makes 480
or 720 content look like a postage stamp in the center of my screen,
but maybe it will help track down the problem.

-Jesse

On 3/12/07, Todd Ignasiak <ignasiak [at] gmail> wrote:
> On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > Todd Ignasiak [ignasiak [at] gmail] wrote:
> > > On 3/12/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > > >
> > > > Is anybody able to play smooth, 1080i video using the MacOSX frontend?
> > >
> > > 1080i works well for me, on my 1.66GHz Core Duo Mac Mini + 720P DLP Display.
> >
> > Cool! What output resulution do you run at?
>
> 1280x720 @ 60FPS. My audio is AC3 passthrough via the digital audio output.
>
> > I've always 1080i problems on my Linux box as well, and was thinking
> > about purchasing a Mini to use as a frontend, which is why I was
> > playing around on MacOSX.
> >
> > > > After upgrading my Linux combined front/backend to 0.20-fixes, I
> > > > decided to try the MacOSX frontend on my 2.16GHz Core2 Duo iMac with a
> > > > Radeon x1600 (1680x1050 lcd). I'm running the MacOSX binary from
> > > > http://www.goof.com/~mmead/MythFrontend-MacOSXUniversal-0.20-fixes-20061001.dmg.bz2.
> >
> > Do you run this same binary, or did you build it yourself..?
>
> No, I built mine, with the osx-packager.pl script.
>
> > > > Standard def, and 720p content works flawlessly, but 1080i has
> > > > annoying jerkiness. The same 1080i files play flawlessly with vlc. I
> > > > have tried the hints in the Wiki, and have tried libmpeg2, etc, but to
> > > > no avail. The machine is 65-75% idle when playing 1080i, so I don't
> > > > *think* CPU is the issue.
> > > >
> > > > One thing I've fixated on is the messages I find in the log when
> > > > I enable verbose playback. This is printed roughly 4 times per
> > > > second:
> > > >
> > > > 2007-03-12 09:52:05.459 NVP: Video is 3.57936 frames ahead of audio,
> > > > doubling video frame interval to slow down.
> > >
> > > Have you tried changing the video playback settings? I have "Use
> > > video as timebase" disabled in my configuration. Maybe also try
> > > different de-interlacing settings to see the effect.
> >
> > I've tried enabling and disabling the "video as timebase", as well
> > as totally disabling de-interlacing. No matter what I do, I still
> > see the "NVP: Video is 3.x frames ahead of audio" several times
> > per second, corresponding to surging, or jerkiness in the video.
> >
> > Can you do me a favor, and play a 1080i video with verbose audio and
> > playback enabled
> > (/Applications/MythFrontend.app/Contents/MacOS/mythfrontend -v
> > audio,playback > log ) and check your log for these messages? And
> > maybe see what the audio format of the recording is and what your
> > audio device gets set to? That might put my mind at ease as to
> > whether this audio thing is what is killing me.
>
> The vast majority of the logs are of the general type:
>
> 2007-03-12 17:16:17.286 NVP: interlaced frame seen after 1 progressive frames
> 2007-03-12 17:16:17.294 AO: Broadcasting free space avail
> 2007-03-12 17:16:17.320 NVP: progressive frame seen after 1 interlaced frames
> 2007-03-12 17:16:17.326 AO: Broadcasting free space avail
> 2007-03-12 17:16:17.358 AO: Broadcasting free space avail
> 2007-03-12 17:16:17.370 NVP: interlaced frame seen after 1 progressive frames
> 2007-03-12 17:16:17.390 AO: Broadcasting free space avail
> 2007-03-12 17:16:17.403 NVP: progressive frame seen after 1 interlaced frames
> 2007-03-12 17:16:17.422 AO: Broadcasting free space avail
> 2007-03-12 17:16:17.453 NVP: interlaced frame seen after 1 progressive frames
>
>
> I did see some messages like yours after I have the video paused then
> restart it. But, after a second or so those messages go away. And,
> I don't notice any problems on the video:
>
> 2007-03-12 17:20:19.034 AO: Broadcasting free space avail
> 2007-03-12 17:20:19.058 NVP: Video is 11.5747 frames ahead of audio,
> doubling video frame interval to slow down.
> 2007-03-12 17:20:19.058 NVP: interlaced frame seen after 1 progressive frames
> 2007-03-12 17:20:19.066 AO: Broadcasting free space avail
> 2007-03-12 17:20:19.098 AO: Broadcasting free space avail
> 2007-03-12 17:20:19.125 NVP: Video is 10.8614 frames ahead of audio,
> doubling video frame interval to slow down.
> 2007-03-12 17:20:19.125 NVP: progressive frame seen after 1 interlaced frames
> 2007-03-12 17:20:19.130 AO: Broadcasting free space avail
> 2007-03-12 17:20:19.162 AO: Broadcasting free space avail
> 2007-03-12 17:20:19.192 NVP: Video is 10.2065 frames ahead of audio,
> doubling video frame interval to slow down.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 12, 2007, 7:19 PM

Post #6 of 19 (3588 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/12/07, Jesse Ward-Karet <jessewk [at] gmail> wrote:
> I just joined the list so I may be late to the discussion here, so
> excuse me if you've already been over this...
>
> On my Mac Mini 1.66 Ghz w/ 1 GB RAM, 1080i playback is also jerky *if*
> I have 'scale video as necessary' enabled. If I uncheck the box, the
> content will play smoothly and it looks great on my 1080p display.
> The difference I notice is that WindowServer sits at 30% CPU when
> scaling is enabled and it's around 3% when it's not enabled. Of
> course, no scaling should be necessary at all given my display
> resolution.
>
> Unchecking scaling it's not really a good solution since it makes 480
> or 720 content look like a postage stamp in the center of my screen,
> but maybe it will help track down the problem.

There have been a few similar reports from people with 1080p displays.
I also have 'save video as necessary' enabled, but on my 720p
display it doesn't have any negative effects. It would be
interesting to see if changing that setting makes any difference on
the original poster's problem. Some people thought the mini's
integrated GPU might be a limiting factor for the higher resolutions,
but Andrew is using an iMac with a Radeon GPU.

You might also try changing your output to 720p, as a test, and see if
the scaling behavior is the same.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 13, 2007, 6:05 AM

Post #7 of 19 (3593 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak [ignasiak [at] gmail] wrote:
> I also have 'save video as necessary' enabled, but on my 720p

I assume you mean 'scale' ;)

BTW, thank you for posting your logs. They convinced me that audio
was not my problem.

> display it doesn't have any negative effects. It would be
> interesting to see if changing that setting makes any difference on
> the original poster's problem. Some people thought the mini's

That setting did not make a difference for me.

What *does* make a difference is displaying on an external monitor,
rather than using the builtin 1680x1050 flat panel. When using a Dell
2001FW (1600x1200, 60Hz), 1080i video is much, much, much more smooth.
I expect that this has something to do with the refresh rate of the
Dell LCD being 60Hz, while the refresh rate for the builting LCD is
150Hz (according to myth, refresh is N/A according to the Display Pref
pane). I guess I'll have to haul the computer downstairs and try
actually hooking it to the TV before I know if it will work.

I have only 2 problems left that I know about right now:

- Myth seems to want to enable/disable deinterlacing at random leading
to motion artifacts:

2007-03-13 08:47:40.763 NVP: interlaced frame seen after 85 progressive frames
2007-03-13 08:47:40.846 Enabled deinterlacing
2007-03-13 08:47:41.780 NVP: progressive frame seen after 29 interlaced frames
2007-03-13 08:47:41.847 Disabled deinterlacing
2007-03-13 08:47:41.948 NVP: interlaced frame seen after 5 progressive frames
2007-03-13 08:47:42.014 Enabled deinterlacing
2007-03-13 08:47:42.431 NVP: progressive frame seen after 14 interlaced frames
2007-03-13 08:47:42.498 Disabled deinterlacing

- MacOSX seems to put an insanely high value on file pages in its
unified buffer cache, and even on machine with 1GB of ram, it tends to
page out nearly everything to make room for a read-once .mpg file,
which won't be needed again. The machine got nearly unresponsive due
to paging out my normal applications. Unmounting the /video partition
freed over 600MB! Dec Tru64 UNIX, the last Mach based OS I worked
with, had a tuning parameter to limit the unified buffer cache
(ubc-maxpercent). I need to see if there is one on MacOSX...

Drew

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 13, 2007, 8:21 AM

Post #8 of 19 (3587 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> What *does* make a difference is displaying on an external monitor,
> rather than using the builtin 1680x1050 flat panel. When using a Dell
> 2001FW (1600x1200, 60Hz), 1080i video is much, much, much more smooth.
> I expect that this has something to do with the refresh rate of the
> Dell LCD being 60Hz, while the refresh rate for the builting LCD is
> 150Hz (according to myth, refresh is N/A according to the Display Pref
> pane). I guess I'll have to haul the computer downstairs and try
> actually hooking it to the TV before I know if it will work.

I tried Myth on my MacBook Pro, with a 1440x900 display, and it worked
on that display. I got a few of the "out of sync" messages, about
very 7-10 seconds or so, but the video display looked good. I
have an old CRT monitor that can do fairly high resolutions.. I'll
have to dig it out of the basement and test some more resolutions to
see if I can replicate what you're seeing.

Also, I doubt the LCD is being run at 150Hz, where does Myth show
that? I think LCDs are set to 60Hz by default, although it's hard to
tell for sure. I installed SwitchResX control panel & output the DDC
data for the display, and it showed it was running 1440x900 @ 60Hz.



> I have only 2 problems left that I know about right now:
>
> - Myth seems to want to enable/disable deinterlacing at random leading
> to motion artifacts:
>
> 2007-03-13 08:47:40.763 NVP: interlaced frame seen after 85 progressive frames
> 2007-03-13 08:47:40.846 Enabled deinterlacing
> 2007-03-13 08:47:41.780 NVP: progressive frame seen after 29 interlaced frames
> 2007-03-13 08:47:41.847 Disabled deinterlacing
> 2007-03-13 08:47:41.948 NVP: interlaced frame seen after 5 progressive frames
> 2007-03-13 08:47:42.014 Enabled deinterlacing
> 2007-03-13 08:47:42.431 NVP: progressive frame seen after 14 interlaced frames
> 2007-03-13 08:47:42.498 Disabled deinterlacing

I sometimes get messages with a many frames (e.g. progressive frame
seen after 11 interlaced frames), but I don't get any "Disabling
deinterlacing" messages. Are you switching to different channels and
maybe showing a 720p station (ABC, Fox)? You can override the
interlacing detection in the menu during playback.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


awk at awkward

Mar 13, 2007, 10:53 AM

Post #9 of 19 (3572 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Quoting Todd Ignasiak <ignasiak [at] gmail>:

> On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:

> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> that? I think LCDs are set to 60Hz by default, although it's hard to
> tell for sure. I installed SwitchResX control panel & output the DDC
> data for the display, and it showed it was running 1440x900 @ 60Hz.

It's a very long time since I looked at it - but there is code in
Myth's videoout 'portions' which attempts to get the refresh rate for
the display but when that fails (there is no refresh rate for a
digitally connected LCD Panel) defaults to 60Hz. If I recall there is
a second place where this reported value is then multiplied by a
constant (I thought 4 - but that doesn't make sense given the reported
value of 150Hz).

Some of this may be different if you're using the CoreVideo output
mechanism which I wrote some months ago but I don't think was ever
committed - is it possible that Andrew G & Todd are not running the
same videout device (CoreVideo vs. 'standard'). The reported refresh
rates may be different between these two approaches (see para. 1 above).

I apologize for the vagueness of the response - it's been some months
since I looked at any of this Myth code.

Andrew 8-)



_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 13, 2007, 12:10 PM

Post #10 of 19 (3560 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak [ignasiak [at] gmail] wrote:
> On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > What *does* make a difference is displaying on an external monitor,
> > rather than using the builtin 1680x1050 flat panel. When using a Dell
> > 2001FW (1600x1200, 60Hz), 1080i video is much, much, much more smooth.
> > I expect that this has something to do with the refresh rate of the
> > Dell LCD being 60Hz, while the refresh rate for the builting LCD is
> > 150Hz (according to myth, refresh is N/A according to the Display Pref
> > pane). I guess I'll have to haul the computer downstairs and try
> > actually hooking it to the TV before I know if it will work.
>
> I tried Myth on my MacBook Pro, with a 1440x900 display, and it worked
> on that display. I got a few of the "out of sync" messages, about

That's another good sign.
>
> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> that? I think LCDs are set to 60Hz by default, although it's hard to
> tell for sure. I installed SwitchResX control panel & output the DDC
> data for the display, and it showed it was running 1440x900 @ 60Hz.

It is reported (for me) when using -v playback:
2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]

Using the Dell LCD, it says '[returning 60]'

<...>

> > 2007-03-13 08:47:42.014 Enabled deinterlacing
> > 2007-03-13 08:47:42.431 NVP: progressive frame seen after 14 interlaced frames
> > 2007-03-13 08:47:42.498 Disabled deinterlacing
>
> I sometimes get messages with a many frames (e.g. progressive frame
> seen after 11 interlaced frames), but I don't get any "Disabling
> deinterlacing" messages. Are you switching to different channels and
> maybe showing a 720p station (ABC, Fox)? You can override the

I think that it might be something about WRAL, our local CBS
affiliate. One hour recordings from this channel have always shown up
as 52 minutes long on my Linux Myth box (and appear the same on
MacOSX).

> interlacing detection in the menu during playback.

This seems to work nicely!

Thank you!

Drew




_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 13, 2007, 12:15 PM

Post #11 of 19 (3564 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Andrew Kimpton [awk [at] awkward] wrote:
>
> Some of this may be different if you're using the CoreVideo output
> mechanism which I wrote some months ago but I don't think was ever
> committed - is it possible that Andrew G & Todd are not running the
> same videout device (CoreVideo vs. 'standard'). The reported refresh
> rates may be different between these two approaches (see para. 1 above).

I'm indeed running "standard".. I hope your patch gets in!

Drew
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 13, 2007, 4:30 PM

Post #12 of 19 (3567 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:

> > Also, I doubt the LCD is being run at 150Hz, where does Myth show
> > that? I think LCDs are set to 60Hz by default, although it's hard to
> > tell for sure. I installed SwitchResX control panel & output the DDC
> > data for the display, and it showed it was running 1440x900 @ 60Hz.
>
> It is reported (for me) when using -v playback:
> 2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]

Hmm,. I grep'd my log for that, and it is also returning150. So, I
looked in videoout_quartz.cpp, and it looks like 150 is the value it
uses if it doesn't get a valid refresh rate:

// Find the refresh rate of our screen
CFDictionaryRef m;
m = CGDisplayCurrentMode(data->screen);
data->refreshRate = get_float_CF(m, kCGDisplayRefreshRate);
if (data->refreshRate == 0.0) // LCD display?
data->refreshRate = 150.0; // Divisible by 25Hz and 30Hz
// to
minimise AV sync waiting


I'm not sure how that effects playback, but it seems to be the
expected behavior for LCDs, and playback is okay on mine. So, I would
guess this is not the issue.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 13, 2007, 4:36 PM

Post #13 of 19 (3552 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/13/07, Andrew Kimpton <awk [at] awkward> wrote:
> Quoting Todd Ignasiak <ignasiak [at] gmail>:
>
> > On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
>
> > Also, I doubt the LCD is being run at 150Hz, where does Myth show
> > that? I think LCDs are set to 60Hz by default, although it's hard to
> > tell for sure. I installed SwitchResX control panel & output the DDC
> > data for the display, and it showed it was running 1440x900 @ 60Hz.
>
> It's a very long time since I looked at it - but there is code in
> Myth's videoout 'portions' which attempts to get the refresh rate for
> the display but when that fails (there is no refresh rate for a
> digitally connected LCD Panel) defaults to 60Hz. If I recall there is
> a second place where this reported value is then multiplied by a
> constant (I thought 4 - but that doesn't make sense given the reported
> value of 150Hz).
>
> Some of this may be different if you're using the CoreVideo output
> mechanism which I wrote some months ago but I don't think was ever
> committed - is it possible that Andrew G & Todd are not running the
> same videout device (CoreVideo vs. 'standard'). The reported refresh
> rates may be different between these two approaches (see para. 1 above).

Hi Andrew,

I am using the standard code for this testing (latest SVN snapshot,
built via the osx-packager.pl script). I tried your Core Video patch
shortly after you submitted it, and it worked great for the most part.
I just had an issue with some "tearing" in the video output, so I
ended up going back to the standard quartz vo module.



Also -- I am using the AC3 passthrough, based on your patch, and that
works great. DD5.1 audio from broadcast HD, and DVDs via the internal
player.

> I apologize for the vagueness of the response - it's been some months
> since I looked at any of this Myth code.
>
> Andrew 8-)
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


awk at awkward

Mar 13, 2007, 5:26 PM

Post #14 of 19 (3558 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak wrote:
> On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
>
>
>>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
>>> that? I think LCDs are set to 60Hz by default, although it's hard to
>>> tell for sure. I installed SwitchResX control panel & output the DDC
>>> data for the display, and it showed it was running 1440x900 @ 60Hz.
>>>
>> It is reported (for me) when using -v playback:
>> 2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]
>>
>
> Hmm,. I grep'd my log for that, and it is also returning150. So, I
> looked in videoout_quartz.cpp, and it looks like 150 is the value it
> uses if it doesn't get a valid refresh rate:
>
> // Find the refresh rate of our screen
> CFDictionaryRef m;
> m = CGDisplayCurrentMode(data->screen);
> data->refreshRate = get_float_CF(m, kCGDisplayRefreshRate);
> if (data->refreshRate == 0.0) // LCD display?
> data->refreshRate = 150.0; // Divisible by 25Hz and 30Hz
> // to
> minimise AV sync waiting
>
>
> I'm not sure how that effects playback, but it seems to be the
> expected behavior for LCDs, and playback is okay on mine. So, I would
> guess this is not the issue.
>
I agree - it's not entirely clear what the intent of that 'magic value'
is. Remember though that this is only used when CoreGraphics doesn't
return a rate - and that only happens for devices such as notebooks and
the iMac which have an integral display panel with an entirely digital
connection between graphics adaptor and panel. For external LCD Displays
connected through a VGA connection kCGDisplayRefreshRate is 'spoofed' to
being 60 Hz.

I think (from dim memory of practical experiments) that changing that
150 value to 60 makes no difference - in fact it may make so little
difference that Andrew G's problems won't go away either. But it might
be worth a shot for someone to change it and repeat the build.

Andrew 8-)

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


awk at awkward

Mar 13, 2007, 5:33 PM

Post #15 of 19 (3561 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak wrote:
> On 3/13/07, Andrew Kimpton <awk [at] awkward> wrote:
>
>> Quoting Todd Ignasiak <ignasiak [at] gmail>:
>>
>>
>>> On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
>>>
>>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
>>> that? I think LCDs are set to 60Hz by default, although it's hard to
>>> tell for sure. I installed SwitchResX control panel & output the DDC
>>> data for the display, and it showed it was running 1440x900 @ 60Hz.
>>>
>> It's a very long time since I looked at it - but there is code in
>> Myth's videoout 'portions' which attempts to get the refresh rate for
>> the display but when that fails (there is no refresh rate for a
>> digitally connected LCD Panel) defaults to 60Hz. If I recall there is
>> a second place where this reported value is then multiplied by a
>> constant (I thought 4 - but that doesn't make sense given the reported
>> value of 150Hz).
>>
>> Some of this may be different if you're using the CoreVideo output
>> mechanism which I wrote some months ago but I don't think was ever
>> committed - is it possible that Andrew G & Todd are not running the
>> same videout device (CoreVideo vs. 'standard'). The reported refresh
>> rates may be different between these two approaches (see para. 1 above).
>>
>
> Hi Andrew,
>
>
> Also -- I am using the AC3 passthrough, based on your patch, and that
> works great. DD5.1 audio from broadcast HD, and DVDs via the internal
> player.
>
>
Todd - when you performed your comparitive analysis with Andrew G's
results were you using the AC3 pass through or a stereo analog connection ?

The two different audio output mechanisms have different clocking
methods for the audio and it may well be that there's a bug in the
analog implementation and that's what's causing Andrew G's issues.

Basically the video frame presentation rate is driven from the current
audio play position - if audio advances 'too fast' in relation to video
then video has to drop a frame or more to 'catch up'. Equally if audio
is 'behind' then video has to display the same frame twice in order to
let audio catch up.

There is an alternative approach to keeping things in sync involving
sample rate converting the audio on playback to an effective sample rate
that is not 44.1 (or 48 etc.) but more closely matches the relationship
between video frame display rate and audio hardware clock rate (ie
something a little less or a little more - and it can change over time).
There's some evidence in the Myth code that this has at least been
considered - but it can't be applied to any encoded audio format (like
AC3 or DTS) since there's no access to the raw underlying samples - if
you're going to support those types of audio encoding you have to 'slew'
the video to match the audio.

Andrew 8-)

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 13, 2007, 8:14 PM

Post #16 of 19 (3549 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/13/07, Andrew Kimpton <awk [at] awkward> wrote:
> Todd Ignasiak wrote:
> > On 3/13/07, Andrew Kimpton <awk [at] awkward> wrote:
> >
> >> Quoting Todd Ignasiak <ignasiak [at] gmail>:
> >>
> >>
> >>> On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> >>>
> >>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> >>> that? I think LCDs are set to 60Hz by default, although it's hard to
> >>> tell for sure. I installed SwitchResX control panel & output the DDC
> >>> data for the display, and it showed it was running 1440x900 @ 60Hz.
> >>>
> >> It's a very long time since I looked at it - but there is code in
> >> Myth's videoout 'portions' which attempts to get the refresh rate for
> >> the display but when that fails (there is no refresh rate for a
> >> digitally connected LCD Panel) defaults to 60Hz. If I recall there is
> >> a second place where this reported value is then multiplied by a
> >> constant (I thought 4 - but that doesn't make sense given the reported
> >> value of 150Hz).
> >>
> >> Some of this may be different if you're using the CoreVideo output
> >> mechanism which I wrote some months ago but I don't think was ever
> >> committed - is it possible that Andrew G & Todd are not running the
> >> same videout device (CoreVideo vs. 'standard'). The reported refresh
> >> rates may be different between these two approaches (see para. 1 above).
> >>
> >
> > Hi Andrew,
> >
> >
> > Also -- I am using the AC3 passthrough, based on your patch, and that
> > works great. DD5.1 audio from broadcast HD, and DVDs via the internal
> > player.
> >
> >
> Todd - when you performed your comparitive analysis with Andrew G's
> results were you using the AC3 pass through or a stereo analog connection ?

On my Mini, I am using only AC3 passthrough. But, on my MacBook Pro,
I just used the analog output.


There have been several reports of poor video playback when using high
resolution displays, like 1080p. This evening I dug out an old CRT
display to try higher resolutions and see if I could replicate the
problem.

I found that everything worked fine at 1600x1200, but when I switched
to 1920x1080p, the video became very choppy. So, it seems to be
related to the resolution being used.

> The two different audio output mechanisms have different clocking
> methods for the audio and it may well be that there's a bug in the
> analog implementation and that's what's causing Andrew G's issues.
>
> Basically the video frame presentation rate is driven from the current
> audio play position - if audio advances 'too fast' in relation to video
> then video has to drop a frame or more to 'catch up'. Equally if audio
> is 'behind' then video has to display the same frame twice in order to
> let audio catch up.
>
> There is an alternative approach to keeping things in sync involving
> sample rate converting the audio on playback to an effective sample rate
> that is not 44.1 (or 48 etc.) but more closely matches the relationship
> between video frame display rate and audio hardware clock rate (ie
> something a little less or a little more - and it can change over time).
> There's some evidence in the Myth code that this has at least been
> considered - but it can't be applied to any encoded audio format (like
> AC3 or DTS) since there's no access to the raw underlying samples - if
> you're going to support those types of audio encoding you have to 'slew'
> the video to match the audio.
>
> Andrew 8-)
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 15, 2007, 8:31 AM

Post #17 of 19 (3542 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Andrew Kimpton [awk [at] awkward] wrote:
> Todd Ignasiak wrote:
> > On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> >
> >
> >>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> >>> that? I think LCDs are set to 60Hz by default, although it's hard to
> >>> tell for sure. I installed SwitchResX control panel & output the DDC
> >>> data for the display, and it showed it was running 1440x900 @ 60Hz.
> >>>
> >> It is reported (for me) when using -v playback:
> >> 2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]
> >>
> >
> > Hmm,. I grep'd my log for that, and it is also returning150. So, I
> > looked in videoout_quartz.cpp, and it looks like 150 is the value it
> > uses if it doesn't get a valid refresh rate:
> >
> > // Find the refresh rate of our screen
> > CFDictionaryRef m;
> > m = CGDisplayCurrentMode(data->screen);
> > data->refreshRate = get_float_CF(m, kCGDisplayRefreshRate);
> > if (data->refreshRate == 0.0) // LCD display?
> > data->refreshRate = 150.0; // Divisible by 25Hz and 30Hz
> > // to
> > minimise AV sync waiting
> >
> >
> > I'm not sure how that effects playback, but it seems to be the
> > expected behavior for LCDs, and playback is okay on mine. So, I would
> > guess this is not the issue.
> >
> I agree - it's not entirely clear what the intent of that 'magic value'
> is. Remember though that this is only used when CoreGraphics doesn't
> return a rate - and that only happens for devices such as notebooks and
> the iMac which have an integral display panel with an entirely digital
> connection between graphics adaptor and panel. For external LCD Displays
> connected through a VGA connection kCGDisplayRefreshRate is 'spoofed' to
> being 60 Hz.
>
> I think (from dim memory of practical experiments) that changing that
> 150 value to 60 makes no difference - in fact it may make so little
> difference that Andrew G's problems won't go away either. But it might
> be worth a shot for someone to change it and repeat the build.
>

For what it is worth, I changed it from 150 to 60, and my problems
went away and I have smooth playback for 1080i. Perhaps 150 is
violating some other assumption which Myth is making?

Drew




_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


ignasiak at gmail

Mar 15, 2007, 10:26 AM

Post #18 of 19 (3540 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

On 3/15/07, Andrew Gallatin <gallatin [at] cs> wrote:
> Andrew Kimpton [awk [at] awkward] wrote:
> > Todd Ignasiak wrote:
> > > On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > >
> > >
> > >>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> > >>> that? I think LCDs are set to 60Hz by default, although it's hard to
> > >>> tell for sure. I installed SwitchResX control panel & output the DDC
> > >>> data for the display, and it showed it was running 1440x900 @ 60Hz.
> > >>>
> > >> It is reported (for me) when using -v playback:
> > >> 2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]
> > >>
> > >
> > > Hmm,. I grep'd my log for that, and it is also returning150. So, I
> > > looked in videoout_quartz.cpp, and it looks like 150 is the value it
> > > uses if it doesn't get a valid refresh rate:
> > >
> > > // Find the refresh rate of our screen
> > > CFDictionaryRef m;
> > > m = CGDisplayCurrentMode(data->screen);
> > > data->refreshRate = get_float_CF(m, kCGDisplayRefreshRate);
> > > if (data->refreshRate == 0.0) // LCD display?
> > > data->refreshRate = 150.0; // Divisible by 25Hz and 30Hz
> > > // to
> > > minimise AV sync waiting
> > >
> > >
> > > I'm not sure how that effects playback, but it seems to be the
> > > expected behavior for LCDs, and playback is okay on mine. So, I would
> > > guess this is not the issue.
> > >
> > I agree - it's not entirely clear what the intent of that 'magic value'
> > is. Remember though that this is only used when CoreGraphics doesn't
> > return a rate - and that only happens for devices such as notebooks and
> > the iMac which have an integral display panel with an entirely digital
> > connection between graphics adaptor and panel. For external LCD Displays
> > connected through a VGA connection kCGDisplayRefreshRate is 'spoofed' to
> > being 60 Hz.
> >
> > I think (from dim memory of practical experiments) that changing that
> > 150 value to 60 makes no difference - in fact it may make so little
> > difference that Andrew G's problems won't go away either. But it might
> > be worth a shot for someone to change it and repeat the build.
> >
>
> For what it is worth, I changed it from 150 to 60, and my problems
> went away and I have smooth playback for 1080i. Perhaps 150 is
> violating some other assumption which Myth is making?

So, now with the value set at 60, 1080i playback is smooth on your
iMac's internal display? And it doesn't require any interlace
detection override or other unusual setting?

I just want to make sure I'm understanding it.. If so, I'll try to
build a modified frontend and see if I can replicate what you're
seeing at 1080p.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


gallatin at cs

Mar 15, 2007, 1:48 PM

Post #19 of 19 (3535 views)
Permalink
Re: MacOSX frontend & 1080i [In reply to]

Todd Ignasiak [ignasiak [at] gmail] wrote:
> On 3/15/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > Andrew Kimpton [awk [at] awkward] wrote:
> > > Todd Ignasiak wrote:
> > > > On 3/13/07, Andrew Gallatin <gallatin [at] cs> wrote:
> > > >
> > > >
> > > >>> Also, I doubt the LCD is being run at 150Hz, where does Myth show
> > > >>> that? I think LCDs are set to 60Hz by default, although it's hard to
> > > >>> tell for sure. I installed SwitchResX control panel & output the DDC
> > > >>> data for the display, and it showed it was running 1440x900 @ 60Hz.
> > > >>>
> > > >> It is reported (for me) when using -v playback:
> > > >> 2007-03-12 09:52:04.014 VideoOutputQuartz::GetRefreshRate() [returning 150]
> > > >>
> > > >
> > > > Hmm,. I grep'd my log for that, and it is also returning150. So, I
> > > > looked in videoout_quartz.cpp, and it looks like 150 is the value it
> > > > uses if it doesn't get a valid refresh rate:
> > > >
> > > > // Find the refresh rate of our screen
> > > > CFDictionaryRef m;
> > > > m = CGDisplayCurrentMode(data->screen);
> > > > data->refreshRate = get_float_CF(m, kCGDisplayRefreshRate);
> > > > if (data->refreshRate == 0.0) // LCD display?
> > > > data->refreshRate = 150.0; // Divisible by 25Hz and 30Hz
> > > > // to
> > > > minimise AV sync waiting
> > > >
> > > >
> > > > I'm not sure how that effects playback, but it seems to be the
> > > > expected behavior for LCDs, and playback is okay on mine. So, I would
> > > > guess this is not the issue.
> > > >
> > > I agree - it's not entirely clear what the intent of that 'magic value'
> > > is. Remember though that this is only used when CoreGraphics doesn't
> > > return a rate - and that only happens for devices such as notebooks and
> > > the iMac which have an integral display panel with an entirely digital
> > > connection between graphics adaptor and panel. For external LCD Displays
> > > connected through a VGA connection kCGDisplayRefreshRate is 'spoofed' to
> > > being 60 Hz.
> > >
> > > I think (from dim memory of practical experiments) that changing that
> > > 150 value to 60 makes no difference - in fact it may make so little
> > > difference that Andrew G's problems won't go away either. But it might
> > > be worth a shot for someone to change it and repeat the build.
> > >
> >
> > For what it is worth, I changed it from 150 to 60, and my problems
> > went away and I have smooth playback for 1080i. Perhaps 150 is
> > violating some other assumption which Myth is making?
>
> So, now with the value set at 60, 1080i playback is smooth on your
> iMac's internal display? And it doesn't require any interlace
> detection override or other unusual setting?

Everything is as good now on the internal display as it was on the
external 1600x1200 LCD. It still requires manual interlace setting,
but this is normal for this station, and happens when I run my old,
pre-built binary on an external 1600x1200 lcd (which reports 60Hz).
When I use my Linux frontend, it says the same thing (I just never
noticed, because I had been running the Linux box at 1080i output w/o
any deinterlace enabled).

As I said before, there has always been something weird about this
station. Perfect 60 minute recordings always appear to Myth as being
52 minutes long. This is WRAL, which is a pioneer in HD, and was one
of the first HD stations in the country. They may be doing something
cutting edge, that Myth wouldn't see elsewhere.

Drew
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.