vdr

vdr@linuxtv.org

3 participants
6742 discussions

Identifying MPEG-4 HE-AAC (LATM, LAOS) audio formats
by Marko Mäkelä 30 Dec '24

30 Dec '24

A couple of weeks ago, Finland took the penultimate step to get rid of DVB-T. Since years, we had DVB-T and DVB-T2 running in parallel. The DVB-T transponders should be shut down in 2025. The step was to introduce a second free-to-air DVB-T2 bouquet to carry some channels that were previously only available with DVB-T and MPEG-2. The VDR channel search failed to find this transponder; I ran a patched version of https://github.com/mighty-p/t2scan/pull/15/ to generate a new channels.conf. (Is this a bug of VDR, or a feature? I remember that when I originally set up VDR, I had to get a channels.conf from tscan or t2scan.) Unlike our first free-to-air DVB-T2 bouquet, which uses MPEG-4 H.264 video with AC3 audio, the second one uses H.264 video and HE-AAC audio, also known as LATM or LOAS. This had to be explicitly enabled for my output device: https://github.com/reufer/rpihddevice/issues/20 The HE-AAC support in rpihddevice is experimental, maybe because the sampling rate is hard-coded as 48 kHz and the number of channels as 2. Unlike AC3, it does not look like these parameters would be available in any audio frame header. As far I understood from a NorDig.org specification, the sampling rate would always be 48 kHz, but the number of channels could be identified by something in the container, specifically, Table 12.28 and Table 12.29 at page 164 of https://nordig.org/wp-content/uploads/2016/03/NorDig-Unified-Requirements-v… What would have to be changed in VDR or rpihddevice or both to correctly switch between 2-channel and 5.1-channel HE-AAC audio? This is mostly an academic question and exercise, because I only have stereo audio hardware and don't know if any programming is actually available with multichannel audio. Best regards, Marko

3 7

Using vdr-dpg package for bug hunting?
by schorpp 06 Dec '24

06 Dec '24

Hello, I'm about fixing this old BUG exiting VDR on every 1st recording start: # gdb attach <pid of vdr> Program received signal SIGFPE, Arithmetic exception. [Switching to Thread 0x9c801b40 (LWP 8182)] 0x08136f6a in cFrameDetector::Analyze(unsigned char const*, int) () (gdb) bt #0 0x08136f6a in cFrameDetector::Analyze(unsigned char const*, int) () #1 0x081295b2 in cRecorder::Action() () #2 0x08165e13 in cThread::StartThread(cThread*) () #3 0xb7693d97 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #4 0xb73addfe in clone () from /lib/i386-linux-gnu/libc.so.6 (gdb) bt full #0 0x08136f6a in cFrameDetector::Analyze(unsigned char const*, int) () No symbol table info available. #1 0x081295b2 in cRecorder::Action() () No symbol table info available. #2 0x08165e13 in cThread::StartThread(cThread*) () No symbol table info available. #3 0xb7693d97 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 No symbol table info available. #4 0xb73addfe in clone () from /lib/i386-linux-gnu/libc.so.6 No symbol table info available. I've installed the vdr-dbg debian package to provide debugging symbols to vdr gdb bt full but there's no README included how to use it. # dpkg -L vdr-dbg /. /etc /etc/init /etc/init/vdr-dbg.conf ?* /etc/init/vdr-exit-other.override ?* /usr /usr/lib /usr/lib/debug /usr/lib/debug/.build-id /usr/lib/debug/.build-id/10 /usr/lib/debug/.build-id/10/e8b576883246ca77ad6f40e2c26053ba2d357c.debug /usr/lib/debug/.build-id/86 /usr/lib/debug/.build-id/86/d9bba0c546ad5d7429259292b259103aabba03.debug /usr/lib/debug/.build-id/6d /usr/lib/debug/.build-id/6d/6631fca1b8d4962b2725add0c729fdeba6aa40.debug /usr/share /usr/share/doc /usr/share/doc/vdr-dbg /usr/share/doc/vdr-dbg/copyright /usr/share/doc/vdr-dbg/changelog.Debian.gz /usr/share/doc/vdr-dbg/changelog.gz /usr/bin /usr/bin/vdr-dbg *Does this package interfere with my production vdr installation? Can I just replace /usr/bin/vdr with /usr/bin/vdr-dbg in runvdr script? There's only a gdb beginners guide in the wiki: http://www.vdr-wiki.de/wiki/index.php/Gdb http://www.vdr-wiki.de/wiki/index.php?title=Spezial%3ASuche&search=vdr-dbg&… ? Y tom

2 13

Buffer overflows recording HDTV with saa7146 and mantis DVB-C tuners
by schorpp 22 Nov '24

22 Nov '24

> Hello, > > I've build a new VDR with h.264 xineliboutput plugin software decoding > > and got a problem now with > > buffer overruns and distorted recordings on all HD channels: > > ... > Nov 5 05:32:03 vdr2 vdr: [32753] ERROR: 47231 ring buffer overflows (8879240 bytes dropped) > Nov 5 05:32:09 vdr2 vdr: [32753] ERROR: 31042 ring buffer overflows (5835896 bytes dropped) > Nov 5 05:32:15 vdr2 vdr: [32753] ERROR: 47325 ring buffer overflows (8897100 bytes dropped) > Nov 5 05:32:21 vdr2 vdr: [32753] ERROR: 28306 ring buffer overflows (5321528 bytes dropped) > Nov 5 05:32:27 vdr2 vdr: [32753] ERROR: 14033 ring buffer overflows (2638204 bytes dropped) > ... > > This occurs with both saa7146 and mantis pci tuner cards. > > This has not occured with the old VDR system using Broadcomm's crystalhd decoder in libxine. > > LIVE TV works fine. > > I've tried stable and testing minidvblinux.de VDR live systems to crosscheck, but same issue occurs. > > If I increase the buffer for the saa7164 cards with module parameter it's getting worse and distorted picture and sound. > > Any Ideas? > > Increase VDR's buffer in source code? > > What is the correct driver module debug parameter to provide a useful debog log? > > Y > tom > > Not a DVB drivers or hardware issue. Good old Kaffeine DVB app recordings are OK, no distorted stream. VDR BUG! y tom

2 4

Buffer overflows recording HDTV with saa7146 and mantis DVB-C tuners
by schorpp 05 Nov '24

05 Nov '24

Hello, I've build a new VDR with h.264 xineliboutput plugin software decoding and got a problem now with buffer overruns and distorted recordings on all HD channels: ... Nov 5 05:32:03 vdr2 vdr: [32753] ERROR: 47231 ring buffer overflows (8879240 bytes dropped) Nov 5 05:32:09 vdr2 vdr: [32753] ERROR: 31042 ring buffer overflows (5835896 bytes dropped) Nov 5 05:32:15 vdr2 vdr: [32753] ERROR: 47325 ring buffer overflows (8897100 bytes dropped) Nov 5 05:32:21 vdr2 vdr: [32753] ERROR: 28306 ring buffer overflows (5321528 bytes dropped) Nov 5 05:32:27 vdr2 vdr: [32753] ERROR: 14033 ring buffer overflows (2638204 bytes dropped) ... This occurs with both saa7146 and mantis pci tuner cards. This has not occured with the old VDR system using Broadcomm's crystalhd decoder in libxine. LIVE TV works fine. I've tried stable and testing minidvblinux.de VDR live systems to crosscheck, but same issue occurs. If I increase the buffer for the saa7164 cards with module parameter it's getting worse and distorted picture and sound. Any Ideas? Increase VDR's buffer in source code? What is the correct driver module debug parameter to provide a useful debog log? Y tom

1 0

VDR User Counter now uses OpenStreetMap
by Klaus Schmidinger 22 Oct '24

22 Oct '24

The newly refurbished VDR User Counter at https://www.tvdr.de/counter.htm now uses OpenStreetMap instead of Google Maps. If you have a user number and password, please log in at https://www.tvdr.de/cgi/vdr-counter?action=edit (click "Edit my entry") and check if your data is still up-to-date. If you don't remember your user number/password, enter your email address and click "Send me a new password". If you're a VDR user and have not yet registered with the VDR User Counter, please go to https://www.tvdr.de/cgi/vdr-counter?action=register and join the VDR community. Disclaimer: The VDR User Counter is an attempt to find out how many people are actually using VDR, so please register only if you are actually using VDR! Note that there is absolutely no obligation to register yourself in order to use VDR. VDR is free, open source software, so you can, of course, use it without anybody's approval. However, developing a program is more fun if the programmers know that it is being used by a great many people ;-). Have fun! Klaus

1 0

Temporarily suspending the video output
by Marko Mäkelä 13 Oct '24

13 Oct '24

I would like to have a function to suspend VDR playback on my Raspberry Pi 2 or 3, so that I could occasionally use the screen for something else, such as a text console. Currently this is impossible because the video overlay would block the view on the text console layer. I can think of several possible ways to achieve this. (1) In the VDR core or in the video output plugin, monitor /sys/devices/virtual/tty/tty0/active for changes and automatically suspend and resume the output based on VDR is running on the active virtual console. The drawback would be: What if I detached the keyboard but forgot to switch the virtual console back, and another family member wants to watch TV? (2) Add a special setting to the video output plugin (rpihddevice in my case), and activate it from the OSD using remote control. (3) Change the VDR shutdown logic in some way, so that when the Power key is pressed, the audio and video output will be disabled immediately, as if the user had been inactive for a long time. The assumption here would be that a shutdown script or the existence of recording timers would prevent an actual shutdown. Years ago, I had written patches to do this. This would be easy to use from the remote control: Just press Power to suspend the output, and any other button to resume it. When the output is suspended, ideally I would like the tuner device descriptor to be closed to save some power. It should only run when needed for recordings or for updating the EPG once in every few hours. Marko

1 0

[ANNOUNCE] VDR version 2.7.3 released
by Klaus Schmidinger 12 Oct '24

12 Oct '24

VDR version 2.7.3 is now available at the official VDR GIT archive git://git.tvdr.de You can also get the latest stable version with git clone --branch stable/latest git://git.tvdr.de/vdr.git or as a tar archive with http://git.tvdr.de/?p=vdr.git;a=snapshot;h=stable/latest;sf=tbz2 The changes since version 2.7.2: - Removed defining DEPRECATED_* macros with value 0, because this is the preprocessor's default (suggested by Winfried Köhler). - Fixed error checking in case of large PTS discontinuities (reported by Matthias Senzel). - Fixed handling negative values in cSource::Position() on systems where 'int' is 64 bit (reported by Markus Ehrnsperger, fix suggested by Winfried Köhler). - Fixed expiring of one-time VPS timers in case there is more than one event with the same VPS time (suggested by Markus Ehrnsperger). - The Channel+/- keys can now be used to jump between errors while replaying a recording (suggested by Stefan Hofmann). - Added vdrrootdir and incdir to vdr.pc (thanks to Stefan Hofmann). - Plugins that have been built with API version 5 do not need to be rebuilt. Homepage: http://www.tvdr.de Facebook: https://www.facebook.com/VideoDiskRecorder Have fun! Klaus

1 0

[ANNOUNCE] VDR version 2.7.2 released
by Klaus Schmidinger 27 Sep '24

27 Sep '24

VDR version 2.7.2 is now available at the official VDR GIT archive git://git.tvdr.de You can also get the latest stable version with git clone --branch stable/latest git://git.tvdr.de/vdr.git or as a tar archive with http://git.tvdr.de/?p=vdr.git;a=snapshot;h=stable/latest;sf=tbz2 The changes since version 2.7.1: - Fix for compilers that don't like non-constant format strings (thanks to Stefan Hofmann). - Deprecated code is now marked with [[deprecated]] to issue a compile time warning when used. - Made APIVERSION independent from VDRVERSION to avoid irritation in case only VDRVERSION is incremented (originally suggested by Winfried Köhler, with contributions from Lars Hanisch and Manuel Reimer). APIVERSNUM is now 30003. - Fixed a problem in cSchedule::Sort(), in case hasRunning was true, but there was no event with RunningStatus() >= SI::RunningStatusPausing (reported by Markus Ehrnsperger). - Silenced a compiler warning with gcc 14.1.0 (reported by Winfried Köhler). - Updated the Italian OSD texts (thanks to Diego Pierotto). - Moved error checking from recorder.c to remux.c. - The number of errors in a recording now represents the number of broken frames. - Now distinguishing between frames with errors and completely missing frames. - Recording errors are now marked in the index file. - Fixed description of cSkinDisplayReplay::SetRecording(). - Errors are now shown as diamond shaped markers in the replay progress display of the default skins. Plugin authors can switch to the new constructor of cProgressBar to benefit from this feature. Of course this only works with recordings that have error information stored in their index file. If you have existing recordings with errors and want them to be displayed in the progress bar, you can re-generate their index file, either by deleting the old index, or by running vdr with the --genindex option. APIVERSNUM is now 30004. - When the index file of a recording is regenerated, errors in the recording are now stored in the index file. - The info file of an edited recording now contains the number of errors in the edited version. Note that this applies only to recordings that have errors stored in their index file. If errors are not stored in the index file, the edited version will have its number of errors set to that of the original recording. APIVERSNUM is now 30005. - Fixed singular when displaying number of errors in the recording info. - Increased the bpp of cProgressBar to 4 to handle all different colors. - Fixed a problem with duplicate events if they are moved to a lower table ID and at the same time get a new event ID (reported by Markus Ehrnsperger). - Plugins need to be rebuilt. Homepage: http://www.tvdr.de Facebook: https://www.facebook.com/VideoDiskRecorder Have fun! Klaus

1 0

[PATCH] Added ID 1d19:6108 Dexatek Technology Ltd. Video Grabber
by Rohan Barar 26 Sep '24

26 Sep '24

--- drivers/media/usb/cx231xx/cx231xx-cards.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/media/usb/cx231xx/cx231xx-cards.c b/drivers/media/usb/cx231xx/cx231xx-cards.c index 92efe6c1f..bda729b42 100644 --- a/drivers/media/usb/cx231xx/cx231xx-cards.c +++ b/drivers/media/usb/cx231xx/cx231xx-cards.c @@ -994,6 +994,8 @@ const unsigned int cx231xx_bcount = ARRAY_SIZE(cx231xx_boards); /* table of devices that work with this driver */ struct usb_device_id cx231xx_id_table[] = { + {USB_DEVICE(0x1D19, 0x6108), + .driver_info = CX231XX_BOARD_PV_XCAPTURE_USB}, {USB_DEVICE(0x1D19, 0x6109), .driver_info = CX231XX_BOARD_PV_XCAPTURE_USB}, {USB_DEVICE(0x0572, 0x5A3C), -- 2.46.1 Dear Maintainers, This patch adds support for the USB device 1D19:6108 (Dexatek Technology Ltd. Video Grabber) to the cx231xx driver. This device is similar to the 1D19:6109, and I have tested it successfully on my system: * Video Capture: CONFIRMED WORKING in OBS & VLC. * Audio Capture: CONFIRMED WORKING via command `arecord -D hw:1,0 -f S16_LE -r 48000 -c 2 audio_capture_test.wav`. The sole modification is including a new entry to the device ID table, which can be found in `drivers/media/usb/cx231xx/cx231xx-cards.c`. I have verified that both video and audio capture are functioning as expected. Signed-off-by: Rohan Barar rohan.barar(a)gmail.com Thank you for considering my patch! Best regards, Rohan Barar

1 0

[ANNOUNCE] VDR version 2.7.1 released
by Klaus Schmidinger 09 Sep '24

09 Sep '24

VDR version 2.7.1 is now available at the official VDR GIT archive git://git.tvdr.de You can also get the latest stable version with git clone --branch stable/latest git://git.tvdr.de/vdr.git or as a tar archive with http://git.tvdr.de/?p=vdr.git;a=snapshot;h=refs/tags/2.7.1;sf=tbz2 The changes since version 2.6.9: - Removed deprecated function cDevice::SetCurrentChannel(const cChannel *Channel). - Removed deprecated function cSkinDisplayMenu::SetItemEvent(const cEvent *Event, int Index, bool Current, bool Selectable, const cChannel *Channel, bool WithDate, eTimerMatch TimerMatch). - Removed deprecated functions from cFile. - The default for DEPRECATED_SCHEDULE_GET_EVENT has been set to 0, which means that the function GetEvent(tEventID EventID, time_t StartTime = 0) is no longer available. You can add 'DEPRECATED_SCHEDULE_GET_EVENT=1' when compiling in order to restore this functionality. However, it is recommended to use GetEventById() and GetEventByTime() instead. - The default for DEPRECATED_SECTIONSYNCER_SYNC_REPEAT has been set to 0, which means that the functions Repeat() and Sync() are no longer available. You can add 'DEPRECATED_SECTIONSYNCER_SYNC_REPEAT=1' when compiling in order to restore this functionality. However, it is recommended to use Check() and Processed() instead. - The default for DEPRECATED_CCONTROL has been set to 0, which means that the function Control(bool Hidden) is no longer available. You can add 'DEPRECATED_CCONTROL=1' when compiling in order to restore this functionality. However, it is recommended to use Control(cMutexLock &MutexLock, bool Hidden) instead. - Changed the error message when trying to attach a player to a primary device without an MPEG decoder. - The new SVDRP command 'AUDI' can be used to list the currently available audio tracks and select one of them. - Fixed a crash when deleting a recording that is currently being edited, and then immediately deleting the edited version, too (reported by Marko Mäkelä). - The '.update' file in the video directory is now created if it doesn't already exist. - Improved the error message when closing a frontend (thanks to Markus Ehrnsperger). - There will be no more distinction between "developer" and "stable" versions regarding version numbering. Version numbers are simply counted upwards, with each of the three parts ("version", "major", "minor") always being a single digit, and '0' being skipped. - Plugins that have been built with API version 2.6.9 do not need to be rebuilt. Homepage: http://www.tvdr.de Facebook: https://www.facebook.com/VideoDiskRecorder Have fun! Klaus

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr