vdr June 2011

vdr@linuxtv.org

46 participants
35 discussions

Can' read mkv with vdr-1.7.18 + mplayer + TT S2-6400 !
by Karim Afifi 17 Aug '11

17 Aug '11

Hello, Since I have upgraded my hardware from "TT Nexus" to "TT S2-6400", I can't read any mkv file anymore from my vdr-1.7.18 and MPlayer. It seems that VDR can't share the device. This limitation is very very annoying : Is there any patch for VDR and/or for MPlayer ? Do you know any workaround or any other solution ? Regards. Karim _______________________________________________________________ Here is the log : logger: *** DEBUG: MPLAYER_RETURN: "0" logger: *** DEBUG: parsed output … [View More]

7 12

[ANNOUNCE] VDR developer version 1.7.19
by Klaus Schmidinger 10 Aug '11

10 Aug '11

VDR developer version 1.7.19 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.19.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.18-1.7.19.diff MD5 checksums: 1eb04ecdc2b11ab8641ebfaa2cb93f42 vdr-1.7.19.tar.bz2 db16ce7bb51e0db837ed56ef4744a67e vdr-1.7.18-1.7.19.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it … [View More]under controlled conditions and for testing and debugging. This version introduces 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. Since apparently the various frontend drivers return different maximum values in their FE_READ_SIGNAL_STRENGTH and FE_READ_SNR functions (some deliver a value in the range 0x0000...0xFFFF, while others return values as "dB/10" or "dBm/10" (the latter with an offset to make the value positive, since the parameter is unsigned), the functions cDvbTuner::GetSignalStrength() and cDvbTuner::GetSignalQuality() use the device's "subsystem ID" to map these values into the range 0...100, which is the normalized return value of these functions. Take a look at these two functions and maybe remove the comment characters from the lines //#define DEBUG_SIGNALSTRENGTH //#define DEBUG_SIGNALQUALITY in dvbdevice.c to get some debug output if your device doesn't return any directly useful values and may have to be added appropriately to the 'switch (subsystemId)' statement. The channel display of the 'sttng' skin uses these values to implement a signal strength/quality display. The changes since version 1.7.18: - Fixed cString's operator=(const char *String) in case the given string is the same as the existing one (thanks to Dirk Leber). - Avoiding a gcc 4.6 compiler error in the skincurses plugin (thanks to Tobias Grimm). - TsGetPayload() now checks if there actually is a payload in the given TS packet (reported by Dirk Leber). - Now sorting the source file names in the call to xgettext, to make sure the results are not dependent on the sequence of the files. Plugin authors may want to change the line containing the xgettext call in their Makefile accordingly by changing "$^" to "`ls $^`". - The primary device is now only avoided for recording if it is an old SD full featured card. This is done through the new function cDevice::AvoidRecording(). - Subtitle PIDs are now also decrypted (thanks to Reinhard Nissl). - Fixed a possible race condition in cDiseqc::Execute() (reported by Marco Göbenich). The return value of cDiseqcs::Get() is now const, so plugin authors may need to adjust their code if they use this function. - The new functions cDevice::SignalStrength() and cDevice::SignalQuality() can be used to determine the signal strength and quality of a given device (thanks to Rolf Ahrenberg for some input on how to use BER and UNC values to generate a "quality" value). - The 'sttng' skin now displays two colored bars at the bottom of the channel display, indicating the strength (upper bar) and quality (lower bar) of the received signal. The number to the left of these bars indicates the actual device the current channel is being received with. - Fixed detecting frames in case the Picture Start Code or Access Unit Delimiter extends over TS packet boundaries (reported by Johan Andersson). In order to fix this, the semantics of cFrameDetector had to be changed a little. See cRecorder::Action() and cIndexFileGenerator::Action() on how to use the new cFrameDetector::NewPayload() function. - The frame detector now only starts collecting PTS values after it has seen the first I-frame, otherwise it might get MaxPtsValues values and stop analyzing even though the incoming data is still garbage (reported by Derek Kelly). - The info file of a recording is now only overwritten with a new fps value if that new value is not the default value (thanks to Derek Kelly for reporting a problem with the fps value being overwritten in case a recording was interrupted and resumed, and the fps value could not be determined after resuming recording). - The initial channel is now stored by the channel ID in the setup.conf file, in order to avoid problems in case channels are reordered or deleted (reported by Lars Bläser). - Added support for "content identifier descriptor" and "default authority descriptor" to 'libsi' (thanks to Dave Pickles). Have fun! Klaus [View Less]

5 11

Re: [vdr] vdr Digest, Vol 77, Issue 29
by Mike Booth 28 Jun '11

28 Jun '11

On Tue, 28 Jun 2011 12:00:01 vdr-request(a)linuxtv.org wrote: > Send vdr mailing list submissions to > vdr(a)linuxtv.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > or, via email, send a message with subject or body 'help' to > vdr-request(a)linuxtv.org > > You can reach the person managing the list at > vdr-owner(a)linuxtv.org > > When replying, please edit your Subject line so … [View More]it is more specific > than "Re: Contents of vdr digest..." > > > Today's Topics: > > 1. vdr-1.7.19 recording issue (Arthur Konovalov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 27 Jun 2011 16:06:51 +0300 > From: Arthur Konovalov <artlov(a)gmail.com> > Subject: [vdr] vdr-1.7.19 recording issue > To: vdr(a)linuxtv.org > Message-ID: <4E08806B.6060602(a)gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello! > > At least one problematic channel on local cable network with recording > problem discoverd using vdr-1.7.19. > > I have successfully recorded movie from Showtime channel by timer: > > Jun 27 03:59:00 akovdr vdr: [13440] switching device 4 to channel 20 > > Jun 27 03:59:00 akovdr vdr: [13440] actuator: switch to channel 20 > > Jun 27 03:59:00 akovdr vdr: [13440] timer 2 (20 0359-0450 'Langev > > taevas: Ela ja ?pi (Falling Skies') start Jun 27 03:59:00 akovdr vdr: > > [13440] Title: 'Langev taevas: Ela ja ?pi (Falling Skies Live and > > Learn, USA 2011)' Subtitle: '---' Jun 27 03:59:00 akovdr vdr: [13440] > > record > > /video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies/2011-06-27.03.59.20-0 > > .rec Jun 27 03:59:00 akovdr vdr: [13440] creating directory > > /video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies Jun 27 03:59:00 > > akovdr vdr: [13440] creating directory > > /video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies/2011-06-27.03.59.20-0 > > .rec Jun 27 03:59:07 akovdr vdr: [13440] SpinUpDisk took 7.33 seconds > > Jun 27 03:59:07 akovdr vdr: [13440] recording to > > '/video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies/2011-06-27.03.59.20- > > 0.rec/00001.ts' Jun 27 03:59:07 akovdr vdr: [16714] recording thread > > started (pid=13440, tid=16714) Jun 27 03:59:07 akovdr vdr: [16715] > > ecmhandler 3 filter thread started (pid=13440, tid=16715) Jun 27 > > 03:59:07 akovdr vdr: [16716] receiver on device 4 thread started > > (pid=13440, tid=16716) Jun 27 03:59:07 akovdr vdr: [16717] TS buffer on > > device 4 thread started (pid=13440, tid=16717) Jun 27 03:59:07 akovdr > > vdr: [16718] logger 3 filter thread started (pid=13440, tid=16718) Jun > > 27 03:59:09 akovdr vdr: [16714] unknown frame delta (-1543570764), > > assuming 25.00 fps Jun 27 04:00:46 akovdr vdr: [13459] channel 20 > > (Showtime) event E 27.06.2011 04:00-05:00 'Langev taevas: Ela ja ?pi > > (Falling Skies Live and Learn, USA 2011)' status 4 Jun 27 04:50:00 > > akovdr vdr: [16714] recording thread ended (pid=13440, tid=16714) Jun > > 27 04:50:00 akovdr vdr: [13440] buffer stats: 145136 (2%) used Jun 27 > > 04:50:00 akovdr vdr: [13440] timer 2 (20 0359-0450 'Langev taevas: Ela > > ja ?pi (Falling Skies') stop Jun 27 04:50:00 akovdr vdr: [16717] TS > > buffer on device 4 thread ended (pid=13440, tid=16717) Jun 27 04:50:00 > > akovdr vdr: [16716] buffer stats: 122952 (2%) used Jun 27 04:50:00 > > akovdr vdr: [16716] receiver on device 4 thread ended (pid=13440, > > tid=16716) Jun 27 04:50:01 akovdr vdr: [13440] cleaning up schedules > > data > > Jun 27 04:51:23 akovdr vdr: [13440] deleting timer 2 (20 0359-0450 > > 'Langev taevas: Ela ja ?pi (Falling Skies') Jun 27 04:55:15 akovdr vdr: > > [16715] ecmhandler 3 filter thread ended (pid=13440, tid=16715) Jun 27 > > 04:55:15 akovdr vdr: [16718] logger 3 filter thread ended (pid=13440, > > tid=16718) > > But trying to replay this recording fails. It just doesn't start: > > Jun 27 12:20:56 akovdr vdr: [17860] replay > > /video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies/2011-06-27.03.59.20-0 > > .rec Jun 27 12:20:56 akovdr vdr: [17860] playing > > '/video/Langev_taevas#3A_Ela_ja_?pi_(Falling_Skies/2011-06-27.03.59.20- > > 0.rec/00001.ts' Jun 27 12:20:56 akovdr vdr: [17928] ttxtsubs player > > thread ended (pid=17860, tid=17928) Jun 27 12:20:56 akovdr vdr: [17860] > > buffer stats: 0 (0%) used > > Jun 27 12:20:56 akovdr vdr: [17860] ttxtsubs: teletext subtitles > > replayer started with initial page 000 Jun 27 12:20:56 akovdr vdr: > > [17929] ttxtsubs player thread started (pid=17860, tid=17929) Jun 27 > > 12:20:56 akovdr vdr: [17930] dvbplayer thread started (pid=17860, > > tid=17930) Jun 27 12:20:56 akovdr vdr: [17930] resuming replay at index > > 0 (0:00:00.01) Jun 27 12:20:56 akovdr vdr: [17931] non blocking file > > reader thread started (pid=17860, tid=17931) Jun 27 12:20:56 akovdr > > vdr: [17927] TS buffer on device 3 thread ended (pid=17860, tid=17927) > > Jun 27 12:20:56 akovdr vdr: [17926] buffer stats: 99640 (2%) used Jun > > 27 12:20:56 akovdr vdr: [17926] receiver on device 3 thread ended > > (pid=17860, tid=17926) Jun 27 12:20:56 akovdr vdr: [17931] non blocking > > file reader thread ended (pid=17860, tid=17931) Jun 27 12:20:56 akovdr > > vdr: [17930] dvbplayer thread ended (pid=17860, tid=17930) Jun 27 > > 12:20:57 akovdr vdr: [17929] ttxtsubs player thread ended (pid=17860, > > tid=17929) Jun 27 12:20:57 akovdr vdr: [17860] buffer stats: 0 (0%) > > used > > After reverting to the vdr-1.7.18 this recording still not playable with > vdr. In the same time VLC media player doesn't have any problem with it > and no problems with recording-playback on the another channels. > > Making a new record on the same channel with vdr-1.7.18 works normally. > > How to determine where problem is in 1.7.19 and how to fix it? > I can upload recording sample somewhere if it helps. > > br, > A > > > > > ------------------------------ > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > End of vdr Digest, Vol 77, Issue 29 > *********************************** Exact same problem in Oz with several channels. Mike [View Less]

1 0

ATSC Channel frequency crashing VDR
by Rob Davis 24 Jun '11

24 Jun '11

Hi Guys, I have two ATSC adapter. On one I scan my channels, create my channels.conf file (via a convoluted script), the channels work on that laptop using 1.6. I make a couple of edits to allow it to work on 1.7.12, but a particular frequency causes VDR to crash and get restarted by the watchdog.. The offending frequency is 567000, It's a Qam256 ATSC Cable frequency. I have an HVR1850 PCI-E adapter. Unfortunetly, it's the mux with all my local SD channels, although I can watch the HD ones, … [View More]

4 17

TT S2-6400 - high bandwidthperformance.
by Richard Scobie 20 Jun '11

20 Jun '11

The original AV711X based "full featured", DVB-S cards have a well known internal bandwidth limitation, that could be addressed by performing the "budget patch" modification to the card. Does anyone know if the same or similar limitation applies to the new S2-6400 card - better, worse or similar performance? Regards, Richard

1 0

vdr-1.7.18 with S2-6400 OSD oops
by Chris Mayo 18 Jun '11

18 Jun '11

I'm getting a repeated (but not frequent or reproducible) oops that occurs when the OSD is already displayed and I do more OSD operations (quickly?). Recently the oopses have been written to syslog (because of some of the newer patches or firmware?) and I have attached one. This is my current set-up (I have had these oops all my time with the S2-6400 but this matches the attachment). Apologies if the problem is because of the way I have got things working. HW: 2 x Nova DVB-T 1 x S2-6400 … [View More]

1 0

How can I add custom information to the EPG?
by John Klimek 16 Jun '11

16 Jun '11

My provider sends EEPG information containing information such as "Original Air Date" and "Episode ID". I think I can add the neccessary DVB descriptors the code but where should I add this in the epg.data file? Does anybody have any information or advice on this? My goal is to use the epgsearch plugin with this extra data to record "new" episodes (ie. never before aired), etc.

4 5

cppcheck: VDR 1.7.18: [timers.c:53]: (error) snprintf size is out of bounds
by Paul Menzel 15 Jun '11

15 Jun '11

Dear VDR folks, Cppcheck 1.49 [1] reports the following error when run against VDR 1.7.18. [timers.c:53]: (error) snprintf size is out of bounds Looking at `timers.c` in `CTimer` `*file = 0` and afterward written to if I am not mistaken. […] cTimer::cTimer(bool Instant, bool Pause, cChannel *Channel) { startTime = stopTime = 0; lastSetEvent = 0; recording = pending = inVpsMargin = false; flags = tfNone; if (Instant) … [View More]

4 4

cppcheck: VDR 1.7.18: [recording.c:1130]: (error) Allocation with UpdateFileName, TouchFile doesn't release it.
by Paul Menzel 15 Jun '11

15 Jun '11

Dear VDR folks, using Cppcheck 1.49 [1] to check VDR 1.7.18 the above error is shown. Unfortunately I do not know how to fix this. The following methods are the following (from two files). void cRecordings::TouchUpdate(void) { bool needsUpdate = NeedsUpdate(); TouchFile(UpdateFileName()); if (!needsUpdate) lastUpdate = time(NULL); // make sure we don't tigger ourselves } const char *cRecordings::UpdateFileName(void) … [View More]

2 1

egyjo@lovete.ro
by Füley István 15 Jun '11

15 Jun '11

Szia, ezt a laptopot tudnám ajánlani: Asus X52JU-SX244D - kijelző 15.6 ColorShine HD (1366x768) LCD - processzor INTEL Core i3 350M (2.26 GHz, cache 3 MB, FSB MHz) - memória 2+1 GB DDR3 (1066 MHz) - HDD 500 GB 5400 rpm - videókártya AMD Radeon HD 6370 (512 MB GDDR3) - hálózat Gigabit, b/g/n - DVD-író - webcam 0.3 MP - 2 év garancia 2160.- RON áfástól köszi, Füley István

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2011