[vdr] FreeviewHD success with Nanostick 290e

2011-08-19 Thread Laz
Hi Chris (and list) I've just been doing a bit more testing with my recently acquired Nanostick 290e... I added a fake channel with the frequency 61800 MHz (my HD mux), QAM256, and everything else set to auto or random values. I then switched to it. vdr then picked up BBC HD, ITV1 HD, Cha

Re: [vdr] FreeviewHD success with Nanostick 290e

2011-08-19 Thread Stuart Morris
Hi I too have just acquired a 290e and I am having difficulty getting it to work with VDR. Apart from the flakey driver at the moment, 'seeding' VDR's channel.conf is difficult. I tried using w_scan like this: w_scan -c GB -o 7 -I my_init_tune_file My tuning file (UK Sandy Heath) contained 1 li

Re: [vdr] FreeviewHD success with Nanostick 290e

2011-08-19 Thread Laz
On Friday 19 Aug 2011, Stuart Morris wrote: > Hi > I too have just acquired a 290e and I am having difficulty getting it > to work with VDR. Apart from the flakey driver at the moment, > 'seeding' VDR's channel.conf is difficult. I tried using w_scan like > this: > > w_scan -c GB -o 7 -I my_init_t

[vdr] [feature request] recording length computation and storage

2011-08-19 Thread Steffen Barszus
Hi ! After having seen that there are several plug-ins computing the recording length on their own and that being a very expensive task (in respect of io and cpu) and also the same implementation needs to be copied over and over again, i would like to request, that vdr is storing the length of a r

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread André Weidemann
Hi Steffen, On 19.08.2011 11:46, Steffen Barszus wrote: Hi ! After having seen that there are several plug-ins computing the recording length on their own and that being a very expensive task (in respect of io and cpu) and also the same implementation needs to be copied over and over again, i w

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Klaus Schmidinger
On 08/19/11 11:46, Steffen Barszus wrote: Hi ! After having seen that there are several plug-ins computing the recording length on their own and that being a very expensive task (in respect of io and cpu) and also the same implementation needs to be copied over and over again, i would like to re

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Steffen Barszus
On Fri, 19 Aug 2011 12:21:24 +0200 Klaus Schmidinger wrote: > On 08/19/11 11:46, Steffen Barszus wrote: > > Hi ! > > > > After having seen that there are several plug-ins computing the > > recording length on their own and that being a very expensive task > > (in respect of io and cpu) and also t

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Klaus Schmidinger
On 19.08.2011 14:39, Steffen Barszus wrote: On Fri, 19 Aug 2011 12:21:24 +0200 Klaus Schmidinger wrote: On 08/19/11 11:46, Steffen Barszus wrote: Hi ! After having seen that there are several plug-ins computing the recording length on their own and that being a very expensive task (in respec

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Steffen Barszus
On Fri, 19 Aug 2011 14:48:46 +0200 Klaus Schmidinger wrote: > On 19.08.2011 14:39, Steffen Barszus wrote: > > On Fri, 19 Aug 2011 12:21:24 +0200 > > Klaus Schmidinger wrote: > > > >> On 08/19/11 11:46, Steffen Barszus wrote: > >>> Hi ! > >>> > >>> After having seen that there are several plug-in

Re: [vdr] FreeviewHD success with Nanostick 290e

2011-08-19 Thread Rob Davis
> > Hi Chris (and list) > > I've just been doing a bit more testing with my recently acquired > Nanostick > 290e... > > I added a fake channel with the frequency 61800 MHz (my HD mux), > QAM256, > and everything else set to auto or random values. I then switched to it. > vdr > then picked up BB

[vdr] Fix for recording problem in VDR 1.7.20

2011-08-19 Thread Klaus Schmidinger
There have been some reports about recording problems with VDR 1.7.20 on some HD channels. This patch should fix this. Klaus --- remux.c 2011/08/15 09:50:14 2.58 +++ remux.c 2011/08/19 15:33:26 @@ -974,8 +974,10 @@ payloadUnitOfFrame = (payloadU

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.20

2011-08-19 Thread Udo Richter
Am 16.08.2011 23:13, schrieb Klaus Schmidinger: > On 16.08.2011 19:56, Udo Richter wrote: >> Am 16.08.2011 18:57, schrieb Klaus Schmidinger: >>> - cSkins::Message() now blocks calls from background threads (thanks to >>>Michael Eiler for reporting a crash in such a scenario). >> >> Unfortunatel

[vdr] Osdserver-0.1.3 and Hard Link Cutter-0.2.2 for VDR-1.7.20

2011-08-19 Thread Udo Richter
Hi list, Updates for VDR-1.7.20 on my web page: Hard Link Cutter for 1.7.20: Fixes rejects http://www.udo-richter.de/vdr/patches.en.html#hlcutter http://www.udo-richter.de/vdr/patches.html#hlcutter Osdserver-0.1.3: - Fix: Message command blocked from background thread, use callback - Update M

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Udo Richter
Am 19.08.2011 15:30, schrieb Steffen Barszus: On 08/19/11 11:46, Steffen Barszus wrote: > i would like to request, that > vdr is storing the length of a recording and make it accessible > to the plug-ins. > > Where it gets stored is not my point, that it can be served from in > meo

Re: [vdr] [feature request] recording length computation and storage

2011-08-19 Thread Steffen Barszus
On Fri, 19 Aug 2011 22:18:03 +0200 Udo Richter wrote: > Am 19.08.2011 15:30, schrieb Steffen Barszus: > On 08/19/11 11:46, Steffen Barszus wrote: > > i would like to request, that > > vdr is storing the length of a recording and make it accessible > > to the plug-ins. > > > > Whe