vdr February 2013

vdr@linuxtv.org

49 participants
41 discussions

Re: [vdr] : Positioner and multi-tuner setup?
by Teemu Suikki 22 Feb '13

22 Feb '13

I'm replying to an old message, because soon I will have similar setup so I'm interested. :) I currently have two tuners with fixed dish to S1.0W, and third tuner with diseqc motor. I'm using diseqc.conf and the gotoxx patch, it works very well! However I'm adding fourth tuner soon. It will be connected to the motor dish too. I have been examining vdr's Device Bonding feature. If two devices are bonded and Diseqc is enabled, vdr will compare the diseqc strings of the already tuned master, with the diseqc string of the new channel on the other device. If they match, channel change is accepted. So basically it should work if you simply have same diseqc config for both bonded devices. However, there is a problem that also the polarisation and low/high frequency range is compared. This means that the bonded device is restricted to same polarisation and frequency range. This would need some patching in dvbdevice.c.. 27.12.2012 16.06 "Antti Hartikainen" <ami+vdr(a)ah.fi> kirjoitti: Hi. I would want to somehow configure VDR to use positioner (H-H motor) and dual tuner setup, to receive two transponders from same source at one time. My current hardware setup is: TechnoTrend S2-6400 dual tuner DVB-S2 with H/W decoder, H-H motor and a quad LNB. I'm using diseqc commands in diseqc.conf to control the motor, as GOTOXX patch and rotorng plugin are both too buggy to be used. Rotorng I used to store the positions. Currently I only have one tuner in use, and it is connected to the motor. I was wondering if it would be somehow possible to get second tuner in use also. It would be connected directly to LNB, and that tuner would be limited to the same satellite source as the other tuner is tuned to, and have independent frequency/polarization. Thanks. PS. What is the current recomended way for using positioner with VDR? Preferred would be a USALS capable setup. _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

5 8

HD Test clip(s)
by th_ziegler＠gmx.de 21 Feb '13

21 Feb '13

Hi, Are there any VDR-compatible (I'm using e-tobi 1.7.29) HD test clips, available somewhere on the net or can s.o. provide one? For better comparisson with SD, the a clip from the German ARD- or ZDF-news would be nice. A few minutes is sufficient. Background for those who are interested: I'm using DVB-T based vdr since a couple of years now for in-house streaming to various devices. I plan to add a DVB-S card to support HD. I'd like to check if HD-streaming works with my current setup before doing the investment in a sattelite dish etc. Any other hints regarding what USB DVB-S receiver, sat-dish, etc. works well is also welcome. Thanks, Thomas

7 9

Device bonding
by Juergen Lock 19 Feb '13

19 Feb '13

Hi! Now that I have a spare DVB-S2 tuner (TechniSat SkyStar USB HD (adapter2); the others on this box are atm Hauppauge Nova-TD model 1172 (adapter 0+1) and TechnoTrend S2-3600 (adapter3) - all USB) I decided to play with vdr device bonding. I discovered three things: (still using vdr 1.7.29, I know I should upgrade... :) 1. The LNB setup OSD menu causes bonding to fail (it's trying to bond a DVB-T tuner) if I set the two DVB-S2 tuners as "connected to sat cable 1"; it works with "sat cable 2". Maybe it somehow thinks of (one of?) the DVB-T tuner(s) as cable 1 too? 2. The infosatepg plugin doesn't check MaySwitchTransponder() and thus grabs a bonded device when it shouldn't, I just patched that in the FreeBSD port: (plugin maintainer Cc'd) http://svnweb.freebsd.org/ports/head/multimedia/vdr-plugin-infosatepg/files… 3. Running with these four tuners (dual DVB-T and the bonded two DVB-S2) I get two different deadlocks waiting for cDvbTuner::bondMutex after live viewing a DVB-T(!) channel for longer (OSD doesn't react anymore and attaching gdb reveals two threads waiting for bondMutex) - the following two changes make it work but there probably is a better fix: (patch may apply with offsets; one of the problems I think is a lock order reversal with cDvbTuner::mutex and bondMutex when cDvbTuner::SetChannel calls back into itself with bondMutex held.) --- dvbdevice.c.orig +++ dvbdevice.c @@ -476,8 +476,10 @@ void cDvbTuner::SetChannel(const cChanne t->SetChannel(NULL); } } - else if (strcmp(GetBondingParams(Channel), BondedMaster->GetBondingParams()) != 0) + else if (strcmp(GetBondingParams(Channel), BondedMaster->GetBondingParams()) != 0) { + bondMutex.Unlock(); BondedMaster->SetChannel(Channel); + } } cMutexLock MutexLock(&mutex); if (!IsTunedTo(Channel)) @@ -761,7 +773,12 @@ bool cDvbTuner::SetFrontend(void) tone = SEC_TONE_ON; } int volt = (dtp.Polarization() == 'V' || dtp.Polarization() == 'R') ? SEC_VOLTAGE_13 : SEC_VOLTAGE_18; - if (GetBondedMaster() != this) { +#if 1 + if (bondedTuner && !bondedMaster) +#else + if (GetBondedMaster() != this) +#endif + { tone = SEC_TONE_OFF; volt = SEC_VOLTAGE_13; } Thanx, Juergen

2 10

Re: [vdr] Device bonding
by Klaus Schmidinger 19 Feb '13

19 Feb '13

On 19.02.2013 01:48, Juergen Lock wrote: > On Mon, Feb 18, 2013 at 11:52:31PM +0100, Klaus Schmidinger wrote: >> On 18.02.2013 23:43, Juergen Lock wrote: >>> In article <5121FBA4.2050108(a)tvdr.de> you write: >>>> On 16.02.2013 16:46, Juergen Lock wrote: >>>>> Hi! >>>>> >>>>> Now that I have a spare DVB-S2 tuner (TechniSat SkyStar USB HD >>>>> (adapter2); the others on this box are atm Hauppauge Nova-TD model >>>>> 1172 (adapter 0+1) and TechnoTrend S2-3600 (adapter3) - all USB) I >>>>> decided to play with vdr device bonding. I discovered three things: >>>>> (still using vdr 1.7.29, I know I should upgrade... :) >>>>> >>>>> 1. The LNB setup OSD menu causes bonding to fail (it's trying to >>>>> bond a DVB-T tuner) if I set the two DVB-S2 tuners as "connected >>>>> to sat cable 1"; it works with "sat cable 2". Maybe it somehow >>>>> thinks of (one of?) the DVB-T tuner(s) as cable 1 too? >>>> >>>> What does the "Setup/LNB" menu look like on your system? >>>> Does it list only the two DVB-S devices, or all four of them? >>>> Which device numbers does it display? >>>> >>>> What does the "DeviceBondings = ..." line in setup.conf look like >>>> in both cases (working/not working)? >>>> >>> working: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 2 >>> Device 4 angeschlossen an Sat-Kabel: 2 >>> >>> -> >>> DeviceBondings = 1 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> broken: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 1 >>> Device 4 angeschlossen an Sat-Kabel: 1 >>> >>> -> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>>> You wrote that your DVB-S2 device is "adapter2". Does this mean it >>>> is actually "adaper2/frontend0" and "adapter2/frontend1"? >>>> >>> No the other DVB-S2 tuner is adapter3 (TechnoTrend S2-3600), all four >>> only have frontend0 no frontend1. >>> >>>> Have you appliead any patches to VDR? >>> >>> Currently the two patches belonging to the iptv and ttxtsubs plugins >>> and my stb0899 signal strength patch, and of course the FreeBSD >>> portability patches. >>> >>>> If so, what happens without them? >>> >>> I will have to check that later tho I guess they are unrelated... >>> >>>> Same for plugins. >>>> >>> I just started vdr with just the xineliboutput plugin (I don't have >>> an ff card) and got the same >>> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> when setting both DVB-S2 tuners as ".. connected to sat cable 1". >>> >>> I wonder, could this be a result of me running vdr with only the DVB-S2 >>> tuners once and the first 1 in DeviceBondings that I may have set then >>> simply doesn't get reset when the first two tuners became DVB-T? >> >> I'll have to further look into this, but you might be on to something here. >> Please stop VDR, set that line to >> >> DeviceBondings = 0 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> >> manually and restart VDR. Does it work then? >> > Yeah, looks like. (I should have tested that earlier... :) Just one more thing: did you get any log messages regarding device bonding when it didn't work? > Btw did you take a look at the bondMutex vs mutex locking yet? I've had > no further deadlocks with the second patch now. I was a little cnfused about this at first ;-) Will look into it later. BTW: you sent your original posting "To" me and "Cc"d the VDR-ML. Therefore my reply inadvertently only went to you and not to the list. I'm no replying explicitly to the list. Please send postings only to the list and do not Cc me (unless you only want to contact me privately). Klaus

2 3

Re: [vdr] Device bonding
by Klaus Schmidinger 19 Feb '13

19 Feb '13

On 19.02.2013 01:48, Juergen Lock wrote: > On Mon, Feb 18, 2013 at 11:52:31PM +0100, Klaus Schmidinger wrote: >> On 18.02.2013 23:43, Juergen Lock wrote: >>> In article <5121FBA4.2050108(a)tvdr.de> you write: >>>> On 16.02.2013 16:46, Juergen Lock wrote: >>>>> Hi! >>>>> >>>>> Now that I have a spare DVB-S2 tuner (TechniSat SkyStar USB HD >>>>> (adapter2); the others on this box are atm Hauppauge Nova-TD model >>>>> 1172 (adapter 0+1) and TechnoTrend S2-3600 (adapter3) - all USB) I >>>>> decided to play with vdr device bonding. I discovered three things: >>>>> (still using vdr 1.7.29, I know I should upgrade... :) >>>>> >>>>> 1. The LNB setup OSD menu causes bonding to fail (it's trying to >>>>> bond a DVB-T tuner) if I set the two DVB-S2 tuners as "connected >>>>> to sat cable 1"; it works with "sat cable 2". Maybe it somehow >>>>> thinks of (one of?) the DVB-T tuner(s) as cable 1 too? >>>> >>>> What does the "Setup/LNB" menu look like on your system? >>>> Does it list only the two DVB-S devices, or all four of them? >>>> Which device numbers does it display? >>>> >>>> What does the "DeviceBondings = ..." line in setup.conf look like >>>> in both cases (working/not working)? >>>> >>> working: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 2 >>> Device 4 angeschlossen an Sat-Kabel: 2 >>> >>> -> >>> DeviceBondings = 1 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> broken: >>> >>> Einstellungen - LNB >>> >>> DiSEqC benutzen: nein >>> SLOF (MHz): 11700 >>> Untere LNB-Frequenz (MHz): 9750 >>> Obere LNB-Frequenz (MHz): 10600 >>> Device 3 angeschlossen an Sat-Kabel: 1 >>> Device 4 angeschlossen an Sat-Kabel: 1 >>> >>> -> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>>> You wrote that your DVB-S2 device is "adapter2". Does this mean it >>>> is actually "adaper2/frontend0" and "adapter2/frontend1"? >>>> >>> No the other DVB-S2 tuner is adapter3 (TechnoTrend S2-3600), all four >>> only have frontend0 no frontend1. >>> >>>> Have you appliead any patches to VDR? >>> >>> Currently the two patches belonging to the iptv and ttxtsubs plugins >>> and my stb0899 signal strength patch, and of course the FreeBSD >>> portability patches. >>> >>>> If so, what happens without them? >>> >>> I will have to check that later tho I guess they are unrelated... >>> >>>> Same for plugins. >>>> >>> I just started vdr with just the xineliboutput plugin (I don't have >>> an ff card) and got the same >>> >>> DeviceBondings = 1 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>> >>> when setting both DVB-S2 tuners as ".. connected to sat cable 1". >>> >>> I wonder, could this be a result of me running vdr with only the DVB-S2 >>> tuners once and the first 1 in DeviceBondings that I may have set then >>> simply doesn't get reset when the first two tuners became DVB-T? >> >> I'll have to further look into this, but you might be on to something here. >> Please stop VDR, set that line to >> >> DeviceBondings = 0 0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> >> manually and restart VDR. Does it work then? >> > Yeah, looks like. (I should have tested that earlier... :) This should fix the device bondings once you open and confirm the Setup/LNB menu: --- menu.c 2013/02/17 13:17:49 2.79 +++ menu.c 2013/02/19 09:33:26 @@ -2965,6 +2965,8 @@ for (int i = 0; i < cDevice::NumDevices(); i++) { if (cDevice::GetDevice(i)->ProvidesSource(cSource::stSat)) Add(new cMenuEditIntItem(cString::sprintf(tr("Setup.LNB$Device %d connected to sat cable"), i + 1), &satCableNumbers.Array()[i], 0, NumSatDevices, tr("Setup.LNB$own"))); + else + satCableNumbers.Array()[i] = 0; } } Klaus

2 1

[ANNOUNCE] VDR developer version 1.7.36
by Klaus Schmidinger 19 Feb '13

19 Feb '13

VDR developer version 1.7.36 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.36.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.35-1.7.36.diff MD5 checksums: e514f72a2a8c44f39e47b540d6ad325f vdr-1.7.36.tar.bz2 9312a0d10bcda87d3c3c7e6dfbebcd05 vdr-1.7.35-1.7.36.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.7.35: - Added maximum SNR value for PCTV Systems nanoStick T2 290e (thanks to Antti Hartikainen). - Added a remark indicating that the coordinates of Rect in a call to cDevice::CanScaleVideo() are in the range of the width and height returned by GetOsdSize() (suggested by Reinhard Nissl). - Modified the Makefiles (thanks to Christopher Reimer). By default VDR is now built according to the FHS ("File system Hierarchy Standard"), and a plain "make" in the VDR source directory just builds everything, but doesn't copy it to ./PLUGINS/lib and ./locale any more. You can use a Make.config file (copied from Make.config.template) and set the parameter LCLBLD=1 to have everything built and installed under the VDR source tree (as was the default in previous versions). If you already have your own Make.config file, you may want to copy the new Make.config.template and adapt it to your needs. If you don't want VDR's data files to be spread around your system according to the FHS, you can set the parameter ONEDIR=1 (using Make.config) to have all files in one /video directory as before. - Fixed the example for cReceiver in PLUGINS.html. - Fixed sorting recordings in case two folders have the same name, but one of them ends in an additional digit, as in "abc" and "abc2" (reported by Andreas Mair). - Added "repeat" function when using the keyboard to control VDR (thanks to Reinhard Nissl). - The SVDRP command LSTR now knows the additional parameter "path", which can be given to get the actual file name of a recording's directory (suggested by Stefan Stolz). - Fixed multiple occurrences of the same directory in the recordings list in case there are directories that only differ in non-alphanumeric characters (reported by Andreas Mair). - Absolute jumps when replaying a recording (via the Red key) are now only performed if an actual value has been entered (suggested by Ulf Kiener). - The last replayed recording is now stored in setup.conf, which allows the blue "Resume" key in the main menu to work even after a restart of VDR. - The SVDRP command NEWT no longer checks whether a timer with the given data already exists (suggested by Malte Forkel). - Implemented scaling of SPU bitmaps (thanks to Johann Friedrichs). - Improved cutting MPEG-2 video (thanks to Sören Moch). - Reduced the number of retries in cTransfer::Receive() to avoid blocking recordings in case the primary device can't handle the current live signal. Have fun! Klaus

8 24

Request to translate cdplayer-plugin
by Ulrich Eckhardt 18 Feb '13

18 Feb '13

Hi, i want to ask, if someone is willing to help to add additional translations to the cd-player plugin? http://www.uli-eckhardt.de/vdr/cdplayer.en.shtml it_IT: 33 translated messages, 1 fuzzy translation, 13 untranslated messages. ro_RO: 41 translated messages, 6 untranslated messages. de_DE: 30 translated messages, 1 fuzzy translation, 16 untranslated messages. Best Regards Uli -- Ulrich Eckhardt http://www.uli-eckhardt.de Ein Blitzableiter auf dem Kirchturm ist das denkbar stärkste Misstrauensvotum gegen den lieben Gott. (Karl Krauss)

5 7

Call for translations for VDR version 2.0.0
by Klaus Schmidinger 18 Feb '13

18 Feb '13

VDR is now approaching version 2.0.0, so this might be a good time for translators to complete the internationalized texts. Here's a list of the language files that still need some work, together with the number of untranslated texts in each of them: nn_NO.po: 261 el_GR.po: 196 ar.po: 138 sl_SI.po: 134 tr_TR.po: 133 sv_SE.po: 133 pl_PL.po: 133 nl_NL.po: 133 hr_HR.po: 133 fr_FR.po: 133 es_ES.po: 133 da_DK.po: 133 ca_ES.po: 133 ru_RU.po: 131 zh_CN.po: 129 hu_HU.po: 105 sr_SR.po: 52 cs_CZ.po: 34 uk_UA.po: 29 pt_PT.po: 27 lt_LT.po: 27 fi_FI.po: 11 ro_RO.po: 6 mk_MK.po: 5 sk_SK.po: 2 it_IT.po: 2 et_EE.po: 2 Please base your work on the latest version of these files in VDR 1.7.37 and send me proper patches. Thanks Klaus

14 38

[PATCH] Suggest naming central plugin make config as plugin.mk.
by Ville Skyttä 18 Feb '13

18 Feb '13

Makes it clearer that it's a Makefile snippet, distinguishes from VDR conf files. Reposted here per Klaus' request, he'd like to see 3 people ack this. --- Make.config.template | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Make.config.template b/Make.config.template index b02d796..5bd0a10 100644 --- a/Make.config.template +++ b/Make.config.template @@ -62,7 +62,7 @@ endif # Use this if you want to have a central place where you configure compile time # parameters for plugins: -#PLGCFG = $(CONFDIR)/plugins.conf +#PLGCFG = $(CONFDIR)/plugins.mk ### The remote control: -- 1.7.11.7

3 2

[ANNOUNCE] VDR developer version 1.7.38
by Klaus Schmidinger 17 Feb '13

17 Feb '13

VDR developer version 1.7.38 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.38.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.37-1.7.38.diff MD5 checksums: f4ef0f60ed662f3c983a830da67df9b2 vdr-1.7.38.tar.bz2 e945b0f44e13ed768de726cf6e66317c vdr-1.7.37-1.7.38.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. Approaching version 2.0.0: ========================== If all goes well, there should be no more functional or API changes before the final version 2.0.0. There will just be a few more fixes. The changes since version 1.7.37: - Updated the Ukrainian OSD texts (thanks to Yarema Aka Knedlyk). - Updated the Estonian OSD texts (thanks to Arthur Konovalov). - Updated the Romanian OSD texts (thanks to Lucian Muresan). - Updated the French OSD texts (thanks to Marc Perrudin, Bernard Jaulini and Peter Münster). - Updated the Macedonian OSD texts (thanks to Dimitar Petrovski). - Fixed moving editing marks, so that they don't get overwritten with old values through an update of the marks file. - Removed an invalid line from channels.conf.terr (reported by Lars Hanisch). - Fixed an unexpected k_Repeat key event after a k_Release in lirc.c. - Fixed permissions of po/sr_SR.po (reported by Dominic Evans). - Updated the Italian OSD texts (thanks to Diego Pierotto). - Fixed using "Pause" and "Slow motion" near the end of a recording (replay stopped a few seconds after the end of the recording file has been reached). - Fixed selecting the last replayed recording in the Recordings menu in case there are folders and plain recordings with names that differ only in non-alphanumeric characters (reported by Andre Weidemann). - Fixed the description of the OSD drawing functions DrawEllipse() (the values -5...-8 for the Quadrants parameter are not implemented). - Made cOsd::DestroyPixmap() "NULL proof". - Now deleting any previously allocated pixmaps in cOsd::SetAreas(). - Added demos of the DrawEllipse() and DrawSlope() function to the 'osddemo' plugin (press '1' or '2', respectively). - Updated the Lithuanian OSD texts (thanks to Valdemaras Pipiras). - The timeout for trying to switch to a valid programme is now reset immediately once a programme has been found. - No longer checking for EOPNOTSUPP in cDvbTuner::GetSignalQuality() to avoid breaking this function in case the driver suddenly decides to return a different errno value if an operation is not supported. - Moved the definition of TIMERMACRO_TITLE and TIMERMACRO_EPISODE from recording.h to config.h and using them to initialize Setup.NameInstantRecord (avoids having the same information in two places). - Fixed the return value of cOsdProvider::StoreImage() in case there is no OSD provider. - Fixed a crash in cMenuEditChanItem::Set() when entering a channel number that doesn't exist (reported by Mikael Hübsch). - Fixed displaying pending timers in "alert" mode in the LCARS skin. - Added missing $(LDFLAGS) to the Makefile of the dvbhddevice plugin (thanks to Ville Skyttä). - Fixed some spellings in PLUGINS.html and Doxyfile (thanks to Ville Skyttä). - Added '-p' to the cp command in the install-conf target of the Makefile (thanks to Ville Skyttä). - Added missing 'const' to cDevice::HasProgramme() and cDevice::HasLock(). - Fixed determining the priority of the primary device in case it is neither replaying nor receiving a live channel (thanks to Matthias Senzel for reporting a problem with switching back to live viewing after replay in a setup with device bonding). - Removed all \return and \param tags from comment lines marked with "///<" for Doxygen. There was only a rather small number of these, and I would probably always forget to put them in place when writing future comments, so I decided to drop them entirely. - Added Doxyfile.filter to have special characters escaped that would otherwise be dropped by Doxygen (reported by Ville Skyttä). - Using 'cat' instead of 'cp' to copy the Doxyfile to avoid problems in case Doxyfile is write protected. - Updated the Doxyfile with a newer version of Doxygen. - Turned off following symlinks in the Doxyfile. - Removed trailing whitespace. - Expanded tabs in PLUGINS/src/dvbhddevice/setup.c. - Some formatting fixes. Have fun! Klaus

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2013