Re: [vdr] [PATCH] Device power saving feature

2016-05-30 Thread Richard F
Thanks - I built it and and have had it running for about 24 hours:

A couple of observations:
I'm seeing this about every 30 - 60 mins as expected, but the timeout
seems to be short - not the PowerdownTimeoutM (I assume minutes?) set at
15 in the config file

May 30 08:51:02 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 1/0
May 30 08:51:46 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
1/0

So during the start of recordings and other programme changes, I see
quite a lot of activity - e.g

May 29 15:32:32 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 1/0
May 29 15:32:36 ha-server vdr: [2306] channel 41 (Channel 4 HD) event Sun 
29.05.2016 15:25-16:30 (VPS: 29.05. 15:25) 'Location, Location, Location' 
status 4
May 29 15:32:37 ha-server vdr: [2306] channel 4 (BBC TWO HD) event Sun 
29.05.2016 15:30-18:00 (VPS: 29.05. 15:30) 'Gymnastics' status 4
May 29 15:33:17 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
1/0
May 29 15:33:38 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 1/0
May 29 15:33:41 ha-server vdr: [2306] channel 45 (Film4) event Sun 29.05.2016 
15:05-16:50 (VPS: 29.05. 15:05) 'Catch That Kid' status 4
May 29 15:33:42 ha-server vdr: [2306] channel 40 (Channel 4) event Sun 
29.05.2016 15:25-16:30 (VPS: 29.05. 15:25) 'Location, Location, Location' 
status 4
May 29 15:34:23 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
1/0

Start of (VPS) recording:

May 29 19:50:07 ha-server vdr: [2296] timer 2 (3 2000-2100 VPS 'Top 
Gear~2016.05.29-20:00-Sun') entered VPS margin
May 29 19:50:07 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:50:08 ha-server vdr: [2303] channel 3 (BBC TWO) event Sun 29.05.2016 
19:00-20:00 (VPS: 29.05. 19:00) 'Rugby Union' status 4
May 29 19:50:09 ha-server vdr: [2303] channel 7 (BBC NEWS) event Sun 29.05.2016 
19:45-20:00 (VPS: 29.05. 19:45) 'Meet The Author' status 4
May 29 19:50:46 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:50:51 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:51:30 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:51:35 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:52:14 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:52:19 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:52:58 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:53:03 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:53:42 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:53:47 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:54:26 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:54:31 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:55:10 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:55:15 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:55:54 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:55:59 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:56:38 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:56:43 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:57:22 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:57:27 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:58:06 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:58:11 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:58:50 ha-server vdr: [2296] dvb tuner: power-down - closing frontend 
0/0
May 29 19:58:55 ha-server vdr: [2296] dvb tuner: power-up - opening frontend 0/0
May 29 19:59:10 ha-server vdr: [2306] channel 61 (Channel 5 HD) event Sun 
29.05.2016 20:00-21:00 (VPS: 29.05. 20:00) 'Secrets of Egypt' status 4
May 29 19:59:11 ha-server vdr: [2296] timer 1 (61 1900-2000 VPS 'Cricket on 
5~England v Sri Lanka: Second Test Day Thr') stop

I haven't had a chance to take the server down to insert the power
monitor yet, but will do so at convenient time in the next few days

Thanks
Richard


On 27/05/2016 14:51, glenvt18 wrote:
> Yes, sure. The patch against VDR-2.2.0:
> http://pastebin.com/D4VQd1rG
>
> While testing set VDR log level to 3 (--log=3) and use this helper
> script to monitor your frontends:
> http://pastebin.com/uW4NW0rZ
>
> Don't forget to enable power saving in the Setup->LNB menu.
>
> If you don't have sudo (you're not on Debian or Ubuntu), remove it and
> run the script as root. It would be great if you could measure the
> power consumption of you tuners (at least the USB one).
>
> Best,
> Sergey Chernyavskiy.
>
> On Fri, May 27, 2016 at 09:59:06AM +0100, Richard F wrote:
>> I'd like to give it a go on DVB &

Re: [vdr] [PATCH] Device power saving feature

2016-05-30 Thread glenvt18
Could you attach (or, better, upload to pastebin.com) the whole log
file. Are you running vdr with --log=3? I need to see 'idle timer' debug
messages and some other debug stuff. Could you also apply this change

diff --git a/eitscan.c b/eitscan.c
index 3899e00..b1c8c13 100644
--- a/eitscan.c
+++ b/eitscan.c
@@ -159,7 +159,7 @@ void cEITScanner::Process(void)
Skins.Message(mtInfo, tr("Starting 
EPG scan"));
}
 }
- //dsyslog("EIT scan: device %d  source  
%-8s tp %5d", Device->DeviceNumber() + 1, 
*cSource::ToString(Channel->Source()), Channel->Transponder());
+ dsyslog("EIT scan: device %d  source  
%-8s tp %5d", Device->DeviceNumber() + 1, 
*cSource::ToString(Channel->Source()), Channel->Transponder());
  if (lastActivity == 0)
 // forced scan - set idle timer for 
each channel switch;
 // this prevents powering down while 
scanning a transponder
--

Thanks for testing.

Best,
Sergey Chernyavskiy.

On Mon, May 30, 2016 at 09:59:46AM +0100, Richard F wrote:
> Thanks - I built it and and have had it running for about 24 hours:
> 
> A couple of observations:
> I'm seeing this about every 30 - 60 mins as expected, but the timeout
> seems to be short - not the PowerdownTimeoutM (I assume minutes?) set at
> 15 in the config file
> 
> ...
>
> I haven't had a chance to take the server down to insert the power
> monitor yet, but will do so at convenient time in the next few days
> 
> Thanks
> Richard
> 
> 
> On 27/05/2016 14:51, glenvt18 wrote:
> > Yes, sure. The patch against VDR-2.2.0:
> > http://pastebin.com/D4VQd1rG
> >
> > While testing set VDR log level to 3 (--log=3) and use this helper
> > script to monitor your frontends:
> > http://pastebin.com/uW4NW0rZ
> >
> > Don't forget to enable power saving in the Setup->LNB menu.
> >
> > If you don't have sudo (you're not on Debian or Ubuntu), remove it and
> > run the script as root. It would be great if you could measure the
> > power consumption of you tuners (at least the USB one).
> >
> > Best,
> > Sergey Chernyavskiy.
> >
> > On Fri, May 27, 2016 at 09:59:06AM +0100, Richard F wrote:
> >> I'd like to give it a go on DVB & DVBT-2 tuners (1 PCI, 1 USB)
> >> Would you be kind enough to post a version for VDR2.20 or advise changes
> >> necessary?
> >>
> >> Thanks
> >> Richard
> >>
> >>
> >> On 26/05/2016 18:44, glenvt18 wrote:
> >>> For about a month now. Tested with 3 different DVB-S/S2 tuners with
> >>> VDR 2.3.1 and VDR 2.2.0 (requires minor changes to the patch) - rock
> >>> solid.
> >>> I don't have VPS, so I can't test it. The same is about DVB-T/C
> >>> tuners. After all, if something doesn't work this feature can be
> >>> disabled (and it is disabled by default),
> >>>
> >>
> >> ___
> >> 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 mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] "TS packets to determine frame type"

2016-05-30 Thread Richard F
Hi Klaus,

I'm 99% of the way to finishing my H264 ffmpeg transcoding script, I'm just 
getting 2 of these warnings when reindexing transcoded files

May 30 21:08:09 ha-server vdr: [31785] WARNING: required 5 video TS packets to 
determine frame type
May 30 21:08:09 ha-server vdr: [31785] WARNING: required 5 video TS packets to 
determine frame type

Sometimes the number is 4. Fortunately not over 6 yet.
Is this a functional problem ? (files play in everything I need them to).
I reduced the I-frame gap which also improves seeking performance, but that's 
not the issue.

Looking at the code I'm not quite sure what it's looking for - can you help?

I may be able to adjust codec / muxer to avoid warnings

Thanks
Richard


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr