Op Do, 8 januari, 2009 08:25, schreef Pierre-Yves Paranthoën:
Hi,
Could some pse tell me what kind of patch and v4l drivers i should use to run vdr-1.7.x in HD mode ?
According to LinuxTV Wiki for your card (source: http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3600):
- Multiproto (not advisable, since it's absolete) - S2API (More precise: http://mercurial.intuxication.org/hg/s2-liplianin)
And for VDR 1.7.x, you have two choices:
- VDR 1.7.0 in combination with my patches from October; - VDR 1.7.3 which was released this week;
If you're running a budget only system (read, no Reel eHD for hardware decoding off H264 or MPEG2) you might want to stick to VDR 1.7.0 because of some issues with the current plugins like xine and/or xineliboutput (at least, this is what I read on the ml). Beware though, VDR 1.7.0 has some audio issues with certain channels like BBC HD (which should be fixed by the implementation of TS format).
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?). Can anybody confirm that this problem still exists? Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins.
thanks,
regards
Pierre
Regards,
Niels Wagenaar
Could some pse tell me what kind of patch and v4l drivers i should use to run vdr-1.7.x in HD mode ?
According to LinuxTV Wiki for your card (source: http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3600):
- Multiproto (not advisable, since it's absolete)
- S2API (More precise: http://mercurial.intuxication.org/hg/s2-liplianin)
And for VDR 1.7.x, you have two choices:
- VDR 1.7.0 in combination with my patches from October;
- VDR 1.7.3 which was released this week;
I don't recommend to install vdr 171 172 173 on your system because current version of vdr-xine/xineliboutput/softdevice don't support it yet
If you're running a budget only system (read, no Reel eHD for hardware decoding off H264 or MPEG2) you might want to stick to VDR 1.7.0 because
yes, vdr 170
of some issues with the current plugins like xine and/or xineliboutput (at least, this is what I read on the ml). Beware though, VDR 1.7.0 has some audio issues with certain channels like BBC HD (which should be fixed by the implementation of TS format).
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?).
imho - yes , software output plugins have problems with vdr > 1.7.0
Can anybody confirm that this problem still exists?
yes
Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins.
let's waiting for vdr-xine 090 and other update version of xineliboutput/softdevice
Goga
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?). Can anybody confirm that this problem still exists? Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins.
Seems still to have. At least xineliboutput-1.0.3 builded but failed to work with 1.7.3. (vdr-sxfe outputs lot of error messages when running). I did not test the cvs version but at least that also failed with vdr-1.7.2.
latest streamdev from CVS failed to build again 1.7.3 (builded ok with 1.7.2 and could be used for showing data once if I just had first tuned to some channel with szap/szap-2 before launching vdr-1.7.2. This is probably a hvr-4000 S2API driver bug)
Mika
On Thu, 8 Jan 2009 18:04:05 +0200 (EET), Mika Laitio wrote
latest streamdev from CVS failed to build again 1.7.3
In the bugtracker you'll find a patch which makes streamdev compile again. It comments out the PES output stuff which causes the problems until a clean solution is available.
http://www.vdr-developer.org/mantisbt/view.php?id=506
Regards, Frank
In the bugtracker you'll find a patch which makes streamdev compile again. It comments out the PES output stuff which causes the problems until a clean solution is available.
Thanks, I applied that patch and streamdev build then fine for vdr-1.7.3 Here are my test results. (5 days old s2-liplianin, hvr-1300 for dvb-t and hvr-4000 for dvb-s/s2)
1) Watching and switching between DVB-T channels (both withing same mux or different muxes) worked ok just by giving commands like
mplayer http://localhost:3000/TS/1 mplayer http://localhost:3000/TS/3
2) Watching of DVB-S and DVB-S2 worked most of the times if I did it in the following sequence
- close vdr-1.7.3 - switch to dvb-s/dvb-s2 channel for example by using ./szap-s2/szap-s2 -a 1 -S 2 -c channels.conf arteHD - close szap-s2 with ctrl-c - launch vdr-1.7.3 - open same channel that was earlier szapped: mplayer http://localhost:3000/TS/6
If I did not pre-tuned s/s2 channel I wanted to watchfirst with szap, mplayer just showed in console: Connecting to server localhost[127.0.0.1]: 3000... Cache size set to 320 KBytes Cache fill: 0.00% (0 bytes)
Sometimes I also needed to use szap-s2 multiple times for being able to watch s2 channels. On those failing cases mplayer showed
Cache fill: 0.00% (0 bytes) TS file format detected. VIDEO MPEG2(pid=6210) AUDIO MPA(pid=6221) NO SUBS (yet)! PROGRAM N. 0 Stream not seekable!
Mika
Hello,
On Thu, Jan 08, 2009 at 06:04:05PM +0200, Mika Laitio wrote:
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?). Can anybody confirm that this problem still exists? Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins.
Seems still to have. At least xineliboutput-1.0.3 builded but failed to work with 1.7.3. (vdr-sxfe outputs lot of error messages when running). I did not test the cvs version but at least that also failed with vdr-1.7.2.
Have you tried to compile vdr with the livebuffer patch? This makes xineliboutput work with VDR (at least 1.7.1).
Regards, Artem
Have you tried to compile vdr with the livebuffer patch? This makes xineliboutput work with VDR (at least 1.7.1).
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one?
- http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch only for vdr-1.5 - VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3) - VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
Mika
Hi,
On Sat, Jan 10, 2009 at 11:11:22AM +0200, Mika Laitio wrote:
Have you tried to compile vdr with the livebuffer patch? This makes xineliboutput work with VDR (at least 1.7.1).
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one?
- http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to apply them all.
Regards, Artem
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one?
- http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to apply them all.
What's this "patch pack"? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies?
Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there.
Mika
Hi,
On Sat, Jan 10, 2009 at 12:08:31PM +0200, Mika Laitio wrote:
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one?
- http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to apply them all.
What's this "patch pack"? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies?
Yes, I think so. I have not tried to apply the patches manually. I am using a Gentoo ebuild which applies them for me.
Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there.
I have just setup S2API drivers with VDR 1.7.2 and the livebuffer patch from VDR Extensions Patch 65.
Everything works pretty well. I can watch even watch HDTV using xineliboutput and vdr-xine.
Regards, Artem
On Sat, Jan 10, 2009 at 2:25 PM, Artem Makhutov artem@makhutov.org wrote:
Hi,
On Sat, Jan 10, 2009 at 12:08:31PM +0200, Mika Laitio wrote:
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one
of
these with vdr-1.7.3 or some other one?
This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to
apply them all.
What's this "patch pack"? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies?
Yes, I think so. I have not tried to apply the patches manually. I am using a Gentoo ebuild which applies them for me.
Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there.
I have just setup S2API drivers with VDR 1.7.2 and the livebuffer patch from VDR Extensions Patch 65.
Everything works pretty well. I can watch even watch HDTV using xineliboutput and vdr-xine.
What are your channel switching times? I've used 1.7.1 + extension patches 64 to have the livebuffer + xinelibout and was unhappy with switching time, even on the same transponder. I've went back to 1.7.0 + the same xinelibout and see big improvements in switching time. I can see "sync early" messages in VDR logs, so I assume it makes the difference. Livebuffer probably breaks the ability to sync early.
Regards, Artem
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
On Sat, Jan 10, 2009 at 02:31:19PM +0200, Alex Betis wrote:
On Sat, Jan 10, 2009 at 2:25 PM, Artem Makhutov artem@makhutov.org wrote:
Hi,
On Sat, Jan 10, 2009 at 12:08:31PM +0200, Mika Laitio wrote:
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one
of
these with vdr-1.7.3 or some other one?
This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to
apply them all.
What's this "patch pack"? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies?
Yes, I think so. I have not tried to apply the patches manually. I am using a Gentoo ebuild which applies them for me.
Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there.
I have just setup S2API drivers with VDR 1.7.2 and the livebuffer patch from VDR Extensions Patch 65.
Everything works pretty well. I can watch even watch HDTV using xineliboutput and vdr-xine.
What are your channel switching times?
I have a switching time of ~2 seconds.
I've used 1.7.1 + extension patches 64 to have the livebuffer + xinelibout and was unhappy with switching time, even on the same transponder. I've went back to 1.7.0 + the same xinelibout and see big improvements in switching time. I can see "sync early" messages in VDR logs, so I assume it makes the difference. Livebuffer probably breaks the ability to sync early.
Ok, I just find out that switching to some channes does not work for me any more. Now I need to find out why. Maybe the Diseqc is not working using S2API on some DVB-S-cards anymore...
Regards, Artem
Hi,
On Sat, Jan 10, 2009 at 01:41:07PM +0100, Artem Makhutov wrote:
Hi,
On Sat, Jan 10, 2009 at 02:31:19PM +0200, Alex Betis wrote:
On Sat, Jan 10, 2009 at 2:25 PM, Artem Makhutov artem@makhutov.org wrote:
Hi,
On Sat, Jan 10, 2009 at 12:08:31PM +0200, Mika Laitio wrote:
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one
of
these with vdr-1.7.3 or some other one?
This page mentions the patch
only for vdr-1.5
- VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include
livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3)
- VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff
You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1.
You can enable single pathes in the "patch pack", so you don't have to
apply them all.
What's this "patch pack"? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies?
Yes, I think so. I have not tried to apply the patches manually. I am using a Gentoo ebuild which applies them for me.
Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there.
I have just setup S2API drivers with VDR 1.7.2 and the livebuffer patch from VDR Extensions Patch 65.
Everything works pretty well. I can watch even watch HDTV using xineliboutput and vdr-xine.
What are your channel switching times?
I have a switching time of ~2 seconds.
I've used 1.7.1 + extension patches 64 to have the livebuffer + xinelibout and was unhappy with switching time, even on the same transponder. I've went back to 1.7.0 + the same xinelibout and see big improvements in switching time. I can see "sync early" messages in VDR logs, so I assume it makes the difference. Livebuffer probably breaks the ability to sync early.
Ok, I just find out that switching to some channes does not work for me any more. Now I need to find out why. Maybe the Diseqc is not working using S2API on some DVB-S-cards anymore...
Ok, I setup VDR just to use individual devices. All of them worked fine. Then I switched back an setup VDR to use all of them together again, and I can tune to all channels without any problems. So I don't know where the problem was, but it has gone without doing real changes...
Regards, Artem
Hi Guys,
Thanks for your help, it worked !
I'm running vdr-1.7.0 with :
- home made LFS distro pure X86_64 (AMD Athlon(tm) 64 Processor 3500+); - S2API (latest drivers from http://mercurial.intuxication.org/hg/s2-liplianin); - Niels' combination patches from October; - Official & valid subscribtion from CanalSat (France) with HD & record options - DVB-S2 card from Technotrend Systemtechnik GmbH S2-3200 - and xineliboutput-1.0.3 plugin
This last one causes me some pb. It looses frames. Is there a particuliar version or patch to use as it is outputing in log :
video_out: throwing away image with pts 3640842 because it's too old (diff : 116836).
Kindest regards from a really pleased vdr user !
Pierre
Niels Wagenaar a écrit :
Op Do, 8 januari, 2009 08:25, schreef Pierre-Yves Paranthoën:
Hi,
Could some pse tell me what kind of patch and v4l drivers i should use to run vdr-1.7.x in HD mode ?
According to LinuxTV Wiki for your card (source: http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3600):
- Multiproto (not advisable, since it's absolete)
- S2API (More precise: http://mercurial.intuxication.org/hg/s2-liplianin)
And for VDR 1.7.x, you have two choices:
- VDR 1.7.0 in combination with my patches from October;
- VDR 1.7.3 which was released this week;
If you're running a budget only system (read, no Reel eHD for hardware decoding off H264 or MPEG2) you might want to stick to VDR 1.7.0 because of some issues with the current plugins like xine and/or xineliboutput (at least, this is what I read on the ml). Beware though, VDR 1.7.0 has some audio issues with certain channels like BBC HD (which should be fixed by the implementation of TS format).
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?). Can anybody confirm that this problem still exists? Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins.
thanks,
regards
Pierre
Regards,
Niels Wagenaar
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-
Alex Betis -
Artem Makhutov -
Frank Schmirler -
Goga777 -
Mika Laitio -
Niels Wagenaar -
Pierre-Yves Paranthoën