vdr August 2011

vdr@linuxtv.org

40 participants
61 discussions

[feature request] recording length computation and storage
by Steffen Barszus 23 Aug '11

23 Aug '11

Hi ! After having seen that there are several plug-ins computing the recording length on their own and that being a very expensive task (in respect of io and cpu) and also the same implementation needs to be copied over and over again, i would like to request, that vdr is storing the length of a recording and make it accessible to the plug-ins. I would imagine, that some logic to store it in the info file after/while generating/writing the index would be a good way. Plug-ins which possibly could make use of that are: * live * extrecmenu * restfulapi I'm sure there are more of it. Has someone allready thought of this ? Are there any plans to have that or someone allready using a patch for this ? Thanks ! Steffen

4 9

Trying to understand MPEG-TS (PMT, PES etc)
by Chris Rankin 23 Aug '11

23 Aug '11

Hi, I am digging into DVB streams and TS demuxing, and I was wondering: is the PMT the *only* (reasonable) way to determine which codec a given PES is using, please? The TS demuxing code that I am reading (*cough* xine's) seems to have the idea that if it receives an audio or video PES with a PID that it hasn't seen before then it can "autodetect" the stream (somehow?!). But if it has to wait for the next PMT anyway to determine which codec to use then I'm not sure that I understand the point. Can anyone advise, please? My research into MPEG-TS has only revealed the following, with regards to PMTs: "Each elementary stream is labeled with a stream_type value." http://en.wikipedia.org/wiki/MPEG_transport_stream#PMT Thanks, Chris

1 0

Wiki update
by Johannes Stezenbach 22 Aug '11

22 Aug '11

So it seemes like MediaWiki-1.14.1 is somewhat broken with PHP-5.3.3 and there have been issues with both the VDR and V4L-DVB Wikis. Thus I've updated MediaWiki to 1.16.5, and full functionality seems to be restored. Please let me know if there are still any issues. Johannes

1 0

Re: [vdr] epgsearch plugin memory leak
by Richard F 21 Aug '11

21 Aug '11

@Christian: I've cloned the Git repo and compiled / running your latest epgsearch with the same config I sent you. Will monitor for a couple of days and let you know, Thanks - R On 21/08/2011 15:50, vdr-request(a)linuxtv.org wrote: > Subject: > Re: [vdr] epgsearch plugin memory leak > From: > Christian Wieninger <cwieninger(a)gmx.de> > Date: > 21/08/2011 15:50 > > To: > VDR Mailing List <vdr(a)linuxtv.org> > > > Hi, > > @Tobi: many thanks, worked like a charm! > > @Richard: > I've found a big leak besides some smaller ones and fixed them in the > git. So please give it a try and let me know if it workes for you now. > > Cheers, > Christian

1 0

Re: [vdr] epgsearch plugin memory leak
by Christian Wieninger 21 Aug '11

21 Aug '11

Hi Richard, thanks for the files. I just gave them a try and using valgrind I could also see that there's a leak when a search timer update is run. ==4060== 452,152 (6,968 direct, 445,184 indirect) bytes in 134 blocks are definitely lost in loss record 287 of 287 ==4060== at 0x4024F20: malloc (vg_replace_malloc.c:236) ==4060== by 0x4C31C90: ??? ==4060== by 0x4C39596: ??? ==4060== by 0x4C9FCF2: ??? ==4060== by 0x8145D96: cThread::StartThread(cThread*) (thread.c:257) ==4060== by 0x406D96D: start_thread (pthread_create.c:300) ==4060== by 0x4342A4D: clone (clone.S:130) But unfortunately valgrind does not give me the information where the leak is caused. Maybe the reason for this is that a search timer update runs in a separate thread or because plugins are dynamically loaded shared libraries? Has anybody an idea how to use valgrind in this case? Cheers, Christian Am 20.08.2011 18:13, schrieb Richard F: > Hi Christian, > > To answer your questions... > My server is headless - I user Vomp and a pair of media mvp's. > I'm using vdr V1.6.0.2 (SD only), I use vdradmin-AM and my epgsearch > updates are just on a timer, every 15 mins. Used to be 30 mins but I > don't think this makes a significant difference looking at the memory > graphs. I've disabled epgsearch conflict checks on timers - I used to > have them enabled, but as I look at vdradmin regularly, I can do it > manually, and it only fills up the logs. > > I also use xmltv2vdr on a daily cron to update the epg with full > programme details. > > I attach a tar'd up copy of all my /etc/vdr configs for you, and > zipped epg.data. If this doesn't show the problem, perhaps you can > tell me how to setup "valgrind" to search for the problem ? > > Thanks for your help and a great plugin! > > cheers > Richard > > > On 20/08/2011 14:02, Christian Wieninger wrote: >> Hi Richard, >> >> unfortunately I'm not aware of any leaks, if so I would have fixed >> them ;) >> Perhaps you can find out in which circumstances the memory usage >> increases. Candidates are: >> - search timer updates, should not matter how you trigger them, e.g. via >> svdrpsend.pl plug epgsearch upds >> - timer conflict check >> - simply navigating through the epgsearch menus in OSD >> >> Using valgrind would also be a good way to search for the leaks. I've >> done this before too. But the leak may also depend on your personal >> usage of epgsearch (e.g. search timer settings, blacklists,...), and >> therefore did not appear in my valgrind checks. >> Feel free to send me your VDR configuration (*.conf, >> epgsearch-config-dir, epg.data) for testing. >> >> Cheers, >> Christian >> >> Am 20.08.2011 12:18, schrieb Richard F: >>> Hi, >>> >>> [ Apologies for using this list - the epgsearch bugtracker is broken ] >>> >>> I've been tracking down memory leaks on my server and narrowed down a >>> significant leak in the epgsearch plugin >>> Approx 500 megs / week is lost - recovered by restarting vdr. I'd like >>> to reduce this obviously. >>> I updated from 0.9.24 to 0.9.25 beta 22 from git as a fix for a memory >>> leak was mentioned in the changelog, but the leak is still about the >>> same. If I remove the plugin from the command line, there is no >>> significant leak. Attached plot shows. >>> >>> >>> >>> Anyone have any ideas? >>> Thanks Richard >>> >>> >>> >>> >>> _______________________________________________ >>> vdr mailing list >>> vdr(a)linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> >

2 2

ANNOUNCE TV-Anytime plugin
by Dave 21 Aug '11

21 Aug '11

A plugin version of my TV-Anytime patch is now available at http://projects.vdr-developer.org/projects/vdrtva The plugin has (most of) the same features as the patch version, but without the need to run a cron job to process the series links. Comments criticisms and suggestions are always welcome... Dave

1 0

ANNOUNCE vdr-ttxtsubs 0.2.3 for VDR 1.7.20
by Tobi 21 Aug '11

21 Aug '11

Catching up with some bug reports/feature requests and supporting VDR 1.7.20. The changes: * Made changes in font settings be applied instantly, without the need to change the channel (patch provided by Rolf Ahrenberg) * Converted *.po to UTF-8 (Thx to Ville Skyttä!) * Updated patch for VDR 1.7.20 (Closes #689) * Don't log all page info received from VDR (Closes #331) * Show subtitles with backround rectangle, if outline width is < 2 (patch provided by Mike Lampard) (Closes #247) As always: Any help is welcome! Development site: http://projects.vdr-developer.org/projects/plg-ttxtsubs Downloads: http://projects.vdr-developer.org/projects/plg-ttxtsubs/files Git-Web: http://projects.vdr-developer.org/git/vdr-plugin-ttxtsubs.git/ Anonymous Git-access : git://projects.vdr-developer.org/vdr-plugin-ttxtsubs.git The VDR patch is also available here: git://projects.vdr-developer.org/vdr-patches.git ...which is based on: git://projects.vdr-developer.org/vdr.git This is intended to be a community maintained project! Don't expect me to fix your problems, I'm merely maintaining the project! Please report any bugs, ideas or feature requests to the project site (no registration required for this!). If you want to contribute patches, new features or whatever, post an issue or patch to the projects issue tracker or request to join the project. I would happily add everyone as a project member, who would like to contribute to the project! Tobias

1 0

FreeviewHD success with Nanostick 290e
by Laz 21 Aug '11

21 Aug '11

Hi Chris (and list) I've just been doing a bit more testing with my recently acquired Nanostick 290e... I added a fake channel with the frequency 618000000 MHz (my HD mux), QAM256, and everything else set to auto or random values. I then switched to it. vdr then picked up BBC HD, ITV1 HD, Channel4 HD, and BBC One HD. It was clever enough to switch to the Nanostick for the HD mux because it's the only device that can do QAM256 (not sure if _only_ DVB-T2 includes QAM256 or whether my other devices are too old ot do it as part of DVB-T). I get now/next EPG for the HD channels but it's encrypted (it needs a plugin to decode, from what others have said). If I switch to BBC One HD, femon gives me a video bit-rate of about 7 Mbit / s and an audio bit-rate of about 150 kbit / s. It claims to have a signal strength of 70% but I'm not sure I believe that! By comparison, BBC One gives me something like 3 Mbit / sv video and 260 kbit / s audio, and signal strength of 70%. vdr has now written out the new entries to channels.conf: BBC HD;BBC:618000000:B8C23D23M256Y0:T:0:101=27:102=eng@17,106=eng@17:0:0:17472:9018:16516:0 ITV1 HD;ITV:618000000:B8C23D23M256Y0:T:0:201=27:202=eng@17,206=eng@17:0:0:17604:9018:16516:0 Channel 4 HD;CHANNEL FOUR:618000000:B8C23D23M256Y0:T:0:301=27:302=eng@17,306=eng@17:0:0:17664:9018:16516:0 BBC One HD;BBC:618000000:B8C23D23M256Y0:T:0:6601=27:6602=eng@17,6606=eng@17:0:0:17540:9018:16516:0 These are from the Emley Moor transmitter (I'm not sure how whether PIDs, etc., are the same between different transmitters but it might help someone.) I'm not seeing anything on my tele' but I suspect my output device (a Matrox G450 with softdevice) can't go up to that high a resolution! Actually, I don't think it will currently play anything other than MPEG2. I have a recording going from BBC One HD and there is a 00001.ts file which is growing rapidly. I just played it back on a different PC. Mplayer output: Playing 00001.ts. TS file format detected. VIDEO H264(pid=6601) AUDIO AAC LATM(pid=6602) SUB DVB(pid=6605) PROGRAM N. 132 FPS seems to be: 25.000000 Load subtitles in ./ ========================================================================== Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264) ========================================================================== ========================================================================== Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio: 0->192000) Selected audio codec: [fflatm] afm: ffmpeg (FFmpeg AAC in LATM) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... Unsupported PixelFormat 61 Unsupported PixelFormat 53 [h264 @ 0xeccca0]mmco: unref short failure Movie-Aspect is 1.78:1 - prescaling to correct movie aspect. VO: [vdpau] 1440x1080 => 1920x1080 Planar YV12 Looking good! As far as I can tell, it seems to be working. :-) Next step, get the epg sorted out... Cheers, Laz

4 6

[ANNOUNCE] VDR developer version 1.7.20
by Klaus Schmidinger 21 Aug '11

21 Aug '11

VDR developer version 1.7.20 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.20.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.19-1.7.20.diff MD5 checksums: eda2911fff1715ba5b1482b20ad18188 vdr-1.7.20.tar.bz2 a8f5bcaf3294cc9fce87283a618d5ce1 vdr-1.7.19-1.7.20.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. This version contains functions to determine the "signal strength" and "signal quality" through cDevice. If you are using a DVB card that contains an stb0899 frontend chip (like the TT-budget S2-3200) you may want to apply the patches from ftp://ftp.tvdr.de/vdr/Developer/Driver-Patches to the LinuxDVB driver source in order to receive useful results from that frontend. The changes since version 1.7.19: - Added some missing 'const' to tChannelID (reported by Sundararaj Reel). - The isnumber() function now checks the given pointer for NULL (thanks to Holger Dengler). - Now checking Setup.InitialChannel for NULL before using it (reported by Christoph Haubrich). - cSkins::Message() now blocks calls from background threads (thanks to Michael Eiler for reporting a crash in such a scenario). - Fixed the return value of the svdrpsend.pl script in case of an error (thanks to Jonas Diemer). - Increased MAXCAIDS to 12 (thanks to Jerome Lacarriere). - Fixed handling DiSEqC codes (thanks to Mark Hawes for reporting the bug, and Udo Richter for suggesting the fix). - Added a mechanism to defer timer handling in case of problems (reported by Frank Niederwipper). - Fixed distortions that happened when splitting recording into several files (was a side effect of "Fixed detecting frames in case the Picture Start Code or Access Unit Delimiter extends over TS packet boundaries" in version 1.7.19). cRecorder::Action() now buffers TS packets in case the frame type is not yet known when a new payload starts. This adds no overhead for channels that broadcast the frame type within the first TS packet of a payload; it only kicks in if that information is not in the first TS packet. - Fixed handling the channelID in cMenuEditChanItem (thanks to Udo Richter). - cStringList::Sort() can now be called with a boolean parameter that controls case insensitive sorting (suggested by Sundararaj Reel). - Now scanning new transponders before old ones, to make sure transponder changes are recognized (thanks to Reinhard Nissl). - Implemented static cIndexFile::IndexFileName(). - The length (as number of frames) of a recording's index file can now be determined by a call to cIndexFile::GetLength() (suggested by Christoph Haubrich). - Fixed some crashes in subtitle display (thanks to Rolf Ahrenberg). - Made DELETENULL() thread safe (reported by Rolf Ahrenberg). - The pic2mpg script of the 'pictures' plugin now generates HD images (thanks to Andre Weidemann for his support in using convert/ffmpeg). The old SD version is still available as pic2mpg-sd. - Added a mutex to protect cOsd::Osds from simultaneous access from different threads (reported by Rolf Ahrenberg). - The cutter now sets the 'broken link' flag for MPEG2 TS recordings (thanks to Oliver Endriss). - Fixed language code entry for Portuguese. - The new command line options --filesize (suggested by Marco Göbenich) and --split can be used together with --edit to set the maximum video file size and turn on splitting edited files at the editing marks. These options must be given before --edit to have an effect. - cTimeMs is no longer initialized to the current time if the value given to the constructor is negative (avoids the "cTimeMs: using monotonic clock..." log message before VDR's starting log message). Have fun! Klaus

4 7

ANNOUNCE vdr-osdteletext 0.9.1
by Tobi 20 Aug '11

20 Aug '11

It has been a long time since the last release and I wanted to at least get the pending language updates out (Thanks to Diego and Milan!) I haven't found much time to work on this, so if anyone wants to help - just pick a bug and send a patch or request to join for commit access. The changes: * Updated Italian translation provided by Diego Pierotto (Closes #450) * Added Slovak translation provided by Milan Hrala (Closes #558) As always: Any help is welcome! Development site: http://projects.vdr-developer.org/projects/plg-osdteletext Downloads: http://projects.vdr-developer.org/projects/plg-osdteletext/files Git-Web: http://projects.vdr-developer.org/git/vdr-plugin-osdteletext.git/ Anonymous Git-access : git://projects.vdr-developer.org/vdr-plugin-osdteletext.git This is intended to be a community maintained project! Don't expect me to fix your problems, I'm merely maintaining the project! Please report any bugs, ideas or feature requests to the project site (no registration required for this!). If you want to contribute patches, new features or whatever, post an issue or patch to the projects issue tracker or request to join the project. I would happily add everyone as a project member, who would like to contribute to the project! Tobias

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr August 2011