Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
On Sat, Jan 10, 2009 at 2:25 PM, Artem Makhutov ar...@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? - http://home.vrweb.de/~bergwinkl.thomashttp://home.vrweb.de/%7Ebergwinkl.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. 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ar...@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? - http://home.vrweb.de/~bergwinkl.thomashttp://home.vrweb.de/%7Ebergwinkl.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. 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.3 + reelbox plugin
I am currently using vdr-1.6.0 with reelbox plugin and would like to test the new vdr-1.7.3. I have Checked out revision 10331 from reelbox.org. Since I am having trouble getting the reelbox plugin to compile with vdr-1.7.3 I thought I'd check first before continuing: - Does the reelbox plugin work with vdr-1.7.3? (does vdr's switching to TS make the current plugin unusable?) - Is there a patch already for vdr-1.7.3 to make it compile with the reelbox plugin? ( I have tested some patches for vdr-1.7.0, but the ones I have tested fail ) Regards, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
On Saturday 10 of January 2009, Josce wrote: I am currently using vdr-1.6.0 with reelbox plugin and would like to test the new vdr-1.7.3. I have Checked out revision 10331 from reelbox.org. Since I am having trouble getting the reelbox plugin to compile with vdr-1.7.3 I thought I'd check first before continuing: - Does the reelbox plugin work with vdr-1.7.3? (does vdr's switching to TS make the current plugin unusable?) - Is there a patch already for vdr-1.7.3 to make it compile with the reelbox plugin? ( I have tested some patches for vdr-1.7.0, but the ones I have tested fail ) Regards, Josce Hi, yersterday I've tried to test it but first problem was S2API drivers - drivers from last versions are unusable for me (kernel 2.6.26, amd64 arch., HVR-4000). I was getting Oops, /dev/dvb was not populated and so on. Totally unusable drivers for my configuration. Then I used S2API from 23.11.2008 - it is necessary to patch this version reg. Klaus need. I've made some patch for reelbox plugin, but I was not able to get sound as well as from eHD as from PC soundcard. It seemed to be that the switching between channels is 2-3 times longer (maybe as syncearly from R.Nissl is not implemented?). So now I'm back at vdr-1.7.0 and last multiproto from Igor. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
Op Za, 10 januari, 2009 15:04, schreef Ales Jurik: On Saturday 10 of January 2009, Josce wrote: Hi, -- SNIP -- I've made some patch for reelbox plugin, but I was not able to get sound as well as from eHD as from PC soundcard. Same here. I just tried it, and the eHD does indeed give no sound. I allready posted it in the Reel forum. Hopefully a fix will popup some day. It seemed to be that the switching between channels is 2-3 times longer (maybe as syncearly from R.Nissl is not implemented?). I didn't encounter longer zapping times. But then again, I didn't look for it especially. So now I'm back at vdr-1.7.0 and last multiproto from Igor. Same here. I'm back to 1.7.0 until the sound-problem has been fixed :) BR, Ales Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.3 + reelbox plugin
yersterday I've tried to test it but first problem was S2API drivers - drivers from last versions are unusable for me (kernel 2.6.26, amd64 arch., HVR-4000). I was getting Oops, /dev/dvb was not populated and so on. Totally unusable drivers for my configuration. yes, me too Then I used S2API from 23.11.2008 - it is necessary to patch this version reg. Klaus need. you can use fresh http://mercurial.intuxication.org/hg/s2-liplianin I don't have such problem as with v4l-dvb Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Roadmap for VDR 1.8
user.vdr a écrit : On Fri, Jan 9, 2009 at 11:27 AM, Artem Makhutov ar...@makhutov.org wrote: What points have to be done to finish 1.7.x and to get to 1.8.0. In the years I've been using VDR, there has always been many development versions before Klaus has released a new stable so based on past experience, I wouldn't expect to see 1.8.0 any time soon. There are some big changes in 1.7.x and I guess it could go either way. He might want to release a new stable after the major stuff has been implimented and tested, saving the little things for the next development line. Or he could just take it slow easy. One nice thing I've learned is that most dev versions are pretty damn stable themselves. I've been running dev versions probably 90%+ of the time on my main vdr box. :) Another thing I've learned is that Klaus never (AFAIK) discussed roadmap details or made his own task list public ;-) -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Color keys replacement
On Sat, Jan 10, 2009 at 8:34 AM, Alex Betis alex.be...@gmail.com wrote: Hi all, A question regarding the color keys functionality in VDR. Some remotes I see in shops don't have the color keys, is there any replacement key for those? Is it possible to map them to 1,2,3,4? Can you think of a scenario both color keys and numbers might be used in the same menu? You can map any function to any key you want. One example of numbers colors being used in the same menu is the main menu itself. Numbers take you straight to sub-menus or plugins while the color keys perform functions like start recording or change the audio pid. My advice, just buy a remote with the color keys and save yourself some hassle! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Roadmap for VDR 1.8
On Sat, Jan 10, 2009 at 8:26 AM, Nicolas Huillard nico...@huillard.net wrote: Another thing I've learned is that Klaus never (AFAIK) discussed roadmap details or made his own task list public ;-) Yeah, that too. Which has driven some of us crazy but I can't honestly say I'd be any different if I were Klaus. There's something about setting your own schedule/priorities that's more appealing then answering to peoples expectations. The good news is that he's willing to shuffle the TODO list if there's more urgent things to take care (as with HDTV and h264 support for example). Like I said, I've ran mostly dev versions of VDR for years with little to no problems but be advised that your experience may vary. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Color keys replacement
On Sat, Jan 10, 2009 at 6:54 PM, user. vdr user@gmail.com wrote: On Sat, Jan 10, 2009 at 8:34 AM, Alex Betis alex.be...@gmail.com wrote: Hi all, A question regarding the color keys functionality in VDR. Some remotes I see in shops don't have the color keys, is there any replacement key for those? Is it possible to map them to 1,2,3,4? Can you think of a scenario both color keys and numbers might be used in the same menu? You can map any function to any key you want. One example of numbers colors being used in the same menu is the main menu itself. Numbers take you straight to sub-menus or plugins while the color keys perform functions like start recording or change the audio pid. Good point. My advice, just buy a remote with the color keys and save yourself some hassle! Yeah, that are my thoughts as well. I just look on the latest products of logitech and see that there are no color buttons. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ANNOUNCE vdr-osdteletext 0.8.0
Hello! A new version of the VDR OSDTeletext plug-in was just released. Recent Changes: - Added Portuguese translation provided by Chris Silva - Updated Italian translation by Davide Cavalca - Removed the OSD from the main menu entry as suggested by Davide Cavalca - Added Ukrainian translation provided by Yarema P. aka Knedlyk - Removed obsolete options -R and -r - Removed remnants of VDR 1.6 support - Updated Russian translation provided by Oleg Roitburd (Closes #46) - Improved error handling - Background toggling now allows to switch between black, the configured background transparency and full transparency as suggested by Walter K. (Closes #41) - Removed the OSDTELETEXT_REINSERTION_PATCH (dead code) - Removed timingdebug code - Merged class ChannelStatus into cTxtStatus and changed the code that detects, if the current live channel has been changed and the OsdTeletext receiver needs to switch to the new channel as well (Thx to Sören Moch!) - Updated French translation provided by Nival Michael (Closes #56) Thanks a lot to all the contributors and translators! Development site: http://projects.vdr-developer.org/projects/show/plg-osdteletxt Downloads: http://projects.vdr-developer.org/projects/list_files/plg-osdteletext Git-Web: http://projects.vdr-developer.org/git/?p=vdr-plugin-osdteletext.git Anonymous Git-access : git://projects.vdr-developer.org/vdr-plugin-osdteletext.git This is intended to be a community maintained project! Don't expect me to fix your problems, I'm merely maintaining the project! Please report any bugs, ideas or feature requests to the project site (no registration required for this!). If you want to contribute patches, new features or whatever, post an issue or patch to the projects issue tracker or request to join the project. I would happily add everyone as a project member, who would like to contribute to the project! If you want to contribute but don't know what to do - start with some code refactoring! Tobias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] German translation for Plugin
On 09.01.2009 20:29, Joachim Wilke wrote: Dear developers, I recommend changing the translation for Plugin in the German language file to a more non-technical term. I suggest Erweiterung instead of Plugin. This helps even non-technical experienced users of VDR to understand what to expect. Well, I have no objection against this (I don't use the German version ;-). But is it really wise to hide such a term from the German users? When they talk about a certain plugin with a (German) user of the English version, it might take a while until the other one realizes that Erweiterung means Plugin. Plugin is such a common word, even for German users, that I doubt avoiding it is a good thing to do. If anybody else thinks translating the word Plugin to Erweiterung makes sense, please speak up (or otherwise argue against it). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Choice of recording format
I was just wondering what prompted the move from recording in PES to TS. Is it because TS is more widely supported? And how does it solve the problem of BBC HD having the wrong PID for audio? And why TS instead of PS? Is it because PS needs a header which is difficult to generate before all the packets intended for it are available (and hence difficulties overlapping playback and recording)? Or is it because the way recordings are played back makes TS more appropriate? -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Choice of recording format
On Sat, Jan 10, 2009 at 4:04 PM, Tony Houghton h...@realh.co.uk wrote: I was just wondering what prompted the move from recording in PES to TS. Is it because TS is more widely supported? And how does it solve the problem of BBC HD having the wrong PID for audio? And why TS instead of PS? Is it because PS needs a header which is difficult to generate before all the packets intended for it are available (and hence difficulties overlapping playback and recording)? Or is it because the way recordings are played back makes TS more appropriate? Switching to TS has been a point of much discussion so you'll find plenty of answers if you search the ml (archive). Btw, any errors on the providers part should be fixed @ the provider, not within VDR. If I'm not mistaken they've already contacted them regarding the pid issue, though I don't know what/if came out of it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
