vdr

vdr@linuxtv.org

6742 discussions

[ANNOUNCE] VDR developer version 2.3.6
by Klaus Schmidinger 04 Jun '17

04 Jun '17

VDR developer version 2.3.6 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.6.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.5-2.3.6.diff MD5 checksums: eab982df03da492a7d263718a8c487c2 vdr-2.3.6.tar.bz2 84a53afa495740bfdf9aab4b8900df99 vdr-2.3.5-2.3.6.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 2.3.5: - Added backtrace functions for debugging (see cBackTrace in thread.h). - Added checking the correct sequence of locking global lists (with help and suggestions from Jasmin Jessich). At the first occurrence of an invalid locking sequence, the 20 most recent locks will be written to the log file, followed by a backtrace that led to the call in question. This code can be activated by defining the macro DEBUG_LOCKSEQ in thread.c (which is on by default). When debugging an actual invalid locking sequence, you can additionally define the macro DEBUG_LOCKCALL in thread.c, which will add information about the caller of each lock. Note that this may cause some stress on the CPU, therefore it is off by default. - The file Make.config.template now reacts on DEBUG=1 in the 'make' command line, and disables code optimizations by setting -O0 (thanks to Jasmin Jessich). This can be helpful when backtracing highly optimized code. You may want to 'make distclean' before running 'make' with a modified setting of DEBUG, to make sure all object files are newly compiled. - Fixed the locking sequence when dumping EPG data. - Fixed the locking sequence when starting a recording. - The Makefiles now use the macro $(Q) instead of a plain '@' in front of their commands, so that verbosity can be controlled by the user (suggested by Jasmin Jessich). Add VERBOSE=1 to the 'make' call in the VDR source directory to see the actual commands that are executed. Plugin authors should modify their makefiles accordingly, by simply preceeding the respective commands with '$(Q)' and inserting '@echo XX $@' (where XX is one of the character combinations listed in the release note for version 2.3.5) before the command. The newplugin script has also been modified accordingly. Note that if you build a plugin directly in the plugin's own source directory, the $(Q) macro won't be defined and commands will be displayed. You can add Q=@ to the make call to have it less verbose (provided the plugin's Makefile was modified as described above). - Added clearing CiResourceHandlers before shutting down the plugin manager. - Fixed a double channel switch when pressing the Channel+/- keys while no menu or channel display is open. - Fixed generating k_Release key events for LIRC remote controls (due to the short timeout another normal key was sometimes put into the queue after the generated release). Also removed some code redundancy and added some buffer checks. - Now using a separate mutex to fix the race between SVDRP CHAN and cDevice::HasProgramme(), because the previous fix caused a deadlock (reported by Derek Kelly). - Fixed a possible crash in case the SVDRP connection to a peer VDR is terminated while getting remote timers. - Fixed the locking sequence when creating a new timer from the Schedules menu. - Fixed the locking sequence when switching between 'Now', 'Next' and 'Schedule' in the Schedules menu. Have fun! Klaus

1 0

ISMAR 2017 - Call for Workshop Papers
by Myriam Servières 01 Jun '17

01 Jun '17

Call for ISMAR 2017 Workshop Papers The ISMAR 2017 organizing committee invites papers to be submitted in the workshops at the ISMAR 2017 conference. The workshops will be held on 9th and 13th October 2017, in Nantes, France. Important Dates * Deadline Workshops Papers: July 3rd, 2017 * Notification Workshops Papers: August 7th, 2017 * Workshops Papers Camera Ready Deadline: August 28th, 2017 * Workshops Dates: Oct 9th and 13th, 2017 List of ISMAR 2017 workshops: https://ismar2017.sciencesconf.org/resource/page/id/29 <https://ismar2017.sciencesconf.org/resource/page/id/29> The workshops provide participants with the opportunity to present and discuss research ideas on cutting-edge research topics related to Augmented, Mixed, and Virtual Reality as Science & Technology and Arts, Media, & Humanities. We encourage researchers from different academic communities as well as from industry and public institutions to bring together and to collaborate and discuss with each other about possible future topics and trends. Contact ISMAR 2017 Workshop and Tutorial Chairs: wt_chairs(a)ismar17.org <mailto:wt_chairs@ismar17.org> * Gerd Bruder, University of Central Florida, USA * Myriam Servières, Ecole Centrale de Nantes, France * Maki Sugimoto, Keio University, Japan

1 0

[ANNOUNCE] VDR developer version 2.3.5
by Klaus Schmidinger 25 May '17

25 May '17

VDR developer version 2.3.5 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.5.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.4-2.3.5.diff MD5 checksums: 9ca7c556d1fdd733facb6cd9053a4067 vdr-2.3.5.tar.bz2 fbadd411b1ef36dcd8be67d23b3ea41d vdr-2.3.4-2.3.5.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 2.3.4: - CAMs are now sent a generated EIT packet that contains a single 'present event' for the current SID, in order to avoid any parental rating dialogs. - Fixed handling UNC values (the shift operator behaves unexpected for shift values larger than the size of the variable). - Log messages about switching channels now include the channel ID (suggested by Dietmar Spingler). - Events in the EIT that end before the EPG linger time are now ignored in the incoming data stream, because they would just be deleted in the next schedules cleanup anyway. - The constructor of cHash (via cHashBase) now has an additional parameter (OwnObjects) which, if set to true, makes the hash take ownership of the hashed objects, so that they are deleted when the hash is cleared or destroyed. - Fixed a memory leak in cSectionSyncerHash. The cSectionSyncerEntry objects put into the hash were never explicitly deleted. Now the cSectionSyncerHash takes ownership of these objects. - cListObject now implements a private copy constructor and assignment operator, to keep derived objects from calling them implicitly. - When selecting a device/CAM combination for live viewing, CAMs that are known to decrypt the requested channel are now given a higher priority than prefering the primary device (reported by Christian Winkler). - Changed the default return value of cEpgHandler::BeginSegmentTransfer() to true, to avoid problems with derived classes that don't implement this function (reported by Frank Neumann). - Fixed selecting delivery system names in case of undefined indexes (thanks to Jasmin Jessich). - Changed the legacy delivery system name "DMBTH" to "DTMB", and added names for DVBC_ANNEX_C and DVBC2. - Added a Status parameter to the interface of cDevice::SignalStats() and cDvbDevice::SignalStats() (thanks to Rolf Ahrenberg). - Fixed handling line numbers in error messages when reading EPG data. - Added handling RI_HOST_CONTROL to the CI protocol (no actual processing, but its presence is required by some CAMs). - Fixed a crash in case the bottom text of a CAM menu is empty. - Extended the CI API to allow plugins to implement additional CAM resources. - Fixed a race between SVDRP CHAN and cDevice::HasProgramme() (reported by Dietmar Spingler). - Reduced the time before a CAM is marked as known to decrypt a particular channel to 3 seconds. - When the connection to a peer VDR is terminated, any remote timers of that peer are no longer shown on the local VDR. - No longer setting a new timer's remote host name if "SVDRP peering" is turned off. - Fixed a double deletion of a cTimer in case HandleRemoteModifications() returned false (thanks to Johann Friedrichs). - Removed TsGetContinuityCounter() from remux.h, using TsContinuityCounter() instead. - Fixed setting the local machine's SVDRP host name (was overwritten if setup.conf contained an empty string). The SVDRP host name is now only written to setup.conf if it differs from the system's host name. - If the Channel+/- keys are pressed while in the Schedules menu, the menu is now switched to the EPG of the new current channel. - The Makefiles have been modified so that during the build process they no longer display the actual (lengthy) commands, but rather just the name of the file that is being built, as in CC vdr.o The first two characters indicate the kind of operation (CC=compile, LD=link, AR=archive, MO=msgfmt, GT=xgettext, PO=msgmerge, IN=install). This way it is much easier to spot error messages and warnings, since they are not buried under tons of text. Plugin authors should modify their makefiles accordingly, by simply preceeding the respective commands with an '@' and inserting '@echo XX $@' (where XX is one of the character combinations listed above) before the command. The newplugin script has also been modified accordingly. - Fixed detecting the inclusion of STL header files in tools.h (thanks to Jasmin Jessich). Have fun! Klaus

1 1

EPG data collected but not shown?
by Markku Tavasti 08 May '17

08 May '17

Hi! I upgraded rather old VDR system (Ubuntu 11.10 -> 16.04) and everyhting seems to work, excepth EPG data is not shown at all. On channel info box or in schedule there is nothing. EPG data is collected correctly. I removed file, it was re-created, with ok looking data. On log there is: May 1 09:24:51 vdr vdr: [2963] epg data writer thread started (pid=1084, tid=2963, prio=low) May 1 09:24:51 vdr vdr: [2963] epg data writer thread ended (pid=1084, tid=2963) I'm running Ubuntu 16.04, vdr is 2.2.0-5build1 Any suggestions? --Tavasti

6 17

[ANNOUNCE] VDR developer version 2.3.4
by Klaus Schmidinger 27 Apr '17

27 Apr '17

VDR developer version 2.3.4 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.4.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.3-2.3.4.diff MD5 checksums: 7b1c985d5e7703f7ec46e3818f546702 vdr-2.3.4.tar.bz2 bacbe7b334a4aa0827d95938e3a1ec6d vdr-2.3.3-2.3.4.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. ** IMPORTANT: ** ========== ** ** If you use any of the plugins "ddci2", "satip" or "dvbapi", please make ** sure you get the latest version from their respective repositories! The changes since version 2.3.3: - The functionality of HandleRemoteModifications(), which synchronizes changes to timers between peer VDR machines, has been moved to timers.[ch] and renamed to HandleRemoteTimerModifications(). It now also handles deleting remote timers. - The function cEpgHandlers::BeginSegmentTransfer() is now boolean (thanks to Jörg Wendel). See the description in epg.h for the meaning of the return value. - Changed tEventID back to u_int32_t (suggested by Jörg Wendel). The change to u_int16_t in version 2.3.1 was ill-conceived, because the description of the "event id" in vdr.5 explicitly mentioned this parameter to be 32 bit in size! The members of cEvent have been slightly rearranged to minimize the memory requirements on both 32 and 64 bit systems. - The file 'cam.data' is no longer written if it is read-only. - Detecting whether a particular CAM actually decrypts a given channel is now done separately for each receiver. - The cEvent class now has a new member 'aux', in which external applications can store auxiliary information with an event (thanks to Jörg Wendel). This string has no meaning whatsoever to VDR itself, and it will not be written into the info file of a recording that is made for such an event. - Added some guidelines and recommendations to the 'Logging' section of PLUGINS.html. The most important being: implement a command line option to control the level of logging (in particular allow turning off logging completely!) and never print anything to stdout or stderr (unless one of the listed exceptions applies). - Added a note to the "Pausing live video" section of the MANUAL, stating that the timer for paused live video will always record on the local VDR, even if an "SVDRP default host" has been set for normal timer recordings. - cOsdMenu::Display() now checks whether the OSD size has changed and if so calls SetDisplayMenu(). - The SVDRP commands that deal with recordings (DELR, EDIT, LSTR, MOVR, and PLAY) now use a unique id for each recording, which remains valid as long as this instance of VDR is running. This means that recordings are no longer continuously numbered from 1 to N in LSTR. There may be gaps in the sequence, in case recordings have been deleted, and they are not necessarily listed in numeric order. Thanks to Sergey Chernyavskiy. - Changed 'number' to 'id' in the help texts of SVDRP commands that deal with timers. - Fixed a deadlock in the SVDRP command PLAY in case there is currently a recording being replayed. - Signal strength and quality (CNR) are now determined via DVB API 5 (if available). Fallback is the old DVB API 3 method. - The function cCamSlot::Decrypt() can now also be called with Data == NULL. This is necessary to allow CAMs that copy the incoming data into a separate buffer to return previously received and decrypted TS packets. See ci.h for details. Plugins that implement a derived cCamSlot need to properly handle this case, and plugins that implement a derived cDevice need to call Decrypt() in their GetTSPacket() function even if the incoming buffer is currently empty (see cDvbDevice::GetTSPacket()). - cTSBuffer::Skip() no longer immediately deletes the given number of bytes from the TS buffer, but rather stores the number for later deletion in the next call to Get(). This is necessary because in cDvbDevice::GetTSPacket() tsBuffer->Skip() is called, but the actual TS packet returned (pointed to by Data) may well be (and typically is, unless the CAM copies the data) in the area of the buffer that would be deleted by Skip(). - The new function cDevice::SignalStats() (if implemented by an actual device) returns statistics about the currently received signal. - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Fixed displaying remote timers in the main menu of skin LCARS. - Fixed editing a remote timer immediately after it has been created. - Fixed handling the uncorrected block counter for DVB API 3 devices when calculating signal quality. - The SVDRP command LSTC can now list the channels with channel ids if the option ':ids' is given (suggested by Dietmar Spingler). - If 0 is given as the channel number in the SVDRP command LSTC, the data of the current channel is listed. - Fixed a possible crash when pulling the CAM while decrypting a channel with MTD. Have fun! Klaus

1 0

private cReplayControl::marks
by dev＠cyphermonks.org 22 Apr '17

22 Apr '17

a plugin which wants to act on replaying can get the cControl and access its GetReplayMode() and GetIndex() and the like, but sadly not its marks as they are private. when setting marks when replaying, these seem not to be written until the replaying is ended. so for the plugin there seems to be no way to get the current marks? i guess it would make sense to make the control's marks public or have a public method to get them?

2 1

vdr-convert version 2 released
by Richard F 09 Apr '17

09 Apr '17

I'm pleased to announce that version 2 of vdr-convert has been released over at https://projects.vdr-developer.org/projects/vdr-convert. There are several significant new features: * Option to convert to H265/HEVC via new -v switch, with potential for file size 1/2 of H264, 1/4 of MPEG2 * Multiple format options in single-use/batch modes via -f flag: avi, mkv, mp4, mov, m2ts, ts, aac, m4a and mp3 * A new debug function facilitated testing and the creation of an extensive player/format/stream compatibility matrix at: https://projects.vdr-developer.org/projects/vdr-convert/wiki/Wiki#Compatibi… "/In summary, some players are good for almost all formats, and if you don't need subtitles or automatic aspect ratio switching, most players will play most formats" / * Added support for Fraunhofer AAC codec and libmp3lame codec for mp3 via new -a switch * Added automatic conversion of AC3/DTS streams in VDR1.x recordings (thanks for sample recording contributions from this list) * Added automatic conversion of editing marks to .edl files for Kodi, mplayer in single-use mode * Info, warn and error criticality for different types of problems + optional email at criticality "error" * Conversion runtime + realtime/runtime ratio logged * Wiki extensively updated with new options at https://projects.vdr-developer.org/projects/vdr-convert/wiki +Various other fixes and improvements; todo's cleared Enjoy! Richard

1 0

ISMAR 2017 - Call for workshops
by Myriam Servières 06 Apr '17

06 Apr '17

ISMAR 2017 - CALL FOR WORKSHOPS The ISMAR 2017 organizing committee invites proposals for workshops to be held in the ISMAR 2017 main conference. The workshops will be held on 9th and 13th October 2017, in Nantes, France. The purpose of the workshops is to provide participants with the opportunity to present and discuss research ideas on cutting-edge research topics related to Augmented, Mixed, and Virtual Reality as Science & Technology and Arts, Media, & Humanities. We encourage researchers from different academic communities as well as from industry and public institutions to bring together and to collaborate and discuss with each other about possible future topics and trends. The scope of the proposals should be consistent with the main conference topics. Please visit the conference webpage: http://ismar17.org/ <http://ismar17.org/> Important Dates Workshops Proposal Deadline: April 24th, 2017 Workshops Acceptance Notification: May 2nd, 2017. Deadline Workshops Papers: July 3rd, 2017 Notification Workshops Papers: August 7th, 2017 Workshops Papers Camera Ready Deadline: August 28th, 2017 Workshops Dates: Oct 9th and 13th, 2017. Format ISMAR workshops provide a platform for presentations of novel work, work in progress and position papers. ISMAR workshops may also serve as a platform to actively experience the insights of a variety of pervasive computing topics in seminars. Since seminars aim for a maximum of interactivity, we ask organizers of seminars to focus on proposals of how to involve attendances. This can be for example, by organizing hands-on sessions or pro-contra discussions of reading lists. Workshops may also be organized as a combination of both, resulting in seminars with presentations of novel work, work in progress or position statements. Workshop organizers can choose one out of two options regarding the publication. (1) The workshop's papers will be published in ISMAR 2017 adjunct Proceedings and IEEE Xplore. OR (2) The workshop's papers will not be published but included in the supplemental material folder of the ISMAR 2017 USB memory proceedings. Submission Guidelines for Workshop Proposals Inquiries for workshop submissions can be directed to: wt_chairs(a)ismar17.org <mailto:wt_chairs@ismar17.org> with the subject "ISMAR 2017 workshop proposal" and a PDF document containing: 1. Title of workshop. 2. Preferable date for the workshop: 9/13/no preference. 3. Theme and topics of interest: o Brief description of research issues that the workshop will address. o Reasons why the workshop is of interest to the conference participants. o Reasons why the workshop is timely and relevant for ISMAR 2017. 4. Format of the workshop (including a rudimentary agenda). 5. Interest to get the paper published. 6. Preliminary Call for Papers. 7. Organizers: o Names. o Affiliations. o Research interest. o Short bio. 8. Potential program committee members. 9. Audience: approximate expected number of participants and submissions (range). After sending your proposal to the aforementioned email address, you should receive an acknowledgment of receipt. Workshop proposal will be reviewed by the committee, and notifications of acceptance will be sent out after the review period. Organizers are expected to be proactive in the field where they propose a workshop. Potential workshop organizers should also note that at least one workshop organizer is required to attend those workshops they are organizing. Any change to the workshop organization team must be submitted in writing at least two weeks prior to the workshop paper deadline. No changes to the workshop organization team can be made after this date to ensure that potential participants submitting papers to workshops are aware of the final organization team. Contact ISMAR 2017 Workshop and Tutorial Chairs: wt_chairs(a)ismar17.org <mailto:wt_chairs@ismar17.org> Gerd Bruder, University of Central Florida, USA Myriam Servières, Ecole Centrale de Nantes, France Maki Sugimoto, Keio University, Japan --------- Myriam Servières myriam.servieres(a)ec-nantes.fr <mailto:myriam.servieres@ec-nantes.fr> ISMAR 2017 - Deputy General Chair http://ismar2017.sciencesconf.org <http://ismar2017.sciencesconf.org/>

1 0

ISMAR 2017 - Call for tutorials
by Myriam Servières 06 Apr '17

06 Apr '17

ISMAR 2017 - CALL FOR TUTORIALS The ISMAR 2017 organizing committee invites proposals for tutorials associated with the ISMAR 2017 conference. The tutorials will be held on 9th and 13th October 2017, in Nantes, France. The purpose of the tutorials is to expand the knowledge in the fields of Augmented, Mixed, and Virtual Reality and foster the next generation of researchers, developers, and artists. Important Dates Tutorials Proposal Deadline: April 24th, 2017. Tutorials Acceptance Notification: May 2nd, 2017. Tutorials Dates: Oct 9th and 13th, 2017. Format Experts, pioneers, and experienced developers and artists are needed to propose and present tutorials that may target a specific application area, a specific research area, or a topic of general interest for Augmented, Mixed, and Virtual Reality. Topics can range from introductory for AR/MR/VR novices to highly technical for researchers. Tutorials can be half or full day tutorials, depending on the scope of topics covered and the presenters available. Submission Guidelines To submit a proposal for a tutorial, please send an email to wt_chairs(a)ismar17.org <mailto:wt_chairs@ismar17.org> with the subject "ISMAR 2017 tutorial proposal" and a PDF document containing: Title and topics: Provide a brief summary of the proposed tutorial Preferable date for the tutorial: 9/13/no preference. Motivation: Explain why ISMAR attendees would be interested in attending this tutorial. Explain how an increased knowledge of this subject will advance mixed and augmented reality. Presenters: Provide a really brief bio of the presenters', list of several relevant publications on the proposed topic tutorial, and contact information (e-mail, phone, affiliation) If you have taught this or a similar tutorial before, where and when was it taught. Target Audience: Describe what population this tutorial is targeted towards (e.g., students, industry professionals, everyone). Expected # of attendees. Outline of Tutorial: Include the order of topics and approximate time for each topic. For example: 1. Topic A: 1.5 hours 1.1. Subtopic A1 1.2. ... 2. Topic B: 1.5 hours 2.1. Subtopic B1 ... After sending your proposal to the aforementioned email address, you should receive an acknowledgment of receipt. Tutorial proposal will be reviewed by the committee, and notifications of acceptance will be sent out after the review period. Contact ISMAR 2017 Workshop and Tutorial Chairs: wt_chairs(a)ismar17.org <mailto:wt_chairs@ismar17.org> Gerd Bruder, University of Central Florida, USA Myriam Servières, Ecole Centrale de Nantes, France Maki Sugimoto, Keio University, Japan --------- Myriam Servières myriam.servieres(a)ec-nantes.fr <mailto:myriam.servieres@ec-nantes.fr> ISMAR 2017 - Deputy General Chair http://ismar2017.sciencesconf.org <http://ismar2017.sciencesconf.org/>

1 0

To: vdr@linuxtv.org,[ANNOUNCE] VDR developer version 2.3.3
by Klaus Schmidinger 28 Mar '17

28 Mar '17

VDR developer version 2.3.3 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.3.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-2.3.2-2.3.3.diff MD5 checksums: 73182b570bcf5a67ab56f7734e479631 vdr-2.3.3.tar.bz2 112c2057dbd7e86c31f8227f61cfd2a6 vdr-2.3.2-2.3.3.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 2.3.2: - Added 'S3W ABS-3A' to sources.conf (thanks to Frank Richter). - Fixed a possible deadlock in the recordings handler thread. - Updated the Russian OSD texts (thanks to Andrey Pridvorov). - Added a missing dependency to the Makefile to avoid error messages in the clean-plugins target (thanks to Tobias Grimm). - The channel/CAM relations (i.e. the information which CAM can decrypt a given channel) are now stored in the file 'cam.data' in the cache directory (suggested by Dietmar Spingler). This speeds up switching to encrypted channels after newly starting VDR, in case there is more than one CAM in the system. - Fixed a flaw in handling timeouts for encrypted channels. - The mechanism of trying different CAMs when switching to an encrypted channel is now only triggered if there acually is more than one CAM in the system. - Fixed updating the elapsed/remaining time in the progress display during fast forward/rewind. - Changed 'unsigned' to 'signed' in some places to avoid trouble with abs() in gcc6+ (reported by Derek Kelly). - CAMs that can handle multiple devices at the same time can now indicate this by creating the first cCamSlot as usual, and every other cCamSlot by giving it the first one as its "MasterSlot". To VDR this means that when searching for a CAM that can decrypt a particular channel, it only needs to ask the master CAM slot whether it is suitable for decrypting, and can skip all the other slots belonging to the same master. This can greatly speed up channel switching on systems with more than one CAM (that can handle multiple devices). - The LCARS skin now displays the master CAM's number when a device is tuned to an encrypted channel. - The Setup/CAM menu now only displays master CAMs. - Fixed setting the local machine's SVDRP host name (was overwritten if setup.conf contained an empty string). - PIDs can now be added to and deleted from a cReceiver while it is attached to a cDevice, without having to detach it first and re-attach it afterwards. - Implemented support for MTD ("Multi Transponder Decryption"). This allows a CAM that is capable of decrypting more than one channel ("Multi Channel Decryption") to decrypt channels from different transponders. See the remarks in mtd.h on what a derived cCamSlot class needs to do in order to activate MTD (thanks to Jasmin Jessich for writing the ddci2 plugin and for valuable input and help with testing and debugging). - The function cRingBufferLinear::Clear() can now be called safely from the reading thread, without additional locking. - Now stopping any ongoing recordings before stopping the plugins, to avoid a crash when stopping VDR while recording. Have fun! Klaus

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr