Hello All,
Today I finished the patch for DVB-S, DVB-S2, DVB-T and DVB-C support using
S2API in combination with VDR 1.7.0. I've tested my code on DVB-S, DVB-S2 and
DVB-T transports and they were all successful. DVB-C is untested (don't have a
DVB-C option where I live) but it should work in *T
Great work,
attached you find two patches, the one against 1.7.1 + extensions 64 patch
and the tuning fix patch.
The situation with the tunig fix is funny. Yesterday in Steve Toth's hg
repository there where the patches from http://dev.kewl.org/v4l-dvb/patches/
included. Today they seems to be gon
> attached you find two patches, the one against 1.7.1 + extensions 64 patch
have you some advantages with vdr 171 than with vdr 170 ?
> and the tuning fix patch.
does this patch from Darron ?
http://dev.kewl.org/v4l-dvb/patches/
> The situation with the tunig fix is funny. Yesterday in Steve
Zitat von ShorTie:
> Trying to rebuild my gentoo system using the latest DirectFB, DFB++ and
> ffmpeg.
>
> Everytime I try to ./configure softdevice.cvs I get
>
>
>
> BudgetVDR softdevice.cvs # ./configure --disable-vidix --disable-xv
> --with-ffmpeg-path /usr/local/src/ffmpeg
>
> ffmpeg path set
Today I announced this version in the german vdrportal forum. The last time I
announced a new pvr350 plugin-version here in the ML was June 2007. So it is
time to write here again to keep the non-german-speaking users informed.
The pvr350-plugin implements an output device for the PVR350 TV out
These are the cvs/svn versions of DirectFB and ffmpeg.
And yes I did do a 'make install' after compiling each.
Tried
./configure --disable-vidix --disable-xv --with-ffmpeg-path /usr/local
As well as
./configure --disable-vidix --disable-xv --with-ffmpeg-path /usr
Both with the same error.
As fa
The pvrinput plugin uses a Hauppauge PVR card as an input device. All cards
supported by the ivtv or pvrusb2 driver should work. (Tested with PVR150,
PVR250, PVR350, PVR500, PVRUSB2).
Winfried Koehler and I work on this plugin since the original maintainer
stopped development in 2006. As far as
I asked in other way
is there any fast method (without demux) for converting the h264 pes records
from vdr to any other containers - ts, avi ?
> I use the solution here :
>
> http://www.vdrportal.de/board/thread.php?threadid=73791
>
> You can use mpeg_ps_extract to transform the vdr file in
http://lwn.net/Articles/299483/
is it possible in the future to implement this patches for vdr distros ?
Goga
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
I've published version 0.1.2 of the OSDServer plugin.
The new version fixes a bug on VDR 1.5.11+ on text edit items.
The new version also adds a new Perl binding module that encapsulates
the OSDServer network protocol within Perl objects. By using the Perl
module, OSDServer is a lot easier
Goga777 wrote:
> I asked in other way
>
> is there any fast method (without demux) for converting the h264 pes records
> from vdr to any other containers - ts, avi ?
if you ask that way - imho - NO
demuxing is the minimum when comming from pes and want to convert to ts
remuxing is a very fast
Uwe Kiewel ha scritto:
> cc -O3 -pipe -Wall -fPIC -g -I/usr/local/include-c -D_GNU_SOURCE
> -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.2"'
> -DHAVE_XRENDER=1 -DHAVE_XDPMS=1 -DHAVE_XINERAMA=1 -DHAVE_EXTRACTOR_H=1
>
Uwe Kiewel ha scritto:
> cc -O3 -pipe -Wall -fPIC -g -I/usr/local/include-c -D_GNU_SOURCE
> -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.2"'
> -DHAVE_XRENDER=1 -DHAVE_XDPMS=1 -DHAVE_XINERAMA=1 -DHAVE_EXTRACTOR_H=1
>
Uwe Kiewel ha scritto:
> cc -O3 -pipe -Wall -fPIC -g -I/usr/local/include-c -D_GNU_SOURCE
> -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.2"'
> -DHAVE_XRENDER=1 -DHAVE_XDPMS=1 -DHAVE_XINERAMA=1 -DHAVE_EXTRACTOR_H=1
>
14 matches
Mail list logo
