> 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 …
[View More]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
[View Less]
About 10 years ago I built an OTA recording system using a SiliconDust
ethernet receiver connected to a BeagleBone (linux) computer recording
to a SD card and then uploading to a NAS file server in the wee hours.
I hired an Elance programmer in Spain to write the code to interface
with the SiliconDust "calls". I recorded Craig Ferguson and football
programs mostly. Later I moved away from Denver and no longer needed
the system.
But all these years later I still was amazed and …
[View More]intimadated by the VDR
system and liked to read about the progress and challenges. All of you
and especially Klaus deserve much thanks for all your efforts and
dedication. I still use KODI on an Android box once in a while, but now
your efforts have prompted me to build my own VDR in tribute to 25 years
of your efforts. Thanks again for all the enjoyment in reading your
exploits.
Bruce
[View Less]
VDR version 2.7.4 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.3:
- Removed all DEPRECATED_* code.
- Fixed error checking in case the fps value can't be determined by the frame parser.
- Updated the Italian OSD texts (…
[View More]thanks to Diego Pierotto).
- The VDR homepage is now accessible via HTTPS.
- Updated the Finnish OSD texts (thanks to Rolf Ahrenberg).
- Fixed some typos in the translation files (thanks to Stefan Hofmann).
- Added some missing locking.
- TS packets with errors are now skipped when parsing for frames.
- Fixed handling the fps value if it can't be determined from the video data.
- Fixed accessing a timer's event schedule in case the event has been removed from the
schedule.
- Fixed a possible deadlock when canceling an editing process.
- Checking for VPS control is now limited to local timers.
- Added 1 to Utf8BufSize() for worst case (thanks to Stefan Hofmann).
- Fixed handling margins for timers that are not VPS controlled and not spawned (thanks
to Markus Ehrnsperger).
- Added a header to the backtrace (thanks to Stefan Hofmann).
- Added parameter checks to strn0cpy() (thanks to Stefan Hofmann). Same for Utf8Strn0Cpy().
- The info files of recordings are now only re-read if they have been modified (thanks
to Stefan Hofmann).
- The new virtual function cStatus::OsdItem2() can be used to get the information whether
a menu item is selectable (thanks to Markus Ehrnsperger). Plugins that implemented
cStatus::OsdItem() will still work as before, because the default implementation of
cStatus::OsdItem2() calls cStatus::OsdItem().
APIVERSNUM is now 30006.
- Fixed setting the file name of the info file after renaming a recording (reported by
Stefan Hofmann).
- Fixed an improper call of cStatus::OsdCurrentItem() before cStatus::OsdItem2() (reported
by Markus Ehrnsperger).
- Fixed an unnecessary redisplay of the menu when pressing a hotkey.
- Fixed unnecessary calls to DisplayCurrent() for editable menu items (thanks to Markus
Ehrnsperger).
- The new virtual function cStatus::OsdCurrentItem2() can be used to get the index of the
current menu item (thanks to Markus Ehrnsperger). Plugins that implemented
cStatus::OsdCurrentItem() will still work as before, because the default implementation
of cStatus::OsdCurrentItem2() calls cStatus::OsdCurrentItem().
- Fixed unnecessary calls to cStatus::OsdCurrentItem2() when scrolling.
- Added missing calls to cStatus::MsgOsdStatusMessage() and added the new virtual function
cStatus::OsdStatusMessage2(), which can be used to get the type of the message (thanks
to Markus Ehrnsperger). Plugins that implemented cStatus::OsdStatusMessage() will still
work as before, because the default implementation of cStatus::OsdStatusMessage2() calls
cStatus::OsdStatusMessage().
- Adjusted PLUGINS.html to the new API version numbering introduced in version 2.7.2.
- The function cPlugin::MainThreadHook() has been deprecated and may be removed in future
versions. Use proper locking instead.
- Fixed unnecessary redisplays of menus.
- Added '~' to the list of delimiters in cTextWrapper (thanks to Stefan Hofmann).
- Fixed progress display when switching from "pause" to "slow back" (reported by Andreas
Baierl).
- Fixed spurious fast frames when switching from "slow back" to "slow forward".
- Fixed cPtsIndex::FindFrameNumber() to handle the case where Pts points to an I-frame.
- Added missing locks to SetMenuItem() functions.
- Revised locking in cMenuSchedule and cMenuWhatsOn.
- Plugins need to be rebuilt.
Homepage: http://www.tvdr.de
Facebook: https://www.facebook.com/VideoDiskRecorder
Have fun!
Klaus
[View Less]
25 years ago today, on February 19, 2000, I released the very first version of the VDR. I never thought that this project would keep me busy for a quarter of a century.
I would like to use this special anniversary to thank the many users who have contributed to the further development of VDR with suggestions, patches, bug fixes and plugins.
At its peak, there were more than two thousand VDR users around the world (who registered with the VDR User Counter), of which today there are still a …
[View More]good 800 active. With the availability of media libraries and streaming, interest in a DVB recorder has naturally waned. However, there are also
advantages to being able to record films and series under your own control without being exposed to the risk that they will disappear from the online offering at some point.
On the page https://www.tvdr.de/cgi/vdr-counter?action=summary I have shown the history of the number of users over the years (generated from the counter's log file). In the first years of VDR, the number of users increased rapidly, peaking at over 2200. In March 2015, the counter started sending
emails to those who had not accessed their entry for more than a year, marking them as "outdated" if they did not respond with a confirmation of their entry. This caused the number of active users to drop abruptly by almost 800, and in the following years it continued to decrease. Apparently many of
the initial 2200 users only used VDR for a short time. In October 2024, this mechanism was revised so that those who have been notified once since 2015 will be notified again on a regular basis and have the option to either confirm or delete their entry. Here too, the number of active users fell by
several hundred and settled at just over 800 in January 2025.
Perhaps the "dark figure" is higher, because not everyone reads the VDR-Portal or the VDR mailing list. In any case, I still enjoy the project, and TV without VDR is unthinkable anyway ;-).
I wish all VDR users continued enjoyment with it!
Klaus
[View Less]
I got some video files in MPEG PS format.
These files would not play in VDR even if put them in directories named
after timestamps and name them 00001.ts. The command vdr --genindex
fails to create any index file.
However, if I first convert them to MPEG TS format with
ffmpeg -i file.mpg -c copy 00001.ts
then VDR will recognize and play the files (but report at least one
error per second).
I was wondering if there is a way to play MPEG PS recordings in VDR, or
a FUSE program that would …
[View More]make the recordings appear as something that
VDR recognizes. If I understand correctly, the MPEG PES format that VDR
originally used (the 001.vdr files) is kind of a subset of the PS
format.
If possible, I'd like to avoid any such conversion, at most add some
index files for VDR playback.
I found https://github.com/vdr-projects/vdr-plugin-dvd which should be
able to deal with the video format (DVD uses MPEG PS), but I suppose it
would only work with an actual DVD (if it is compatible with a current
VDR version).
Marko
[View Less]