vdr

vdr@linuxtv.org

2 participants
6731 discussions

mplayer w/ softdevice
by Vladimir Shved 04 Nov '05

04 Nov '05

Is it possible to show VDRs OSD when playing file with mplayer plugin when using softdevice? Also is it possible to set mplayer plugin so when replying stops, it would drop back to mplayer plugin file browsing list OSD menu? The way its setup here is very inconvenient. When I browse through my media library, every time I finish viewing one file with mplayer, I have to go back to mplayer plugin using Menu, then down, down.. keys etc. I'd like to get it to same behavior as VDRs recordings menu, so when replay finishes it puts you back to the place where I left off, i.e. in VDRs recordings menu and selection at the file that I was playing. Also with softdevice I get mplayers OSD, i.e. I can't see what's playing or at what position it is until I hit forward or backward buttons, etc. I know this is not the case on FF cards output. Is there any workarounds to these issues or am I doing something wrong? Thanks in advance, --Vlad softdevice 0.2.0/-vo dfb:mgatv DFB/DFB++ CVS 0.9.23 G450-DH

4 4

Radio Horeb: VDR changes transponder on its own
by Sascha Volkenandt 04 Nov '05

04 Nov '05

Hi, today I noticed a quite strange behaviour when I wanted to program Radio Horeb into my channels. I took an arbitrary channel entry and started editing it: Freq. 10832 Pol. H Srate 22000 FEC 5/6 Sid 61960 APid 64 Then I saved and tuned to it. I heard the sound of Radio Horeb... for two seconds. That's what happened: Oct 30 13:59:08 lascala user.debug vdr[1500]: changing transponder data of channel 1563 from S19.2E:10832:h:22000:5 to S19.2E:11739:v:27500:3 Well everything I edited was set back to the original values (the arbitrary entries I tried were NICKELODEON FRANCE and CANAL ALGERIE) except for APid and Sid. And this is reproducible. Any idea on how to debug this? VDR is 1.3.33 but I couldn't find related entries in the 1.3.34 ChageLog. Greetings, Sascha

5 4

which lib*softdevice*so.1.3.31 to use?
by André Bischof 04 Nov '05

04 Nov '05

Hello, I successfully compiled softdevice-0.2.0, which I'd like to use with my vdr-1.3.31. My video-card is a NVidia GForce 6600 SilentPipe with built-in MPEG decoder and an HDTV-Out adapter. After compiling the plugin I now have libsubvdr-softdevice-dfb.so.1.3.31 -rwxr-xr-x 1 root root 88995 Nov 4 16:14 libsubvdr-softdevice-fb.so.1.3.31 -rwxr-xr-x 1 root root 100863 Nov 4 16:14 libsubvdr-softdevice-vidix.so.1.3.31 -rwxr-xr-x 1 root root 158028 Nov 4 16:14 libsubvdr-softdevice-xv.so.1.3.31 -rwxr-xr-x 1 root root 401866 Nov 4 16:14 libvdr-softdevice.so.1.3.31 Which one should I use? Or do I have to copy them all to my plugin-dir? I didn't find anything regarding this question on vdr-wiki, maybe someone could help me? What do I have to change in xorg.conf? I'm running Xorg, I think I have to enable another screen-section to get the monitor out working, or do I have to use the nvtv daemon? Thanks alot for helping, André

1 0

RE: [vdr] patch: Consistent menu behaviour - Privat
by christian jacobsen 04 Nov '05

04 Nov '05

Hallo Thiemo, > as said a few days ago, i modified the posted patch to apply > and work cleanly > on vanilla-vdr. > > this patch does two things: (sorry Klaus ;) ) > > 1. makes the "menu" button close a plugin if it is open > (instead of opening > the main menu) > 2. makes the channelinfo remain visible forever if the user > requested it (with > the OK button). this option can (now) be turned off via > Setup->OSD->Timeout > requested channel info Thanks, works very nice :) Also thans to Klaus for "fixing" this later in VDR :) Greetings Christian Jacobsen

1 0

Status plugin interface bug?
by Bernd Juraschek 04 Nov '05

04 Nov '05

Hi, recently I got the evil VDSB error (with kernel 2.4.X :-(). After self restarting VDR continued the recording - but this fails with the "no tuner lock" error. cStatus::Recording() was not called in this case. But the function was called to signal the end of this (never really startet) timer. Therefore there is a imbalance between start and stop status notifications - which may lead to some plugin misbehavior :-( I'was not able to find quickly the way cTimer::Stop() was executed so I have no solution yet ... Greetings, Bernd -- Es gibt 10 verschiedene Arten von Menschen: Die einen verstehen das Binärsystem und die anderen verstehen es nicht.

4 4

Turning off the status debugging?
by Jan Ekholm 04 Nov '05

04 Nov '05

Hi, Is there any way to turn off the below status messages that VDR outputs in syslog? Oct 31 16:31:38 vdr[6491]: channel 12 (TV4) event 15:40 'Nyheterna' status 1 Oct 31 16:31:38 vdr[6491]: channel 12 (TV4) event 15:40 'Nyheterna' status 4 Oct 31 16:31:38 vdr[6491]: channel 12 (TV4) event 15:40 'Nyheterna' status 1 Normally there is a few of these per hour, but lately there have been a "few more". This filled up the /var disk on our logging server, and that happened after 120000 of these messages. I guess the cable provider again has fubar data that they send out (happens quite often) and VDR isn't at fault (other than logging the status changes). I could of course just comment out the line in question and recompile... Regards, Jan Ekholm -- 'Educational' refers to the process, not the object. Although, come to think of it, some of my teachers could easily have been replaced by a cheeseburger. -- Terry Pratchett, alt.fan.pratchett

3 2

CAM-Start: Delay?
by Wolfgang Goeller 04 Nov '05

04 Nov '05

Hello When I restart vdr due to a failure in the descrambling sometimes vdr does initialize the CAM too late. During the initalizing vdr starts recording but the CAM is not ready. Channel not available.... Would it be possible to give a longer delay before vdr starts recording from a encrypted channel? Would be nice allthough there are other workarounds. Regards Wolfgang

3 12

cAnal Digital and card binding
by Lauri Tischler 04 Nov '05

04 Nov '05

cAnal Digital has started to use so called card binding, where the card is paired with receiver. I dont know if the card is paired with the box itself or the Conax CAM. Would VDR be able to do this ?

2 1

@Klaus, before I start working on this patch...
by Lucian Muresan 04 Nov '05

04 Nov '05

Hi, I'd like to provide a patch for VDR but would like to expose the rough implementation idea and of course, the purpose, and therefore get an opinion if it makes sense and last but not least, if it will be accepted. The need: Let's assume the following usage scenario: I'm using VDR mostly as a recording daemon on a FF-less system, therefore when I'm watching live TV or recordings in VDR I have to use softdevice or vdr-xine. I'm always loading the vdr-xine plugin when VDR is running as a service, to be able to connect to it with df_xine. Until now I'm doing this step manually (either starting vdr with the softdevice plugin, or starting df_xine to let it display the VDR OSD and decode it's streams when VDR is already running in deamon mode). Now I'd like to be able to start df_xine from within Freevo ( http://freevo.sourceforge.net/screenshots_blurr.html#freevo_ss1 ) which already has a plugin for this, which is talking to VDR via SVDRP. The problem: Because I sometimes shut down Freevo and let VDR just run in deamon mode, and eventually start df_xine again manually this time, the VDR deamon has to run with remotes enabled (I'm using LIRC and sometimes keyboard). When Freevo is up, it's controlled by LIRC and/or keyboard, too, and that's a conflict(*), I wouldn't even see what the keystrokes I do for Freevo instruct VDR to do when not having it displayed in df_xine, for example when doing other things than VDR in Freevo, like watching movies or pictures, or listening to music(**), and even while displaying VDR in df_xine invoked by Freevo, they would both react at the same time directly to keystrokes. My proposal: I thought I'd introduce a new SVDRP command which would enable/disable all or just a specific remote, and therefore reset/set a disable-flag in cRemote, which would cause the cRemote::Put(..) and cRemote::PutMacro(..) methods return whithout executing their normal code. Then I would disable my remotes in VDR via SVDRP when starting df_xine from Freevo and let Freevo control VDR via SVDRP, and when leaving df_xine I would re-enable them again. What do you think of this? Further implementation questions, if what way I described makes sense: - What should the cRemote::Put(...) methods return when disabled, true or false? - at a first look, the disable flag could be checked only in bool cRemote::Put(eKeys Key, bool AtFront) which actually does the work in the other 2 methods, too, would it have side-effects if implemented that way (I think not really)? So, should I go this way? Best regards & thanx for this great software, Lucian *) I know about the --no-kbd and the --lirc=PATH_TO_DEVICE command line switches of VDR, but on my system --no-kbd does not prevent VDR getting keyboard events, only specifying --lirc=/dev/null or something like that prevents VDR getting LIRC commands, but it always logs errors (which is understandable). But even then, this would be inflexible for me as a change in the behaviour of reacting or not to cRemote events would require restasrting VDR. **) Please don't tell me VDR can do all theese too, I know it can, but on a budget-only system with just 1GHz Freevo is more efficient at those, because it's using xine for DVDs, or diplays pictures natively on DirectFB without transcoding them to MPEG frames first, and Freevo's UI also doesn't need this transcoding stuff like text2skin would need, as it all was designed for FF-cards.

3 4

Problems with rotor plugin and kernel 2.6.14
by Rene Caspari 04 Nov '05

04 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I want to upgrade my linux kernel to 2.6.14. Now i have the problem, that my vdr with the rotor plugin doesn't want to move the dish. It exactly does nothing :-) I use vdr 1.3.23 with the rotor plugin 0.1.0. Any ideas or same experiences? bye, rene - -- ___ _ _ ___ __ ___ ____ _ _ ___ ___ / _ \| |_| | _ ) / _|/ _ \ / __/ | \| | __| | Rene Caspari| _ | _ | . \( (_| _ |\__ \ _ | .' | _| | | http://rene.|_| |_|_| |_|_|\_|\__|_| |_|____/|_||_|\_|___||_| -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDazi9i7H4n8pAp5MRAjWCAJ9EYMllq6YykaEAQLOLbIAMIui4TwCfcCbG tc+KMYtNmcoO4Z0a6JujdGc= =trrG -----END PGP SIGNATURE-----

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