Hi!
Yes there are some VDR-Skin-Plugins around. For example mine at
http://andreas.vdr-developer.org/enigmang
What output device do you use?
You should be aware that e.g. Full-Featured DVB-S cards have limited OSD
capabilities (~90kb). So hires hi-color OSD will be a problem here.
Regards,
Hi!
Yes there are some VDR-Skin-Plugins around. For example mine at
http://andreas.vdr-developer.org/enigmang
What output device do you use?
You should be aware that e.g. Full-Featured DVB-S cards have limited OSD
capabilities (~90kb). So hires hi-color OSD will be a problem here.
On 20/04/07, Markus Schuster [EMAIL PROTECTED] wrote:
Am Donnerstag, 19. April 2007 15:06:54 schrieb Alasdair Campbell:
config_xineliboutput
# field parity
# { none top bottom }, default: 0
#video.device.directfb_field_parity:none
That's funny, my config_xineliboutput doesn't have this
On Friday 20 April 2007 20:50:16 Alasdair Campbell wrote:
My experiences with a 16:9 TV are different but theres some issues
with scaling OSD that I would like to fix..
Maybe it's just a config-problem, at least it's a bit non-intuitive :)
I noticed that any scaling of the OSD results in
In [EMAIL PROTECTED], Alasdair Campbell wrote:
On 20/04/07, Markus Schuster [EMAIL PROTECTED] wrote:
BUT I have to admit that xineliboutput uses only half of the CPU power of
softdevice, so it's video decoder has to be more efficient...
Odd, because xine also uses ffmpeg. Perhaps it has a
On Fri, 2007-04-20 at 03:27 +0200, Markus Schuster wrote:
With Bloomberg (German news/stock channel) I see a very odd behavior: To have
to video itself fullscreen, I have to enable local frontend scaling but then
the OSD is renderd much too big. So I have to enable OSD resizing/downscaling
