Yes, Myth has an odd bug there, it sets the vbi-insertion on variable to
the vbi passthrough value (which it happens not to set).  So seems that
causes it to choose the wrong type of insertion,should be '1' and 
then should set passthrough mode to 4 or whatever tv standard is being
decoded to the VBI output. 

I fixed this right after my email and re-uploaded, but it may still
get triggered on PAL systems I suspect since they may have passthrough
modes less than 4, so triggers different insertion types.  It's a 
nasty little bug there in Myth because we need to use the insertion
variable, used to only be 0/1 for off/on, to do other types of insertion,
yet it's confused that with the passthrough mode (which also needs to
be set by the application and isn't, I now can see why Myth isn't
setting that, because it thought the insertion ioctl variable was for that).

I'm trying to think of some way to work around it for now, but really
points to a bug which puts a burdon on us for setting up vbi insertion mode
and making it logical to switch modes to other types.


Thanks,
Chris

On Tue, May 17, 2005 at 08:59:15PM +0200, Patrick @ Mythtv wrote:
> Chris, 
> 
> This version gave me slow images and blocks in the screen and after 15-20
> sec. a black screen. Changing channels did not solved this. Back to 0.3.4.s
> for me 
> 
> In the 0.3.4s version i've noticed that changing channels has been slowed
> down.
> 
> 
> 
> > -----Oorspronkelijk bericht-----
> > Van: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] Namens Chris Kennedy
> > Verzonden: dinsdag 17 mei 2005 10:40
> > Aan: [email protected]
> > Onderwerp: [ivtv-devel] #0.3.4u vbi insertion and display improvements
> > 
> > This makes vbi output to the saa7127 yet more correct, and 
> > may help timing and vsync things like YUV decoder output too.
> > 
> > Please test the VBI and report the results, also I have setup 
> > two modes of embedding more than before, 2 gets insertion of 
> > User Data packets, and
> > 3 gets private packets, done by the firmware.  The User Data 
> > packets don't disrupt the video but are not able to be 
> > decoded yet, while the private packets corrupt the mpeg video 
> > badly.  This is there to further that development since the 
> > way we do vbi re-insertion requires parsing just about every 
> > byte of the mpeg stream (hence the jittery video when using 
> > Myth for some, it's CPU intensive and just inefficient, but 
> > best way we can for now).
> > 
> > 
> > #0.3.4u: http://www.ivtv.tv/data/releases/ivtv-0.3/
> > 
> > 
> > Thanks,
> > Chris
> > --
> > ---
> >  Chris Kennedy / [EMAIL PROTECTED]
> >   Engineer KMOS-TV/KTBG-FM
> >   Broadcasting Services Department
> >   Central Missouri State University
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Oracle Space Sweepstakes
> > Want to be the first software developer in space?
> > Enter now for the Oracle Space Sweepstakes!
> > http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/ivtv-devel
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel

-- 
---
 Chris Kennedy / [EMAIL PROTECTED]
  Engineer KMOS-TV/KTBG-FM
  Broadcasting Services Department
  Central Missouri State University


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to