Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On Tue, 06 Jan 2009 16:06:02 +0100, Klaus Schmidinger wrote Instead of Priority and Lifetime, the directory name now contains the channel number from which the recording was made, and the resume id of this instance of VDR. This avoids problems if several VDR instances record the same show on different channels, or even on the same channel. I'd opt for a dedicated VDR instance parameter instead of using the resume ID. In my understanding the resume ID corresponds to the actual user watching, hence the resume ID is subject to change. At least that's how I use it in the remotetimers-plugin. Regards, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
Could some pse tell me what kind of patch and v4l drivers i should use to run vdr-1.7.x in HD mode ? you have to install http://mercurial.intuxication.org/hg/s2-liplianin vdr 170 and 2 patches http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj vdr-1.7.0-s2api-07102008-h264-clean.patch.gz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] WinTV USB CI-Module and recommended distribution for VDR?
Hi all, as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD videos), it's now time to choose a DVB-S/2 card. I consider the TT 3200 and with a slight preference the Haupauge HVR-4000 (drivers in the kernel since 2.6.28 seems a bit more comfortable). The only point I'm unsure about is the Haupauge WinTV CI-module USB. Does anyone know about its linux compatibility? Or do you recommend the TT 3200 if I need an CI module? And the second question is about the preferred distribution to use VDR with. Are there any distributions optimized for VDR and fast boot times? (Yes I know [1], but that didn't help me with choosing one optimized for short boot times.) LinVDR seemed to be such, but the last version is now 4 years old. I personally have experiences with Gentoo and Debian, so that would be my choices if no one has a better option worth trying. Greetings -Sascha- [1]http://www.vdr-wiki.de/wiki/index.php/%C3%9Cbersicht_Software#Distributionen ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Sascha Vogt a écrit : And the second question is about the preferred distribution to use VDR with. Are there any distributions optimized for VDR and fast boot times? (Yes I know [1], but that didn't help me with choosing one optimized for short boot times.) LinVDR seemed to be such, but the last version is now 4 years old. I personally have experiences with Gentoo and Debian, so that would be my choices if no one has a better option worth trying. I started with a bare-minimum Debian/e-tobi install (with debootstrap on an NFS share, which gives a really light bootable system), then installed whatever needed, but nothing fancy (ie. X with a tiny WM, but no login manager, ACPI, no dbus, etc...). Boot time is not spectacular, but OK. Next step, as others did, will be to suspend to RAM instead of shuting down, which means boot time will become irrelevant... Install size is 724MB, with full docs (à la Debian), stock kernel, modules and initrd, some VDR plugins, etc. (including 187MB of useless cached packages). That's work, but at least everything came in binary... -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Hi, Nicolas Huillard schrieb: Sascha Vogt a écrit : And the second question is about the preferred distribution to use VDR with. Are there any distributions optimized for VDR and fast boot times? I started with a bare-minimum Debian/e-tobi install (with debootstrap on an NFS share, which gives a really light bootable system), then installed whatever needed, but nothing fancy (ie. X with a tiny WM, but no login manager, ACPI, no dbus, etc...). Boot time is not spectacular, but OK. [...] Can you provide any figures? 30 seconds, 50 seconds, 90 seconds? To get at least a rough idea. Greetings -Sascha- PS: Suspend to Ram can be a good alternative, that's true. Hopefully that'll be working on that ASUS board... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Sascha Vogt a écrit : Nicolas Huillard schrieb: Sascha Vogt a écrit : And the second question is about the preferred distribution to use VDR with. Are there any distributions optimized for VDR and fast boot times? I started with a bare-minimum Debian/e-tobi install (with debootstrap on an NFS share, which gives a really light bootable system), then installed whatever needed, but nothing fancy (ie. X with a tiny WM, but no login manager, ACPI, no dbus, etc...). Boot time is not spectacular, but OK. [...] Can you provide any figures? 30 seconds, 50 seconds, 90 seconds? To get at least a rough idea. 30s on an Athlon XP 1.8GHz roughly 45s on a C3 600MHz Simply recompiling the kernel, removing unneeded modules and initrd, could reduce by 5-10s... -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Sascha Vogt wrote: Hi all, as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD videos) Couldn't find M2N78Pro, do you mean M3N78PRO ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] S2-3200 vdr needed material ?
Hy all, But I must contradict you all, I use vdr-1.7.2 with v4l-dvb from linuxtv.org but with patches from Alex, for stb8900 search algo on an sky star hd aka tt-3200. with vdr-xine-0.8.2 wit curent xine-lib-1.2 and ffmpeg, and it is working perfectly on gentoo linux. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 08.01.2009 18:50, user.vdr wrote: On Tue, Jan 6, 2009 at 7:06 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: + The directory name for a recording has been changed from -MM-DD-hh[.:]mm.pr.lt.rec (pr=priority, lt=lifetime) to -MM-DD-hh.mm.ch-ri.rec (ch=channel, ri=resumeId). Is the channel number even necessary information to store in a dirname? I've experienced many times where channels have been shuffled (requiring a rescanning a new channels.conf) so channel 100 could be one network today and a different one tomorrow. Maybe a better choice would be using the channel shortname, for example: -MM-DD-hh.mm.CNN-ri.rec -MM-DD-hh.mm.BBC-ri.rec The channel number would be unnecessary, because that information is stored in the 'info' file. However, it is contained in the recording's directory name, so that in case two timers of the same VDR instance record the exact same programme, but on different channels, they don't mix their data into one big pile of goo (which could have happenend in VDR 1= 1.7.2). No need to make this a string - it's just a safety precaution (besides, two channels might have the *same* name, but never the same number). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On 08.01.2009 20:41, Alex Betis wrote: On Thu, Jan 8, 2009 at 7:50 PM, user. vdr user@gmail.com mailto:user@gmail.com wrote: On Tue, Jan 6, 2009 at 7:06 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de mailto:klaus.schmidin...@cadsoft.de wrote: + The directory name for a recording has been changed from -MM-DD-hh[.:]mm.pr.lt.rec (pr=priority, lt=lifetime) to -MM-DD-hh.mm.ch-ri.rec (ch=channel, ri=resumeId). Is the channel number even necessary information to store in a dirname? I've experienced many times where channels have been shuffled (requiring a rescanning a new channels.conf) so channel 100 could be one network today and a different one tomorrow. Maybe a better choice would be using the channel shortname, for example: -MM-DD-hh.mm.CNN-ri.rec -MM-DD-hh.mm.BBC-ri.rec I don't know how VDR work, but I think it will be wise to have a file with the same filename and .info or even .epg extension that will have relevant EPG section for the recorded program including full channel name. That's all already contained in the 'info' file of a recording. If the recording timer was set manualy, maybe it should include all programs that lay between start and end of the recording. It stores the EPG data of the longest broadcast within the timer window. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
On Thu, Jan 8, 2009 at 11:17 PM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: On 08.01.2009 20:41, Alex Betis wrote: On Thu, Jan 8, 2009 at 7:50 PM, user. vdr user@gmail.com mailto:user@gmail.com wrote: On Tue, Jan 6, 2009 at 7:06 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de mailto:klaus.schmidin...@cadsoft.de wrote: + The directory name for a recording has been changed from -MM-DD-hh[.:]mm.pr.lt.rec (pr=priority, lt=lifetime) to -MM-DD-hh.mm.ch-ri.rec (ch=channel, ri=resumeId). Is the channel number even necessary information to store in a dirname? I've experienced many times where channels have been shuffled (requiring a rescanning a new channels.conf) so channel 100 could be one network today and a different one tomorrow. Maybe a better choice would be using the channel shortname, for example: -MM-DD-hh.mm.CNN-ri.rec -MM-DD-hh.mm.BBC-ri.rec I don't know how VDR work, but I think it will be wise to have a file with the same filename and .info or even .epg extension that will have relevant EPG section for the recorded program including full channel name. That's all already contained in the 'info' file of a recording. Great! So I didn't reinvent the wheel :) If the recording timer was set manualy, maybe it should include all programs that lay between start and end of the recording. It stores the EPG data of the longest broadcast within the timer window. That's fine if only one program is intended to be recorded. What if someone wants to record a bunch of programs? There are lots of music shows in the night between 31/12 and 01/01 of every year. With old tape recorder I just pressed REC and hope that the tape will contain as many programs as possible. In such case I would like to see all recorded programs descriptions. Klaus ___ 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
