vdr February 2008

vdr@linuxtv.org

148 participants
104 discussions

Wakeup methods
by Kartsa 13 Feb '08

13 Feb '08

What different wakeupmethods are there? I've built a few vdr boxes and I've been forced to use different motherboards and they do not all work the same. I've used nvram-wakeup on some and acpi on others when nvram-wakeup has not worked. Now I have Biostar 945GZ 775 SE with which I'm having trouble in starting on timers. What methods are people using with VDR? \\Kartsa

8 14

Wakeup methods
by Tero Purra 13 Feb '08

13 Feb '08

>So some say wakeup must be enabled in bios and some that it must be >disabled. Tried both with writing twice to /proc/acpi/alarm. Still no luck. > >Any other suggestions? Anybody? > >\\Kartsa I had to disable "update HWCLOCK at shutdown" -feature before ACPI wakeup started to work. I'm using gentoo and the feature is found /etc/conf.d/clock # If you want to set the Hardware Clock to the current System Time # during shutdown, then say "yes" here. CLOCK_SYSTOHC="no" br: tero

3 2

trouble changing Setup variables from Plugin.
by sundararaj reel 12 Feb '08

12 Feb '08

Hi, I change a VDR's setup setting from inside a plugin like: ::Setup.UseSmallFont = 0; ::Setup.Save(); // commit the change to setup.conf This is done only when the plugin's setting is changed. ( in the Store() ). When changes are accepted with OK, the setup.conf is written but it is immediately overwritten by a Setup.Save() call from cMenuSetupBase::Store(). How can I avoid this ? Is there a more orderly way to modify VDR's setup settings ? -- Sundararaj

2 2

CoreAVC + xineliboutput
by Per Mellander 11 Feb '08

11 Feb '08

I have done all the patching to xine-lib, ( patch from coreavc-for-linux-read-only + additional from happysat ). Then I've put CoreAVCDecoder.ax in /usr/lib/win32. I'm running VDR with xineliboutput. -P "xineliboutput --fullscreen --local=sxfe --audio=alsa --remote=none" What more do I have to do, ( extra arguments etc. ) to use CoreAVC? When I start VDR now I can't see any difference from using ffmpeg. .... load_plugins: plugin /usr/local/lib/xine/plugins/1.1.9/xineplug_dmx_nsv.so found load_plugins: plugin /usr/local/lib/xine/plugins/1.1.9/xineplug_decode_a52.so found video_out_xv: using Xv port 275 from adaptor NV17 Video Texture for hardware colour space conversion and scaling. video_out_xv: this adaptor supports the yuy2 format. video_out_xv: this adaptor supports the yv12 format. audio_alsa_out : supported modes are 8bit 16bit 24bit 32bit mono stereo (4-channel not enabled in xine config) (4.1-channel not enabled in xine config) (5-channel not enabled in xine config) (5.1-channel not enabled in xine config) (a/52 and DTS pass-through not enabled in xine config) xine: found input plugin : VDR (Video Disk Recorder) input plugin input cache plugin disabled xine: found demuxer plugin: DVD/VOB demux plugin video_out_xv: VO_PROP_INTERLACED(1) av_offset=0 pts video_out_xv: VO_PROP_ZOOM_X = 100 prebuffer=14400 pts prebuffer=14400 pts prebuffer=14400 pts prebuffer=14400 pts prebuffer=14400 pts video: synced early prebuffer=14400 pts prebuffer=14400 pts video: synced early prebuffer=14400 pts prebuffer=14400 pts video: synced early [h264 @ 0x11c43f0]non existing PPS referenced [h264 @ 0x11c43f0]decode_slice_header error [h264 @ 0x11c43f0]non existing PPS referenced [h264 @ 0x11c43f0]decode_slice_header error ....

10 57

trouble with asprintf
by Wolfgang Rohdewald 11 Feb '08

11 Feb '08

Hi, I am making the muggle plugin work with UTF-8 and have a little problem: since asprintf leads to segfaults if feeded with incorrect UTF-8 characters, I wanted to write a wrapper function which would then check the return value of asprintf. However I have a problem with the variable argument list and the va_* macros. Using gdb shows that, in the following example, in res=asprintf (strp, fmt, ap); ap is interpreted not as a list of arguments but as an integer. What is wrong here? BTW I am quite sure that vdr will sometimes coredump since it never checks the return value of asprintf. One suspect would be if somebody used a latin1 charset and had special characters like äöü in file names and then changes to utf-8 without converting file names to utf-8. If vdr then passes such a file name to asprintf, corrupted memory results. Might be difficult to debug remotely. #include <stdarg.h> #include <stdio.h> #include <string.h> int msprintf(char **strp, const char *fmt, ...) { va_list ap; int res; va_start (ap, fmt); res=asprintf (strp, fmt, ap); va_end (ap); } int main() { char *buffer; asprintf(&buffer,"test: %d\n",5); write(1,buffer,strlen(buffer)); free(buffer); msprintf(&buffer,"test: %d\n",5); write(1,buffer,strlen(buffer)); free(buffer); } -- Wolfgang

5 15

Old schedule / old timers
by UseNet-Posting-Nospam-74308-＠zocki.toppoint.de 11 Feb '08

11 Feb '08

Hello after upgrading from 1.4.3 to 1.4.5 i found that the schedule does not contain any old events. The current event is marked, but it is always the top of the list. What's the sense of tagging the current, when it's always at the top line and can't be scrolled "back"? That is very annoying because i sometimes found a programm worth to be timed, but the schedule entry is not available anymore. Too, long time ago "one time timers" were not deleted automatically. That has the advantage that if i found that "one time" worth to be recorded again, it was easy by editing that old "used" one time timer. Manually deleting the superflous "used" timers was much easier than to wait for EPG to show that event in future. How i can, user, select this featuers? - EPG history (at least) 4 hours, 1 day or 2 days "back" - Manually delete one timer timers/delete after 7 days/4 weeks Rainer

3 2

disable stk webcam
by serge pecher 11 Feb '08

11 Feb '08

Hello, I am trying to configure a new vdr streaming client. As 1.5.14 needs the multiproto driver, I did download it from Mercurial. When I compile I get an error about "stk-webcam" I found that one of the solutions was to disable this webcam in make menuconfig. My problem is that I can't find any driver looking to have something to do with stk-webcams. Can anyone tell me where to find the driver I have to disable ? I am using kubuntu 7.04 wit a 2.6.20 kernel Thanks a lot, Serge

1 0

vdr-xine "buffer usage:" messages
by Simon Baxter 11 Feb '08

11 Feb '08

Hi I run vdr-xine with the following syntax: xine --fullscreen -r anamorphic --hide-gui -V xv -A alsa -D --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes The "post" options seem to cause a continuous stream of the following messages: buffer usage: 62, 0, 7, 0, 0x94aa6f8 buffer usage: 101, 0, 6, 1, 0x94aa6f8 buffer usage: 86, 0, 7, 1, 0x94aa6f8 buffer usage: 75, 0, 7, 0, 0x94aa6f8 buffer usage: 95, 0, 7, 4, 0x94aa6f8 buffer usage: 85, 0, 6, 0, 0x94aa6f8 Is there some sort of debugging turned on? How do I stop these messages?

4 3

Transfer-Mode without remux
by Klaus Schmidinger 10 Feb '08

10 Feb '08

In a crude attempt to run VDR's Transfer-Mode without using a cRemux (and thus avoiding all the extra buffering and processing) I am trying to send the payload of the TS packets directly to the device. The attached patch implements cDevice::PlayTS() and handles video and audio packets with fixed PIDs (just for testing). I do get audio and video (using a FF-DVB card as output device), but there are some distortions. From all the debug output I've made there doesn't seem to be anything wrong - even the TS continuity counters check out (except for the initial one, which is to be expected). Am I missing something obvious here? Maybe somebody on the list can find out what's wrong here - or can argue why this attempt can't work in the first place. If you try the patch, just change the hardcoded PIDs in cDevice::PlayTS() to whatever video and audio PID the channel has you're going to test with. Klaus

4 7

Problem with VDR 1.5.14 and FF card version 2.1 card and channels with high bitrate
by Magnus Andersson 10 Feb '08

10 Feb '08

Hello! I have problems with channels that uses high bitrate on Thor 1W. A few channels uses between 10-11 Mbit/s mpeg2 and if I use tv-out from FF card vdr 1.5.14 the picture glitches and the remote response becomes really slow. It can take 10 seconds or more to change channel. There are no problems if I use xineliboutput and vdr 1.5.14 or channels with low bitrate. VDR 1.4.7 is ok with both xinliboutput plugin and tv-out from FF card so my question is how to log this? I start vdr with option -l 3 but there is nothing in the log. vdr 1.5.14 patches: vdr-1.5.14-liemikuutio-1.17.diff vdr-1.5.14-ttxtsubs-0.0.5.diff vdr-1.5.14-dvb-api-emulate-0.1.diff I have seen this in earlier versions of 1.5 so it is not related to 1.5.14 only. /Magnus

4 9

← Newer
1
...
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2008