vdr

vdr@linuxtv.org

6731 discussions

Patch to use Skip keys (Next + Previous)
by Peter Juszack 15 Apr '06

15 Apr '06

Hallo Since a long time I wondered when the very common skip keys are available in VDR. I believe these keys are available but unused on most remote controls. The attached patch adds to new keys kNext and kPrevious to keys.h and keys.c. The patch modifies vdr.c and menu.c to switch channel up/down whith the new keys. I also modified the mp3 and dvd plugins to use the new keys. I can provide patches therefor if the patch will be intergrated in VDR. As logical mp3 jumps between tracks. When playing a DVD Next and Previous have the same meaning like 4 and 6 and jump between DVD chapters. That is the common behaviour of stand-alone DVD players. Very smart when replaying music DVDs because the different songs are DVD chapters. I can also imagine to use Prev/Next to navigate between cutting marks in a recording. (not yet implemented) If you find the new keys useful please contact the list to convince Klaus to integrate the patch. Regards Peter diff -Naur vdr-1.3.43.orig/keys.c vdr-1.3.43/keys.c --- vdr-1.3.43.orig/keys.c 2006-02-20 14:04:53.000000000 +0100 +++ vdr-1.3.43/keys.c 2006-02-20 14:05:18.000000000 +0100 @@ -39,6 +39,8 @@ { kRecord, "Record" }, { kFastFwd, "FastFwd" }, { kFastRew, "FastRew" }, + { kNext, "Next" }, + { kPrevious, "Previous" }, { kPower, "Power" }, { kChanUp, "Channel+" }, { kChanDn, "Channel-" }, diff -Naur vdr-1.3.43.orig/keys.h vdr-1.3.43/keys.h --- vdr-1.3.43.orig/keys.h 2006-02-20 14:04:53.000000000 +0100 +++ vdr-1.3.43/keys.h 2006-02-20 14:05:22.000000000 +0100 @@ -33,6 +33,8 @@ kRecord, kFastFwd, kFastRew, + kNext, + kPrevious, kPower, kChanUp, kChanDn, diff -Naur vdr-1.3.43.orig/menu.c vdr-1.3.43/menu.c --- vdr-1.3.43.orig/menu.c 2006-02-20 14:04:53.000000000 +0100 +++ vdr-1.3.43/menu.c 2006-02-20 14:10:09.000000000 +0100 @@ -3170,12 +3170,16 @@ case kUp: case kDown|k_Repeat: case kDown: + case kNext|k_Repeat: + case kNext: + case kPrevious|k_Repeat: + case kPrevious: case kChanUp|k_Repeat: case kChanUp: case kChanDn|k_Repeat: case kChanDn: { eKeys k = NORMALKEY(Key); - cChannel *ch = NextAvailableChannel(channel, (k == kUp || k == kChanUp) ? 1 : -1); + cChannel *ch = NextAvailableChannel(channel, (k == kUp || k == kChanUp || k == kNext) ? 1 : -1); if (ch) channel = ch; else if (channel && channel->Number() != cDevice::CurrentChannel()) @@ -3184,6 +3188,8 @@ // no break here case kUp|k_Release: case kDown|k_Release: + case kNext|k_Release: + case kPrevious|k_Release: case kChanUp|k_Release: case kChanDn|k_Release: if (!(Key & k_Repeat) && channel && channel->Number() != cDevice::CurrentChannel()) diff -Naur vdr-1.3.43.orig/vdr.c vdr-1.3.43/vdr.c --- vdr-1.3.43.orig/vdr.c 2006-02-20 14:04:53.000000000 +0100 +++ vdr-1.3.43/vdr.c 2006-02-20 14:05:30.000000000 +0100 @@ -1018,6 +1018,11 @@ case kLeft: case kRight|k_Repeat: case kRight: + // Skip Channel Select: + case kPrevious|k_Repeat: + case kPrevious: + case kNext|k_Repeat: + case kNext: // Up/Down Channel Select: case kUp|k_Repeat: case kUp:

2 1

Re: [vdr] vdr-1.3.6 wrong parameter when calling shutdown script
by Klaus Schmidinger 15 Apr '06

15 Apr '06

Helge Lenz wrote: > Hi, > since I use 1.3.6 I have problems to shut my system down when there is > no timer programmed. I tried with a plain vdr-1.3.6 and found out, that > the "time to next timer"-parameter ($2) is not zero but it seems to be > the negative current time as t_time. Ok, I could treat number less than > - -72000 (recording capacity of my system) as zero, because a timer that > startet that long ago should be finished by now, but maybe somebody > could have a look onto this. I just found this rather old posting in my inbox - sorry for not getting back to you on this earlier... I believe the fix should look like this: --- vdr.c 2006/04/15 11:05:49 1.257 +++ vdr.c 2006/04/15 11:29:13 @@ -1132,7 +1132,8 @@ cControl::Shutdown(); int Channel = timer ? timer->Channel()->Number() : 0; const char *File = timer ? timer->File() : ""; - Delta = Next - time(NULL); // compensates for Confirm() timeout + if (timer) + Delta = Next - time(NULL); // compensates for Confirm() timeout char *cmd; asprintf(&cmd, "%s %ld %ld %d \"%s\" %d", Shutdown, Next, Delta, Channel, *strescape(File, "\"$"), UserShutdown); isyslog("executing '%s'", cmd); Can you confirm this? Klaus

1 0

[Announce] epgsearch-0.9.15
by Christian Wieninger 14 Apr '06

14 Apr '06

Hi, here's the next release of epgsearch: 2006-04-14: Version 0.9.15 new: - the EPG menus can now be customized with the file epgsearchmenu.conf (sample file in 'conf' subdirectory), e.g. the entry: MenuWhatsOnNow=%chnr%:3|%progrt2s%:5| %time% %t_status%:8|%category%:6| %title% ~ %subtitle%:35 creates a menu line starting with the channel number, followed by a progress bar in text2skin style, the start time, the timer status, the EPG category (like "movie") and finally the title and subtitle. You can customize each menu ('What's on now, next, other times, schedule and search results with a separate line). Please refer to the MANUAL for more information. - IMPORTANT change to search timers: epgsearch now removes timers, that are not needed anymore (if vdr >= 1.3.44). These are: * timers, that are no more valid because of EPG changes. This should avoid the double recordings after an EPG change. * timers, that do not match the search criterions after a change of the search timer. So you don't have to remove them manually anymore. If the user has modified start or stop of such a timer, it will be kept. - new search mode 'fuzzy' in searches. This performs a fuzzy search applying an algorithm like it's used in agrep. The error tolerance can be set with the edit field 'Tolerance'. - added the 'one press' timer creation feature in EPG menus as introduced in vdr-1.3.38 with one small difference: If the event is already running or about to start within MarginStart + 2 minutes, the timer edit menu will be popup to allow editing the file/directory entry, because this cannot be changed when the recording immediatly starts. Else, the timer is created immediately. Can be turned off in setup. - with the red button in epgsearch's own timer edit menu one can now delete an existing timer, suggested by Rolf Ahrenberg. - if the main menu entry is not hidden, it's name can now be set by setup. (Note: when changing the name to something different than the default, it is no more dependent on the OSD language) - changed the default main menu entry from 'Search' to 'Program guide' - some people requested a separate main menu entry for epgsearch's search menu. Therefore I've added a little plugin called 'epgsearchonly' that simply calls epgsearch's search menu. It's main menu entry is 'Search'. Compilation of epgsearchonly is automatically done, but can be switched off in the Makefile when uncommenting the line #WITHOUT_EPGSEARCHONLY=1. To use it simply put '-P epgsearchonly' to your VDR start script. (requires >= vdr-1.3.30) - new service interface "Epgsearch-searchmenu-v1.0" to call epgsearch's search menu from other plugins. - new action 'Delete created timers?' for search entries to delete all timers created from the current search timer. Does not affect recording timers. - When deleting a search, you can now decide if all timers created from this search should also be deleted. - If the user modifies the start/stop time of a timer created by epgsearch this timer will not be changed anymore(only vdr >= 1.3.44 ) - If an event is currently recorded, the status flag in the EPG menus is now 'R' instead of 'T' - Support for wareagle-icon-patch (activate it by adding the line 'WarEagleIcons=1' to epgsearchmenu.conf) - Progressbar in Now/Next beautified when using setup option 'graphical', inspired by Nordlichts-EPG-Plugin - new setup option to show/hide radio channels in the EPG menus, suggested by Patrice Staudt. - new service interface "Epgsearch-searchresults-v1.0", that returns a result list of events matching a given search, suggested by Andreas Brugger - removed some special setup options, because their function can also be realized with a customized menu now: * "show progress bar in 'Next'", in default menu now off * "display width for progressbar", in default menu now 4 * "show short channel name", in default now always short * "Show episode text in schedules", now always displayed - update for finnish translation, thanks to Rolf Ahrenberg - aux field is now formatted in full XML style (if vdr >= 1.3.44). As a result of this, an updated recordingdone.sh is provided in the 'scripts' subdirectory. Thanks to Mike Constabel for providing a patch. - search timer update now always runs in low priority, suggested by Christian Jacobsen - new SVDRP command 'FIND'. This allows searching an event and returns a list of results consisting of 'NEWT' lines, that can be used to immediately create a timer for a result. Suggested by Lari Tuononen fixes: - thanks to Darren Salt for patches for g++ 4.1 and some things concerning thread safeness and code review - fixed some memory leaks - fixed calling user defined EPG commands, thanks to rzndl@vdrportal - fixed blacklist match for search timers, thanks to Christian Jacobsen - make sure that the episode name of a timer is less then MAX_SUBTITLE_LENGTH, thanks to Mike Constabel - speedup for search timer update Description and download: http://people.freenet.de/cwieninger/html/vdr-epg-search__english_.html wget: http://people.freenet.de/cwieninger/vdr-epgsearch-0.9.15.tgz BR, Christian

1 0

[PATCH] jumpplay patch 0.7
by Thomas Günther 14 Apr '06

14 Apr '06

Hi! Here is a new version of the jumpplay patch: http://toms-cafe.de/vdr/download/vdr-jumpplay-0.7-1.3.46.diff (applicable to VDR >= 1.3.29) Changes since version 0.6: - Fixed jump to first mark (crashed with plugin extrecmenu-0.9) - Added version define JUMPPLAYVERSNUM - Added placeholders for Czech language texts - Cleaned up i18n entries (support only VDR >= 1.3.29) - Improved description of i18n placeholders - hoping for real language texts This patch changes the replay behaviour for recordings that contain editing marks. It allows to immediately continue the replay after jumping forward to the next mark, and to automatically jump over the commercial break to the next "start" mark, if an "end" mark is reached. The features of this patch can be turned on or off in the replay setup. See README.jumpplay included in the patch for details, history and contributors. Tom

1 0

Encrypted channel without cam and channel switching
by Antti Hartikainen 14 Apr '06

14 Apr '06

Hello.. I today finally proved that this feature is in vanilla vdr and not with any plugin/patch. If setting encrypted channel CA to 0 (FTA), so i can change to "encrypted" channel.. After few seconds vdr gots "real" CA value from the stream, shows channel few secs and then thinks channel is unavailable, and changes channel until it founds channel that it thinks it can tune for.. There are some channels in hotbird that have CA-value, but aren't really encrypted. This annoying "feature" has been added somewhere before 1.3.34 i think. In my opinion, there should be an option to disable this "feature".. Changing CA to DVB card number is possible tho, but i have two DVB-S cards so it is not an option for me. Or is there CA-value that covers all different type cards (T/S/C) and on the same time says "don't touch this CA-field"?

4 8

changing transponder data of channel
by Richard Lithvall 13 Apr '06

13 Apr '06

Hi VDR-gurus. I get repeatedly annoying syslog messages from vdr stating transponder data change. I randomly grep'ed after one of many channels this happens to in the log: # grep "changing transponder data of channel 205" /var/log/syslog|tail -4 Apr 12 15:55:54 localhost vdr: [29208] changing transponder data of channel 205 from S1.0W:12303:v:27800:3 to S1.0W:12303:v:27799:3 Apr 12 15:57:41 localhost vdr: [29208] changing transponder data of channel 205 from S1.0W:12303:v:27799:3 to S1.0W:12303:v:27800:3 Apr 12 16:00:46 localhost vdr: [29208] changing transponder data of channel 205 from S1.0W:12303:v:27800:3 to S1.0W:12303:v:27799:3 Apr 12 16:02:34 localhost vdr: [29208] changing transponder data of channel 205 from S1.0W:12303:v:27799:3 to S1.0W:12303:v:27800:3 As you see it changes the freq from 27800 to 27799 and back again so I started to dig into the source and immediately found this: bool cChannel::SetSatTransponderData(int Source, int Frequency, char Polarization, int Srate, int CoderateH) { // Workarounds for broadcaster stupidity: // Some providers broadcast the transponder frequency of their channels with two different // values (like 12551 and 12552), so we need to allow for a little tolerance here if (abs(frequency - Frequency) <= 1) Frequency = frequency; As one can see, there is already a workaround for this behavior but it seems that it doesn't work. Any idea of what could be wrong? (I recently upgraded to 1.3.46, but I've seen this behavior since at least 1.3.34) Regards, Richard

4 4

Problems with xine's aspect ratio & padding with 4:3 aspect ratio
by C.Y.M 12 Apr '06

12 Apr '06

I am viewing NTSC-M with a 4:3 aspect ratio using vdr-1.3.46 and xine-0.7.8. Standard definition broadcasting. My television resolution is set to 720x480@60Hz with my ModeLine: ModeLine "720x480_60" 28.20 720 736 856 896 480 490 493 525 -hsync -vsync I have noticed that when I play a vdr recording (001.vdr) with mplayer using the XV video output, I get full screen on my television (no black borders) with perfect aspect ratio. But, when I play the same vdr recording (001.vdr) with xine and XV video output, there are huge amounts of padding (black borders) on the television. It is like xine can not expand the 4:3 aspect ratio to properly fit my tv. Is there a way to make it zoom out a little so it doesnt look like that with the black borders on all four sides of the video on the tv? Mplayer looks just fine at full screen.. I'm just trying to get the same output. I have tried disabling video scaling inside xine and that did not help. BR.

2 5

[Announce] LNB-sharing patch for VDR 1.3.46
by Matthias Lötzke 11 Apr '06

11 Apr '06

Hello! A new release of the configurable LNB-sharing patch for VDR 1.3 is available at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurableLNBshare-VDR_… Changes: - adapted to the new channel up&down switching behaviour since VDR 1.3.42 (Thanks to Ralf Fittje and Kim Sandberg for reporting and anaylsing) - added a check whether the source is an DVB-S card or not for mixed source DVB systems (Thanks to Kim Sandberg) - adapted to VDR 1.3.46 Personally I am still using VDR 1.3.38 so this release contains code changes which I have not tested. For general information about the LNB-sharing patch have a look at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt http://www.vdr-wiki.de/wiki/index.php/Lnbsharing-patch (german) Matthias.

1 0

NordlichtsEPG-8a-Plugin (DaLiMan)
by vdr＠daliman.de 11 Apr '06

11 Apr '06

Der gemailte "Patch" ist nicht komplett gewesen und somit auch nicht funktionsfähig, daß kann man in der Antwortmail vom Martin nachlesen. Angefügt habe ich jetzt einen funktionierenden Patch. Sorry. Gruß, DaLiMan The first "Patch" was incomplete. This ist the right stuff. Greet, DaLiMan --eMail1------------------------------------------------------------------------------------------- vdr(a)daliman.de schrieb: Sorry, but my english is not good enough to translate that. Ein Fehler im NordlichtsEPG-8b-Plugin bewirkt daß die Beschriftung der roten Taste nicht vorhanden ist, wenn im SetupMenü "Umschalten mit OK" gewählt wurde. Das Ändern einer Codezeile in der Datei nordlichtsepg.c, ca. Zeile 157 " *if*(switchwithok)" korrigiert das. SetHelp(next?tr("Button$Now"):NULL,"<<",">>",tr("Button$Info")); muß in SetHelp(next?tr("Button$Now"):tmp,"<<",">>",tr("Button$Info")); geändert werden. Gruß, DaLiMan --eMail2--------------------------------------------------------------------------------------------- Hi, jumping to the in the setup adjusted time with red doesn't work in alternative keymap mode, so it is pretty useless to label the red button with this time. Look at the README before complaining about an error that isn't one. Btw. is it not your task to give version numbers! Greets Martin

1 0

VDR-1.3.46 Segmentation fault
by Thomas Günther 11 Apr '06

11 Apr '06

Hi! If I try to set the time transponder the vdr crashes. :-( Program received signal SIGSEGV, Segmentation fault. (gdb) bt #0 0x401f4cff in strlen () from /lib/libc.so.6 #1 0x401f4a55 in strdup () from /lib/libc.so.6 #2 0x080e0b2f in cMenuEditItem::SetValue (this=0xa268768, Value=0x0) at menuitems.c:39 #3 0x080e3035 in cMenuEditChanItem::Set (this=0xa268768) at menuitems.c:576 #4 0x080e332e in cMenuEditTranItem (this=0xa268768, Name=0x81c91ea "Use time from transponder", Value=0xa268374, Source=0xa268370) at menuitems.c:618 #5 0x080d17d9 in cMenuSetupEPG::Setup (this=0xa268198) at menu.c:2238 #6 0x080d1b8a in cMenuSetupEPG::ProcessKey (this=0xa268198, Key=kRight) at menu.c:2284 #7 0x080e807e in cOsdMenu::ProcessKey (this=0xa237d88, Key=kRight) at osdbase.c:463 #8 0x080d69dd in cMenuSetup::ProcessKey (this=0xa237d88, Key=kRight) at menu.c:2709 #9 0x080e807e in cOsdMenu::ProcessKey (this=0xa2382b0, Key=kRight) at osdbase.c:463 #10 0x080d8226 in cMenuMain::ProcessKey (this=0xa2382b0, Key=kRight) at menu.c:2900 #11 0x08134494 in main (argc=16, argv=0xbffffa14) at vdr.c:990 Tom

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr