vdr November 2009

vdr@linuxtv.org

74 participants
71 discussions

Re: [vdr] ttxtsubs patch for vdr-1.7.10
by Mr. Tux 27 Nov '09

27 Nov '09

Hi Magnus Thanks for the patch - runs like a charm :-) bye Mr Tux > > > > ------------------------------ > > Message: 9 > Date: Sun, 22 Nov 2009 16:59:28 +0100 > From: Magnus H?rlin <magnus(a)alefors.se> > Subject: [vdr] ttxtsubs patch for vdr-1.7.10 > To: VDR Mailing List <vdr(a)linuxtv.org> > Message-ID: <4B095FE0.3040502(a)alefors.se> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, just thought I'd post an unofficial ttxtsubs patch for vdr-1.7.10 in > case someone wants to use it. /Magnus H > > >

1 0

Dynamic PIDs
by Jouni Karvo 27 Nov '09

27 Nov '09

hi, is there somewhere a patch that would remove the break when the broadcaster uses "dynamic pids" (such as YLE). Now, when a programme starts at YLE, they change the Audio PID number, leading to VDR re-tuning or something, that leads to a 1-2s break in the show. There is no change in frequency, so I don't see any reason why there is such a break. Or is this a problem of co-operation with vdr-xine, instead of tuning the card? yours, Jouni

5 13

Cannot replay recordings on FF card if recorded with s2 card
by Matthias Fechner 25 Nov '09

25 Nov '09

Hi, I have now replaced my primary video with a nice Atom board and inserted there a Tevii S470 card. Output is via HDMI and the xineliboutput plugin. It is working really great, thanks a lot for the really fantastic software! But I have now a big problem. I upgraded now from vdr 1.7.2 to 1.7.10. If I record now a normal PAL movie I cannot replay it with my FF card on my old TV. Sound is stuck and picture as well. I had a similar problem with vdr 1.7.9 and went then back to 1.7.2 which solved the problem. But now I cannot switch back to an older version because xine will not work then without patching a ot of stuff. Is there a know issue with vdr newer 1.7.2 and replay on a FF (TechnoTrend Rev 1.3) card? Bye, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

2 2

skinsoppalusikka box size in HD
by Jiri Dobry 24 Nov '09

24 Nov '09

Hello, I am using skinsoppalusikka(thanks Rolf for great job). VDR with latest xineliboutput allow use full HD OSD. But it is problem because box size for timers and status is divided from symbol size and it is too small. I can't use font sizes over 3.6%. Here is bugfix for replay screen. Jiri PS: exept this bug, skinsoppalusikka use olny one lineWeight. If you try use bigger small font than normal characters overload from boxies, but it is not fixed in this patch. ------------------------------------------------------- diff -urN skinsoppalusikka-1.6.4/soppalusikka.c skinsoppalusikka-1.6.4-patched/soppalusikka.c --- skinsoppalusikka-1.6.4/soppalusikka.c 2009-04-14 03:20:00.000000000 +0200 +++ skinsoppalusikka-1.6.4-patched/soppalusikka.c 2009-11-24 16:08:35.000000000 +0100 @@ -1175,18 +1175,20 @@ cSkinSoppalusikkaDisplayReplay::cSkinSoppalusikkaDisplayReplay(bool ModeOnly) { int sw = bmFastReverse.Width() + bmSlowReverse.Width() + bmPlay.Width() + bmPause.Width() + bmSlowForward.Width() + bmFastForward.Width(); - lineHeight = cFont::GetFont(fontOsd)->Height(); + lineHeight = cFont::GetFont(fontSml)->Height(); + if (lineHeight < bmPause.Height()) lineHeight = bmPause.Height(); drawdate = true; modeonly = ModeOnly; x0 = 0; x1 = x0 + BigGap; x2 = x1 + Roundness; - x3 = x2 + sw + 5 * Gap; + x3 = x2 + cFont::GetFont(fontSml)->Width("XXX 00.00.00 00:00") + 2 * Gap; x4 = x3 + 4 * BigGap; x10 = cOsd::OsdWidth(); x9 = x10 - BigGap; x8 = x9 - Roundness; - x6 = x8 - sw - 5 * Gap; + x6 = x8 - cFont::GetFont(fontSml)->Width("00:00:00/00:00:00") - 2 * Gap; + if (x6 > x8 - sw - 5 * Gap) x6 = x8 - sw - 5 * Gap; x7 = x6 + (x8 - x6) / 2; x5 = x6 - 4 * BigGap; y0 = 0;

1 0

Yaepghd record dialog
by Stuart Morris 24 Nov '09

24 Nov '09

I have been trying out the yaepghd plugin. It looks very impressive but the record dialog appears to be disabled. Does anyone know if this has been intentionally disabled or is only partially implemented? There has been no development activity on this plugin for about 9 months now.

3 3

Odd filesystem errors (Theunis Potgieter)
by HighlyCaffeinated 23 Nov '09

23 Nov '09

________________________________ >>On 23.11.2009 17:38, HighlyCaffeinated wrote: >>>> what does this return ? >>>> find /video0 >> >> Enough output that I instead chose to `find /video0 > found` >> to more easily look through it. Careful inspection reveals > those directories are not shown and find produces no errors > in the process. > >This sounds very odd. > >Have you run an fsck on that disk, yet? > >Klaus I have. e2fsck ran against the (unmounted) volume and found no errors. I've never experienced something like this before and to be honest would not believe it if I hadn't seen it. I have successfully copied the sub-directories and data across the network using Windows/Samba, then copied it back to a new folder name. Both played perfectly. I just can't get rid of the original directories. -Todd

2 1

Odd filesystem errors (Theunis Potgieter)
by HighlyCaffeinated 23 Nov '09

23 Nov '09

>> what does this return ? >> find /video0 Enough output that I instead chose to `find /video0 > found` to more easily look through it. Careful inspection reveals those directories are not shown and find produces no errors in the process. <<shrugs>> -Todd

2 1

VDR 1.7.9 fails to record one channel
by Jouni Karvo 23 Nov '09

23 Nov '09

hi, I have the following problem: When live viewing with 1.7.9 and vdr-xine 0.9.3, this channel (in cable) is shown properly: TV7;HTV:386:M128:C:6900:800+802=2:801=fin:0:0:61500:42249:16:0 If I try to record anything, vdr restarts constantly, and the recording is of zero length. The output of vdr (or xine) says: DiscontinuityDetected: triggering soft start With 1.7.7 and the same vdr-xine version, recording works, but vdr is not able to jump forward or backward in the recording. 1.7.9 is also able to show the recordings made with 1.7.7 (but not able to jump forward or backwards.) Any debugging hints? yours, Jouni

3 4

Re: [vdr] Odd filesystem errors
by HighlyCaffeinated 23 Nov '09

23 Nov '09

Date: Sun, 22 Nov 2009 14:20:56 +0100 From: Peter Evertz <leo2(a)pec.homeip.net> Subject: Re: [vdr] Odd filesystem errors To: VDR Mailing List <vdr(a)linuxtv.org> Message-ID: <4B093AB8.4000905(a)pec.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Klaus Schmidinger schrieb: > On 07.11.2009 02:07, HighlyCaffeinated wrote: > >> I've got an unusual situation with my VDR installation ...<snip>... >> bothersome. >> That is "normal" situation on a samba share that has (windows) "illegal" characters in it's name. eg: "CSI: Next Session" is illegal because of the ":" and will be translated to something like you have seen on the windows box. Peter > > Can you check the syslog file to see what names VDR used to create > the recording directories? > > Klaus > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > Peter: I am not too concerned with the existence of a tilde in the filename. If the filename had been created per your example, I would have expected Windows to display it as "CSI_Ne~1". A recent directory shows in Linux as NCIS:_Los_Angeles as it should. My concern is that I cannot see (and therefore manipulate or delete) these directories in Linux. Linux will not show the directory names or inodes. Windows does, but the names are illegal and so won't operate on them. Klaus: I will keep an eye out for the creation of any more such directories but cron took care of the syslog files long before I noticed that the directories were there. Anyone: Any clue how to delete the directories besides formatting the partition? Thanks for your help! -Todd

2 1

vdr 1.7.10: missing reset of file size
by Klaus Schmidinger 22 Nov '09

22 Nov '09

I'm afraid I forgot to reset the file size when regenerating the index file. This should fix this in case the recording is split over several files: --- recording.c 2009/11/22 11:20:53 2.18 +++ recording.c 2009/11/22 19:38:04 @@ -1412,8 +1412,11 @@ // Read data: else if (ReplayFile) { int Result = Buffer.Read(ReplayFile, BufferChunks); - if (Result == 0) // EOF + if (Result == 0) { // EOF ReplayFile = FileName.NextFile(); + FileSize = 0; + FrameOffset = -1; + } } // Recording has been processed: else { Klaus

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2009