Re: [vdr] [ANNOUNCE] VDR developer version 2.3.1

2015-10-10 Thread Matti Horila

Finnish DVB-T channels not updating.

I was building new vdr system and copied only one channel to channels.conf from 
my current production system and noticed that channels were not updating.

Probably something to do with this:


- Fixed setting the source value of newly created channels, in case the NIT is
   received from a different, but very close satellite position (reported by 
Daniel
   Ribeiro). The code for handling different NITs has been removed from nit.c, 
because
   according to the DVB standard table id 0x40 carries only the NIT of the 
actual
   network.


After enabling DebugNit and added some more debug messages, i found out that 
sdtFilter->Trigger(Source) @nit.c:270 was never triggered.

With quick'n dirty hack others than currently tuned transponder started to 
update:
--- a/nit.c 2015-10-10 13:42:19.690169490 +0300
+++ b/nit.c 2015-10-10 13:43:04.114821083 +0300
@@ -266,7 +266,7 @@
}
}
 }
- if (ISTRANSPONDER(Frequency / 100, Transponder()))
+ //if (ISTRANSPONDER(Frequency / 100, Transponder()))
 sdtFilter->Trigger(Source);
  }
  break;


-Matti

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] [ANNOUNCE] VDR developer version 2.3.1

2015-09-14 Thread Klaus Schmidinger

VDR developer version 2.3.1 is now available at

  ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.1.tar.bz2

A 'diff' against the previous version is available at

  ftp://ftp.tvdr.de/vdr/Developer/vdr-2.2.0-2.3.1.diff

MD5 checksums:

391c2ed60e2f7d24563fe3ed5854bc4f  vdr-2.3.1.tar.bz2
983fd4bad7d19cd98301d54173107129  vdr-2.2.0-2.3.1.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.

*** PLEASE BE VERY CAREFUL WHEN USING THIS DEVELOPER VERSION, ESPECIALLY
*** IF YOU ENABLE THE NEW SVDRP PEERING! KEEP BACKUPS OF ALL YOUR TIMERS
*** AND OBSERVE VERY CLOSELY WHETHER EVERYTHING WORKS AS EXPECTED. THIS
*** VERSION INTRODUCES SOME MAJOR CHANGES IN HANDLING GLOBAL LISTS AND
*** LOCKING, SO ANYTHING CAN HAPPEN! YOU HAVE BEEN WARNED!

The main focus of this developer version is on the new locking mechanism
for global lists, and the ability to handle remote timers.
Any plugins that access the global lists of timers, channels, schedules
or recordings, will need to be adjusted (see below for details). Please
do initial tests with plain vanilla VDR and just the output plugin you
need.

Known bugs/problems:

- After deleting the last recording in a sub folder, the cursor may not
  be positioned correctly.
- Instant recordings and pausing live video don't (yet) use the default
  SVDRP host for recording.

The changes since version 2.2.0:

- The new function cOsd::MaxPixmapSize() can be called to determine the maximum 
size
  a cPixmap may have on the current OSD. The 'osddemo' example has been modified
  accordingly. Plugin authors may want to use this function in case they use 
pixmaps
  that are larger than the full OSD size. The default implementation sets this 
limit
  to 2048x2048 pixel.
- The Setup/CAM menu now displays which device an individual CAM is currently
  assigned to (suggested by Frank Neumann).
- Added detection of 24fps (thanks to Thomas Reufer).
- Added a note about the VDR User Counter and VDR's facebook page to the README 
file.
- The dvbhddevice plugin is no longer part of the VDR source archive.
  You can get the latest version of this plugin from the author's repository at
  https://bitbucket.org/powARman/dvbhddevice.
- The dvbsddevice and rcu plugins are no longer part of the VDR source archive.
  You can get the latest versions of these plugins from 
ftp://ftp.tvdr.de/vdr/Plugins.
- Added a section about Output Devices to the INSTALL file.
- Fixed setting the source value of newly created channels, in case the NIT is
  received from a different, but very close satellite position (reported by 
Daniel
  Ribeiro). The code for handling different NITs has been removed from nit.c, 
because
  according to the DVB standard table id 0x40 carries only the NIT of the actual
  network.
- Added some comment to cPixmap about the relation between OSD, ViewPort and 
DrawPort
  (suggested by Thomas Reufer).
- Improved syncing on sections when parsing the NIT and SDT.
- Fixed scaling subtitles (their areas could sometimes extend outside the 
actual OSD).
- Reduced the priority of the "video directory scanner" thread (suggested by 
Thomas
  Reufer) and checking cIoThrottle::Engaged() when it is running.
- The script that gets called for recordings is now also called right before a
  recording is edited, with the first parameter being "editing" (suggested by
  Dieter Ferdinand).
- The new setup option "OSD/Default sort mode for recordings" can be used to 
define
  how recordings shall be sorted by default (either by time or by name, with "by 
time"
  being the default). If a particular sort mode has been selected for a folder 
by
  pressing '0', the default no longer applies to that folder. Repeating timers 
no
  longer write a ".sort" file into a recordings folder to have the recordings 
sorted
  by time.
- The command line option -D now accepts the value '-' (as in -D-), which 
prevents
  VDR from using any DVB devices (suggested by Dietmar Spingler).
- The -V and -h options now list the plugins in alphabetical order (suggested by
  Dietmar Spingler).
- Fixed a compiler warning in font.c.
- Commented out the line
  #define DEPRECATED_VIDEOSYSTEM
  in device.h. If a plugin doesn't compile with this version of VDR, you can 
uncomment
  this line as a quick workaround. In the long run the plugin will need to be 
adapted.
- The function cOsd::GetBitmap() is now 'protected'. If a plugin doesn't 
compile with
  this version of VDR, you can uncomment the line
  //#define DEPRECATED_GETBITMAP
  in osd.h as a quick workaround. In the long run the plugin will need to be 
adapted.
- The -u option now also accepts a numerical user id (suggested by Derek Kelly).
- The SVDRP port now accepts multiple concurrent connections. You can now keep 
an
  SVDRP connection open as long as you wish, without preventing others from
  connecting. Note, though, that SVDRP connec