On Dienstag, 8. Februar 2005 20:46, Tony Houghton wrote:
> In <[EMAIL PROTECTED]>, Stefan Lucke wrote:
> 
> > Back to the  list (the right one ?):
> 
> It's mostly on-topic, but I may want to bring up some related points
> that are related to VDR and not DirectFB.
> 
> > On Sonntag, 6. Februar 2005 21:12, Tony Houghton wrote:
> > > 
> > > Unfortunately I'm only getting a blank white screen - with black bars
> > > top and bottom, because the 16:9 option only works if I select it
> > > manually at start-up, but that problem is lower priority ATM! VDR is
> > > working correctly in the background, I can hear the sound and change
> > > channels. When the OSD comes up I can see a white area overlapping the
> > > border in the shape of the proper OSD. I remember seeing this white
> > > screen phenomenon before, but I can't remember why or what I did to stop
> > > it.
> > 
> > That previous diff failed the test on my vdr-1.2.1 G400 system too, got
> > a flickering green image via s-video. But time goes on and this next one
> > works with:
> >
> > a) vdr-1.3.18, DirectFB cvs from 2005-02-05, G550, composite out +
> > monitor, P4 2.2G
> > b) vdr-1.2.1, DirectFB 0.9.20, G400, s-video out, P3 Celeron 1.2G
> 
> c) vdr-1.3.19, DirectFB 0.9.21, G450, S-Video, P3 Celeron 1.2GHz.
> 
> :-)

OK, I commited the diff to cvs.

> 
> > To be honest, on system "b" viewing is unacceptable. When OSD kicks in,
> > video seems to be slow motion. Without OSD there is a jitter/flicker
> > every now and then. CPU load at that time was about 50%.
> > 
> > That has to be resolved too, next step(s). I'm wondering why these
> > effects are not noticable on system "a".
> 

So now we get OT for this list and should continue on softdevice-devel.
https://lists.berlios.de/mailman/listinfo/softdevice-devel

> It works quite smoothly for me with the same CPU as your (b), so I
> suspect it's due more to the outdated VDR or (more likely) DirectFB than
> CPU power. VDR 1.2 may be worth supporting until 1.3 becomes 1.4 stable
> release, but I think you should try upgrading from DirectFB 0.9.20 to
> .21 before worrying.
> 
> I do have some issues though, I'm afraid:
> 
> (a) A/V sync is a bit of a problem. It's probably mostly my fault for
> buying a sound card that cost only about �5 new and may therefore have a
> dodgy clock, but without any guarantee that a more expensive card would
> fix the problem I'd rather see a software workaround of dynamic
> resampling. I'm willing to do most of the work on this myself, but I
> think I might need lots of help from you, explaining the stages the
> sound goes through as it's decoded and buffered etc.
> 
> (b) Sometimes when starting VDR after using MPlayer I get the blank
> white screen problem again and I can't make it work properly until I
> reboot.
> 
> (c) I can't use VDR's mplayer plugin for two reasons. One is that
> softdevice appears to be leaving the sound card tied up, so mplayer
> can't play sound. The other is that when returning to VDR it either
> plays a couple of seconds of sound with a black screen, then locks up
> with lots of ringbuffer errors in the log, or produces a garbled screen
> in garish colours with only room for about half the OSD. When I used to
> use th DXR3 plugin, starting the mplayer plugin would pop up a message
> about releasing DXR3 devices, so I guess something similar is needed for
> softdevice to make it fully shut down and reinitialise.
> 


-- 
Stefan Lucke



Reply via email to