vdr September 2007

vdr@linuxtv.org

65 participants
61 discussions

Re: [vdr] Not good behaviour from vdr
by dom.plu 30 Sep '07

30 Sep '07

Hi thanks for this future option, I have the same problem not caused directly by card or drivers but in a multiple frontend system (dvb-s + dvb-t) if at least one provider did not send signal , you loose all other concurrent records It can be interresting to use the emergency shutdown only when there are no other records running at the same time Regards Le samedi 29 septembre 2007 11:06, Klaus Schmidinger a écrit : > On 09/29/07 09:30, Timothy D. Lenz wrote: > > I don't know about it restarting. The crashing with loss of signal is > > suposed to be a safe guard against creating blank recordings. Seems like > > a bad idea to me to. Just delete the bad recordings, don't crash the > > system. > > Well, let me just comment on the nomenclature here ;-) > When VDR does an "emergency exit" because there is no video data for > a while, this is a *controlled* action that shall allow the driver > to be reloaded. Full featured cards sometimes have the problem that > they completely lock up, and reloading the driver fixes this. > > So this can *not* be called "crashing", and especially not "crashing > the system", because I'm pretty sure your Linux system will not be affected > by this. > > > Here is the fix we've been using: > > > > Locate the line in recorder.c and comment it out. > > > > esyslog("ERROR: video data stream broken"); > > - ShutdownHandler.RequestEmergencyExit(); > > + // ShutdownHandler.RequestEmergencyExit(); > > Since several users have been complaining about this in the past, > I'll make this a setup parameter in one of the next versions, so > everybody can decide for themselves whether they prefer lost > recordings or an occasional restart. > > Klaus > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -------------------------------------------------------

6 7

Improving quality of xvideo output for vdr-sxfe
by Rob Davis 30 Sep '07

30 Sep '07

I know this is slightly of topic but I am not sure where else to turn. I am using the binary drivers from nidia on a GeForce 5500 graphics card. I have two cables plugged into it, one dvi to vga adapter which is plugged into my flat panel tv then other a normal vga cable plugged into a flat panel screen. Both screens are mirrored on 1280x1024. The effect I have is that overlay XV displays appear to cut and tear in both mplayer and vdr-sfxe. If I use the xvmc driver then I don't get a video overlay (ie, no menus) although the quality is much better. There are no strange options that I can see if xorg.conf. Can anyone recommend anything I can try?

2 1

Re: [vdr] forgot name of a patch....
by Travel Factory S.r.l. 29 Sep '07

29 Sep '07

Patch is vdr-1.3.22-Source-dependant-NewChannels-Insertation and it applies quite correctly to vdr 1.4.7. Compiling is ok. Now I should test it. Francesco

1 0

forgot name of a patch....
by Travel Factory S.r.l. 29 Sep '07

29 Sep '07

I'm rebuilding my vdr station. I saved all my old stuff an a notebook that has been stolen.... There was a patch that permitted to add new channels on different parts of a channel list according to satellite-terrestrial/tv-radio/pay-free Do you remember about this patch ? (or has it been included in 1.4.... ?) Thank you, Francesco

1 0

Rotor plugin crashing with valid data in diseqc.conf
by Timothy D. Lenz 29 Sep '07

29 Sep '07

Built a new system with an Athlon64 x2 running and64 linux. I went with vdr-1.5.9. I tried to use the diseqc.conf from my old system, but vdr crashes in startup when the rotor plugin is used. I found the problem seems to be the use of commands to control the rotor in the diseqc.conf. with [E0 31 6B 26] and rotor plugin, vdr crashes at startup. remove ether the rotor plugin or all [E0 31 6B xx] entries and it starts. I used the vdr-1.5.5 patch in the patches folder of rotor. Starting VDR - Linux Video Disk Recorder: runvdr. *** glibc detected *** /usr/local/bin/vdr: munmap_chunk(): invalid pointer: 0x0000000005613804 *** ======= Backtrace: ========= /lib/libc.so.6(cfree+0x1b6)[0x2aff4f3486b6] /usr/local/bin/PLUGINS/lib/libvdr-rotor.so.1.5.9(_ZN12cPluginRotor5StartEv+0 x299)[0x2aff53aac659] /usr/local/bin/vdr(_ZN14cPluginManager12StartPluginsEv+0x5d)[0x49bc6d] /usr/local/bin/vdr(main+0x1496)[0x4cd626] /lib/libc.so.6(__libc_start_main+0xf4)[0x2aff4f2f0b44] /usr/local/bin/vdr(__gxx_personality_v0+0x229)[0x44b849] ======= Memory map: ======== 00400000-0052d000 r-xp 00000000 03:01 1736706 /usr/local/bin/vdr 0072c000-00730000 rw-p 0012c000 03:01 1736706 /usr/local/bin/vdr 00730000-0562b000 rw-p 00730000 00:00 0 [heap] 40000000-40001000 ---p 40000000 00:00 0 40001000-40801000 rw-p 40001000 00:00 0 40801000-40802000 ---p 40801000 00:00 0 40802000-41002000 rw-p 40802000 00:00 0 41002000-41003000 ---p 41002000 00:00 0 41003000-41803000 rw-p 41003000 00:00 0 41803000-41804000 ---p 41803000 00:00 0 41804000-42004000 rw-p 41804000 00:00 0 42004000-42005000 ---p 42004000 00:00 0 42005000-42805000 rw-p 42005000 00:00 0 42805000-42806000 ---p 42805000 00:00 0 42806000-43006000 rw-p 42806000 00:00 0 2aaaac000000-2aaaac021000 rw-p 2aaaac000000 00:00 0 2aaaac021000-2aaab0000000 ---p 2aaaac021000 00:00 0 2aff4de26000-2aff4de43000 r-xp 00000000 03:01 819205 /lib/ld-2.6.1.so 2aff4de43000-2aff4de46000 rw-p 2aff4de43000 00:00 0 2aff4de46000-2aff4df7e000 r--p 00000000 03:01 1281421 /usr/lib/locale/locale-archive 2aff4e042000-2aff4e044000 rw-p 0001c000 03:01 819205 /lib/ld-2.6.1.so 2aff4e044000-2aff4e065000 r-xp 00000000 03:01 1262770 /usr/lib/libjpeg.so.62.0.0 ........

2 3

[ANNOUNCE] DVB-S2 + H.264 support for VDR-1.5.9
by Reinhard Nissl 27 Sep '07

27 Sep '07

Hi, as both support patches interfere with each other, I've attached a merged patch which contains all my patches posted in the thread "[ANNOUNCE] H.264 updates for VDR-1.5.9". DVB-S2 support was kindly contributed to me by Marco Schluessler -- thanks a lot! WARNING 1: after adding DVB-S2 support to VDR, it will nolonger compile with "standard" DVB drivers. You'll definitely need Manu Abraham's DVB repository. WARNING 2: some API changes still have not been ported to the drivers for DVB-S hardware so you'll most likely only be able to use hardware with DVB-S2 support. In other words: tuning doesn't work for e. g. a NOVA-S while it works for example for a TT S2 3200. WARNING 3: the driver is still BETA. Don't use it in a productive environment as tuning and reception issues may damage recordings. Keep in mind that FF cards cannot handle H.264 streams and my behave strange! IMPORTANT NOTE: don't tie up Manu's or Marco's resources by sending unqualified support requests. This release is mainly intended for developers. For those who want to experiment, have a look at locations like that one for further information: http://www.vdr-wiki.de/wiki/index.php/OpenSuSE_DVB-S2_-_Step_by_Step_Instal… Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

1 0

Plugindefined svdrp-commands not working?
by Torsten Kunkel 27 Sep '07

27 Sep '07

Hi List, sorry but it's me again :/ I'm still trying to get plugindefined svdrp-commands to work, but even the svdrpdemo-plugin doesn't work: > torsten@vdr-entw:/usr/src/vdr/vdr$ ./svdrpsend.pl help > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:20:53 2007 > 214-This is VDR version 1.5.9 > 214-Topics: > 214- CHAN CLRE DELC DELR DELT > 214- EDIT GRAB HELP HITK LSTC > 214- LSTE LSTR LSTT MESG MODC > 214- MODT MOVC MOVT NEWC NEWT > 214- NEXT PLAY PLUG PUTE REMO > 214- SCAN STAT UPDT VOLU QUIT > 214-Plugin svdrpdemo v0.0.3 - How to add SVDRP support to a plugin > 214- DATE TIME > 214-To report bugs in the implementation send email to > 214- vdr-bugs(a)cadsoft.de > 214 End of HELP info > 221 vdr-entw closing connection (no error in syslog, loglevel 3) > torsten@vdr-entw:/usr/src/vdr/vdr$ ./svdrpsend.pl DATE > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:22:06 2007 > 500 Command unrecognized: "DATE" > 221 vdr-entw closing connection (no error in syslog, loglevel 3) > torsten@vdr-entw:/usr/src/vdr/vdr$ ./svdrpsend.pl help DATE > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:22:09 2007 > 504 HELP topic "DATE" unknown > 221 vdr-entw closing connection (no error in syslog, loglevel 3) The vdr building commands are working: > torsten@vdr-entw:/usr/src/vdr/vdr$ ./svdrpsend.pl help REMO > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:22:57 2007 > 214-REMO [ on | off ] > 214- Turns the remote control on or off. Without a parameter, the current > 214 status of the remote control is reported. > 214 End of HELP info (btw, here the 221-line is missing and I'm getting "Sep 27 09:22:57 vdr-entw vdr: [16622] ERROR (svdrp.c,410): Broken pipe" in my syslog) > torsten@vdr-entw:/usr/src/vdr/vdr$ ./svdrpsend.pl REMO off > 220 vdr-entw SVDRP VideoDiskRecorder 1.5.9; Thu Sep 27 09:23:11 2007 > 250 Remote control disabled > 221 vdr-entw closing connection (I'm getting "Sep 27 09:23:11 vdr-entw vdr: [16622] ERROR (svdrp.c,410): Broken pipe" in my syslog) I think I'm making something completely wrong, but I have no idea what this could be... Helpless Greetings Torsten

2 3

[Announce] vdr-fritzbox 0.0.7
by Joachim Wilke 26 Sep '07

26 Sep '07

Dear Fritz!Box- and VDR-Users, a new version of the Fritz!Box Plugin is available at http://joachim-wilke.de/index.htm?alias=vdr-fritz - - - The Fritz!Box Plugin connects to your Fritz!Box to inform you about incoming calls. The plugin can automatically mute or pause VDR when a call comes in. Via VDR's main menu you can browse your Fritz!Box phone book and initiate calls out of it via the [OK]-button. Via the colour keys you can navigate to the following call lists: * Incoming Calls * Missed Calls * Outgoing Calls Pressing [OK] in these lists initiates a call similar to the phone book. - - - The last changes are: - fixed wrong display of call details when date separator is enabled or call lists are filtered (reported by Saxman2k [14]) - now using std::string::erase for compatibility with old libstdc++2.10 - added some includes for better gcc-2.95 compatibility patch provided by Tobias [1] - - - Regards, Joachim.

1 0

[ANNOUNCE] vdr-spider-0.2.0
by Thomas Günther 26 Sep '07

26 Sep '07

Hi! There is a new version of the 'Spider Arachnid' plug-in. Download: http://toms-cafe.de/vdr/spider/vdr-spider-0.2.0.tgz Changes since version 0.1.4: - Renamed *.c files to C++ suffix *.cpp. - Added namespaces. - Added gettext support (VDR >= 1.5.7). - Resume the last game. - Customizable width and height. - OSD error compensation (shrink width/height or reduce colors). - Added setup option to hide the top row. - Set normal variation (two decks and 10 piles) as standard, together with "shrink height" and "hide top row". - Added user-defined variations. - Improved key handling. - Updated German language texts. 'Spider Arachnid' is an implementation of the best patience game played on the On Screen Display of the VDR. See the project's homepage for details: http://www.toms-cafe.de/vdr/spider Tom

1 0

Help of SVDRP commands
by Torsten Kunkel 25 Sep '07

25 Sep '07

Hi, I noticed new SVDRP commands are limited to 9 characters. ./svdrpsend.pl help [...] 214-Plugin dummy v0.0.1 - Enter description for 'dummy' plugin 214- 123456789 [...] [...] static const char *HelpPages[] = { "12345678901234567890\n" " Print some stuff.", [...] I found MAXHELPTOPIC in the svdrp.c causing this limitation. But why? :) I don't see any reasons for this limitation. When calling the Plugin, this limit to 10 chars isn't implemented. At least there should be a hint in the PLUGIN.html on this abbreviation. Greetings Torsten

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2007