vdr

vdr@linuxtv.org

6731 discussions

Xine and ChannelSwitch
by Patrick Fischer 18 Jan '06

18 Jan '06

Hello Last coupe of hours I spend on detect why the device, given by ChannelSwitch(...), can't receive the Channel. (better I can't attach a receiver which should receiver this Channel) Maybe this is a littel bit confusing. The status function ChannelSwitch told me that device X has switched to channelnumber Y. But if Im using BudgetOnly DevelopSystem, the device is set to the XineDevice which can't receive the Channel. So I can't attach a receiver to this device. Is that right? So I need to detact an other device which can receiver this Channel. Greetings Patrick

1 0

epg.data stays empty (vdr 1.2.6 + xmltv2vdr 1.0.6)
by Francois Dessart 18 Jan '06

18 Jan '06

Hello, I am trying to populate VDR EPG data with xmltv + xmltv2vdr. 1)xmltv works fine and created a correct XML file 2)then I try to push it to VDR with xmltv2vdr: -xmltv2vdr connects correctly to VDR using SVDRP: "connection accepted" -around 3 minutes later "connection close" Nothing is reported in between: neither success nor failure. Should I see something? The problem is that although the epg.data file is getting touched (if existing) or created (if not existing) by VDR, it stays empty...and no EPG data is available in VDR. As there is absolutely no error message, I am a bit stuck on how to troubleshoot this. Could someone, who is using it successfully, tell me if anything should be printed between "connection accepted" and "connection closed"? Thanks for your advise on this. Francois.

1 0

Channel list views and other ideas
by "Sami J. Mäkinen" 18 Jan '06

18 Jan '06

I have a couple of ideas that might be handy in VDR. A) left/right arrow key annoyance In my setup, update from 1.3.38 to 1.3.39 changed the behaviour of <- -> keys: before, they searched through the channel list "headings" or "section marks" (they begin with a colon in channels.conf). Now the left/right arrow keys change the output volume! Aaargh, I have separate keys for that in my Hauppauge remote and furthermore, volume adjustment in VDR does nothing since I use the digital PCM output to my amplifier. I bet there is a way to configure this to behave like it should. How? B) channel list views Since I have some 2400+ channels available, from 5 different satellites, I am a relatively happy user of the channelsort plugin, just to keep all my channels in decent order. (that is, S1.0W, S5.0E, S13.0E, S19.2E and S28.2E) Now, because of different "pay" channels etc. I can either group the channels according to some automatic criteria or sort them out strictly by hand by putting "my" favourite channels to the beginning of list and only let autosort take care of the rest. I think it would be most convenient to have e.g. 10 different "views" to the channel list. So that I can 1) in the channel list view, decide which channel groups a particular channel belongs to. 2) in the channel view, easily switch from the "all channels" view to any of the other views. 3) browse channels up/down in the live view, only in the channels that belong to the currently selected "channel list view". 4) it would be very handy to be able to define some rules (regexp channel name, regexp provider name, source, CA value etc.) for some views and the list/view is updated dynamically. Sorting the channel list is one way, but different users in a family may want to see different sorting of the channels, for example. One solution might be to simply allow duplicate entries in channels.conf, but I think this restriction has been made for a reason. For example, I like to have my channel list sorted according to the satellite and free/pay (ca) value, and tv/radio separately, of course. Still I would like to have a sublist of all the different music channels that I have available. There are plenty of them... News channels are another list etc. Someone (other than me) may similarly want to have a list of all the sports channels. This is where we come to different VDR users in the same family. :) I am using the word "view" here as like the views in SQL databases. The data is not duplicated, but you may have different selections of the lines that may be read like a real table. C) access rights Some others have come up with similar ideas. There might be some kind of user levels in VDR, by a pin code for example. It is easily entered with a remote. On a "guest" level, only certain channels, recordings and timers are visible and modifiable. In "supervisor" mode, channels (and channel views, see above) may be flagged as limited visibility, and they can not be seen in guest level. Same goes with recordings and timers. -sjm

2 2

[Announce] VDR-Maintenance-Patch f. 1.3.38 and .39
by Joachim Wilke 18 Jan '06

18 Jan '06

Hello everyone, the maintenance-patch is now available for vdr-1.3.38 / 1.3.39, for details see below. For those of you interested, you can download the patch from: http://joachim-wilke.de/vdr-patches.htm Joachim. > I have created a "maintenance-patch", which does daily > housekeeping-tasks at a predefined time. This tasks are: > > - automatic calling of noad for new recordings > > - cut all recordings, marked as ready before > Till now, pressing '2' in a recording starts the cutting immediately. > Now, you have the possibility to press '3' and mark this recording as > "ready for cutting". Cutting is then done during the next maintainance > run. Pressing '3' again removes the ready mark. You can see the > current status of a recording in the Recordings overview. Recordings > marked for cutting are indicated with a "+"-sign. > > In the Settings-Menu you can setup the different features in the new > "Maintainance"-submenu. >

5 8

Splash screen?
by Chris Miles 18 Jan '06

18 Jan '06

What is the best way to display a splash screen through my DVB-C card whilst my box is booting? Chris

2 1

Remote plugin and keys repeating too fast
by Paavo Hartikainen 18 Jan '06

18 Jan '06

VDR 1.3.38 and remote 0.3.4, Hauppauge Nova-T PCI 923 (needed for remote control that came with it...) in DVB-C server. Keys of remote control were repeating too fast and soon, so I tried increasing values of "repeatdelay" from 350 to 1000 and "repeatfreq" from 100 to 250 in "remote.c". Parents say it is better now, so I assume it changed for better (that DVB server is hundreds of kilometers away, so I cannot go and test remote control by myself). Maybe this should be configurable in settings dialog of remote plugin? Something like "key repeat delay: [short|medium|long]" and "key repeat frequency: [slow|normal|fast]". -- "pienena / Paavo "Rainbow Rat" Hartikainen minusta / E-mail: pahartik(a)sci.fi tulee / URL: http://www.sci.fi/~pahartik/ rotta" / EFnet: pahartik at #Atari and #LionKing

1 0

Behavior of Menu key, next round
by Udo Richter 17 Jan '06

17 Jan '06

Hi list, After the release of 1.3.39, the menu key debate has cooled down again, and now I'll do another attempt on intuitive behavior. Comments are of course welcome, as this is just one possible solution of many. I really like to close things like OSDTeletext using the menu key, using the new behavior. However, for example if I switch to some channel and directly want to start OSDTT again, I'm annoyed because I have to press menu twice, one time to dismiss the channel status, one time to open the menu. My suggestion is to let the OSD decide about how the menu key behaves, so that some more informational OSDs can directly open the menu. The attached patch does that by adding cOsdObject::menuKeyAction that can be set to one of the following values: menuKeyAlwaysCloses: Close this OSD if the menu key is pressed, and don't open the main menu. This is set for VDR native menus. menuKeyAlwaysOpens: Close this OSD and open the main menu always. This is set for status displays like channel display, volume control and replay 'cutmarks' control. menuKeyConfigurable: For compatibility sake, this decides based on the "Menu button closes" setup option. This is the default for plugins, and is used for the audio track menu. To summarize, with "Menu button closes" disabled, the patch should behave as 1.3.37. With "Menu button closes" enabled, behavior is as 1.3.39, except for channel display, volume control and replay control. Plugins and patches that re-open the OSD quickly (like subtitles), or only show additional information, may set menuKeyAction to menuKeyAlwaysOpens. Don't forget to rebuild your plugins after applying the attached patch! Cheers, Udo diff -au vdr-1.3.39-old/menu.c vdr-1.3.39/menu.c --- vdr-1.3.39-old/menu.c 2006-01-15 19:35:23.000000000 +0100 +++ vdr-1.3.39/menu.c 2006-01-16 19:07:06.000000000 +0100 @@ -3021,6 +3021,7 @@ timeout = Switched || Setup.TimeoutRequChInfo; channel = Channels.GetByNumber(Number); lastPresent = lastFollowing = NULL; + menuKeyAction = menuKeyAlwaysOpens; if (channel) { DisplayChannel(); DisplayInfo(); @@ -3035,6 +3036,7 @@ group = -1; number = 0; lastPresent = lastFollowing = NULL; + menuKeyAction = menuKeyAlwaysOpens; lastTime.Set(); withInfo = Setup.ShowInfoOnChSwitch; displayChannel = Skins.Current()->DisplayChannel(withInfo); @@ -3223,6 +3225,7 @@ :cOsdObject(true) { currentDisplayVolume = this; + menuKeyAction = menuKeyAlwaysOpens; timeout.Set(cDevice::PrimaryDevice()->IsMute() ? MUTETIMEOUT : VOLUMETIMEOUT); displayVolume = Skins.Current()->DisplayVolume(); Show(); @@ -3712,6 +3715,7 @@ lastSpeed = -1; timeoutShow = 0; timeSearchActive = false; + menuKeyAction = menuKeyAlwaysOpens; marks.Load(fileName); cRecording Recording(fileName); cStatus::MsgReplaying(this, Recording.Name(), Recording.FileName(), true); diff -au vdr-1.3.39-old/osdbase.c vdr-1.3.39/osdbase.c --- vdr-1.3.39-old/osdbase.c 2006-01-08 12:40:02.000000000 +0100 +++ vdr-1.3.39/osdbase.c 2006-01-16 19:04:56.000000000 +0100 @@ -76,6 +76,7 @@ cOsdMenu::cOsdMenu(const char *Title, int c0, int c1, int c2, int c3, int c4) { isMenu = true; + menuKeyAction = menuKeyAlwaysCloses; digit = 0; hasHotkeys = false; title = NULL; diff -au vdr-1.3.39-old/osdbase.h vdr-1.3.39/osdbase.h --- vdr-1.3.39-old/osdbase.h 2006-01-06 12:55:30.000000000 +0100 +++ vdr-1.3.39/osdbase.h 2006-01-16 19:14:25.000000000 +0100 @@ -66,16 +66,20 @@ virtual eOSState ProcessKey(eKeys Key); }; +enum eMenuKeyBehavior { menuKeyAlwaysCloses, menuKeyConfigurable, menuKeyAlwaysOpens }; + class cOsdObject { friend class cOsdMenu; private: bool isMenu; protected: bool needsFastResponse; + eMenuKeyBehavior menuKeyAction; public: - cOsdObject(bool FastResponse = false) { isMenu = false; needsFastResponse = FastResponse; } + cOsdObject(bool FastResponse = false) { isMenu = false; needsFastResponse = FastResponse; menuKeyAction = menuKeyConfigurable; } virtual ~cOsdObject() {} bool NeedsFastResponse(void) { return needsFastResponse; } + eMenuKeyBehavior MenuKeyAction(void) { return menuKeyAction; } bool IsMenu(void) { return isMenu; } virtual void Show(void); virtual eOSState ProcessKey(eKeys Key) { return osUnknown; } diff -au vdr-1.3.39-old/vdr.c vdr-1.3.39/vdr.c --- vdr-1.3.39-old/vdr.c 2006-01-15 14:31:57.000000000 +0100 +++ vdr-1.3.39/vdr.c 2006-01-16 19:41:44.000000000 +0100 @@ -791,13 +791,12 @@ // Menu control: case kMenu: { key = kNone; // nobody else needs to see this key - bool WasOpen = Interact != NULL; - bool WasMenu = Interact && Interact->IsMenu(); + eMenuKeyBehavior MenuAction = (Interact) ? (Interact->MenuKeyAction()) : (menuKeyAlwaysOpens); if (Menu) DELETE_MENU; else if (cControl::Control() && cOsd::IsOpen()) cControl::Control()->Hide(); - if (!WasOpen || !WasMenu && !Setup.MenuButtonCloses) + if (MenuAction == menuKeyAlwaysOpens || MenuAction == menuKeyConfigurable && !Setup.MenuButtonCloses) Menu = new cMenuMain; } break;

2 6

problem with VDR 1.3.39
by Peter Juszack 17 Jan '06

17 Jan '06

Hi list, after updating to 1.3.39 vdr did react on keys any more. With 1.3.38 everything worked fine. in syslog I discovered the following Jan 16 13:47:32 fontina vdr[4440]: ERROR: unknown plugin 'snapshot' Jan 16 13:48:03 fontina last message repeated 341237 times Jan 16 13:48:05 fontina last message repeated 33642 times after some searching I discovered that the snapshot plugin remained in the keymacros.conf allthough I have uninstalled it. After I tidied up the keymacros.conf everything is fine. Regards Peter

3 2

Problem with Remote Wonder and VDR :(
by Chris Miles 17 Jan '06

17 Jan '06

I have built and installed LIRC with the configure switch for the AT Usb device. I have /dev/lircd and /dev/lirc0 - permissions are correct. I have a lircd.conf which is setup correctly for my remote control. lircd would not run because /dev/lirc did not exist so I just created a symlink to lirc0 which works fine. I can execute lircd fine. irw executes as well and catches all the remote control presses so the remote control is working fine. I am using VDR 1.3.38 which I made with make REMOTE=LIRC NO_KBG=1 I then startup VDR and it wants to setup the RC unit... it does not recognise any button presses. /var/log/syslog is still saying setting up KBD ??? Jan 17 02:36:18 localhost vdr[6413]: remote control KBD - learning keys Jan 17 02:36:18 localhost vdr[6413]: KBD remote control thread started (pid=6413, tid=6422) I forced --lirc=/dev/lircd --no-kbd onto the command when I execute vdr. syslog now says Jan 17 02:24:57 localhost vdr[6367]: remote control LIRC - learning keys Jan 17 02:24:57 localhost vdr[6367]: LIRC remote control thread started (pid=6367, tid=6376) No other messages in the log but still not doing anything when I hit keys on the remote :( any ideas folks?? Chris

2 2

Bitstreamout not working, help?
by Ari Huttunen 17 Jan '06

17 Jan '06

Hi! Sorry to bother with possibly a stupid question, but I have VDR 1.3.something (the latest one in Ubuntu distro) and Bitstreamout (ditto), and.. well.. it doesn't work. VDR runs nicely with analog output, I have S/PDIF cable connected from motherboard's output to a Yamaha AV Receiver. I can play MP3s with VLC via S/PDIF to Yamaha and to the connected speakers. Bitstreamout is loaded, and I can tweak its parameters via the OSD; as far as I know the card/device parameters are correct. However, when I play TV (or recording) with VDR I can hear nothing on the speakers connected to the Yamaha? Help!? Thanks, Ari Huttunen

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr