On Tue, 2007-05-22 at 23:27 +0100, Alasdair Campbell wrote:
On 21/04/07, Petri Hintukainen [EMAIL PROTECTED] wrote:
2) unscaled OSD: OSD and video are mixed by hardware using either
colorkeying (no opacity) or hardware RGBA layer. OSD and video can be of
different size and OSD can be
On 25/05/07, Petri Hintukainen [EMAIL PROTECTED] wrote:
Yes, patch against xine-lib 1.1.6 is available from
http://phivdr.dyndns.org/xine-lib/directfb/
Thanks so much for that!
I'll be able to try it over the weekend and I'll let you know how I get on.
many thanks
--
A l a s d a i r C a m
On Sunday 22 April 2007 22:47:40 Petri Hintukainen wrote:
Well, this changes are more than 7 month old, maybe there have been some
changes to DirectFB to make it work in the meanwhile... As far as I saw
it's only a two line patch, so I could try to manually revert it and
compile xine-lib
On 21/04/07, Petri Hintukainen [EMAIL PROTECTED] wrote:
On Fri, 2007-04-20 at 19:21 +0100, Alasdair Campbell wrote:
I'll have a look at the softdevice src this weekend compare with
xineliboutput.
Better to compare with xine-lib (src/video_out/video_out_directfb.c), as
there's not even
On 21/04/07, Markus Schuster [EMAIL PROTECTED] wrote:
Well, this changes are more than 7 month old, maybe there have been some
changes to DirectFB to make it work in the meanwhile... As far as I saw it's
only a two line patch, so I could try to manually revert it and compile
xine-lib again...
On Sat, 2007-04-21 at 23:30 +0200, Markus Schuster wrote:
(Well, another possibility would be upscaling video in
software).
Does upscaling really have to be done in software? Excuse my (maybe?) stupid
question but as far as I know video scaling can be done by a backend scaler
in
On 20 Apr 2007, at 19:21, Alasdair Campbell wrote:
I'll have a look at the softdevice src this weekend compare with
xineliboutput.
Why aren't you just using softdevice?
--
Torgeir Veimo
[EMAIL PROTECTED]
___
vdr mailing list
vdr@linuxtv.org
On 21 Apr 2007, at 11:37, Torgeir Veimo wrote:
On 20 Apr 2007, at 19:21, Alasdair Campbell wrote:
I'll have a look at the softdevice src this weekend compare with
xineliboutput.
Why aren't you just using softdevice?
Ignore my question, I hadn't read the full thread.. Saturday morning
On 21/04/07, Tony Houghton [EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED], Alasdair Campbell wrote:
Because I'm using a 550Mhz P3, my only option is to use the
xineliboutput until I figure out what is causing the big CPU load
variations. As I've never had softdevice successfully running on
On 21/04/07, Petri Hintukainen [EMAIL PROTECTED] wrote:
On Fri, 2007-04-20 at 19:21 +0100, Alasdair Campbell wrote:
I'll have a look at the softdevice src this weekend compare with
xineliboutput.
Better to compare with xine-lib (src/video_out/video_out_directfb.c), as
there's not even
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
On 19/04/07, Torgeir Veimo [EMAIL PROTECTED] wrote:
On 19 Apr 2007, at 09:41, Alasdair Campbell wrote:
In the original post I was just wondering if xineliboutput has been
written with the matrox specific instructions that softdevice's -vo
dfb:mgatv uses. As I don't understand the
On Thu, 2007-04-19 at 12:53 +0100, Alasdair Campbell wrote:
Using df_xine -a 5:4 -l 0 -s -f top 001.vdr
I get perfect output! This is what Markus and I are seeing for a few
seconds before the field sync gets screwed
With df_xine -a 5:4 -l 0 -s -f bottom 001.vdr
The output is constantly
Sorry for replying to myself, but in the meantime, while waiting for
xineliboutput to work again, anyone reading know if I can use df_xine
for the video display, while retaining xineliboutput as the lirc
transport to my headless server running vdr-xineliboutput.
** I know there has been a
On Thu, 2007-04-19 at 13:54 +0100, Alasdair Campbell wrote:
Sorry for replying to myself, but in the meantime, while waiting for
xineliboutput to work again, anyone reading know if I can use df_xine
for the video display, while retaining xineliboutput as the lirc
transport to my headless
ignore that, I was being an idiot, set to 'top' now.
--
A l a s d a i r C a m p b e l l
r a g a w u @ g m a i l . c o m
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Am Donnerstag, 19. April 2007 10:41:01 schrieb Alasdair Campbell:
If you make any progress please let me know!
I'll do! But I hope we both get a pointer in the correct direction here!
What sort of hardware do you have?
Here it's an old P4 with 2.0 GHz. It's at 40-50% with softdevice, so
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 config option per
default...
But I can insert it and
Can vdr-xineliboutput utilize the excellent interlaced output of a
Matrox G450 with VGASCART cable?
I'm asking myself the same question. I've played arround with xineliboutput
and softdevice the last days and came across the same issues you reported.
I'm seeing what I can only describe as
22 matches
Mail list logo
