vdr

vdr@linuxtv.org

6731 discussions

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

ttxtsubs patch for vdr-1.7.10
by Magnus Hörlin 22 Nov '09

22 Nov '09

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

Editing recordings and no instant video update when moving markers
by Ian Bates 22 Nov '09

22 Nov '09

Hello, When editing recordings I am struggling to fine tune marker placement as adjustments made with '4' and '6' keys while moving the marker as indicated by the time line do not update the video display with the corresponding position in the recording. Current setup: SW: VDR-1.7.9 (with freesat patch), NVIDIA driver 185-something, xineliboutput and xine as outptut plugins, ffmpeg-svn / xine-lib-1.2- hg from about two weeks ago, v4l-dvb-hg from about two weeks ago, slackware64-current OS HW: M2NPV-VM with onboard Nvidia 6150, Athlon something 64 bit dual core (at least 2.1GHz), a couple of SATA disks. - This problem only occurs with TS recordings, PES recordings made with vdr-1.7.0 with this setup work as expected. - With the xineliboutput plugin the display does not update at all when moving the marker. - With xine plugin the display updates but with seemingly random time intervals, from almost realtime as expected to delays of 1-5 seconds to sometimes not at all, depending on the recording and the position of the marker. I have a tedious workaround: set marker, play - If adjustment needed then - select marker, adjust with '4' or '6', play, repeat until no further adjustment needed. Does anyone have the same problem? Does anyone NOT have this problem? What can I do to fix this? Best wishes, Ian.

3 2

vdr 1.7.8 shows wrong recording length
by Martin Dauskardt 22 Nov '09

22 Nov '09

I have a TS recording of more than two hours which seems to have no errors (Project X demux log looks fine). When I start playing it with vdr, the replay osd shows a recording lenghth of only 9 minutes. The same values is displayed in the recording menu (yes I know, this is not a vdr feature but comes from a patch) Is it worth to investigate it? I still have this recording on my disc. Greets, Martin

2 1

Odd filesystem errors
by HighlyCaffeinated 22 Nov '09

22 Nov '09

I've got an unusual situation with my VDR installation that has me completely stumped. My /video0 directory is located on a 1TB ext2 filesystem. When I perform an 'ls-al' I get an incomplete list of the directories located there. If I open that filesystem on a Windows box via Samba, I see that two recent directories have been created that the 'ls' does not show me. The directories are named COO66K~7 (a CSI recording) and N3OZM1~R (an NCIS recording) in Windows. I can drill down into either directory and find the expected filesystem structure and two recordings that we had thought had failed. They are only visible through Windows/Samba. I can copy the contents of the directory to a Windows box and then copy them back to VDR (with a new folder name) and they play normally. As Debian refuses to acknowledge their existence, I cannot rename or delete the directories and I cannot copy data from the subdirectories. I have tried masking the tilde in the filenames, and that didn't change anything as I suspect the filenames are instead REALLY long. I am running vdr 1.7.7 with ATSC tuners and the ATSCepg plugin, and the system regularly creates successful recordings. Anyone with a pointer on how to deal with this and what may be causing such an odd set of circumstances? e2fsck didn't find anything it considered to be bothersome. -Todd

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr