vdr

vdr@linuxtv.org

6731 discussions

vdr 1.4.1: Confused after /video full
by Wolfgang Fritz 25 Jun '06

25 Jun '06

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 well meant but useless efforts at the latest if the event to record is over? Wolfgang

4 5

DVB device discovery at startup
by Laz 25 Jun '06

25 Jun '06

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 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

3 4

OS Upgrade left VDR broken...
by Mlists 24 Jun '06

24 Jun '06

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 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

2 3

Seperate lgo file ?
by Pierre-Yves Paranthoen 24 Jun '06

24 Jun '06

Hi all Is there a way to get vdr infos displayed on the run console in a seperate log file instead of syslog ? Tnx Pierre

2 1

multiple dvb cards
by Pierre-Yves Paranthoen 24 Jun '06

24 Jun '06

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++;

1 0

How to determine which recording is cutted
by Martin Prochnow 24 Jun '06

24 Jun '06

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

2 3

Possible bug in cPipe
by s.huelswitt＠gmx.de 24 Jun '06

24 Jun '06

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/

2 1

hardcoded NTSC/PAL values in VDR?
by C.Y.M 23 Jun '06

23 Jun '06

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.

6 9

vdr-xine pvrinput audio stuttering ??
by Simon Baxter 23 Jun '06

23 Jun '06

Hello. I've just managed to get my vdr-1.4.0, pvrinput (PVR-150), ivtv 0.6.3 and entirely NTSC system working here in the US, after weeks of diagnosis, hardware replacement, home-grown patches and help from multiple lists <cheers from crowds> :) I have another problem. VDR recordings are fine, but playing live TV through vdr-xine I get an audio stutter every 2 seconds or so. There are no errors on std-out or in the logs. Any ideas?

2 1

Re: vdr-xine pvrinput audio stuttering ??
by Martin Dauskardt 23 Jun '06

23 Jun '06

Hi Simon, you could try the following: in device.c from pvrinput: change codec.stream_type = IVTV_STREAM_PS; // IVTV_STREAM_DVD_S2 to codec.stream_type = IVTV_STREAM_DVD_S2 // IVTV_STREAM_PS; Andreas Kool switched to this stream in analogtv : // for PES, we now uses IVTV_STREAM_DVD_S2, not IVTV_STREAM_PS (XP MediaCenter edition uses it too) codec.stream_type = (s.mpeg_encoder == PVRTS) ? IVTV_STREAM_TS : IVTV_STREAM_DVD_S2; and this solved a stuttering problem with analogtv-plugin. I don´t know why the author of pvrinput decided to use IVTV_STREAM_PS, but I must say that I have no stuttering with both streams. But I think it`s worth a try.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr