vdr September 2006

vdr@linuxtv.org

80 participants
76 discussions

Re: vdr Digest, Vol 20, Issue 8
by nitin 05 Sep '06

05 Sep '06

I have just downloaded the vdr source code and successfully build it. But it seems that present code will work only for some specific tuner card. Can it work for recorded transport stream which are stored in hard disk. Please let me know if it is possible and also suggest how to do so. Thanks... warm regards, Nitin J

2 1

Recording stops and starts again
by Lauri Tischler 04 Sep '06

04 Sep '06

I seem to remember that there was a patch to prevent stopping and starting recording if audio-pid changes. Was there ? *** recording starts here *** Sep 2 20:47:30 vdr vdr: [2977] setting audio track to 1 (0) Sep 2 20:48:00 vdr vdr: [2891] switching device 3 to channel 2 Sep 2 20:48:00 vdr vdr: [2891] timer 1 (2 2048-2157 'Siska') start Sep 2 20:48:00 vdr vdr: [2891] Title: 'Siska' Subtitle: 'Viimeinen tehtävä. Siska ryhtyy tutkimaan yksityisetsivä Zellerin murhaa. Oliko Zeller saanut … [View More]tietoonsa joitakin niin arkaluontoisia asioita, että hänet haluttiin vaientaa lopullisesti? Stereo.' Sep 2 20:48:00 vdr vdr: [2891] record /video/Siska/2006-09-02.20.48.99.99.rec Sep 2 20:48:00 vdr vdr: [2891] creating directory /video/Siska Sep 2 20:48:00 vdr vdr: [2891] creating directory /video/Siska/2006-09-02.20.48.99.99.rec Sep 2 20:48:02 vdr vdr: [2891] recording to '/video/Siska/2006-09-02.20.48.99.99.rec/001.vdr' Sep 2 20:48:02 vdr vdr: [2996] file writer thread started (pid=2891, tid=2996) Sep 2 20:48:02 vdr vdr: [2997] recording thread started (pid=2891, tid=2997) Sep 2 20:48:02 vdr vdr: [2998] receiver on device 3 thread started (pid=2891, tid=2998) Sep 2 20:48:02 vdr vdr: [2999] TS buffer on device 3 thread started (pid=2891, tid=2999) *** Program really starts and audio pids are set up*** Sep 2 20:50:12 vdr vdr: [2900] channel 2 (YLE TV2) event La 02.09.2006 20:50-21:47 'Siska' status 4 Sep 2 20:50:17 vdr vdr: [2900] buffer stats: 0 (0%) used Sep 2 20:50:18 vdr vdr: [2903] changing pids of channel 2 from 513+129:660=fin,661=sve:2321 to 513+129:660=deu:2321 Sep 2 20:50:18 vdr vdr: [2891] stopping recording due to modification of channel 2 Sep 2 20:50:18 vdr vdr: [2997] recording thread ended (pid=2891, tid=2997) Sep 2 20:50:18 vdr vdr: [2996] file writer thread ended (pid=2891, tid=2996) Sep 2 20:50:18 vdr vdr: [2891] buffer stats: 0 (0%) used Sep 2 20:50:18 vdr vdr: [2999] TS buffer on device 3 thread ended (pid=2891, tid=2999) Sep 2 20:50:18 vdr vdr: [2998] buffer stats: 78960 (3%) used Sep 2 20:50:18 vdr vdr: [2998] receiver on device 3 thread ended (pid=2891, tid=2998) Sep 2 20:50:18 vdr vdr: [2891] cTS2PES got 2 TS errors, 3 TS continuity errors Sep 2 20:50:18 vdr vdr: [2891] cTS2PES got 0 TS errors, 3 TS continuity errors Sep 2 20:50:18 vdr vdr: [2891] cTS2PES got 1 TS errors, 3 TS continuity errors Sep 2 20:50:18 vdr vdr: [2891] cTS2PES got 2 TS errors, 1 TS continuity errors Sep 2 20:50:18 vdr vdr: [2891] buffer stats: 105468 (2%) used Sep 2 20:50:18 vdr vdr: [2891] timer 1 (2 2048-2157 'Siska') stop Sep 2 20:50:18 vdr vdr: [2891] retuning due to modification of channel 2 Sep 2 20:50:18 vdr vdr: [2891] switching to channel 2 Sep 2 20:50:18 vdr vdr: [2977] transfer thread ended (pid=2891, tid=2977) Sep 2 20:50:18 vdr vdr: [2891] buffer stats: 68432 (3%) used Sep 2 20:50:18 vdr vdr: [3005] transfer thread started (pid=2891, tid=3005) Sep 2 20:50:18 vdr vdr: [2891] buffer stats: 0 (0%) used Sep 2 20:50:18 vdr vdr: [2891] switching device 3 to channel 2 Sep 2 20:50:18 vdr vdr: [2891] timer 1 (2 2048-2157 'Siska') start Sep 2 20:50:18 vdr vdr: [2891] Title: 'Siska' Subtitle: 'Viimeinen tehtävä. Siska ryhtyy tutkimaan yksityisetsivä Zellerin murhaa. Oliko Zeller saanut tietoonsa joitakin niin arkaluontoisia asioita, että hänet haluttiin vaientaa lopullisesti? Stereo.' Sep 2 20:50:18 vdr vdr: [2891] record /video/Siska/2006-09-02.20.48.99.99.rec Sep 2 20:50:18 vdr vdr: [2891] recording to '/video/Siska/2006-09-02.20.48.99.99.rec/002.vdr' Sep 2 20:50:18 vdr vdr: [3007] file writer thread started (pid=2891, tid=3007) Sep 2 20:50:18 vdr vdr: [3008] recording thread started (pid=2891, tid=3008) Sep 2 20:50:18 vdr vdr: [3009] receiver on device 3 thread started (pid=2891, tid=3009) Sep 2 20:50:18 vdr vdr: [3010] TS buffer on device 3 thread started (pid=2891, tid=3010) Sep 2 20:50:20 vdr vdr: [3005] setting audio track to 1 (0) [View Less]

4 4

Re: vdr-mousemate-0.1.0.tgz
by Joachim Welker 04 Sep '06

04 Sep '06

Hi, this is an english mailing list, so please stay at vdr-portal.de. I will answer there at any one time ;). Regards, Joachim PS: I'm *not* a developer.

1 0

sofdevice and softplay cvs cleanups
by C.Y.M 03 Sep '06

03 Sep '06

I have been trying to clean up my builds and when updated softdevice and softplay via cvs, noticed several warning about unused variables. Also, it appears that softplay does not have the current Makefile fixes required to build under the latest VDR. Best Regards,

1 1

sofdevice cvs unused variables
by C.Y.M 03 Sep '06

03 Sep '06

1 0

xineliboutput: other rtp clients ?
by syrius.ml＠no-log.org 03 Sep '06

03 Sep '06

Hi, I'm the happy user of xineliboutput 1.0.0pre3. I'd like to know if it's possible for other rtp clients to play the multicast stream. (while xine+xineliboutput is playing it) In fact i'd like to be able to use vlc to transcode/re-stream it. what's the format of the video stream sent by xinelibout ? is it something vlc can read directly ? Or how hard would it be to give vlc the ability to play this stream ? Any idea ? Thanks in advance. --

2 2

[ANNOUNCE] VDR maintenance patch 1.4.2-1
by Klaus Schmidinger 03 Sep '06

03 Sep '06

VDR maintenance patch 1.4.2-1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.2-1.diff This is a 'diff' against the official version 1.4.2. 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 is … [View More]

1 0

ttxtsubs question
by Jukka Palko 03 Sep '06

03 Sep '06

Now that I've gotten my system running smoothly with my cable channels, I have a short question about ttxtsubs. Looks like the subtitles get shown when viewing a channel that sends them, but they don't either get stored onto the recordings or they don't get decoded out on playback. I have the settings to show and record these turned on in my plugin setup. Any way I could debug this? If any of you use gentoo on your vdr, could the use flag "debug" on the plugin merging and FEATURES=nostrip … [View More]

2 2

[ANNOUNCE] vdr-span-0.0.1
by Christian Leuschen 03 Sep '06

03 Sep '06

Hello folks, with my first post on this ML I'm glad to announce a new plugin called span. I have written a plugin that can receive PCM-data from other plugins (e.g. mp3ng) to compute frequency-data and to provide them to other plugins to display a 'Sp'ectrum 'An'alyzer. It is meant as a kind of middleware between these providers and clients to be as generic as needed to be able to implement the visualisation on all kinds of output-devices (OSD, lcd, graphlcd, framebuffer, etc.). It is … [View More]available at http://lcr.vdr-developer.org/ There's a thread also at http://www.vdr-portal.de/board/thread.php?postid=513343#post513343 providing the latest information. @Klaus: Is there an obstacle to get all plugins that support some kind of service? s.th like static cPlugin **CallAllServicePlugins(const char *Id, void *Data = NULL); that returns a list of all plugins supporting the requested service. I would like to use it to collect the names of all data-providers and all visualization-clients. Kindly yours Christian Leuschen Abstract from the plugins's README: This is a 'Sp'ectrum 'An'alyzer Plugin for the Video Disk Recorder (VDR). Requirements: VDR & (lib)fftw3 Description: A plugin that can receive PCM-data from other plugins (e.g. mp3ng) to compute frequency-data and to provide them to other plugins to display a 'Sp'ectrum 'An'alyzer. It is meant as a kind of middleware between these providers and clients to be as generic as needed to be able to implement the visualisation on all kinds of output-devices (OSD, lcd, graphlcd, framebuffer, etc.). Sketch of the architecture: | Data-provider sends PCM-data ---> | SpAn-plugin | >--- Visualization-clients request the spectrum-data "making s.th. handsome out of it" | Installation: cd /put/your/path/here/VDR/PLUGINS/src tar -xzf /put/your/path/here/vdr-span-X.Y.Z.tar.bz2 ln -s span-X.Y.Z span cd /put/your/path/here/VDR make make plugins ./vdr -P span Setup: Activate spectrum analyzer? yes/no De-(Activates) the plugin. yes: The plugin receives data (only if clients also request data) and on request hands the results over to clients. no: In this case all data provider- and visualization-plugins are rejected when trying to hand over data or to request results. Use logarithmic diagram yes/no A (yet naive) try to equalize the heights of the bars a bit. Lower frequencies are prevailing which results in an "high dynamic range of the heights of the bars" (= mostly few extremely high bars on the left, further right more decreasing or even no bars at all). yes: Suspends a "no" at "Use pure (unequalized) data". Scaling of the heights of the bars is done logarithmically. no: No logarithmic scaling is done. Tips to improve this way of equalizing are warmly welcome! Hide mainmenu entry yes/no Should be self-explanatory. At the moment there is no use of displaying the plugin's entry in the main menu. See ToDo (way below) for the reason. Use pure (unequalized) data yes/no yes: Really compute the pure data without equalizing anyhow. no: Values of higher frequencies are emphasized resulting in a "bit nicer way of displaying the frequencies" than with pure data. Notes: - Tested on VDR-1.4.0 with a FF-DVB-s 2MB (CPU = PIII 1,2GHz) with mp3ng-plugin as self-made data provider as well as visualization-client. Additionally the lcdproc-plugin was used as visualization-client, but just as a proof-of-concept. Thus, there were two clients active simultaneously. - I would be very glad if the authors of plugins for rendering vdr-information on (external) displays (graphlcd/graphtft/lcdproc/etc.) or the OSD (mp3(ng)/ cdda/radio?/muggle?) used the data provided by this plugin to visualize a spectrum analyzer. Generic example how to use it: // Please see the "real" README for the "HowTo". TODO: - Test the stuff with cdda-plugin (provider) and graphlcd-plugin (visualization) - Test it on my streaming-client (it's a PIII 450MHz with DXR3 now) - Implement the output of the names of all data-source- and visualization-plugins on selecting the mainmenu's entry. A change in the "Plugin-Service-Protocol" could be neccessary to support getting ALL plugins that can handle a service. - Implement bar-peaks and their fall off [View Less]

2 1

lost comment in runvdr script
by Matthias Becker 03 Sep '06

03 Sep '06

Hi, when reorganizing my runvdr I found some lost comment in the file that is delivered with vdr 1.4.2. There is still some comment about the variable VDRUSR. It says: # Set the environment variable VDRUSR to the user id you # want VDR to run with. If VDRUSR is not set, VDR will run # as user 'vdr'. I suggest either to re-introduce this variable or to throw out this comment. Regards, Matthias

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2006