vdr August 2006

vdr@linuxtv.org

86 participants
78 discussions

vdr slow when syslogd running
by joern＠bredereck.net 07 Aug '06

07 Aug '06

Hi, I tried several vdr versions, but they all share the same problem on my Ubuntu (currentyl 6.06) box: vdr starts very slowly when the syslog daemon is running. The vdr bootup takes about 1-2 minutes with syslog running. After stopping the syslogd vdr starts in about 10 seconds and responds in no time. Has anybody heard of this problem and has some kind of clue how to fix it or to dig deeper in order to find the reason? Thanks! Joern

2 1

[ANNOUNCE] vdr-filebrowser-0.0.6
by Holger Brunn 07 Aug '06

07 Aug '06

Hello list, I'm glad to announce a new version of the filebrowser plugin, you can get it from http://www.stud.uni-karlsruhe.de/~uqg8/vdr/filebrowser/vdr-filebrowser-0.0.… Changelog: - Fixed Makefile for APIVERSION - Added the possibility to set a pin for certain commands (suggested by Ronny Kornexl, UI inspired by mailbox plugin) - Changed the demo for reusing filebrowser in other plugins (developers/filebrowserdemo) to build a static library, avoiding possible filename clashes - Fixed automatic scolling in thread's output menu - Fixed confirmation for commands that use a destination (%d or %D) Your comments, bug reports and patches would be appreciated, regards Holger

1 0

Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-3
by e9hack 06 Aug '06

06 Aug '06

Hi, after applying the patch, I get many entries (30 per second) in the syslog: Aug 6 23:20:23 very-new-darkstar vdr: [11415] ERROR (svdrp.c,84): Address already in use The HD-LED is flashing like during recording. - Hartmut

2 1

how to build working channels.conf?
by joern＠bredereck.net 06 Aug '06

06 Aug '06

Hello, Can anyone point me to a documentation that describes how to use "scan" (dvb-utils) to build a working channels.conf? Apparently the syntax of the channels.conf or the parameters of scan have changed over the years, because the parameters that used to work for me once don't do it anymore. :-( root@tuxhome:/video# dpkg -l | grep -i dvb-utils ii dvb-utils 1.1.0-9 Viewer programs for DVB cards I used the following command to scan Astra19.2: scan -o vdr -e 4 -s 1 -v /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E >> 19.2-scan.txt Here is a line of a working channels.conf: PREMIERE START,START;PREMIERE:11797:hC34:S19.2E:27500:255:256=deu:32:1722,1801,1702:8:133:2:0 And here is the line that scan just generated: PREMIERE START;PREMIERE:12070:h:S19.2E:27500:3071:3072=deu:32:1:8:1:1:0 The caid information and some other stuff that I can't figure out seem to be missing. :-( (Don't bother about the different frequencies. This channel changed about a week ago; that's one of the reasons why I need to do a new scan). Thanks for any help! Joern

2 2

vdr suggestions & osd colour oddity
by Chris Elsworth 06 Aug '06

06 Aug '06

Hello! I've just started using vdr 1.4.0 in Ubuntu and I have to say I'm extremely impressed and very happy with it - very nice work, well done to the author :) I have a couple of things I'd like to suggest and wonder if they'd be up for consideration. When viewing a channel, pressing Up/Down currently changes channel; would it be possible to allow these buttons to just show channel information (with now/next in) for the previous/next channels, allowing one to quickly view what is on the other channels? ie, I could keep pressing Up to go through the channels, seeing what is on now and next, but without actually changing channel - then press OK to change the channel once I find one to watch. I think it would also be nice if there were more than one rewind/fastforward speed, achievable by repeated pressing of the appropriate button; press ff once to ff at 2x speed, again for 4x speed, again for 8x speed? I'd like to have a go at adding these features myself but I've not read much of the code yet. I'll see how much I can decipher in due course, but maybe someone already did these, or they're planned. I'm suffering a problem that I have no idea how to fix, however - I've read the list archives and noted a few months ago that some posts were made about oddly-coloured OSD when using softdevice and nvidia cards. I believe this is the same problem that I currently see too; it only seems to happen with low resolution broadcasts - when the resolution drops below 640x480 or thereabouts, the OSD turns "pink" for me. On any channel with a higher resolution than this it's ok. I'm using an NVidia 7600 connected to a TV using softdevice/xv. The NVidia natively directs output to the TV since it's the only output device connected, so X is running on it at 1024x768 without any other special configuration. Changing the softdevice/hue to either 0 or 100 as was suggested in those previous posts did not fix the problem for me - I was wondering if anyone else had any tips on what I might try to fix this. thanks very much for any replies & advice, -- Chris

3 5

[ANNOUNCE] vdr-1.4.0 Alternative Channel Patch 0.0.3
by Jochen Noller 06 Aug '06

06 Aug '06

Hi all, I would like to submit the improved alternative channel patch for vdr 1.4.0. There was a problem with uninitialized variables with 0.0.2 which should be solved by taking directly the channel id instead of storing the channel id-string. What's the patch for: This patch add to vdr the function of an alternative channel for recordings. With this patch vdr will use the alternative channel for a recording whenever the original channel is not available (for example another recording on the same card on another transponder is running) What's the benefit: Now you can add an alternative record channel for a assumed better channel regarding the quality. In my case I use this for DVB-C channels and add as an alternative analogue channels. There is no recursive function in this patch! How to use the patch: Untar the attachement. There you will find two files. The patch an the configuration file for this feature. You have to put the configuration file to vdr's configuration directory (same directory, where the channels.conf is stored) and rename it to channel_alternative.conf. The next step is to patch the vdr-source like this: patch < vdr-1.4.0_AlternativeChannelPatch_0.0.3.diff There should be no rejects. After this you have to adapt the configuration file in the following manner: Add a line for each "alternative channel"-pair like this channel id of the original channel;channel id of the alternative channel The Patch will not affect live TV - at least at the moment. !!! ATTENTION !!! This patch manipulates directly the recording behaviour of vdr! Be careful and check your first recordings when you use alternative recording channels. Have fun. Regards, Jochen

1 0

[ANNOUNCE] VDR maintenance patch 1.4.1-3
by Klaus Schmidinger 06 Aug '06

06 Aug '06

VDR maintenance patch 1.4.1-3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-3.diff This is a 'diff' against version 1.4.1-2 (which is the official version 1.4.1, patched with ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff and ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-2.diff). Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply the above patch and report whether it works (or if it causes any new problems). This version requires plugins to be recompiled. The changes since version 1.4.1-2: - Fixed assigning schedules to channels in case there is no initial EPG information (thanks to Frank Schmirler). - Increased the APIVERSION to allow plugins that relied on the cStatus::MsgSetVolume() bug to react properly (suggested by Stefan Huelswitt). - Fixed cDevice::ToggleMute() (thanks to Christoph Haubrich). - Fixed deleting the last character of a string menu item in insert mode (thanks to Udo Richter). - The /video/.update file is now touched _after_ an editing process is finished in order to avoid excessive disk access (thanks to Artur Skawina). - Fixed handling the running status of EPG events before the currently running one, in case they are added after the current event (cont'd from version 1.4.1-2). - Modified the shutdown mechanism, so that the shutdown script is never given a time in the past (reported by Helmut Auer). If a timer is currently recording, or a recording would start within the next 30 minutes (default for the "Min. event timeout" setup parameter), and the user insists in shutting down now, the reboot time given to the shutdown script will correspond to a time that is "Min. event timeout" minutes (default is 30) in the future. - Avoiding shutdown message "Recording in ... minutes, shut down anyway?" with a negative number of minutes (reported by Udo Richter). - Fixed getting the next active timer when shutting down (thanks to Udo Richter). - Modified the cSVDRP::Close() function to avoid code duplication. Have fun! Klaus

1 0

2GB limit overcome?
by JikJikMan 05 Aug '06

05 Aug '06

Hi, How should I prevent vdr to split files in 2 GB files? Thanks. John.

4 3

(no subject) solved
by Alex Golks 05 Aug '06

05 Aug '06

yeah, this was it. i didn't get audio out of my alsadev, just because the vdr user wasnt in this audio group. Dec 25 12:17:03 gockels-video vdr: [5644] [softdevice-audio] Opening alsa device default Dec 25 12:17:03 gockels-video vdr: [5644] [softdevice-audio] Using alsa AC3 device hw:0,1 Dec 25 12:17:04 gockels-video vdr: [5666] [softdevice-audio] samplerate: 48000Hz, channels: #2 Dec 25 12:17:04 gockels-video vdr: [5666] [softdevice-audio] Period size 1024 Buffer size 9216 Dec 25 12:17:04 gockels-video vdr: [5666] [softdevice-audio] Hardware initialized thanks alot for helping! alex -- Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl

1 0

(no subject)
by Alex Golks 05 Aug '06

05 Aug '06

at first, thanks alot for the help. perhaps i "not see the wood for the trees" (is this right in english). wanna say, perhaps im just too stupid... here are some debuggin outputs, for just to be sure that alsa works for me: cat /dev/urandom >/dev/dsp works, get this funny white noise out of my speakers. alsamixer screen: ---------------------------------- Card: C-Media PCI CMI8738-MC6 Chip: CMedia PCI View: [Playback] Capture All Item: Master ---------------------------------- $ cat /proc/asound/devices 0: [ 0] : control 4: [ 0- 0]: hardware dependent 16: [ 0- 0]: digital audio playback 17: [ 0- 1]: digital audio playback 18: [ 0- 2]: digital audio playback 24: [ 0- 0]: digital audio capture 26: [ 0- 2]: digital audio capture 33: : timer $ cat /proc/asound/pcm 00-02: CMI8738-MC6 : C-Media PCI IEC958 : playback 1 : capture 1 00-01: CMI8738-MC6 : C-Media PCI 2nd DAC : playback 1 00-00: CMI8738-MC6 : C-Media PCI DAC/ADC : playback 1 : capture 1 -------------- without -ao: -------------- Dec 24 20:57:32 gockels-video vdr: [4525] [softdevice-audio] Opening alsa device default Dec 24 20:57:32 gockels-video vdr: [4525] [softdevice-audio] Using alsa AC3 device hw:0,1 Dec 24 20:57:33 gockels-video vdr: [4525] [softdevice-audio] Playback open error: default, No such device FATAL exiting -------------- with -ao alsa:pcm=default -------------- Dec 24 20:59:19 gockels-video vdr: [4698] [softdevice-audio] Opening alsa device default Dec 24 20:59:19 gockels-video vdr: [4698] [softdevice-audio] Using alsa AC3 device hw:0,1 Dec 24 20:59:19 gockels-video vdr: [4698] [softdevice-audio] Playback open error: default, No such device FATAL exiting -------------- with -ao alsa:pcm=default#ac3=default# -------------- Dec 24 21:01:37 gockels-video vdr: [4977] [softdevice-audio] Opening alsa device default Dec 24 21:01:37 gockels-video vdr: [4977] [softdevice-audio] Using alsa AC3 device hw:0,1 Dec 24 21:01:37 gockels-video vdr: [4977] [softdevice-audio] Playback open error: default, No such device FATAL exiting -------------- with -ao dummy: -------------- Dec 24 21:03:30 gockels-video vdr: [5290] [softdevice-audio-dummy] Device opened! Ready to play so, its true, i've no spdif output on this card. but when you can tell softdevice what $dev_name (as mentioned in the softdevice readme) it should use for ac3 output (for it insists on using this), where do i get the $dev_name from? my driver is called cmipci, doesn't work. /dev/dsp or audio doesn't work either... xine can do a down-mix, and i get sound from vdr with xine plugin for example. on the other hand, there was a time, when i had 5 speaker connected to this card and heard nice digital surround sound from a dvd. i just can't get the idea behind all this (did i said this things about my foolischness?) -- Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr August 2006