vdr

vdr@linuxtv.org

2 participants
6731 discussions

[ANNOUNCE] file browser plugin
by Holger Brunn 15 Oct '05

15 Oct '05

Hello folks, as you get more and more lazy, you just want to lie on your couch and do everything via the remote of your vdr without the need to power on your office computer. And many tasks you do with computers follow the scheme: "do something with some file{,s} and maybe write a result anywhere". So here is a file browser plugin that lets you do just this: Browsing files and execute arbitrary actions on them. Here is the link: http://www.stud.uni-karlsruhe.de/~uqg8/vdr/filebrowser I would appreciate any comments, reviews, tips, bug reports, patches, whatever. Regards, Holger And here a quick copy&paste from README: ------------ Description: ------------ This plugin is a filebrowser with user-defined commands to execute on files. Commands run asynchronously, so you can have longer tasks without the need of at and friends while being able to see current output and to kill them if appropriate. ------------- Installation: ------------- There are no special requirements despite of a simple patch to be applied to vdr sources: cd [vdr source dir] && patch < PLUGINS/src/filebrowser/patches/vdr-menuitems-protected-members.diff (Makes a member protected that is private) Then build as usual. [Tested with vdr 1.3.34] -------------- Configuration: -------------- Configuration files are located in a directory named "filebrowser" in your plugin configuration directory, i.e. /var/lib/vdr/plugins/filebrowser. Example configuration files are provided in this package in directory "examples", which also contains some scripts that could be used as commands. To the config files: * commands.conf * A file defining commands to be run on files, roughly based on vdr's original commands.conf syntax: Columns are separated by colons, first column is the name of the command. When it ends with a question mark, you will be asked whether you really want to execute this command. The second column contains a filename pattern, that you only see commands useful in current context. The third column contains the command to be executed, where following expansions are made: %f: current file %d: if available, a destination file must be choosed, which is inserted here %D: if available, a destination file must be choosed, with the possibility to create a new one %m: expands to currently marked files, separated by a space. If no file is marked, current file is used %M: the same as %m, but this will chage some time - don't use it %%: % %:: : Examples: Remove?:*:rm -rf %m Move:*.c:mv %m %D * order.conf * A file to reorder commands. Usually you will see internal commands first, then commands from commands.conf and then a command to show the thread list. To reorder, just insert the names of the commands in this file, one per line. Attention: Internal command names are localized, so your order.conf needs to be changed when you switch from english to french, and again when you switch from french to german. Attention2: For custom commands, remove the question mark and escaped colons. Commands not mentioned in order.conf are appended to ordered commands. Example (uses commands.conf-snippet from above): Remove #shows remove first Threads #an internal command to see currently executing commands Mark #an internal command Please note that those comments aren't supported in order.conf at the time! * Setup parameters * Here we have two: Base Directory: The path where browsing starts (and is limited to) - this will be superceded by the sources approach known from other plugins somewhen (default: /) Show hidden files: Determines whether to show hidden files or not (default: no) ------ Usage: ------ When selecting the plugin, you can browse your files as you would do it with mp3/mplayer and friends. The only difference is that entering a directory is considered opening a new menu, so pressing back will send you to the parent directory and not to main menu as in some plugins. I think that enhanches user experience. You can execute commands using the color keys of your remote, if there are more than 4, you have to "scroll" using the blue key (it's shown as ">>"). That will be improved by opening a menu with commands some time (See HISTORY->TODO). Usually, commands are run against the current file, but you can also mark/unmark files and execute a command for more files. Note that this only works when the command is configured to use marked files (see section Configuration above). When a command is executed, you will see the output in a scrolling text menu. The menu tries to scroll to the bottom automaticially, that you see the most recent lines of output. So if you want to scroll up to inspect currently invisible lines, you should pause updates (yellow key) to prevent automated scrolling after the next update. Pressing the blue key kills the command, Back closes the output menu (but the command is still running if it was not killed). This output menu is available for every started command when selecting command "Threads" in the browsing menu. This menu also enables you to kill a runnig command, or to remove a finished command from the list.

1 0

VDR compile error
by cardboil 14 Oct '05

14 Oct '05

I'm trying to install VDR on FC4 with a Hauppauge Nexus-s card. Dependencies (libjpeg, libjpeg-devel, openssl) already installed. Using the DVB drivers included in the kernel. VDR-1.2.6 (using older version because I'm using a HOWTO from someone else) is in /usr/local/src/vdr-1.2.6 with a symlink to /usr/local/src/VDR /usr/local/src/DVB is linked to /usr/src/kernels/2.6.13-1.1526_FC4-i686 When I do "make DEBUG_OSD=1", I get the following error message: g++ -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD -DREMOTE_ -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" -DDEBUG_OSD -I../DVB/include config.c sections.h:21: warning: 'class cSectionsScannerCallback' has virtual functions but non-virtual destructor eit.h:82: error: 'cSchedule' has not been declared eit.h:112: error: 'cSchedules' has not been declared make: *** [config.o] Error 1 Any ideas? Appreciate the help.

3 3

A new generation of DVB devices
by Klaus Schmidinger 14 Oct '05

14 Oct '05

Several years ago, when VDR was first developed, it was based upon a then all new DVB card, which implemented a complete device with tuner, MPEG decoder and optional CI adapter. Now, more than five years later, and with the advent of HDTV, it's time for a new generation of DVB devices. Here's a list of the features such a device should have: http://www.cadsoft.de/vdr/hdtv-dream.htm Ok, this is a dream I have - I don't know if any manufacturer will ever come up with such a device. But then again, in the mid-nineties the DVB cards we have now were a dream as well... Please let me know what you think about this, and if I have forgotten anything or got something wrong. Klaus

10 17

RE: [vdr] Thread priority of cutting thread in vdr
by christian jacobsen 14 Oct '05

14 Oct '05

Hallo, > > Concurrent cutting threads would decrease the cutting > performance. A > > queue for cutting would be more helpful like in this patch: > > http://www.vdr-wiki.de/wiki/index.php/Cutterqueue-patch The CutterQueue would indeed be nice :) > From the user's standpoint the important points are: > I would like to cut many recordings, I do not want to wait for > the current cutting to complete before I can start the next one > and I would not like the current cutting to slow down my work > on the next one or any other interactive use of VDR. > I suppose petri's patches support this very well. > Has anyone tried them in the latest VDR? The CutterBandwithLimit.patch from the CutterQueue author helps lowering the used bandwith and is configurable. @Carsten You could try my AutoCutter scripts - they use a Queue for Cutting. Please also take a look at the last post with a CutterBandwithLimit patch for vdrcutter2 ;) http://www.vdrportal.de/board/thread.php?threadid=34583 German site, but README in Englisch. By the way it also includes a Queue for Sharemarks. A way to share Cuttingmarks - making the cutting work easier for all of us :) Greetings Christian Jacobsen

1 0

analogtv compile errors on vdr 1.3.34
by Cristiano 14 Oct '05

14 Oct '05

Hi all, I am trying to compile analogtv-0.9.37 with vdr-1.3.34 but I had some problems, here is my log: g++ -Wall -O4 -march=i486 -mcpu=i686 -pipe -ffast-math -fomit-frame-pointer -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"analogtv"' -DHAVE_FAST_MEMCPY -DNEED_OWN_SIP -I../../../include -I../../../../DVB/include device.c In file included from device.c:29: device.h:65: error: syntax error before `{' token device.h:75: error: `int dup' redeclared as different kind of symbol /usr/include/unistd.h:466: error: previous declaration of `int dup(int)' device.h:83: error: `TS_SIZE' was not declared in this scope device.h:84: error: syntax error before `*' token device.h:85: error: conflicting types for `short unsigned int pid' player-analogtv.h:190: error: previous declaration as `int pid' device.h:97: error: syntax error before `protected' device.h:99: error: virtual outside class declaration device.h:100: error: virtual outside class declaration device.h:101: error: virtual outside class declaration device.h:102: error: virtual outside class declaration device.h:103: error: virtual outside class declaration device.h:104: error: virtual outside class declaration ... I had the same problems with analogtv CVS but I had no problems with vdr 1.2.21 and analogtv 0.9.37 any suggestions? thanks Cristiano

1 0

Howto compile rotor in vdr-1.3.34?
by Suur Karu 14 Oct '05

14 Oct '05

Hi! Is there any patch to compile rotor-0.1.1 plugin with vdr-1.3.34? menu.c: In member function `void cMenuScan::AddChannel(int)': menu.c:330: error: no matching function for call to `cChannel::SetPids(int, int, int[33], char[33][4], int[17], char[17][4], int)' ../../../include/vdr/channels.h:201: error: candidates are: void cChannel::SetPids(int, int, int*, char (*)[8], int*, char (*)[8], int) menu.c: In member function `void cMenuScan::SetPids(int, int, int, int*, char (*)[4], int*, char (*)[4], int)': menu.c:360: error: no matching function for call to `cChannel::SetPids(int&, int&, int*&, char (*&)[4], int*&, char (*&)[4], int&)' ../../../include/vdr/channels.h:201: error: candidates are: void cChannel::SetPids(int, int, int*, char (*)[8], int*, char (*)[8], int) make[1]: *** [menu.o] Error 1 Regards, SK

2 1

Anyone experience with stability of Alphacrypt compared to Irdeto Allcam?
by Matthias Schniedermeyer 14 Oct '05

14 Oct '05

Hi After 4,5 years of using 2 Irdeto Allcams in 2 VDR-systems i'm in the process of buying the parts for a third VDR-instance. First i bought an Alphycrypt ((light) which i got yesterday) to test if it works with our biggest pay-tv-provider in germany. It does work. And the recordings since yesterday evening (only 6 so far) were all OK. Now i wonder if the Alphacrypt is more "stable" than the Allcam. Every now and then the Allcams "lose" sync for a few seconds to a few minutes and in the last few month the data-rate on the movie channels (1,2 and 3) were increased and most times need more than one attempt to get a corruption-free recording. I've had up to 20 "glitches" in movie recordings in the past few month, whereas there is normaly only 1 at most 2 in a "normal" corrupted recording on any other channel.(*) So i wonder if anyone knows from experience if the Alphacrypt is better(tm) and if i should replace the 2 Allcams with another 2 Alphacrypts. *: I "vdrsync" my recordings into a single .mpg file. Only when vdrsync throws is NO or only a 'PTS overflow' error in the process i define that recording as "error-free" and keep it. Otherwise i flush it don't the toilet. -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.

2 2

vdr 1.3.34 on SuSE 10.0.
by Carsten Koch 14 Oct '05

14 Oct '05

I just received my SuSE 10.0 package and I am wondering if it will be a good idea to update my vdr system to SuSE 10.0. Has anyone tried it yet? How about the VDSB problem with kernel 2.6.13? That applies to the SuSE kernel as well, right? Carsten.

4 5

premiere Problems
by Halim Sahin 14 Oct '05

14 Oct '05

2 2

[vdr][PATCH] spanish i18n for burn-0.0.6i
by Jose Alberto Reguero 13 Oct '05

13 Oct '05

Spanish i18n for burn-0.0.6i Jose Alberto

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