vdr

vdr@linuxtv.org

2 participants
6731 discussions

Re: [vdr] xineliboutput and xine-ui not fitting together
by Tobi 08 Feb '12

08 Feb '12

On 08.02.2012 01:31, Darren Salt wrote: > I see that that's been uploaded. Which just leaves vdr-plugin-xine... Coming soon. I'm trying to backport libxine to Squeeze, but I'll probably give up and go ahead switching my VDR to Wheezy so I'm able to at least test it before uploading. Tobias

1 0

Fonts
by Richard Scobie 04 Feb '12

04 Feb '12

Hi, I am setting up a vdr system and am trying to minimise the number of packages - there is no X11 installed. On Fedora 16, I have installed the required fontconfig and freetype packages, but when I run vdr, I get a "OSD No fonts found" message. I have also installed fontpackages-filesystem, xorg-x11-fonts-ISO8859-1-100dpi and xorg-x11-font-utils but am still getting the same error. Can someone suggest anything else I need, or where the fonts need to be? Regards, Richard

1 1

OT: Patches posted to support interlaced modes in intel-gfx
by Paul Menzel 28 Jan '12

28 Jan '12

Dear VDR folks, there is a request for testing on the intel-gfx list for patches enabling interlaced modes [1]. After porting the driver to KMS interlaced modes did not work anymore and the patches enable support again. So Intel hardware seems to even more suited for a HTPC. 15:48 < danvet> yeah, together with libva an recent intel gpu should make a nice htpc 15:49 < danvet> although we don't support tv-out on ilk and later 15:49 < danvet> but iirc rodrigo vivi is working on that Daniel Vetter told me to remind you that these patches are experimental though and will (only) land in Linux 3.4. So to test them you will have to build the Linux kernel yourself. Maybe frame rate control patches from Thomas Hilber and VGA2SCART will also get upstream in the feature if somebody gets her/his hands dirty porting those. Thanks, Paul [1] http://lists.freedesktop.org/archives/intel-gfx/2012-January/014757.html [2] http://frc.easy-vdr.de/

1 0

vdr-sxfe and IEC958 audio
by Dominic Evans 28 Jan '12

28 Jan '12

I have a digital S/PDIF output from my VDR frontend hooked up to a decent home amplifier and surround speakers. In the past I've had no problems using this via a vdr-sxfe frontend both for stereo MPEG-2 audio, as well as for 5.1 AC-3 on HD channels. audio.device.alsa_default_device:plughw:0,1 audio.device.alsa_front_device:plughw:0,1 audio.device.alsa_passthrough_device:plughw:0,1 audio.device.alsa_surround51_device:plughw:0,1 audio.output.speaker_arrangement:Pass Through However, recently (perhaps due to a kernel / alsa update?) I've found that I have to execute `iecset audio on` (to make analog MPEG-2 audio work) and `iecset audio off` (to make AC-3 passthrough work). Any idea why this might be?

2 3

playback problems with recordings with vdr-1.7.20 and newer
by Andreas Albert 27 Jan '12

27 Jan '12

Hello, this problem have already been posted at the mailing list in post http://www.linuxtv.org/pipermail/vdr/2012-January/025616.html > Then i got an other problem. When watching a recording, and i > fastforward of rewind the program, i get to a situation that the > "timecounter" get's stuck to the frame i start from. The film moves, but > when i hit play, i end up back to the frame from where i started to > rewind/fastforwad. The only way to fix this is to jump with the > yellow/green buttons. AFter this i can rewind/fastforwad normally. This > again works for a while, but again if it fails to stop to the place i > rewind to, i have to "reset" the rewind-issue with the yellow/green > buttons... My output device is a Technotrend FF S-2300 with the dvbsddevice-plugin. I wrote this topic again, because there isn't an answer in the topic above. Can anyone help me? Greetings Andreas

3 2

Weird frame rate issue (VDR 1.6 recording, VDR 1.7 playback)
by Tobi 26 Jan '12

26 Jan '12

Hi! Several recordings recorded from JSC Sports (S13.0E-318-500-8440) seem to have a weird framerate. The recordings were done in PES format with VDR 1.6, so there's no framerate setting in the info file and VDR will use 25 fps by default. This leads to a wrong recording length display (30 minutes for a recording that was actually 20 minutes long). VDR 1.7.22 is used for playback and with a small patch I can provide the framerate via the info.vdr (Which might be a useful feature anyways, patch attached.). So far so good, but the recording seems to have a weird framerate This is the recording: 501593483 2012-01-20 13:15:00.000000000 +0100 001.vdr 366032 2012-01-20 13:15:00.000000000 +0100 index.vdr 149 2012-01-20 12:55:05.000000000 +0100 info.vdr The mtime diff between info.vdr and 001.vdr is 19:55 minutes. index.vdr is 366032 bytes in size, which divided by 8 gives a framerate of 38,29 fps. Can anyone explain this framerate? ffmpeg and mediainfo both say 25fps (see below) and VLC tells me it's 50fps. When I convert the recording to TS using project-x, set the framerate in the info.vdr to 25 and reindex it with VDR 1.7.22, it still shows the wrong length. bye, Tobias ffmpeg says: Input #0, mpeg, from '001.vdr': Duration: 00:19:55.77, start: 59497.383833, bitrate: 3355 kb/s Stream #0.0[0x1e0]: Video: mpeg2video (Main), yuv420p, 720x576 [PAR 64:45 DAR 16:9], 3049 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc and mediainfo says: Complete name : 001.vdr Format : MPEG-PS Duration : 19mn 55s Video Format : MPEG Video Format version : Version 2 Duration : 19mn 55s Width : 720 pixels Height : 576 pixels Display aspect ratio : 16:9 Frame rate : 25.000 fps Standard : PAL

3 7

Cleaner TS/h264 cutting possible?
by Tobi 26 Jan '12

26 Jan '12

Hello, cutting a TS recording, where two cut points are joined, always leads to some artifacts at this join when playing the cutted result. When VDR cuts only at I-Frames, shouldn't the cut point be unnoticeable in the output? Checking the cutted result with TS-Doctor shows a bunch of errors, while the original recording contained none. Is this an issue with the way VDR cut's recordings or is there simply no clean way to cut TS recordings without re-encoding them? BR, Tobias

2 1

[ANNOUNCE] VDR developer version 1.7.23
by Klaus Schmidinger 23 Jan '12

23 Jan '12

VDR developer version 1.7.23 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff MD5 checksums: de136f7be28c4b6f1fa0e2218b4acc11 vdr-1.7.23.tar.bz2 2977b75cd8dacad187d11c10b867d56a vdr-1.7.22-1.7.23.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.22: - Removed the '.pl' suffix from svdrpsend.pl (sorry, I missed that one). - Fixed bonding more than two devices. - Fixed handling symbolic links in cRecordings::ScanVideoDir() (reported by Sundararaj Reel). - Fixed a memory leak in cRecordings::ScanVideoDir() in case there are too many link levels (reported by Sundararaj Reel). - Removed redundant memset() in the ctor of cSatCableNumbers (triggered by Ville Skyttä pointing out that the argument sequence in the call was wrong). - Removed a redundant NULL check in cDvbSpuDecoder::setTime() (thanks to Ville Skyttä). - Added HasSnr to the DEBUG_SIGNALQUALITY output in cDvbTuner::GetSignalQuality() (triggered by Ville Skyttä pointing out that the variable HasSnr was unused). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added support for HbbTV to libsi (thanks to Christoph Haubrich). - Added support for devices with more than one delivery system per frontend. This requires a DVB driver with version 5.5 or higher that can handle the DTV_ENUM_DELSYS call. With older drivers it will fall back to one delivery system per frontend. - Updated the Hungarian language texts (thanks to István Füley). - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner sends SCR commands at any given time (reported by Frank Neumann). - cEvent::FixEpgBugs() now replaces any newline characters in stream component descriptions with blanks (thanks to Torsten Lang for reporting a problem with EPG data from BSkyB's "MTV MUSIC", S28.2E-2-2010-7012). - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf Ahrenberg). - Fixed cListBase::Move() in case From and To are equal (reported by Sundararaj Reel). - Added support for DVB-T2 to libsi (thanks to Rolf Ahrenberg). - Added support for handling DVB-T2 transponders. This requires a DVB driver with version 5.3 or higher that can handle the DTV_DVBT2_PLP_ID call (thanks to Rolf Ahrenberg). - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to Ville Skyttä). - Fixed a possible memory corruption in cTsToPes::GetPes() in case of broken TS packets, e.g. when switching channels. - Fixed the SVDRP command CLRE for a single channel in case there are events that have a timer (thanks to Timo Eskola). - BIDI support now checks at runtime whether the system runs with UTF-8 (suggested by Torsten Lang). - Added member functions Adapter() and Frontend() to cDvbDevice (suggested by Rolf Ahrenberg). - The parameters that are only used by "second generation" delivery systems (DVB-S2 and DVB-T2) are no longer written into channels.conf for "first generation" delivery systems (DVB-S and DVB-T). - Changed IndexToHMSF() so that it can handle negative Index values. - Added option -N to the msgmerge call in the Makefile, because fuzzy translation mostly resulted in useless strings. - The new setup option "Replay/Show remaining time" can be used to switch between showing the total length or the remaining time of the recording that is currently replayed. - Fixed wrongfully displaying the length of a recording in the title of the replay progress display. - Fixed frozen live view with device bonding in case the bonded master is used for live viewing (reported by Uwe Scheffler). Have fun! Klaus

8 11

where can I find a working vnsiserver
by Arturo Martinez 19 Jan '12

19 Jan '12

where can I find a working vnsiserver for vdr 1.7.21 and current git XBMC ? ( I am looking for source code, not a .deb package)

3 2

LiveBuffer for vdr 1.7.x
by René 17 Jan '12

17 Jan '12

Hi All, I'm stuck to vdr 1.6.0-2 because i can't find a current LiveBuffer patch for any current vdr 1.7.x. Does anyone know if there is any work going on with this great patch? Regards, René

11 36

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr