vdr

vdr@linuxtv.org

2 participants
6731 discussions

OT. CPU type
by Lauri Tischler 09 May '05

09 May '05

I have two VDR boxes, one with VIA C3 and other with AMD K7. What would be the CPU-type to use to compile the kernel so that the same bzImage would run on both boxes. I know that type 486 will run but how about Pentium-Classic, Pentium-MMX, Pentium-Pro, Pention-II or Pentium-III -- lwgt(a)iki.fi * Using HTML-mail is like breaking wind in a church * 60.2N 24.7E * it is not illegal, just extremely bad manners *

3 2

vdr-1.3.23: BUG: cPesAssembler dropped data resulting in delayed crash of VDR
by Reinhard Nissl 09 May '05

09 May '05

Hi, while recording the radio channel "Bayern 1" on Astra 19.2E from 0900 to 1000 this morning, I've discoverd that VDR crashed at about 0932. After debugging the whole afternoon I've recently found the bug that caused this crash. It's cPesAssembler that drops some data in certain circumstances. The crash has nothing todo with recording this channel, but with the transfer mode I'm using with vdr-xine, as it makes use of cPesAssembler. BTW: To reproduce this crash just tune to the mentioned channel in transfer mode and wait for about 33 minutes. The bug has to do with cPesAssembler's length member, as it conforms to this equation: length == 0 || length >=4 It's therefore impossible for cPesAssembler to store any fragments of less than 4 bytes. But the problem is, that these bytes have modified it's shift register "tag" which leads to wrong synchronisation on the next fragment. For this channel, it seems to happen that cPesAssembler sees data blocks that end with the sequence 00 00 01. These 3 bytes are stored in cPesAssembler's "tag" member. But when the next data block arrives, these bytes are ignored, as "length" is still 0, and further data is dropped, as it needs to sychronize on the next start code (00 00 01). When the next fragment is to be stored, it results in "data" beeing something like that 00 00 01 00 00 01 c0 ... As a result, the expected length evaluates to 6 bytes, but "length" containes already more than that (in the above case it was 79). This finally leads to "Rest" beeing -73 which then causes a crash in memcpy. The attached patch fixes this issue by introducing a new variable "hasFragment". It helps to recognize that 1 to 3 bytes are already stored in cPesAssembler. Feel free to drop this new variable and use "length" instead. Where length is checked for beeing 0, it should be checked for beeing < 4 and where "hasFragment" is set to true, "length" should be set to any value != 0 and < 4. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

8 18

RE: [vdr] Feature request, indication of conflicting timers.
by jori.hamalainen＠teliasonera.com 09 May '05

09 May '05

> It would be very good feature to see from timers list that > when recordings are incorrectly timed. > VDR knows this so it should tell it to user as well! Have you tried Timeline plugin? http://www.js-home.org/vdr/timeline/index.php It is not VDR build-in support, but via it you can check the overlapping timers. Best regards, Jori

2 1

[ANNOUNCE] noad-0.6.0
by the Noad 09 May '05

09 May '05

Hi, there is a new Version of noad available. You can find it on the noad-Homepage: www.freepgs.com/noad Changes Version 0.6.0 - add audio-silence-detection - add check for ac3-scan - fixed a bug in online-scan (wrong marks if there is a short part with ac3-sound at the start of the recording) Version 0.5.3 - change the way to find the mpeg2-headers in configure look for pkg-config else try /usr/include else try /usr/local/include - fixed a bug in restart scan after searching for a new logo in online mode - changed umask for create mark-files What is noad? noad is a small programm that tries to detect advertising breaks in vdr-recordings and write cutting marks into the marks.vdr. Read more on the noad-Homepage. theNoad

5 5

[ANNOUNCE] timercmds.conf - patch
by Gerhard Steiner 08 May '05

08 May '05

Hello, I wrote a little patch to get commands for the timer items in the timer-menu. This is similar to the commands in the recording-menu. You need to have the file timercmds.conf in your <video>-dir. The syntax for the timercmds.conf is the same as for the reccmds.conf. Download: http://vdrportal.de/board/thread.php?postid=306151&sid=#306151 You will also find a little script to allow playback of the currently recording timer. For this you will need the SVDRP-Patch from HFlor: http://vdrportal.de/board/thread.php?threadid=32789&sid= Winni will probably make some script public to allow automatic searching of a timer item with epgsearch. Have fun Gerhar -- +++ Neu: Echte DSL-Flatrates von GMX - Surfen ohne Limits +++ Always online ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

2 1

Re: [vdr] Softdevice + vidix + matrox G550 - is this possible?] - need help adjusting fb.modes file
by anthony hornby 08 May '05

08 May '05

Hi All, I have it almost sorted out - perfect quality on monitor when monitor output is enabled - still a little garbled on tv though. This seems to be a fb.modes problem. I planning to play around with the modes to try to resolve this. Can anyone point me to any tools or howto's around adjusting modes in a sensible logical fashion? Any & all advice appreciated :-) Thanks a lot. Regards Anthony. -------- Forwarded Message -------- From: anthony hornby <anthony.hornby(a)cdu.edu.au> Reply-To: anthony.hornby(a)cdu.edu.au, Klaus Schmidinger's VDR <vdr(a)linuxtv.org> To: Klaus Schmidinger's VDR <vdr(a)linuxtv.org> Subject: Re: [vdr] Softdevice + vidix + matrox G550 - is this possible? Date: Sun, 08 May 2005 12:07:49 +0930 Hi Nicolas, Thanks for the tips. I have directfb working but am experiencing a problem where the output is only on the attached monitor and nothing on the TV. When I switch plugs over the output stays on the monitor only. I guess this means it can't find mode lines that can work with the TV. I just want vdr output on the TV out and normal X on the main hread of the G550. Can anyone who is using a G550 send me a copy of their fb.modes file and also /etc/directfbrc plus any mods you made to your xorg.conf (or XFree equivalent config file). Thanks a lot. Any further tips appreciated. Regards Anthony. On Thu, 2005-05-05 at 03:40 +0200, Nicolas Huillard wrote: > anthony hornby a écrit : > > Hi, > > I want to set up my VDR to use softdevice and use the output of my > > Matrox G550 card. > > > > I have got the latest CVS for softdevice, directFB, DFB++, vidix and > > ffmpeg. Am running Fedora core 3 with the latest 2.6.11 series kernel. > > > > Have built all successfully. > > Now I want to keep the second head on my G550 running X (a gnome desktop > > on the local monitor on the box is handy) but also have accelerated > > output on the tv-out. > > > > I think this means I am restricted to using vidix - is this correct? > > I don't think so. You can also use DirectFB. > There was a recent (<2 months) thread regarding your problem on the > softdevice ML or the DirectFB ML. IIRC, everything was solved for the > original poster. > _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

1 0

VDR not removing recordings
by Kartsa 08 May '05

08 May '05

For a few days now vdr has not been deleting recordings from the harddisk. They are deleted using osd and the name has properly changed from .rec to .del but the files stays. And there is no hint in log about why this is happening. Any ideas? - Kartsa No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.2 - Release Date: 2.5.2005

7 22

ANNOUNCE: graphlcd-0.1.2-pre6
by Andreas Regel 08 May '05

08 May '05

Hi, here is a new pre-release of the GraphLCD base package and plugin for VDR. The main change since pre5 is the integration of the freetype2 patches from Lucian Muresan. I hope that this will be the last prerelease of 0.1.2. You can download the packages from the berlios project's file page: http://developer.berlios.de/project/showfiles.php?group_id=3566 Andreas Changes since 0.1.2-pre5: graphlcd-base: - glcdgraphics: Added additional type casts to std::min calls to make it compile on x86-64 (thanks to Stefan Bergler). - glcddrivers: fixed a bug in serdisp.c. When using direct IO the port string was truncated (thanks to Stefan Bergler). - glcddrivers: Added method cConfig::GetConfigIndex for getting a configuration by its name (thanks to Lucian Muresan). - Added some $(DESTDIR) all over the Makefiles (thanks to Lucian Muresan). - glcddrivers: sed1330: Added setting of CS line in 6800 mode (thanks to Wolfgang Astleitner). - glcdgraphics: Added FreeType2 support based on patch by Lucian Muresan. -- You have to set HAVE_FREETYPE2 in Make.config to enable this -- Added some helper functions to GLCD::cFont class vdr-graphlcd: - moved plugin initialisation to cPluginGraphLCD::Initialize and added a wait for the start of the display thread to cPluginGraphLCD::Start to don't miss first channel switch (thanks to wofritz from vdrportal.de) - added rumanian translations (thanks to Lucian Muresan) - Added support for Freetype2 fonts based on the patch by Lucian Muresan. -- the fonts used by the plugin are no longer specified through symbolic links to the font files but in a config file named fonts.conf that is located in the graphlcd config directory (where logonames.alias is) -- the entries in the fonts.conf file are defined in a URL like way, a prefix gives the type of the font and a absolute or relative path gives the font file, plus the size in case of freetype2 -- I provided several sample fonts.conf files as a replacement for the old symbolic links

2 1

AverTv771, Dxr3 -> glitches with hdd activity
by Michael Schröder 08 May '05

08 May '05

Hi out there, maybe someone has a hint for me. I'm trying to get vdr run smoothly since a while now and I 'm close to giving up. Watching TV works fine, but as soon as I start recording, timeshifting or just doing some harddisk activity, there are a lot of glitches in the video/audio. Power management/ACPI is switched off in the kernel, HDD uses UDMA5 mode, so everything should be fine ?? Of course all drivers seem to load without probs. At least there are none reported in dmesg. My system: VDR 1.3.16 /VDR1.3.23 latest CVS version of video4linux, dxr3, dvb drivers.. I also tried several releases/older versions. Kernel 2.6.11 / 2.6.9 AverTV 771 DVB-T dxr3 ECS K7SEM (SIS) / Asrock K7VM2 (VIA) mainboard Duron1600 CPU 512 MB Samsung 120G HDD Any ideas anyone ?? Thanks. Michael -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.6 - Release Date: 06.05.2005

1 1

How to repair damaged AC3 stream of old recordings
by Stefan Lucke 08 May '05

08 May '05

Hi, as old recordings (pre vdr1.3.19) have damaged ac3 substream ids, and this damaged substream id is part of crc'd data it would be necessary to replaced the damaged substream id by 0x80 and to re-crc if previous crc is ok. Does someone know if there is a batch utility which can do that ? -- Stefan Lucke

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr