n Wed, Oct 20, 2021 at 10:04:26PM +0300, Marko Mäkelä wrote:
> Mon, Oct 18, 2021 at 11:44:32PM +0300, glenvt18 wrote:
> > What is the output of
> >
> >lsof | grep frontend
> >
> > when VDR is in the "idle" state?
>
> I produced some output f
What is the output of
lsof | grep frontend
when VDR is in the "idle" state?
On Sun, Oct 17, 2021 at 10:52:11PM +0300, Marko Mäkelä wrote:
> Tue, Oct 12, 2021 at 07:21:10PM +0300, glenvt18 wrote:
> > Here you can find an updated version of the patch:
> > https:
Hi.
Here you can find an updated version of the patch:
https://github.com/glenvt18/vdr/commits/vdr-2.4.6
On Mon, Oct 11, 2021 at 04:02:43PM +0100, Richard F wrote:
> Mon, Sep 13, 2021 at 08:51:05PM +0200, Martin Wache wrote:
> > So, back to the plan with the Raspberry Pi 2B. One probl
the way it was done with timers in 2.3.1.
Using cRecordings list index as a recording id is a bad idea. If a
recording is deleted between LSTR and DELR, the id passed to DELR might
not be valid anymore. In VDR-2.3.2 (and, probably, in 2.3.1 too) even
each subsequent DELR command in a series might
This was tested with Alpine Linux 3.5/musl-1.1.15/gcc-6.2.1/vdr-2.3.2.
While building for Alpine, add -lintl to LIBS:
echo 'LIBS += -lintl' >> Make.config
Some notes:
1. __attribute__((__format_arg__(n))) is supported since gcc-2.8 (1998).
2. freopen() can be reworked to work with musl if
.
>
> Regards,
>
> Richard
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
glenvt18
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
nt?
BTW. Device bonding itself is a nice VDR feature. Unfortunately I can't
test it (with 3+ devices) :(
On Tue, Dec 27, 2016 at 01:38:51PM +0100, Klaus Schmidinger wrote:
> On 22.12.2016 16:07, glenvt18 wrote:
> > I understand. But this code looks confusing (at least). And, just to
&
=
cDevice::GetDeviceForTransponder(Timer->Channel(), LIVEPRIORITY);
// Switch the device to the transponder:
if (Device) {
...
has no sense.
On Thu, Dec 22, 2016 at 02:56:10PM +0100, Klaus Schmidinger wrote:
> On 26.05.2016 17:58, glen
On Sat, Sep 24, 2016 at 11:57:51PM +0200, Klaus Schmidinger wrote:
> On 23.09.2016 16:59, glenvt18 wrote:
> > Hi folks,
> >
> > The code in cDevice::Action() (device.c:1588) which checks whether a
> > stream can be descrambled by a particular CAM relies on the hard-code
ramblingTimeout() which can return 0.
@Klaus, what is your opinion on that?
More info on this issue:
https://github.com/FernetMenta/vdr-plugin-vnsiserver/pull/74#issuecomment-249086037
--
glenvt18
___
vdr mailing list
vdr@linuxtv.org
https://www.linu
Hi Klaus,
Thanks for reviewing.
> > diff --git a/config.c b/config.c
> > index e5f5463..794c9f8 100644
> > --- a/config.c
> > +++ b/config.c
> > @@ -395,6 +395,9 @@ cSetup::cSetup(void)
> >PositionerSpeed = 15;
> >PositionerSwing = 650;
> >PositionerLastLon = 0;
> > + PowerdownEnable
I've renamed PowerDown() to PowerDownMode() as Lars suggested and
added a comment on IsTunedToTransponder().
Klaus, could you take a look at this please.
A copy of this patch:
http://pastebin.com/skxw80hN
VDR 2.2.0 version:
http://pastebin.com/JQLjMKvu
Add a newline to the end of a patch file d
ed the device's frontend must be opened
prior to zapping and kept open for a while (38 sec as you see in the
log). If you have power-related issues you're likely to see ioctl()
errors in the log and emergency exits after a recording starts (VDR will
Hi Richard,
As there are no debug messages in your log I tried to reconstruct some
of them (power-related) - see my comments. Note that an extra second is
added to all timeouts due to the 'greater than' comparison. It was done
on purpose to add some save margin. Power-saving looks to work OK. But.
y. So ~70Wh saving / day pays for ongoing SD recording
> compression and multi-TB historical library compression in about 3
> months. I free up a 1TB or so of RAID :-)
>
> Thanks
> Richard
>
>
> On 7/06/2016 14:45, glenvt18 wrote:
> > Hi Richard,
> >
> > U
D (USB2) and an old Leadtek DTV1000 T (PCI)
> for SD - both of which are super-reliable BTW.
>
> Obviously other tuners will vary, and if the PSU isn't the efficient 90%
> one like this, the savings will be marginally more.
>
> Richard
>
>
> On 2/06/2016 17:15, glenv
http://pastebin.com/DR4gUdZR
Now it prints timestamps and it's output can be searched and grep-ed.
Run it with '|tee' for several days.
Best,
Sergey Chernyavskiy.
On Thu, Jun 02, 2016 at 03:35:49PM +0100, Richard F wrote:
> On 1/06/2016 03:49, glenvt18 wrote:
> > >From
> I agree with you. I hope, dynamite was a little inspiration for you. :)
Yes, I used it for some time. Thanks a lot for your work, Lars!
> I plan (for several years now, sadly) to break out the udev-part of dynamite
> to make the vdr more dynamic in device
> management. The idle-part is a goo
ecording 16:15 to 16:45, other than
> that idle I can run it for longer if you need it, though it's creating
> a fair bit of log. I seem to get a lot of erroneous EPGsearch results
> at level 3, not sure why. http://pastebin.com/8DbYQdTX
>
> Let me know what it tells y
ery 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 th
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 wit
bled (and it is disabled by default),
Best,
Sergey Chernyavskiy.
2016-05-26 20:15 GMT+03:00 Richard F :
> Interesting.
> How long have you been running it / testing it?
> Have you tested with VPS timers enabled ?
>
> Thanks
> Richard
>
> On 26/05/2016 16:36, glenvt18 wrote:
>
32 bytes is not enough for multi-byte utf8 strings
Date string is truncated.
Please review,
Sergey Chernyavskiy.
---
PLUGINS/src/skincurses/skincurses.c | 2 +-
skinclassic.c | 2 +-
skinlcars.c | 2 +-
skinsttng.c | 2 +-
4 f
d->MaySwitchTransponder(Channel) is always false here
Please review,
Sergey Chernyavskiy.
---
device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/device.c b/device.c
index 18867cd..542d120 100644
--- a/device.c
+++ b/device.c
@@ -342,7 +342,7 @@ cDevice *cDevice::GetDevi
Hi folks.
This patch introduces a feature which allows an idle device (a device
which is not currently recording or streaming) to enter a power-down
mode after some period of time. Given two timeout values,
PowerdownTimeoutM and PowerdownWakeupH, it works like this: when a
device becomes idle, it
Yes, I too don't see how it can be harmful. In case you want to
collect statistics, I did it with this patch (for a single device):
http://pastebin.com/6NAVNMda
Best,
Sergey Chernyavskiy.
2016-03-20 16:07 GMT+03:00 Klaus Schmidinger :
> On 18.03.2016 22:14, glenvt18 wrote:
>
otice that the
max value is 1.6x higher in the case of vanilla VDR. So, the threshold
value of about 10 is OK.
Best,
glenvt18.
2016-03-14 19:05 GMT+03:00 glenvt18 :
> Hi Klaus,
>
> I've tested your patch on x86_64 and ARM (I picked the weakest HW I
> have). I've gathere
a bit scaring. How
about increasing the threshold value to, say, 10, or 500 * TS_SIZE
or even higher? In other words, treat delayed read() as a normal
operation, and not delayed one as an emergency case. I can test it on
x86_64 with 50-60 Mbit/s. What do you think of it?
Best,
glenvt18.
2016-03
st VDR 2.3.1, but it can be applied to VDR
2.2.0 as well.
Please review.
glenvt18
---
Index: b/device.c
===
--- a/device.c2015-09-18 01:04:12.0 +0300
+++ b/device.c2016-03-10 03:38:50.078400715 +030
29 matches
Mail list logo
