vdr

vdr@linuxtv.org

2 participants
6731 discussions

cRemux single threaded?
by Udo Richter 13 Aug '05

13 Aug '05

Hi list, I've been hunting down a bandwidth problem in my little streaming plugin, and finally realized that the performance bottleneck actually is cRemux and its internal resultBuffer. The resultBuffer is initialized with resultBuffer->SetTimeouts(0, 100), in other words, if no data is available, cRemux::Get will wait up to 100ms for data to arrive. Thats fine as long as cRemux is filled from another thread, but wastes time if cRemux is only filled from within the same thread. Unfortunately, the resultBuffer is completely hidden inside the cRemux, so I cannot change this behavior. Does anyone have good ideas how to avoid this without spawning another thread? (the thread would actually just copy data from one buffer to another...) This resultBuffer is really some kind of black hole, no way to control it, no way to know how much is in it... Cheers, Udo

2 10

VDR developer version 1.3.28
by Klaus Schmidinger 13 Aug '05

13 Aug '05

VDR developer version 1.3.28 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.28.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.27-28.diff The changes since version 1.3.27: - Added a sleep in cDvbPlayer::Action() in case there is no data to send to the device, which avoids a busy loop on very fast machines (thanks to Martin Wache). - Modified the description of cDevice::Poll() to avoid misunderstandings. - Updated Croatian language texts (thanks to Drazen Dupor). - cDvbPlayer::Goto() now appends a Sequence End Code to get the image shown immediately with softdevices (thanks to Reinhard Nissl). - Reactivated cVideoRepacker in remux.c after some fixes (thanks to Reinhard Nissl). - Removed the fix for handling VPS timers, so that they only record if the event they are assigned to actually has the given VPS time. This has caused repeating VPS timers to stop recording prematurely. - Avoiding duplicate components in EPG events when reading epg.data or in the PUTE SVDRP command (thanks to Olaf Titz for reporting this one). - Added the command line options '--lirc', '--rcu' and '--no-kbd' to allow setting the remote control at runtime (based on a patch by Darren Salt). - Now checking whether timers or channels are currently being edited via the menu before making changes through SVDRP (thanks to Andreas Brugger for reporting a problem with this). - Files and directories are now created with rights according to the shell's umask settings (thanks to Andreas Brachold). - Fixed the cChannel copy constructor (thanks to Marcel Wiesweg for pointing out a problem with it). - Fixed an out-of-bounds memory access with audio language ids (thanks to Matthias Lenk for reporting, and Udo Richter for suggesting a fix). - Updated the Finnish OSD texts (thanks to Rolf Ahrenberg). - Added missing storing of the MenuScrollPage parameter (thanks to Frank Krömmelbein). - Added cRemux::SetTimeouts() for better use of cRemux in a single thread (thanks to Udo Richter for reporting a problem with this). - Modified cEITScanner::Process() so that it uses the primary device if it is replaying and is the only device that provides the given transponder, and that a forced EPG scan works even if EPG scan timeout is set to 0 (thanks to Bernhard Stegmaier for reporting a problem with this). - Fixed cDvbSpuBitmap::putPixel() (thanks to Reinhard Nissl). - Fixed setting system time to avoid time jumps in case of faulty data (thanks to Andreas Böttger). - Fixed a memory leak in the SVDRP command LSTE (thanks to Stefan Huelswitt). The DVB driver I am currently using can be found at ftp://ftp.cadsoft.de/vdr/Developer/linux-dvb.2004-12-26.tar.bz2 which is the CVS 'HEAD' version from 2004-12-26, made available as a complete archive for your convenience. Of course, you can also use any newer driver version. Have fun! Klaus

12 18

lirc & mplayer plugin
by Leo Márquez 12 Aug '05

12 Aug '05

Hi!, I'm using vdr with lirc without problems but with mplayer i don't have remote control. I have readed that the recommended mode of mplayer to act as vdr plugin is slave. But I see in mplayer.sh in the SLAVE sentence -nolirc. I don't know if I have to remove this option, or compile mplayer with lic support. Anyone has running this ? Thanks Leo

2 1

Re: [vdr] How to speed up vdr start ?
by s.huelswitt＠gmx.de 12 Aug '05

12 Aug '05

On 07 Aug 2005 "Christoph Hermanns" <Christoph.Hermanns(a)web.de> wrote: > How can i speed up the starting of the dvb driver and vdr ? If you're using a FF dvb card, loading the firmware takes some time. You can speed up this (or actually hide some time) if you don't let runvdr load the driver but rather create an own startup script to load the driver and run this one very first after boot i.e. S01. You have to background (&) the make insmod call. You can further speed up things, if you don't use seperate startup scripts but rather one single boot script. Scanning IDE bus e.g. for DVD-ROM blocks my machine for several seconds. So I compiled IDE driver as a module (doing network boot, so no boot drive). I call modprobe ide-detect very late in the boot process. Regards. -- Stefan Huelswitt s.huelswitt(a)gmx.de | http://www.muempf.de/

3 3

Re: [vdr] vdr killing its recording on symlink directory
by peter.dittmann＠freenet.de 12 Aug '05

12 Aug '05

>Von: "Emil Naepflein"<Emil.Naepflein(a)philosys.de> > On Wed, 10 Aug 2005 22:23:26 +0200, Klaus Schmidinger wrote: > > > An even better idea (IMHO) would be to drop that whole video > > directory symlinking stuff altogether and say "If you want a large disk, > > use something like RAID or whatever". I was never a friend of this > > linking, and regret the day I agreed to implement it... > > I am totally against dropping this functionality. Sound I triggered another religios war. I hope I will never regret this posting ;D > > On server systems with multiple TB of storage it would be just brain > > dead to put all recordings on one large raid filesystem. A single error > > in the filesystem could kill all the recordings. Basically the usually distribution between /videoX directories doesn't help here improving safety (doesn't matter if on RAID or single discs). A single failing disc/RAID will cause almost all recordings to fail because they are distributed. Often all recordings will miss at least one file after that. All thats left then are partial recordings, ergo useless. This was/is the reason quite a lot of people move the cutted recording completely to one /videoX , so one recording is kept on one harddrive completely. To make this work you HAVE to symlink to /video0. > The symlink functionality works fine since more than 4 years. It is easy > to use and it is easy to expand storage without doing any > reorganisation. It is one of the most important features of vdr. Agree, but for a different reason. Most people have not the money to start a RAID 5 at the beginning. I usually buy a new additional HD if needed. Ok there is LVM . . . Althought LVM works, a single disc failing in LVM crashes everything. And try one time to add a new additional disc to a RAID 5 installation . . . But thats another war . . . > Those people that have problems with it have not unterstood how it > works. Nobody is forced to use this functionality, but those that use it > intentionally appreciate it very much. See remark above. That you don't understand the intentions of others should not cause you to blaim others for not understanding vdr ;-) I was just pointing out a weekness that may be worth fixing . . . > So keep it, please. I would personnally rather vote for a round robin distribution of recordings not single files, but that a different thread. The circulating patch changing the file distribution method is not applied my vdr because I feared worse side effect. regards Peter

1 0

DVB Device in info.vdr?
by Dominique Simon 12 Aug '05

12 Aug '05

Hi! For debug purposes i wan't to know on which DVB Device a recording has been made (device 0 or 1). Anyone has a idea how this can be realised? A small line C++ Code at the right place should do it, but which and where ;) TIA, Dominique!

1 0

BBC To Open Source This Project
by edafe 12 Aug '05

12 Aug '05

'Promise.tv takes advantage of digital television technology to automatically record a full seven day's broadcasting across all selected TV channels.' http://www.promise.tv/

6 8

osdteletext and problem with OSD
by Marcel Wiesweg 12 Aug '05

12 Aug '05

Hi, I received a bug report for osdteletext which describes a way to crash the FF cards' OSD, and I am able to reproduce this. (Open teletext on a channel with colorful teletext such as RTL, press repeatedly, fast and in random order Yellow Key for half page and Green Key for zoom.) Then the OSD seems to hang a short time, then disappears, after a while some garbage appears. I tested with the in-kernel drivers from 2.6.11 and 2.6.12. Neither VDR nor the kernel driver seem to crash, but the OSD will not work again. In dmesg I read multiple times: dvb-ttpci: warning: timeout waiting in BlitBitmap: 0, 1 Reloading dvb-ttpci fixes the problem. Obviously this is some sort of driver/firmware bug. What I am concerned with is: Does osdteletext do anything wrong? Has this to be fixed somewhere in user level code, or is it just another firmware bug? Marcel

3 3

[Fwd: Re: [vdr] Mac mini + Xine plugin = perfect vdr client?]
by Reinhard Nissl 10 Aug '05

10 Aug '05

-------- Original Message -------- Subject: Re: [vdr] Mac mini + Xine plugin = perfect vdr client? Date: Wed, 10 Aug 2005 21:38:33 +0200 From: Carsten Rietzschel <cr7(a)darav.de> To: Reinhard Nissl <rnissl(a)gmx.de> CC: Klaus Schmidinger's VDR <vdr(a)linuxtv.org> References: <42FA3522.9070901(a)icem.com> <42FA5383.3090908(a)gmx.de> Hello, I'm using the MacMini as my VDR since a few weeks :) configuration: - Cinergy T2 (DVB-T) - ATI remote wonder - gentoo linux with vdr 1.3.24 - xine-plugin (thanks Reinhard for OSD fix :) And it works very well! No big problems so far, except one: TV-Out doesn't work yet for me. I've tried using gatos.sf.net-drivers from Rune Petersen - but no luck yet. Maybe someone can help!!?!? Some minor problems still must be solved: - Mplayer plugin (using /usr/bin/xineplayer) doesn't work - DVD playback is sometimes choppy But currently I'm too busy to investigate - may be at the weekend. Please share your experiences too :)

1 0

[Announce] LNB-sharing patch for VDR 1.3.28
by Matthias Lötzke 10 Aug '05

10 Aug '05

Hello! A new release of the configurable LNB-sharing patch for VDR 1.3 is available at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurableLNBshare-VDR_… Changes: - adapted to VDR 1.3.28 The DiSEqC support still needs more testing - I do not have DiSEqC hardware myself. Please provide feedback. For general information about the LNB-sharing patch have a look at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt http://www.vdr-wiki.de/wiki/index.php/Lnbsharing-patch (german) Matthias.

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