Re: [mythtv-users] Re: Need advice with 'Pixelization
Well, I feel like a total idiot :) I went throught the list of deinterlace filters, trying them one by one, and discovered that Bob 2x DOES work for me. Hmmm. Why is that, you ask? Well, I discovered that the playback settings are not applied unless I click 'next' and step through ALL the screens. I think this may have caused me to misdiagnose my config settings first time around. It sure would be nice if myth warned that changes are not applied unless all the menus are acknowledged. Maybe there should be an apply button on each screen that allows pending changes to be committed? Larry On 4/16/05, Will Dormann [EMAIL PROTECTED] wrote: Jeff Wormsley wrote: Will Dormann wrote: I think this is the worst method for video timing.(i.e. least-smooth)RTC would be better than that, and OpenGL better than RTC. Sorry to butt in. How do you change this?Nothing I have set has ever changed it. Sometimes I see other things being tried, but they always fail and its right back to where I started. If you compile MythTV with OpenGL VSYNC support, it will use it as longas your video card driver supports it. I believe it will fall back toRTC, assuming your kernel provides enhanced RTC support.If you use RTC, make sure the frequency is set to 1024:http://lists.debian.org/debian-powerpc/2003/05/msg00586.html---WD___ mythtv-users mailing listmythtv-users@mythtv.orghttp://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Well, it sure appears as though I spoke prematurely. When I enable deinterlacing (Bob 2x), my system becomes unstable. I am mostly unsuccessful with the other options as well (XvMC h/w decoding, libmpeg2). I also tried realtime priority, but I have not done the suid root thingy, so the log indicates that option was rejected. Below is a snippet of my mythfrontend log. Perhaps Jarod or others who use the mythtv-suite distro can weigh in regarding what deinterlacing methods are available? My video quality is not great without deinterlacing, but looks wonderful with deinterlacing...until it crashes and burns :) Thanks, Larry 2005-04-15 21:34:34.675 mythfrontend version: 0.17.20050130-1 www.mythtv.org 2005-04-15 21:34:34.675 Enabled verbose msgs : important general 2005-04-15 21:34:34.748 mythfrontend version: 0.17.20050130-1 www.mythtv.org 2005-04-15 21:34:34.748 Enabled verbose msgs : important general 2005-04-15 21:34:35.236 Switching to square mode (blue) 2005-04-15 21:34:35.363 Switching to square mode (blue) 2005-04-15 21:34:36.106 Joystick disabled. 2005-04-15 21:34:36.152 Registering Internal as a media playback plugin. 2005-04-15 21:34:36.294 Registering MythDVD DVD Media Handler as a media handler 2005-04-15 21:34:36.294 Registering MythDVD VCD Media Handler as a media handler 2005-04-15 21:34:36.390 Joystick disabled. 2005-04-15 21:34:36.413 Registering Internal as a media playback plugin. 2005-04-15 21:34:36.423 Registering MythDVD DVD Media Handler as a media handler 2005-04-15 21:34:36.423 Registering MythDVD VCD Media Handler as a media handler 2005-04-15 21:34:36.634 Registering MythMusic Media Handler as a media handler SIP listening on IP Address 192.168.1.101:5060 NAT address 192.168.1.101 2005-04-15 21:34:37.536 Registering MythMusic Media Handler as a media handler SIP listening on IP Address :5060 NAT address SIP: Cannot register; proxy, username or password not set Destroying SipFsm object 2005-04-15 21:34:52.321 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) SIP: Cannot register; proxy, username or password not set 2005-04-15 21:34:52.321 Connecting to backend server: 127.0.0.1:6543 (try 1 of 5) 2005-04-15 21:34:52.329 Using protocol version 14 2005-04-15 21:34:52.332 Using protocol version 14 2005-04-15 21:34:52.392 Using protocol version 14 2005-04-15 21:34:52.412 Using protocol version 14 2005-04-15 21:34:54.510 Opening audio device '/dev/dsp'. 2005-04-15 21:34:54.510 Opening OSS audio device '/dev/dsp'. 2005-04-15 21:34:54.521 Using XV port 105 2005-04-15 21:34:54.785 Realtime priority would require SUID as root. 2005-04-15 21:34:54.808 Changing from None to WatchingLiveTV 2005-04-15 21:34:54.897 Video timing method: USleep with busy wait 2005-04-15 21:34:57.572 taking too long to be allowed to read.. 2005-04-15 21:35:02.567 RemoteFile::Read() failed in RingBuffer::safe_read(). 2005-04-15 21:35:02.573 taking too long to be allowed to read.. 2005-04-15 21:35:04.788 Waited 2 seconds for data to become available, waiting again... 2005-04-15 21:35:05.965 prebuffering pause 2005-04-15 21:35:06.789 Waited 2 seconds for data to become available, waiting again... 2005-04-15 21:35:08.790 Waited 2 seconds for data to become available, waiting again... 2005-04-15 21:35:10.792 Waited 2 seconds for data to become available, waiting again... 2005-04-15 21:35:12.788 RemoteFile::Read() failed in RingBuffer::safe_read(). 2005-04-15 21:35:12.794 Waited 2 seconds for data to become available, waiting again... 2005-04-15 21:35:12.812 Changing from WatchingLiveTV to None --More--(65%) On 4/15/05, Larry K [EMAIL PROTECTED] wrote: OK, I went into mythfrontend - Settings - TV settings - Playback, and added the Bob 2x Deinterlace option, as well as the Use video as Timebase option. This seemed to correct the artifacts that I was seeing, both in live TV, and in peviously recorded material. Based ont his, can I assume that the artifacts were there becasue of the way the encoded video was being decoded for display? As opposed to it being a flaw in the way the PVR-250 was encoding the video in the first place? I went on to experiment further with the XvMC hardware decoding, and that seemed to introduce stutter. I noticed that the CPU consumption of mythfrontend dropped by 50% when I did this. Based on this, I assume that when this box is not checked, myth is doing XvMC software decoding instead? So, one way or the other, XvMC decoding is being done? I did not try libmpeg2 or XV. I gather that XV and XvMC are mutually exclusive options. Is that correct? And what about libmpeg2? Is that to be used in combination with either XV or XvMC? I guess at some point, it will become increasingly difficult to discern any improvement, as the picture quality gets closer to nirvana.On 4/14/05, Will Dormann [EMAIL PROTECTED] wrote: Larry K wrote: I'll bet that's my problem, then.FWIW, my recordings are 2.2GB/hour, which seems pretty reasonable. I'll try the Bob Deinterlacing when I get home.Thanks!This
Re: [mythtv-users] Re: Need advice with 'Pixelization
Larry K wrote: 2005-04-15 21:34:54.897 Video timing method: USleep with busy wait I think this is the worst method for video timing. (i.e. least-smooth) RTC would be better than that, and OpenGL better than RTC.It shouldn't be unstable, though, whatever you mean by that... Try the other deinterlacing options to see what works well. Though without bob, you won't have the smoothest video. -- -WD ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Will Dormann wrote: I think this is the worst method for video timing. (i.e. least-smooth) RTC would be better than that, and OpenGL better than RTC. Sorry to butt in. How do you change this? Nothing I have set has ever changed it. Sometimes I see other things being tried, but they always fail and its right back to where I started. Jeff. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Jeff Wormsley wrote: Will Dormann wrote: I think this is the worst method for video timing. (i.e. least-smooth) RTC would be better than that, and OpenGL better than RTC. Sorry to butt in. How do you change this? Nothing I have set has ever changed it. Sometimes I see other things being tried, but they always fail and its right back to where I started. If you compile MythTV with OpenGL VSYNC support, it will use it as long as your video card driver supports it. I believe it will fall back to RTC, assuming your kernel provides enhanced RTC support. If you use RTC, make sure the frequency is set to 1024: http://lists.debian.org/debian-powerpc/2003/05/msg00586.html -- -WD ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Artifacts! That's the word I was looking for. That's what I'm seeing, no doubt. I am watching myth on a 27 TV (soon to be 32 TV) fed by s-video from my AGP geforce4 mx440 128MB card. When I get home, I'll check the bit rate I'm using, but it's most certainly the default (does anyone remember the default bitrate?). Also, do I need to set the deinterlace thingy for TV playback, or does that apply to a computer monitor only? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Joe Votour wrote: I see the same pixelization, and I'm capturing at 720x480, with a bitrate between 5000 and 6500. snip In my case though, the cable TV coax coming into my apartment is pretty crappy The input quality probably makes a big difference. I'm capturing at the same resolution, but about half the bitrate. My input is digital cable, and the final result is really no worse than if the digital cable box were plugged directly into the TV. -WD ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
Larry K wrote: remember the default bitrate?). Also, do I need to set the deinterlace thingy for TV playback, or does that apply to a computer monitor only? You absolutely need to deinterlace. Otherwise, motion scenes will not look right. Check out http://www.100fps.com I recommend Bob Deinterlacing for the smoothest motion. -D ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: Need advice with 'Pixelization
I see the same pixelization, and I'm capturing at 720x480, with a bitrate between 5000 and 6500. I'm inclined to believe that it's the MPEG-2 generated by the PVR-250 that is the cause, but my knowledge of MPEG-2 isn't enough for me to even begin to offer an explanation. The only thing that I can think of is that there's so much movement (or change) in the scene, that the delta frame (I forget what letter it is called, but it's definitely not the I-frame) ends up with the blockiness. In my case though, the cable TV coax coming into my apartment is pretty crappy (there's ingress according to the Comcast tech, but it's my landlord responsible for the line, not Comcast, so I have to live with it). I haven't brought the RF analyzer home from work yet, but I know that my signal is around 30dBmV, which is on the crap side. I get some artifacts in MythTV, and occasionally, if I watch something on the TV (not in Myth), I end up with a staticy (is that even a word?) picture, or wavy lines in it. I also get the odd dropped frame. I attribute the blockiness to these factors (in my case, anyway). -- Joe --- Ian Trider [EMAIL PROTECTED] wrote: AFAIK, the MythTV defaults for bitrate are way too low. You need (if recording at 480x480) roughly 5000kbit/s for a good image. Also, you might be seeing interlacing artefacts if you are playing back on a computer monitor/standard video card graphics out and aren't deinterlacing -- make sure Deinterlace playback is enabled in the settings. On 4/13/05, Larry K [EMAIL PROTECTED] wrote: Let me add that I am not doing HD, and I am taking all the mythtv defaults for bitrates, etc. On 4/13/05, Larry K [EMAIL PROTECTED] wrote: I'm somewhat perplexed, so I figured I'd post here and see if anyone has solved this issue already. A search of the database does not produce anything that looks like what I am seeing. In brief, I have the following system: Athlon 2500 256MB RAM 160GB DMA HD PVR-250 I have only had the system working for about a week, but already I notice that when I watch live TV, or play back a recording, I notice areas of what I call pixelization where there is sudden or significant movement in the image. The image does not stutter or act jerky, to the extent that the entire image does not seem affected by this issue. The problem appears in isolated areas, and then as the motion in that ares of the image subsides, the pixelization subsides as well. If I had to guess, it's almost as if the PVR could not encode the movement sufficiently to make it appear smooth during playback. Does anyone have any thoughts as to what might cause this? Thanks, Larry ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- Ian Trider [EMAIL PROTECTED] ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
