Hi,
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Excerpt from HISTORY:
2009-01-12: Version 0.9.0
- Updated INSTALL and MANUAL accordingly. - Fixed several multithreading issues which got triggered on SMP systems (thanks to Edgar (gimli) Hucek for reporting issues and testing fixes). - Added support for VDR-1.7.3 besides TS still pictures. - Pulled patched VDR-1.7.2's remux.[ch] for a quick adaption to to VDR-1.7.3 (thanks to Klaus Schmidinger for his approval). - Fixed PTS handling in xine-lib's FFmpeg decoder for recent FFmpeg versions which should provide better A/V sync now. - Added patch sets to input_vdr.c which allow to omit parts of the MRL, e. g. vdr:// should be sufficient now (thanks to Ludwig Nussel for providing them). - Make use of new OSD functionality in xine-lib-1.2. For now an OSD implementation must provide both new features to have vdr-xine make use of it. - Extended OSD support in xine-lib-1.2 to allow truecolor OSDs as well as hardware scaled OSDs. The new functionality is currently only provided by VDPAU enabled installations. - Added frame grabbing support for accelerated frame formats to xine-lib. Previously, xine-lib exitted the app when frame grabbing was requested for accelerated frame formats like xxmc. You'll now get a green image in that case. Reading back the content of an accelerated frame is currently only provided by VDPAU enabled installations. - Hacked support for VDR-1.7.1's new cDevice::PlayTs() method. - Grab image nolonger needs pnmcut to select the relevant area of the TV image. Besides that, grab image respects the aspect ratio you select in VDR's setup menu, i. e. a 16:9 setup and a 16:9 broadcast will grab you a image without black borders. A mismatch of aspect ratios will add black borders to the image to match the visual impression you get on your TV set. Additionally, the grabbing of field pictures was corrected with regard to color upsampling. - A script mkNoSignal.sh is provided to create custom logos. Just provide PNG files named noSignal16x9*.png (and ...4x3... respectively) and have the tools mentioned in INSTALL in your path. You'll have to move your custom logos then over the default files. - The vdr-xine logo is now available in two aspect ratios (4:3 and 16:9) as more channels provide 16:9 content. Then vdr-xine selects the logo which matches VDR's DVB setup option video format. - Added the ability to detect discontinuities in live TV and to start a new buffering period in such a case. This will help to resume to fluent playback from bad weather conditions or when disconnecting and reattaching the antenna cable. - Updated it_IT.po (thanks to Diego Pierotto for providing the translations).
Enjoy.
Hi.
after being away 7 month from VDR development
Have a nice new year and welcome back! :)
I'm pleased to announce release 0.9.0.
I guess it's >= 1.7.3 only because I gave it a quick whirl with vdr 1.7.2 and all I got were lot's of errors like:
Jan 13 09:48:25 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:26 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:27 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:28 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:29 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:30 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:31 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:32 vdr: [15268] ERROR: TS packet not accepted in Transfer Mode Jan 13 09:48:32 vdr: [15269] ERROR: driver buffer overflow on device
As vdr 1.7.3 is not yet ready for general consumption :) I guess I'll have to stay with vdr 1.7.1 and xineliboutput for the time being even though I really would like to get HD up and running once and for all. Actually it is a pity that no software output device solution gets added to vdr itself because that would usually mean it just works, no matter what vdr version one tries... :-(
Thanks for your great work, btw!
Best regards, matthias.
Hi,
Matthias Dahl schrieb:
I guess it's >= 1.7.3 only because I gave it a quick whirl with vdr 1.7.2 and all I got were lot's of errors like:
Well, vdr-xine-0.9.0 should be compatible till VDR-1.2.x. But VDR-1.7.1 and 1.7.2 miss an adapted APIVERSNUM so vdr-xine-0.9.0 assumes that there is no PlayTS().
Please change APIVERSNUM to 10701 in VDR's config.h
Bye.
Reinhard Nissl schrieb:
Hi,
Well, vdr-xine-0.9.0 should be compatible till VDR-1.2.x.
Hi, I tried with vdr-1.6.0.2 and got messages "trying to connect" or so, but never a connect. I used the added xine-lib (+ patch) and -ui under Suse 11.1. vdr-xine-0.8.2 works well. As I have no X I use fbxine. Joerg
Hi,
Joerg Riechardt schrieb:
I tried with vdr-1.6.0.2 and got messages "trying to connect" or so, but never a connect. I used the added xine-lib (+ patch) and -ui under Suse 11.1. vdr-xine-0.8.2 works well. As I have no X I use fbxine.
Couldn't reproduce this issue. fbxine worked with vdr-1.7.3 and xine-ui with 1.6.0.
Thought of an issue (deadlock) with 1.6.0 but discovered later that 1.7.3 was running at the same time, using the same fifos.
Bye.
Date: Mon, 12 Jan 2009 23:43:33 +0100 From: rnissl@gmx.de To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Hi,
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Welcome back - many people will be pleased about you beeing back to vdr! :)
Excerpt from HISTORY:
2009-01-12: Version 0.9.0
[..]
- Make use of new OSD functionality in xine-lib-1.2. For now an OSD implementation must provide both new features to have vdr-xine make use of it.
- Extended OSD support in xine-lib-1.2 to allow truecolor OSDs as well as hardware scaled OSDs. The new functionality is currently only provided by VDPAU enabled installations.
Maybe a little bit OT, but i'm having a problem with compiling the latest xine-lib-1.2 HG. Earlier versions (last tested with xine-lib-1.2 from 2008-08-18) didn't show this effect. I'm compiling the libs as you suggested in this post: http://www.linuxtv.org/pipermail/vdr/2008-March/016195.html . Before i patched the sources with the xine-lib-1.2 vdpau patch from here http://www.jusst.de/vdpau - patching worked very well!:
so:
./autogen.sh noconfig
in src-dir and
CFLAGS='-g3 -O3 -fPIC -lm -mtune=k8 -pipe' ../xine-lib-1.2-hg-2009-01-13/configure --disable-debug --with-external-ffmpeg=/opt/src/vdr/VDR-download/DVB-S2/ffmpeg-svn-2009-01-13 --disable-dxr3
in build directory. "configure" worked well, but with make i'm getting:
. . make[1]: Leaving directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/po' Making all in misc
make[1]: Entering directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/misc' gcc -DHAVE_CONFIG_H -I. -I../include -I../../xine-lib-1.2-hg-2009-01-13/misc -I../../xine-lib-1.2-hg-2009-01-13 -I../include -I../../xine-lib-1.2-hg-2009-01-13/include -I../../xine-lib-1.2-hg-2009-01-13/src -I../src/xine-engine -I../../xine-lib-1.2-hg-2009-01-13/src/xine-engine -I../../xine-lib-1.2-hg-2009-01-13/src/xine-utils -I../src/input -I../../xine-lib-1.2-hg-2009-01-13/src/input -I../lib -I../../xine-lib-1.2-hg-2009-01-13/lib -DNDEBUG -D_REENTRANT -DXINE_COMPILE -pipe -Wall -Wformat=2 -Wno-format-zero-length -Wmissing-format-attribute -Werror-implicit-function-declaration -Wstrict-aliasing=2 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wpointer-arith -g -g3 -O3 -fPIC -lm -mtune=k8 -pipe -Wall -Wchar-subscripts -Wnested-externs -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wmissing-format-attribute -Wno-pointer-sign -Wformat=2 -Wno-format-zero-length -Wstrict-aliasing=2 -Werror=implicit-function-declaration -MT xine-list.o -MD -MP -MF .deps/xine-list.Tpo -c -o xine-list.o ../../xine-lib-1.2-hg-2009-01-13/misc/xine-list.c cc1: error: unrecognized command line option "-Werror=implicit-function-declaration" make[1]: *** [xine-list.o] Error 1 make[1]: Leaving directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/misc' make: *** [all-recursive] Error 1
"configure" also returned a line "checking if gcc supports -Werror=implicit-function-declaration flag... (cached) yes".
i'm using kernel 2.6.26.5 on an AMD64 x86_64 platform with
gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
Any pursuing hints would be very gratifying!
ciax _________________________________________________________________ Hol dir 30 kostenlose Emoticons für deinen Windows Live Messenger http://www.livemessenger-emoticons.com/funfamily/de-at/
Date: Mon, 12 Jan 2009 23:43:33 +0100 From: rnissl@gmx.de To: vdr@linuxtv.org Subject: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Hi,
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Welcome back - many people will be pleased about you beeing back to vdr! :)
Excerpt from HISTORY:
2009-01-12: Version 0.9.0
[..]
- Make use of new OSD functionality in xine-lib-1.2. For now
an OSD implementation must provide both new features to have vdr-xine make use of it.
- Extended OSD support in xine-lib-1.2 to allow truecolor OSDs
as well as hardware scaled OSDs. The new functionality is currently only provided by VDPAU enabled installations.
Maybe a little bit OT, but i'm having a problem with compiling the latest xine-lib-1.2 HG. Earlier versions (last tested with xine-lib-1.2 from 2008-08-18) didn't show this effect. I'm compiling the libs as you suggested in this post: http://www.linuxtv.org/pipermail/vdr/2008-March/016195.html . Before i patched the sources with the xine-lib-1.2 vdpau patch from here http://www.jusst.de/vdpau - patching worked very well!:
so:
./autogen.sh noconfig
in src-dir and
CFLAGS='-g3 -O3 -fPIC -lm -mtune=k8 -pipe' ../xine-lib-1.2-hg-2009-01-13/configure --disable-debug --with-external-ffmpeg=/opt/src/vdr/VDR-download/DVB-S2/ffmpeg-svn-2009-01-13 --disable-dxr3
in build directory. "configure" worked well, but with make i'm getting:
. . make[1]: Leaving directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/po' Making all in misc
make[1]: Entering directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/misc'
gcc -DHAVE_CONFIG_H -I. -I../include -I../../xine-lib-1.2-hg-2009-01-13/misc -I../../xine-lib-1.2-hg-2009-01-13 -I../include -I../../xine-lib-1.2-hg-2009-01-13/include -I../../xine-lib-1.2-hg-2009-01-13/src -I../src/xine-engine -I../../xine-lib-1.2-hg-2009-01-13/src/xine-engine -I../../xine-lib-1.2-hg-2009-01-13/src/xine-utils -I../src/input -I../../xine-lib-1.2-hg-2009-01-13/src/input -I../lib -I../../xine-lib-1.2-hg-2009-01-13/lib -DNDEBUG -D_REENTRANT -DXINE_COMPILE -pipe -Wall -Wformat=2 -Wno-format-zero-length -Wmissing-format-attribute -Werror-implicit-function-declaration -Wstrict-aliasing=2 -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -Wpointer-arith -g -g3 -O3 -fPIC -lm -mtune=k8 -pipe -Wall -Wchar-subscripts -Wnested-externs -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wmissing-format-attribute -Wno-pointer-sign -Wformat=2 -Wno-format-zero-length -Wstrict-aliasing=2 -Werror=implicit-function-declaration -MT xine-list.o -MD -MP -MF .deps/xine-list.Tpo -c -o xine-list.o ../../xine-lib-1.2-hg-2009-01-13/misc/xine-list.c cc1: error: unrecognized command line option "-Werror=implicit-function-declaration" make[1]: *** [xine-list.o] Error 1 make[1]: Leaving directory `/opt/src/download/xine-vdpau/xine-0.9.0/build-ciax/misc' make: *** [all-recursive] Error 1
"configure" also returned a line "checking if gcc supports -Werror=implicit-function-declaration flag... (cached) yes".
i'm using kernel 2.6.26.5 on an AMD64 x86_64 platform with
gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release x86_64-linux-gnu Thread model: posix gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
Any pursuing hints would be very gratifying!
ciax
hello, just to close up this specific compiling problem - my gcc version was to old! now, with version 4.3.2 xine-lib-1.2 and xine-0.9.0 builds fine!
greets, ciax
_________________________________________________________________ Teste jetzt die neue Windows Live Messenger Beta! http://download.live.com/
it's me wrote:
hello, just to close up this specific compiling problem - my gcc version was to old! now, with version 4.3.2 xine-lib-1.2 and xine-0.9.0 builds fine!
http://www.kosunen.fi/gentoo/xine-vdpau/media-libs/xine-lib/files/xine-lib-1...
Here is configure.ac patch for older gcc.
Reinhard Nissl wrote:
Hi,
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r'
I demand that Lauri Tischler may or may not have written...
Reinhard Nissl wrote:
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r'
They're wherever the rest of the key bindings are for whichever xine-lib front end you happen to be using.
Darren Salt wrote:
I demand that Lauri Tischler may or may not have written...
Reinhard Nissl wrote:
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r'
They're wherever the rest of the key bindings are for whichever xine-lib front end you happen to be using.
Sort of assumed that they would be defined in VDR's remote.conf file, where the Lord intended them to be :)
Hi,
Lauri Tischler schrieb:
Darren Salt wrote:
I demand that Lauri Tischler may or may not have written...
Reinhard Nissl wrote:
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r'
They're wherever the rest of the key bindings are for whichever xine-lib front end you happen to be using.
Sort of assumed that they would be defined in VDR's remote.conf file, where the Lord intended them to be :)
The problem was that xine-ui didn't provide enough keys to cover all VDR functionality. That's why we introduced further VDR specific events. But they are not bound to any key by default.
See MANUAL for additional information about the keys.
Bye.
Hi,
Reinhard Nissl schrieb:
Lauri Tischler schrieb:
Darren Salt wrote:
I demand that Lauri Tischler may or may not have written...
Reinhard Nissl wrote:
after being away 7 month from VDR development I'm pleased to announce release 0.9.0. You can find it on my homepage as usual:
Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r'
They're wherever the rest of the key bindings are for whichever xine-lib front end you happen to be using.
Sort of assumed that they would be defined in VDR's remote.conf file, where the Lord intended them to be :)
The problem was that xine-ui didn't provide enough keys to cover all VDR functionality. That's why we introduced further VDR specific events. But they are not bound to any key by default.
So it made no sense to go through the remote learning mode if these additional keys had to be bound in xine-ui anyway.
See MANUAL for additional information about the keys.
Bye.
-
Darren Salt -
it's me -
it's me ciax
-
Joerg Riechardt -
Lauri Tischler -
Matthias Dahl -
Pertti Kosunen -
Reinhard Nissl