vdr

vdr@linuxtv.org

6731 discussions

[ANNNOUNCE] tvonscreen plugin for VDR 1.4.1
by Jürgen Schmitz 20 Jun '06

20 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! It took its time, now here it is, the official tvonscreen plugin for VDR 1.4.x. <http://www.js-home.org/vdr> This plugins shows the EPG data in the typical way a TV magazine does. The channels are shown from left to right, 3 on one screen. You can scroll though the channels and the time, create timers, show details, search for events and add vdradmin auto timers. Jürgen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFElwQG5D0yJ3ikF4QRAiUwAJ9HnyFDsfAQEi2zSRj9MBRr0vBHyQCZAUFf oqfbfR9EWEencgeUGLJcfJY= =uttx -----END PGP SIGNATURE-----

4 3

Re: [vdr] VDR Help - Xine Engine error
by Mike 20 Jun '06

20 Jun '06

On Tuesday 20 June 2006 18:35, Gulab Chandra Yadava wrote: > Hi Mike > Still I have the same problem. ok... > Can u tell what does **8 xine vdr:/tmp/vdr-xine/stream#demux:mpeg_pes > *** mean ???????? it tells xine to use the vdr plugin, and hands it the location of a pipe, which the vdr plugin creates when it starts.... > Does any directory needs to created as /tmp/vdr-xine ... ????? no, the plugin will do that itself I think. > Can u tell me any command line option to record stream through VDR > ???????? whenever I am able record thrugh dvb-apps. > I think maybe you havent setup vdr. you need to create a vdr channels.conf for it to work. if you use the dvb-apps to create a channels.conf, use the -o vdr option to create a vdr compatible file, then put it in the /video directory and restart vdr. Cheers Mike > > --Thanks and Regards > Gulab Chandra Yadava > > > -----Original Message----- > From: Mike [mailto:mike@secnet.net.au] > Sent: Tuesday, June 20, 2006 1:23 PM > To: Gulab Chandra Yadava > Subject: Re: [vdr] VDR Help - Xine Engine error > > Hi > > On Tuesday 20 June 2006 17:13, Gulab Chandra Yadava wrote: > > Hi > > I run > > # vdr -Pxine in one console > > > > # xine 'vdr:tmp/vdr-xine/stream#demux:mpeg_pes in other console (or # > > xine -p -s vdr) > > > > I get xine osd and I found screen is displayed with following error > > (If > > > I click on VDR button) > > <snip> > > > - xine engine error - > > There is no input plugin available to handle > > 'vdr:tmp/vdr-xine/stream#demux:mpeg_pes' > > this is caused by the fact that there is a missing forwardslash after > the vdr. > it ought to be: xine vdr:/tmp/vdr-xine/stream#demux:mpeg_pes > > <snip> > > > And in /var/log/messages > > > > ERROR: 13890 ring buffer overflows (2611320 bytes dropped) > > > > (similar message keeps on repeating) > > hmm.. dont know about this one.... sorry. > > > Can anybody suggest me what wrong with vdr and vdr-xine. > > Regards > Mike > > > Gulab Chandra Yadava > > > > ______________________________________________________________ > > DISCLAIMER: > > This electronic message, and any attachments to this electronic > > message are > > > intended for the exclusive use of the addressee(s)named herein and may > > contain legally privileged and confidential information. It is the > > property > > > of Celstream Technologies Pvt. Ltd. If you are not the intended > > recipient, > > > you are hereby strictly notified not to copy, forward, distribute or > > use > > > this message or any attachments thereto. If you have received this > > message > > > in error, please delete it and all copies thereof from your system and > > notify the sender at Celstream Technologies or > > administrator(a)celstream.com > > > immediately > > _______________________________________________________________

1 0

xineliboutput plugin: how to control vdr from xine-ui?
by Eckhart Guthöhrlein 20 Jun '06

20 Jun '06

Hi, I am using the xineliboutput plugin: vdr -P"xineliboutput --nolocal --remote=37890" and then connect to vdr from xine-ui with xine "xvdr://127.0.0.1:37890#nocache;demux:mpeg_block" as described in the plugin readme (http://users.tkk.fi/~phintuka/vdr/vdr-xineliboutput/README). This works, in principle, but I cannot control vdr via the keyboard from within xine, although it should work out of the box according to the docs. I have configured the keys both in vdr and in xine, so this cannot be the problem. Using the vdr-sxfe frontend that comes with the plugin, keyboard control works. Of course, I would prefer using xine-ui with all its functions. Can anybody give me a hint what's wrong or missing? Thanks in advance, Eckhart

4 11

[PATCH] vcd plugin
by Halim Sahin 20 Jun '06

20 Jun '06

Hello, I found no patches for the vcd plugin to get it work with vdr-1.4.x So I tried to make one. Here it is Best regards Halim -- Halim Sahin E-Mail: halim.sahin(a)t-online.de

2 1

[ANNNOUNCE] timeline plugin for VDR 1.4.1
by Jürgen Schmitz 19 Jun '06

19 Jun '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! It took its time, now here it is, the official timeline plugin for VDR 1.4.x. <http://www.js-home.org/vdr> Shows a timeline of all programmed timers per day and informs you of timer conflicts: - - record transmissions at the same time and - - transmissions are on different channels (on different frequencies) and - - there are not enough input devices Jürgen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFElwQL5D0yJ3ikF4QRAic1AJ474rjfoBI17I54wDk8CIH2i3bfrwCfbE/6 u9RNqKiVBM4Qn81+P83Gavk= =ZKVQ -----END PGP SIGNATURE-----

1 0

vdr-1.4.1: bug report and fix: ReadLink with relative targets
by Patrick Cernko 19 Jun '06

19 Jun '06

Hi Klaus, hi list, today I discovered that the ReadLink function (used in e.g. cSafeFile) does not handle relative links correctly. I used a symlinked channels.conf like that: errror@ds9:/var/lib/vdr> ll channels.conf lrwxrwxrwx 1 errror vdr 20 2006-06-12 00:03 channels.conf -> channels.conf.normal but vdr tried to write to channels.conf.$$$ in its current working directory ("/") which failed. :-( The bug is caused by the ReadLink function which always took the unchanged value of the found link as target (without prepending the links path for relative links). As a fix, I added a check for relative links (== not starting with a '/') and prepend the directory of the symlink. For that purpose I use some small parts from the coreutils "dirname" program as I learned for a long time that doing something so easy as computing the directory part of a path can lead to several errors if not done right. :-) Appended you find the patch, which makes vdr handle relative symlinks correctly. @Klaus: Feel free to review/reduce the code but pay attention to the special cases! ;-) So long, -- Patrick Cernko | mailto:errror@errror.org | http://www.errror.org "Hello, Tech Support? How do I set my laser printer to stun?" (anonym) --- vdr-1.4.1.orig/tools.c +++ vdr-1.4.1/tools.c @@ -478,6 +478,99 @@ return -1; } +// BEGIN: taken from coreutils-5.2.1: dir_name() & base_name() functions and helpers +#include <stddef.h> +#include <stdlib.h> +#include <string.h> + +#if FILESYSTEM_ACCEPTS_DRIVE_LETTER_PREFIX +# define FILESYSTEM_PREFIX_LEN(Filename) \ + ((Filename)[0] && (Filename)[1] == ':' ? 2 : 0) +#else +# define FILESYSTEM_PREFIX_LEN(Filename) 0 +#endif + +#if FILESYSTEM_BACKSLASH_IS_FILE_NAME_SEPARATOR +# define ISSLASH(C) ((C) == '/' || (C) == '\\') +#else +# define ISSLASH(C) ((C) == '/') +#endif + +/* In general, we can't use the builtin `basename' function if available, + since it has different meanings in different environments. + In some environments the builtin `basename' modifies its argument. + + Return the address of the last file name component of NAME. If + NAME has no file name components because it is all slashes, return + NAME if it is empty, the address of its last slash otherwise. */ + +char * +base_name (char const *name) +{ + char const *base = name + FILESYSTEM_PREFIX_LEN (name); + char const *p; + + for (p = base; *p; p++) + { + if (ISSLASH (*p)) + { + /* Treat multiple adjacent slashes like a single slash. */ + do p++; + while (ISSLASH (*p)); + + /* If the file name ends in slash, use the trailing slash as + the basename if no non-slashes have been found. */ + if (! *p) + { + if (ISSLASH (*base)) + base = p - 1; + break; + } + + /* *P is a non-slash preceded by a slash. */ + base = p; + } + } + + return (char *) base; +} + +/* Return the length of `dirname (PATH)', or zero if PATH is + in the working directory. Works properly even if + there are trailing slashes (by effectively ignoring them). */ +size_t +dir_len (char const *path) +{ + size_t prefix_length = FILESYSTEM_PREFIX_LEN (path); + size_t length; + + /* Strip the basename and any redundant slashes before it. */ + for (length = base_name (path) - path; prefix_length < length; length--) + if (! ISSLASH (path[length - 1])) + return length; + + /* But don't strip the only slash from "/". */ + return prefix_length + ISSLASH (path[prefix_length]); +} + +/* Return the leading directories part of PATH, + allocated with xmalloc. + Works properly even if there are trailing slashes + (by effectively ignoring them). */ +char * +dir_name (char const *path) +{ + size_t length = dir_len (path); + int append_dot = (length == FILESYSTEM_PREFIX_LEN (path)); + char *newpath = (char*) malloc (length + append_dot + 1); + memcpy (newpath, path, length); + if (append_dot) + newpath[length++] = '.'; + newpath[length] = 0; + return newpath; +} +// END: taken from coreutils-5.2.1 + char *ReadLink(const char *FileName) { char RealName[PATH_MAX]; @@ -489,7 +582,20 @@ else // some other error occurred LOG_ERROR_STR(FileName); } - else if (n < int(sizeof(RealName))) { // got it! + else + if (RealName[0] != '/') { // relative symlink, we must prepend the path of FileName + char* dirname = dir_name(FileName); + size_t dirnamelen = strlen(dirname); + char linkval[n+1]; + memcpy(linkval, RealName, n); + memcpy(RealName, dirname, dirnamelen); // first prepend the path of FileName + RealName[dirnamelen] = '/'; + memcpy(RealName+dirnamelen+1, linkval, n); // append the gotten n bytes from the link value + n += 1 + dirnamelen; + free(dirname); + free(linkval); + } + if (n < int(sizeof(RealName))) { // got it! RealName[n] = 0; TargetName = RealName; }

2 5

vdr -help: syntax for timers.conf and reccmds.conf
by Gulab Chandra Yadava 19 Jun '06

19 Jun '06

Hi For vdr-1.3.43 Linux Kernel version -2.6.16 I believe that VDR reads timers.conf and reccmds.conf to record. Can anybody tell me syntax for these files with example. My VDr does not show any OSD and I am using Budget card. So How to record stream from console. And what is the location for recorded file. --Thanks and Regards Gulab ______________________________________________________________ DISCLAIMER: This electronic message, and any attachments to this electronic message are intended for the exclusive use of the addressee(s)named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof from your system and notify the sender at Celstream Technologies or administrator(a)celstream.com immediately _______________________________________________________________

2 1

USA channels.conf for analog 'pvrinput'
by Simon Baxter 18 Jun '06

18 Jun '06

Hi. I'm running vdr-1.4.0 with pvrinput-0.1.1 and can't get any sound, or a clean picture. All channels configured tune ok, but they have the top 2/3rds of the screen black & white with flickering distortion, a fuzzy bar below that and what looks like the remaining top of the picture, below that. here's a bunch of my channels: 4 KOMO;KOMO:67250:C0I0:C:0:301:300:305:A1:12003:1:1089:0 5 KING;KING:77250:C0I0:C:0:301:300:305:A1:12003:1:1090:0 6 KONG;KONG:83250:C0I0:C:0:301:300:305:A1:12003:1:1091:0 7 KIRO;KIRO:175250:C0I0:C:0:301:300:305:A1:12003:1:1092:0 8 DSCP;DSCP:181250:C0I0:C:0:301:300:305:A1:12003:1:1093:0 9 KCTS;KCTS:187250:C0I0:C:0:301:300:305:A1:12003:1:1094:0 10 KTWB;KTWB:193250:C0I0:C:0:301:300:305:A1:12003:1:1095:0 (I gather the last 4 fields are arbitrary?) the frequencies I obtained from ivtv-tune -l 4 67.250 5 77.250 6 83.250 7 175.250 8 181.250 9 187.250 10 193.250 also, if I set the 3rd field to C0I999 (PAL) it has no affect. If I set it to C0I1 (SECAM) it says 'can't start transfer mode' - which is what I would expect. if I use ivtv, it works fine with freevo and mplayer: [vdruser@media vdr-1.4.0]$ ivtv-tune -c4 /dev/video0: 67.250 MHz (Signal Detected) Am I doing this right?

2 4

[ANNOUNCE] VDR maintenance patch 1.4.1-1
by Klaus Schmidinger 18 Jun '06

18 Jun '06

VDR maintenance patch 1.4.1-1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.1-1.diff This is a 'diff' against the official version 1.4.1. 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 to the original VDR version 1.4.1 and report whether it works (or if it causes any new problems). This version is binary compatible to the previous version, so plugins don't need to be recompiled. The changes since version 1.4.1: - Added "-fPIC" to the compiler options in Make.config.template when compiling plugins (thanks to Udo Richter). If you use your own Make.config file, you may want to add these lines there, too. - Added some comment to cDevice::GetDevice() to explain how the individual conditions are put together to make a decision on which device to use. - Updated 'S13E' in 'sources.conf' (thanks to Antti Hartikainen). - Now making sure VPS timers don't get stuck with outdated events, and that the actual device isn't used for updating a VPS timer's event as long as other free devices are available. - Modified rcu.c to better handle RC5 codes. - Added a missing variable initialization in cRingBufferLinear::cRingBufferLinear() (thanks to Prakash Punnoor). - Fixed handling relative link targets in the ReadLink() function (reported by Patrick Cernko). - Now making sure a VPS timer has a schedule in case the epg.data file didn't contain one when VDR was started. Have fun! Klaus

1 0

softdevice2net plugin
by Luis Palacios 17 Jun '06

17 Jun '06

Hi, I'm having this problem compiling the plugin and wonder if you could help me. Could also any of the developers comment on the future of this plugin?. I think it's a very good idea. Thanks, luis make[1]: Entering directory `/home/vdr/ies-1.4.0/vdr-1.4.0/PLUGINS/ src/softdevice2net-0.0.1' g++ -g -O2 -Wall -Woverloaded-virtual -c -DUSE_MMX -DUSE_MMX2 - DPLUGIN_NAME_I18N='"softdevice2net"' -D_GNU_SOURCE -I../../../../DVB/ include -I../../../include -I../../../../DVB/include -I/usr/include/ ffmpeg/ -I/usr/lib/libavformat video-net.c video-net.c: In member function `AVStream* cFBVideoOut::add_video_stream(AVFormatContext*, int)': video-net.c:39: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c:49: error: 'struct AVCodecContext' has no member named 'frame_rate' video-net.c:50: error: 'struct AVCodecContext' has no member named 'frame_rate_base' video-net.c: In member function `void cFBVideoOut::open_video (AVFormatContext*, AVStream*)': video-net.c:102: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c: In member function `void cFBVideoOut::write_video_frame (AVFormatContext*, AVStream*, AVFrame*)': video-net.c:177: error: cannot convert `AVCodecContext**' to `AVCodecContext*' in assignment video-net.c: In member function `void cFBVideoOut::close_video (AVFormatContext*, AVStream*)': video-net.c:210: error: cannot convert `AVCodecContext**' to `AVCodecContext*' for argument `1' to `int avcodec_close (AVCodecContext*)' video-net.c: At global scope: video-net.c:222: warning: 'fb_mutex' defined but not used make[1]: *** [video-net.o] Error 1

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