Hi,
Noticed minor bug in channel list when I added more groups to the list.
When the group name is the next line after the last one on the screen it
is not shown in the next page. One way to see the group name is to
scroll the list backwards till the group because it is not in the same
position anymore (this depends on the number of the channels in the list).
Br, Pasi
>> is there a way to determine, which recording is cutted while cutting
>> is in progress? I need this for my ExtRecMenu-plugin to avoid editing
>> this recording.
>Has nobody a useful idea for this problem?
Via VDR no, via Unix/shell use 'lsof' with VDR process ID & user fields to see open files. Probably process with open files "/video/AAA/001.vdr" and "/video/%AAA/.." is the cutting process => directory AAA is cutted to dir %AAA.
I think in Linux lsof is …
[View More]reading from proc so you could also do it directly from there.
Regards,
Jori
[View Less]
I am running vdr 1.4.1. Some days ago I found it running in the morning.
It hadn't shut down after a recording. Trying a manual shutdown gave the
error message:
"Recording in -244 minutes. Really shutdown?" (not this message exactly,
but the German version). Pressing "OK" did not work, I had to log in to
a console and to do a "shutdown -h".
Reason: /video was full, no recordings could be deleted, so VDR tried
in vain again and again to start the programmed recording.
Shouldn't VDR stop its …
[View More]well meant but useless efforts at the latest if
the event to record is over?
Wolfgang
[View Less]
I've got one PCI DVB device and two USB DVB devices. Sometimes vdr would
only find one device, even though the others seemed to be working OK.
I've now tracked down why.
vdr starts with /dev/dvb/adapterX/frontend0 where X = 0, increments X
until it can't access the device, and then stops looking. This is
probably the right way to do this but occasionally, I end up with the
following devices:
/dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/frontend2
/dev/dvb/adapter0/frontend3
I have yet …
[View More]to work out what causes this but I'm pretty sure it has to do
with the USB driver and hotplug which somehow manages to load and unload
the USB drivers several times in succession! Unplugging the USB devices
and rebooting sorts them back to how they should be, i.e. 0-2 but it's a
pain if I don't notice and I end up with lots of timer conflicts because
only one device has been found.
Obviously, this is a broken driver issue and vdr isn't really at fault but
is it worth allowing for a situation where a device may be 'missing' in
the sequence? Is there any simple way of determining how many devices
have been discovered, apart from looking in the log output, e.g. could
this info be added to the STAT SVDRP command or similar?
I doubt this is a common issue and I'm not really after a fix: just
thought others might find the info useful!
:)
Cheers,
Laz
[View Less]
Hi all -- I did an OS update today and it seems to have broken a few
things. In particular it might be related to GCC being 4.1.1 now.
Here's the error:
ccache g++ -fPIC -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD
-DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
-DVIDEODIR=\"/video0\" -DPLUGINDIR=\"./PLUGINS/lib\" -DVFAT
-I/vdr/DVB/include config.c
menuitems.h:23: error: extra qualification 'cMenuEditItem::' on member
'SetValue'
I was also getting a bunch of …
[View More]errors from plugins but I will deal with
each problem one at a time since I'm not sure if they are related yet.
Any help is greatly appreciated.
Norm
[View Less]
Works nicely. Thanks Christian.
----------------------------------------------------------------------------
REAL PORTION of Microsoft Windows code:
while (memory_available) {
eat_major_portion_of_memory (no_real_reason);
if (feel_like_it)
make_user_THINK (this_is_an_OS);
gates_bank_balance++;
Hi folks,
I asked it some time ago but got no answer so I try it again:
is there a way to determine, which recording is cutted while cutting is
in progress? I need this for my ExtRecMenu-plugin to avoid editing this
recording.
Greets,
Martin
Hi,
It think there is a bug in cPipe::Open() :
if (strcmp(Mode, "r") == 0) {
mode = "r";
iopipe = 1;
}
close(fd[iopipe]);
f = fdopen(fd[1 - iopipe], mode);
if ((f = fdopen(fd[1 - iopipe], mode)) == NULL) {
LOG_ERROR;
close(fd[1 - iopipe]);
}
Seems to be a double fdopen(), leaking some memory/stream
descriptor.
Regards.
--
Stefan Huelswitt
s.huelswitt(a)gmx.de | http://www.muempf.de/
There seem to be a few hardcoded values for PAL in VDR's source code. Klaus, can
you tell me if any of these would make a difference to a NTSC only system? I
know that most tv's in Europe can do both NTSC and PAL. Unfortunately, almost
all the tv's in America only support NTSC and cant handle the PAL formats.
BR.