vdr June 2005

vdr@linuxtv.org

132 participants
147 discussions

Re: [vdr] firmware does not load
by Olaf Meltzer 18 Jun '05

18 Jun '05

Hi! Since this is my first message, have a look at my local equipment: Mobo : ASUS CPU : Athlon XP 2600 RAM : 512 MByte Video: nVIDIA GeForce MX/MX 400 (nVIDIA 3D driver) Sound: 1.) Onboard (inactiv) 2.) Soundblaster 16 digital (system and TV-sound) 3.) M-Audio Delta Audiophil 2496 (audio editing) TV : 1.) Hauppauge Nexus S (satellite) 2.) Terratec 1200 DVB-T PCI (terrestial) One and a half year ago or so I started my first vdr-installation on SuSE 8.2 and with the Hauppauge Nexus only, downloading the sources of dvb-driver, vdr and kvdr. Later, under SuSE 9.1 and now 9.3, I used the delivered system. The Hauppauge Nexus S was detected automatically. Now I bought the budget Terratec 1200 DVB-T PCI, which, as the VDR-WIKI told me, should be fine in conjunction with the fullfeatured Nexus. And it is! @leo The only dvb-ttpci-01.fw on my system is a symbolic link to one of the actual firmware-files /usr/lib/hotplug/firmware/dvb-ttpci-01.fw -> /usr/lib/hotplug/firmware/dvb-ttpci-01.fw-261d The other firmware-file resides in the same location /usr/lib/hotplug/firmware/dvb-ttpci-01.fw-261d I got the appropriate firmware for the Terratec through the help of a perl script 'get_dvb_firmware' located in /usr/src/linux/Documentation/dvb/ To access the local DVB-T channels in Hamburg, I filled the appropiate channels list from VDR-WIKI into my /etc/vdr/channels.conf Most of these stations come in clear, without one bouquet (NDR). But this in another message. Greetings -- Olaf Meltzer -- Olaf Meltzer, Im Fliederbusch 31, 22589 Hamburg Telefon +49-40-871146 Mobil +49-179-3669047 Fax: +49-40-871146 Email: olaf.meltzer(a)gmx.de

1 0

Low volume on Pro7 ?
by Harald Milz 17 Jun '05

17 Jun '05

Hi, is it just my setup or does Pro7 actually have a far lower volume than all other channels? I'm using Werner's 261d firmware with AC3overDVB from a FF 1.3 card over an optical SPDIF link into a home cinema system. While we're at that, has anyone been working on a limiter to keep the advertising blocks' volumes down? As most of you will know, the ad blocks have an average level 3 dB above the average level in the rest of the material. This is very annoying particularly after a low volume scene in a film. ... :-( Noad's algos could be helpful here. -- Justice is incidental to law and order. -- J. Edgar Hoover

14 41

Firmware 0x261e and DVD playback
by André Weidemann 17 Jun '05

17 Jun '05

Hello Werner, I was wondering whether or not you changed anything in the new firmware that improves the Pan&Scan problem inside menus we discussed a while ago. I just tried the latest firmware under vdr-1.3.23 with the CVS-version of the dvd plugin. But from what I could see the Pan&Scan option still does nothing more than a center-cut-out. Did you change anything in the firmware to improve the display? André.

3 4

Problem with vdr+softdevice
by Rose M 17 Jun '05

17 Jun '05

Hello, I'm trying to use vdr with softdevice but I only have this output when I run them: ./vdr -Psoftdevice [softdevice] processing args [softdevice] argv [0] = softdevice Segmentation fault I'm using Fedora Core 3 with kernel 2.6.11.11, I've tried the last version of softdevice and 0.1.0, but no changes. I've configurated softdevice with framebuffer and DirectFB, but both same results. Why it could happen? Any idea would be wellcomed, Thanks in advance, Rose M ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

replay audio record, fastrewind, play: firmware hangs
by Wolfgang Rohdewald 16 Jun '05

16 Jun '05

hi, I am using vdr 1.3.25 unpatched with the latest beta firmware 261e. This is what I get after having added a little bit more debug output showing the SubStreamType. The SubStreamType found varies. The record is not pre 1.3.19. This happens _only_ after fastrewind/play, fastforward/play works correctly. I'd say there is a bug in vdr which triggers a bug in the firmware (assuming the firmware should never hang on wrong input) Also, are those messages "SetBrokenLink..." really needed for pure audio records? vdr ignores timeouts on OSDSetBlock and similar functions. Shouldn't it rather do something like restart itself and the driver? (up to now the driver never returned error codes for these functions but the CVS drivers now do so) Jun 15 03:19:28 mm vdr[28881]: playing '/var/lib/video/ARD-Nachtkonzert/2005-04-15.02.04.50.50.rec/001.vdr' Jun 15 03:19:28 mm vdr[29121]: dvbplayer thread started (pid=29121, tid=147463) Jun 15 03:19:28 mm vdr[29121]: resuming replay at index 25211 (0:16:48.12) Jun 15 03:19:28 mm vdr[29122]: non blocking file reader thread started (pid=29122, tid=163848) Jun 15 03:19:28 mm vdr[29121]: SetBrokenLink: no video packet in frame Jun 15 03:19:28 mm vdr[29121]: setting audio track to 33 Jun 15 03:19:36 mm vdr[29121]: SetBrokenLink: no video packet in frame Jun 15 03:19:37 mm vdr[29121]: switching to pre 1.3.19 Dolby Digital compatibility mode,SubStreamType:176 Jun 15 03:19:37 mm vdr[29121]: setting audio track to 33 Jun 15 03:19:45 mm vdr[29121]: ERROR: incomplete PES packet write! Jun 15 03:19:46 mm kernel: dvb-ttpci: warning: timeout waiting in LoadBitmap: 0, 1 // -110 is -ETIMEDOUT Jun 15 03:19:46 mm kernel: dvb-ttpci: OSDSetBlock(): returns -110 Jun 15 03:17:33 mm vdr[27579]: SetBrokenLink: no video packet in frame Jun 15 03:17:35 mm vdr[27579]: SetBrokenLink: no video packet in frame Jun 15 03:17:35 mm vdr[27579]: switching to pre 1.3.19 Dolby Digital compatibility mode,SubStreamType:0 Jun 15 03:17:35 mm vdr[27579]: setting audio track to 33 Jun 15 03:17:37 mm vdr[27579]: SetBrokenLink: no video packet in frame Jun 15 03:18:32 mm vdr[27580]: non blocking file reader thread ended (pid=27580, tid=163848) Jun 15 03:18:33 mm vdr[27579]: dvbplayer thread ended (pid=27579, tid=147463) Jun 15 03:18:33 mm vdr[27517]: switching to channel 2 Jun 15 03:18:33 mm vdr[27973]: transfer thread started (pid=27973, tid=180231) Jun 15 03:18:33 mm vdr[27974]: receiver on device 1 thread started (pid=27974, tid=196616) Jun 15 03:18:33 mm vdr[27975]: TS buffer on device 1 thread started (pid=27975, tid=213001) // I believe this is a result of the above bug: Jun 15 03:18:37 mm vdr[27973]: clearing device because of consecutive poll timeouts Jun 15 03:18:38 mm vdr[27973]: clearing device because of consecutive poll timeouts Jun 15 03:18:39 mm vdr[27973]: clearing device because of consecutive poll timeouts -- Wolfgang

2 8

Remote control questions
by Rose M 16 Jun '05

16 Jun '05

Hello, I want to know what are the differences between rcu and lirc plugins? I'm using lirc in this moment and it works fine with hauppauge remote control but I'm interested in using other type remote control, is it possible? Could someone help me with this doubts? Thanks in advance, Rose M. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

[update] DeepBlue-0.1.4
by vdr＠pfroen.de 15 Jun '05

15 Jun '05

Hello List, I made a new release of the DeepBlue-skin and put it on my website (http://vdr.pfroen.de). There are no new graphical improvements, but hopefully a better performance. form the HISTORY: ----------- 2005-06-13 Version 0.1.4 - Convertet all textfiles with dos2unix - Optimized all images and logos for a better performance (thanks to Sascha Volkenandt for the hint and Michael Reinelt for the scripts) - Added some finish translations and a better view for finish recording-infos (thanks to Rolf Ahrenberg) --------------- Stefan

3 3

trouble with fast scrolling
by Wolfgang Rohdewald 15 Jun '05

15 Jun '05

crossposting since I am not sure where the problem is: vdr or firmware if I watch a channel with DD audio like ZDF (even if I only select the normal audio channel) and then do pagewise scrolling in the channel list (right or left arrow), vdr dies soon with Jun 15 07:00:52 mm vdr[10220]: clearing device because of consecutive poll timeouts if I increase the poll timeout from 100 to 1000 in cTransfer::Action(), I instead get this: Jun 15 07:11:33 mm vdr[18854]: buffer usage: 70% (tid=147463) Jun 15 07:11:34 mm vdr[18854]: buffer usage: 80% (tid=147463) Jun 15 07:11:34 mm vdr[18854]: buffer usage: 90% (tid=147463) Jun 15 07:11:34 mm vdr[18853]: clearing transfer buffer to avoid overflows if I watch a channel with only normal audio like RTL, all this does not happen, and scrolling is much faster. this is here with vdr 1.3.25, firmware 261d and 261e do the same. I could imagine that too much OSD drawing activity does not give the Nexus enough time to process fat DVB streams. Could the firmware be changed such that it gives the DVB stream processing higher priority than OSD drawing? Or should vdr add some artificial delay somewhere? -- Wolfgang

1 0

Problems with Mplayer plugin and VDR timers
by C.Y.M 15 Jun '05

15 Jun '05

I am using the latest release of the Mplayer Plugin (0.9.12) and when I play an mpeg with it, VDR will crash if a timer goes off while I am playing the file. I get the following error: Jun 14 14:07:14 sid vdr[12949]: switching to channel 182 Jun 14 14:07:14 sid vdr[14045]: transfer thread ended (pid=14045, tid=360458) Jun 14 14:07:14 sid vdr[12949]: buffer stats: 0 (0%) used Jun 14 14:07:14 sid vdr[12949]: ERROR (dvbdevice.c,819): Invalid argument Jun 14 14:07:14 sid vdr[12949]: ERROR: can't set PID 6437 on device 1 Jun 14 14:07:14 sid vdr[12949]: ERROR (dvbdevice.c,831): Invalid argument Jun 14 14:07:14 sid vdr[12949]: ERROR: failed to set PIDs for channel 182 on device 1 Does anyone else have this problem? I dont remember this error happening before, so I am wondering if it is driver/firmware related. I am using a FF card, so my first impression was it was related to the firmware. The problem persists with versions 0x261d and 0x261e. Best Regards,

2 3

master-timer list of usable channels ?
by Gregoire Favre 14 Jun '05

14 Jun '05

Hello, what's the way to tell master timer which channels that could be used ? Would it be possible to tell him to "only" use the channels 1 to 123 for example, as autopid could add some "not usable" channels after those ? Thank you very much, -- Gr\'egoire Favre

3 3

← Newer
1
...
5
6
7
8
9
10
11
...
15
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 June 2005