From: Darren S. <li...@yo...> - 2005-04-26 18:46:36
|
I demand that Miguel Freitas may or may not have written... > On 4/20/05, Darren Salt <li...@yo...> wrote: >> For configuration reasons, gxine (CVS HEAD) may have multiple copies of >> various plugins around. This doesn't always work as intended, such as when >> you're currently using the pp deinterlacer and you want to switch to >> tvtime - one instance is created for configuration purposes then, when the >> changes are applied, a second instance is created (it's not yet time to >> destroy the first) but it doesn't actually do anything to the video >> stream. > [...] there is a further interaction you should consider: previously the > deinterlacing feature was enabled/disabled using XINE_PARAM_VO_DEINTERLACE. > this property is still used by tvtime to inform the video_out plugin > whether it should perform deinterlacing (for example, using hardware > support) or not. Not good... are there any objections to this being removed in 1.1? > cascading multiple tvtime instances might cause the first one to disable > the second using XINE_PARAM_VO_DEINTERLACE (just like if it were disabling > the vo hardware deinterlacer). therefore, when you remove the first > instance you might end with just a disabled tvtime instance. you can check > this by inspecting the "enabled" parameter. I saw enabled=0... :-| XINE_PARAM_VO_DEINTERLACE is now enabled if deinterlacing is enabled. It was previously also required that no plugins were enabled in the deinterlacer chain. -- | Darren Salt | nr. Ashington, | d youmustbejoking,demon,co,uk | Debian, | Northumberland | s zap,tartarus,org | RISC OS | Toon Army | @ | You too can roll your own kernel... asleep%=FALSE:sleep%=0:REPEAT sleep%+=1:UNTIL asleep% |