vdr April 2005

vdr@linuxtv.org

148 participants
179 discussions

avoid using primary FF-card for reception
by Patrick Boettcher 10 Apr '05

10 Apr '05

Hi list, is there a way how to tell vdr to not use the primary FF-Card for reception, but only for MPEG2 decoding? My setup is as follows: - Siemens FF DVB-C card (ves1820). The reception qualitiy is more than bad, but I need it for viewing (attempts to use softdevice or df_xine were not satisfying). That's why I added a - Technisat CableStar (stv0297). With the same cable, I have every channel without BER and UNC. Is it possible to deactivate particular cards for reception in VDR? If not, where should I start looking in the code? Thanks for any help. best regards Patrick.

2 2

'Fake' FTA channels impossible to tune
by Luca Olivetti 10 Apr '05

10 Apr '05

VDR doesn't let you switch to a channel that you cannot decrypt. I usually like this feature, so I won't switch to a channel I cannot see, but today some channels at 28.5E are FTA (a sky promotion or a technical glitch?), even if they have a caid!=0, so I had to modify cDvbDevice::ProvidesCa to alway return true. I know that sky's to blame (or maybe they just don't want to advertise their channels as FTA), but maybe it should be a configurable option. Bye -- - Yo también quiero una Europa libre de Patentes de Software - - I want a Software Patents Free Europe too! And you? - --------------------------------------------------------------- EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es

4 6

Vdr error: vdr: no primary device found - using first device!
by ElChef 10 Apr '05

10 Apr '05

I ask to myself... mea culpa... I forget to install the frontend module, well, recompilng kernel again. So, as a root do: root@LinEspa:/usr/src/linux# make menuconfig And then the menu must show like this: Device Drivers ---> Multimedia devices ---> Digital Video Broadcasting Devices ---> [*] DVB For Linux <M> DVB Core Support --- Supported Frontend Modules <M> STV0299 based DVB-S frontend (QPSK) <==== THIS WAS THE GUILTY OF MY HEADACHES!!! Well, then exit -> exit -> Yes and now: root@LinEspa:/usr/src/linux# make root@LinEspa:/usr/src/linux# make modules_install root@LinEspa:/usr/src/linux# modprobe stv0299 root@LinEspa:/usr/src/linux# exit linespa@LinEspa:/usr/src/linux$ cd ~ linespa@LinEspa:~$ sh mi_vdr.sh YESSSSSS!!! YESSSS!!!! Finally it WORKS!! Thanks a lot to all the people that helps me!

1 0

Vdr error: vdr: no primary device found - using first device!
by ElChef 10 Apr '05

10 Apr '05

Well, after read in this thread: http://www.linuxtv.org/pipermail/vdr/2005-February/000055.html I try to load this modules: ves1x93 cx24110 grundig_29504-491 mt312 stv0299 Using modprobe, and always same result: root@LinEspa:/# modprobe ves1x93 FATAL: Module ves1x93 not found. root@LinEspa:/# modprobe cx24110 FATAL: Module cx24110 not found. root@LinEspa:/# modprobe grundig_29504-491 FATAL: Module grundig_29504_491 not found. root@LinEspa:/# modprobe mt312 FATAL: Module mt312 not found. root@LinEspa:/# modprobe stv0299 FATAL: Module stv0299 not found. I test dvb-ttpci module with this: root@LinEspa:/# modprobe dvb-ttpci -r root@LinEspa:/# modprobe dvb-ttpci --verbose insmod /lib/modules/2.6.8.1/kernel/drivers/media/dvb/ttpci/ttpci-eeprom.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/video/videodev.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/video/v4l2-common.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/video/v4l1-compat.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/common/saa7146.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/video/video-buf.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/common/saa7146_vv.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/dvb/dvb-core/dvb-core.ko insmod /lib/modules/2.6.8.1/kernel/drivers/media/dvb/ttpci/dvb-ttpci.ko And this is the kern.log: Apr 10 10:03:59 localhost kernel: Linux video capture interface: v1.00 Apr 10 10:04:00 localhost kernel: saa7146: register extension 'dvb'. Apr 10 10:04:00 localhost kernel: ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 5 (level, low) -> IRQ 5 Apr 10 10:04:00 localhost kernel: saa7146: found saa7146 @ mem d0994000 (revision 1, irq 5) (0x13c2,0x0003). Apr 10 10:04:00 localhost kernel: DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1). Apr 10 10:04:00 localhost kernel: Technotrend/Hauppauge PCI rev2.1 adapter 0 has MAC addr = 00:d0:5c:20:a6:e2 Apr 10 10:04:00 localhost kernel: gpioirq unknown type=0 len=0 Apr 10 10:04:00 localhost kernel: DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261d Apr 10 10:04:00 localhost kernel: DVB: AV7111(0) - firmware supports CI link layer interface Apr 10 10:04:00 localhost kernel: av7110(0): Crystal audio DAC detected Apr 10 10:04:00 localhost kernel: videodev: "av7110" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/ Apr 10 10:04:00 localhost kernel: saa7146_vv: saa7146 (0): registered device video0 [v4l2] Apr 10 10:04:00 localhost kernel: av7110: found av7110-0. Wich frontend I need? How I must install this module?

1 0

[PATCH] wapd-0.7a for vdr-1.3.23
by Anssi Hannula 09 Apr '05

09 Apr '05

Hi! This patch enables wapd-0.7a to compile under vdr-1.3.23. To be honest, I didn't quite understand the changed functionality, so someone might want to confirm that the patch is correct ;) -- Anssi Hannula

1 0

Re: [vdr] Re: vdr-burn-0.0.5: no free space
by admin LoLO 09 Apr '05

09 Apr '05

if I use this solution I have error message during gcc : main.c: Dans la fonction « main »: main.c:1658: error: `LC_ALL' undeclared (first use in this function) main.c:1658: error: (Each undeclared identifier is reported only once main.c:1658: error: for each function it appears in.) with #include<local.h> I have the same problem can you help me ? Timo Helkiö a écrit : >ma, 2004-12-13 kello 16:32 +0100, Ingo Janetzki kirjoitti: > > >>Hi, >> >>I'm running vdr 1.3.12 with the vdr-burn-0.0.5 plugin. I made a test >>DVD with a short recording (about 30 mins) and it worked without a >>problem. >> >>But my second try was not that succesful. I marked a really big >>recording (about 6 GB) for burning. But instead of shrinking I only >>got an error message about "... not enough space ...". I do not >>remember the exact message text. Which space is meant here? On the >>harddisk partition (for ISODIR) there are about 13 GB of free space. >>(I'm using the settings "DVD with menus" and "Only ISO image".) >>Or does the plugin need additional space somewhere else? >> >>Ingo >> >> >> > >Hi, this propably means, that your requant-program has same error as >mine (see log file). Requant is not working at all and iso-file does not >fit to dvd. >Requant expects to get the shrinking factor as a decimal number "." as >decimal separator like 1.23 and Burn gives it like 1,23 You can see it >by giving command > >"requant 1,23". > >If you get > >"Using 1.000000 as factor" > >that's the case > >I corrected it by adding "setlocale(LC_ALL,"fi_FI.ISO-8859-1");" to >main.c in M2VRequantizer-program like this: > >int main (int argc, const char * argv[]) >{ >setlocale(LC_ALL,"fi_FI.ISO-8859-1"); > uint8 ID, found; > >and compiling > > "gcc -o requant main.c -lm" > > Timo > > > > > > > >

2 2

Emergency exit if EPG scan timeout > 0
by Kartsa 09 Apr '05

09 Apr '05

If I have EPG scan timeout something else than 0 there will be emergency exit in vdr. And then it will stay in loop. Normally this happens´when a timed recording starts. timer 54 (5 1659-1810 'Farmarit') start Title: 'Farmarit' Subtitle: 'Sarja jatkuu' record /video/Farmarit/2005-04-08.16:59.50.99.rec creating directory /video/Farmarit creating directory /video/Farmarit/2005-04-08.16:59.50.99.rec recording to '/video/Farmarit/2005-04-08.16:59.50.99.rec/001.vdr' file writer thread started (pid=7499, tid=983050) recording thread started (pid=7500, tid=999435) receiver on device 2 thread started (pid=7501, tid=1015820) TS buffer on device 2 thread started (pid=7502, tid=1032205) ERROR: video data stream broken initiating emergency exit emergency exit requested - shutting down stopping plugin: subtitles recording thread ended (pid=7500, tid=999435) TS buffer on device 2 thread ended (pid=7502, tid=1032205) buffer stats: 0 (0%) used receiver on device 2 thread ended (pid=7501, tid=1015820) file writer thread ended (pid=7499, tid=983050) buffer stats: 0 (0%) used timer 54 (5 1659-1810 'Farmarit') stop saved setup to /video/setup.conf tuner on device 1 thread ended (pid=4769, tid=16386) removed client <=== lirc client receiver on device 1 thread ended (pid=7355, tid=950280) Section handler thread ended (pid=4770, tid=32771) tuner on device 2 thread ended (pid=4811, tid=49156) Section handler thread ended (pid=4812, tid=65541) deleting plugin: subtitles buffer stats: 19928 (10%) used exiting emergency exit! Then vdr restarts and loads all configurations starts the recording again and after about 30 seconds it stops again with the same error. And this does not happen if EPG scan timeout is 0. Is this a known bug (or is it bug?) and am I forgetting something? Oh, and I have vdr 1.3.23 with 2.6.10-1.737_FC3 using dvb drivers that come with the kernel. And I am in cable with two dvb-c cards. Although the problem is the same with one card. - Kartsa No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.5 - Release Date: 7.4.2005

2 1

vdr-1.3.23 cant set PID after playing DVD
by C.Y.M 09 Apr '05

09 Apr '05

Hi, It appears that VDR loses the ability to set PID's after I play a DVD in vdr-1.3.23. Has anyone else come across this problem? Apr 8 21:59:08 sid vdr[9049]: dvbplayer thread ended (pid=9049, tid=540680) Apr 8 21:59:08 sid vdr[4376]: switching to channel 10305 Apr 8 21:59:08 sid vdr[4376]: ERROR (dvbdevice.c,817): Invalid argument Apr 8 21:59:08 sid vdr[4376]: ERROR: can't set PID 5666 on device 1 Apr 8 21:59:08 sid vdr[4376]: ERROR (dvbdevice.c,829): Invalid argument Apr 8 21:59:08 sid vdr[4376]: ERROR: failed to set PIDs for channel 10305 on device 1 Apr 8 21:59:08 sid vdr[4376]: retrying Apr 8 21:59:08 sid kernel: dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff) Apr 8 21:59:08 sid kernel: dvb_demux_feed_del: feed not in list (type=0 state=0 pid=ffff) Apr 8 21:59:08 sid vdr[4376]: ERROR (dvbdevice.c,817): Invalid argument Apr 8 21:59:08 sid vdr[4376]: ERROR: can't set PID 5666 on device 1 Apr 8 21:59:08 sid vdr[4376]: ERROR (dvbdevice.c,829): Invalid argument Apr 8 21:59:08 sid vdr[4376]: ERROR: failed to set PIDs for channel 10305 on device 1 Apr 8 21:59:08 sid vdr[4376]: retrying Best Regards, C.Y.M.

1 0

dxr3plugin analog audio output with dvdplugin
by James Lamont 08 Apr '05

08 Apr '05

Hi All, Frustrated by the fact that dvd AC3 audio via the dxr3's analog output hasn't been working for a while I had a bit of a look into the source code and managed to get it going. I'm using vdr-1.3.21, dxr3plugin CVS (vdr-dxr3-0-2 branch) and dvdplugin latest CVS. The problem seems to be that the dxr3 plugin won't decode an LPCM audio stream. The dvd AC3 audio is downmixed to a PCM stream by the dvdplugin when UseDolbyDigital is set to "no" in vdr setup. My quick and dirty hack was to make a minor change in dxr3demuxdevice.c at around line 510. Here we have : else if (pesFrame.GetPesDataType() == cDxr3PesFrame::PES_PRIVATE_DATA && m_demuxMode != DXR3_DEMUX_VIDEO_ONLY_MODE && !cDxr3ConfigData::Instance().GetAc3OutPut() && !bAc3Dts) if we omit the check for bAc3Dts... else if (pesFrame.GetPesDataType() == cDxr3PesFrame::PES_PRIVATE_DATA && m_demuxMode != DXR3_DEMUX_VIDEO_ONLY_MODE && !cDxr3ConfigData::Instance().GetAc3OutPut()) // && !bAc3Dts) we get working analog audio from AC3 and PCM dvds. This isn't intended as a permanent fix since I'm assuming that the private stream always contains PCM data, if it doesn't vdr crashes immediately. Hopefully someone will write a proper patch to fix it soon.

1 0

VDR restart when recording a scrambled program
by Ondrej Wisniewski 08 Apr '05

08 Apr '05

It's been a while that I have noticed a strange behaviour and I am wondering if there is a workaround for this. In Italy there are some channels which are actually "free to air" but for some reason certain transmissions are scrambled. When switching to such a channel while the transmission is scrambled the screen becomes black and the "channel not available" message is displayed. So far so good. However if I program a timer for a program which is scrambled (it's usually not possible to know beforehand which transmission is scambled and which is not), VDR restarts when trying to record the program. After the restart the timer is still active and another restart is performed and so on. Why does VDR behave like this ? If the program cannot be recorded why does VDR restart ? Is this a driver problem ? I would expect that the recording stops and the timer is deleted. Can someone explain this and maybe propose a solution ? I am using VDR 1.3.17. Thanks, Ondrej

1 0

← Newer
1
...
10
11
12
13
14
15
16
17
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr April 2005