vdr June 2010

vdr@linuxtv.org

58 participants
58 discussions

Re : vdr 1.7.10 no record channel
by Senufo 30 Jun '10

30 Jun '10

Hi, I read the ISO / IEC 13818-2: 1995 for trying to better understand how is the detection of I-frames. In Chapter 6.2 the header image will begin by picture_start_code in remux.c if (scan == 0x00000100) (/ / Picture Start Code If I understand the detection of the i-frame is in the picture_coding_type according to Table 6-12 picture_coding_type / coding method 000 / forbidden 001 / intra-coded (I) 010 / predictive-coded (P) 011 / bidirectionally-predictive-coded (B) 100 / Shall Not Be Used (dc intra-coded (D) in ISO/IEC11172- 2) 101 / reserved 110 / reserved 111 / reserved I do not understand this line of code: independentFrame = ((Data [i +2]>> 3) & 0x07) == 1 / / I-Frame thank you for your answers Regards Senufo On 05/19/10 22:20, Senufo wrote: > Hi, > > Thanks Klaus > Klaus I agree, but the video looks good because I can see this live > stream and when I use the patch records are correct. > I did a test with vdr 1.6.0 with the same channels.conf and there I can > see the live stream and recordings works. > > Why ? I have no idea. Of course, the whole frame detection is different in VDR 1.7. You might want to debug that area to see why it doesn't work any more. Simply changing that bit from '1' to '0' can't be the solution. Klaus > On 05.05.2010 22:11, Senufo wrote: > >> > Hi, >> > > I found the problem. VDR does not detect the frame independent in this >> > stream because in the function : >> > > cFrameDetector:: Analyze (const uchar * Data, int Length) >> > > in the file remux.c. >> > > ((Data [i +2]>> 3) & 0x07) is equal to 0 instead of 1 for stream >> that work. >> > > I applied this patch : >> > > --- remux.c 2010-05-04 14:55:50.000000000 +0200 >> > +++ remux.c.orig 2010-05-04 21:57:38.000000000 +0200 >> > @@ -960,6 +960,7 @@ >> > return Processed; // flush everything before this new frame >> > newFrame = true; >> > independentFrame = ((Data[i + 2] >> 3) & 0x07) == 1; // I-Frame >> > + if (((Data[i + 2] >> 3) & 0x07) == 0) { independentFrame = 1;} >> > if (synced) { >> > if (framesPerPayloadUnit <= 1) >> > scanning = false; >> > > and record is working again. >> > I do not know what has changed in the stream. >> > > I tested this patch since yesterday and so far I have not had any >> problems. >> > > What do you think? >> > > If this stream marks independent frames with '0' instead if '1', > I would say it is broken. > > Klaus

2 1

[Test] Release candidate streamdev-0.5.0-rc1
by Frank Schmirler 28 Jun '10

28 Jun '10

Hi there, I'm about to prepare streamdev releases 0.4.0 (final release for VDR-1.4) and 0.5.0 (for VDR-1.6/1.7). The 0.5.0 release will contain two larger changes which have not been commited to the main CVS branch yet. Maybe some of you want to review and comment on these. Get the tarball at http://streamdev.vdr-developer.org. @all: Please see chapter "Updating" in the README file which is part of the streamdev source distribution. The new version won't run out of the box. You will have to rename the config directory first! Those using externremux.sh will also have to modify their script. @package maintainers: Upon request I split up the language resources for streamdev-client and streamdev-server. Instead of one vdr-streamdev.mo you will now get a vdr-streamdev-server.mo and a vdr-streamdev-client.mo. Consistently the plugin configuration directory changed from streamdev to streamdev-server (there are no configuration files for streamdev-client yet). To build only one plugin, use "make client" or "make server" respectively. @externremux users: The remux script is now responsible for emitting HTTP headers. Make sure you update your script! In turn the script gets a CGI like environment which gives you access to request headers, context information and details on the channel. A new sample externremux.sh is included which makes heavy use of request parameters. To reflect these changes, the HTTP URL path for externremux changed from EXTERN to EXT. Enjoy, Frank

5 7

Does vdr buffer TS/PES packets intern
by Christian Gmeiner 28 Jun '10

28 Jun '10

Hi all, I am still working to improve the vdr-plg-dxr3 and I run into an issue. Lets say I watch TV but there is nothing interesting to watch, so I want to playback a recording. But this happens now in the plugin: Jun 28 11:52:46 vdr vdr: [4160] video pts 808983 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 830583 Jun 28 11:52:46 vdr vdr: [4160] video pts 852183 Jun 28 11:52:46 vdr vdr: [4160] video pts 852183 Jun 28 11:52:46 vdr vdr: [4160] video pts 852183 Jun 28 11:52:46 vdr vdr: [4160] video pts 852183 Jun 28 11:52:47 vdr vdr: [4160] video pts 852183 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4139] [dxr3-device] setting playmode 0 Jun 28 11:52:47 vdr vdr: [4139] audio enable 0 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr kernel: em8300-0: adjusting scr: 1032444 Jun 28 11:52:47 vdr vdr: [4139] replay /var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec Jun 28 11:52:47 vdr vdr: [4139] playing '/var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec/001.vdr' Jun 28 11:52:47 vdr vdr: [4139] loading /var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec//marks.vdr Jun 28 11:52:47 vdr vdr: [4139] [dxr3-device] setting playmode 1 Jun 28 11:52:47 vdr vdr: [4139] audio enable 1 Jun 28 11:52:47 vdr vdr: [4175] dvbplayer thread started (pid=4139, tid=4175) Jun 28 11:52:47 vdr vdr: [4175] resuming replay at index 6708 (0:04:28.09) Jun 28 11:52:47 vdr vdr: [4176] non blocking file reader thread started (pid=4139, tid=4176) Jun 28 11:52:47 vdr vdr: [4175] SetBrokenLink: no GOP header found in video packet Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] [dxr3-device] Poll Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] [dxr3-device] Poll Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] [dxr3-device] Poll Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] [dxr3-device] Poll Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] [dxr3-device] Poll Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] setting audio track to 1 (0) Jun 28 11:52:47 vdr vdr: [4175] [dxr3-audiodecoder] found new audio header Jun 28 11:52:47 vdr vdr: [4175] [dxr3-audiodecoder] calculated frame size 768 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts 1079487 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 Jun 28 11:52:47 vdr vdr: [4175] video pts -718037321 As you can see the video pts is for some time increasing to about 1079487. And then suddenly it changes to the correct value of the recording. I assume that vdr does the following: Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr vdr: [4139] [dxr3-device] setting playmode 0 Jun 28 11:52:47 vdr vdr: [4139] audio enable 0 Jun 28 11:52:47 vdr vdr: [4160] video pts 873783 Jun 28 11:52:47 vdr kernel: em8300-0: adjusting scr: 1032444 Jun 28 11:52:47 vdr vdr: [4139] replay /var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec Jun 28 11:52:47 vdr vdr: [4139] playing '/var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec/001.vdr' Jun 28 11:52:47 vdr vdr: [4139] loading /var/vdr/video/MTV_Live/2008-06-07.21.58.50.99.rec//marks.vdr Jun 28 11:52:47 vdr vdr: [4139] [dxr3-device] setting playmode 1 Jun 28 11:52:47 vdr vdr: [4139] audio enable 1 Jun 28 11:52:47 vdr vdr: [4175] dvbplayer thread started (pid=4139, tid=4175) Jun 28 11:52:47 vdr vdr: [4175] resuming replay at index 6708 (0:04:28.09) Jun 28 11:52:47 vdr vdr: [4176] non blocking file reader thread started (pid=4139, tid=4176) Jun 28 11:52:47 vdr vdr: [4175] SetBrokenLink: no GOP header found in video packet now there should not be any left over from the previous audio/video stream, but only the new data a pts value around -718037321. Is this a bug or a feature of VDR? thanks -- Christian Gmeiner, MSc

2 2

Re: [vdr] vdr 1.7.15 & eHD & French HD DTV
by ECLiPSE 27 Jun '10

27 Jun '10

I know that is not directly related to vdr, as my problem should come from the reel src and not vdr. I know there is here a good community of developpers and perhaps someone can look at the src of the hdplayer and see if it could be possible to add the detection of e-ac3 audio format , (and perhaps finding the way to decode it or at least enable the ac3 compatibility?). hdplayer3.tgz: http://depositfiles.com/files/wdprj8brd thx to the developers who will look at the src, for me it's chinese ECLiPSE

5 6

[ANNOUNCE] S2API wrapper patch 0.6
by Udo Richter 26 Jun '10

26 Jun '10

... or why two legs are better than one. Hi list. Due to some unexpected S2 capable hardware, there's a new version of my S2API wrapper patch available for download. The new version adds S2API auto-detection at runtime, so that one binary vdr executable can handle old DVB V3 drivers and DVB V5 (S2API) drivers without any changes. As before, the patch compiles fine against the old V3 header files and the new V5 header files, and even if vdr was compiled against V3 headers, the resulting vdr can still tune to S2 channels when using it with V5 capable drivers. As a fallback, the patched vdr understands the command line switches --dvbapi=3 and --dvbapi=5 to manually select the API to use. The patch applies to VDR from 1.7.13 at least up to 1.7.15. If there's any need for VDR versions 1.7.12 and earlier, contact me. Get it at: http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper Cheers, Udo

1 0

rotor
by Mike Booth 25 Jun '10

25 Jun '10

the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 (australian). Piece of cake. Or am I missing something? Mike

3 5

Dual DVB-S2 Tuner cards
by Theunis Potgieter 25 Jun '10

25 Jun '10

Hi guys, do any of you have information with regards to Dual DVB-S2 Tuners on a PCI or preferably a PCI-E type card working on vdr? I did have a look on http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards But only mentions 2 and they seem to be a rare find. Well at least where I live. Does anybody else know of working DVB-S2 cards for Linux? I did find plenty of Hybrid/Dual type cards but they seem to be supporting DVB-T + DVB-S/S2 and not even both at the same time :( Any advice would be appreciated. Thanks, Theunis

11 13

eepg plugin
by martinez 24 Jun '10

24 Jun '10

Anybody got the Digital+ epg on 19e working with eepg (or some other way offering more than NOW and NEXT)

1 0

Re: [vdr] Xine plugins and LATM AAC audio (was Re: vdr 1.7.15 & eHD & French HD DTV)
by Rolf Ahrenberg 23 Jun '10

23 Jun '10

On Wed, 23 Jun 2010, Luis Fernandes wrote: > and yes Femon 1.7.7 does not detect this audio codec, this one must be I've added a preliminary LATM parser to femon-1.7.8 that will be hopefully released tonight. BR, -- rofa

1 0

rotor screen missing stuff
by martinez 23 Jun '10

23 Jun '10

The plugin has been downgraded. There are people who use a patched and patched 0.1.4 rather than the official 0.1.5 The situation with the rotor plugin is so bad (so much patching needed to get it to work and then I found it makes vdr unstable) I've resorted to having two parallel installations of vdr one I use just for the rotor plugin when I need to use it to align the dish and store the positions. In my 'normal' vdr installation I don't use the rotor plugin but rather diseq commands 'Go to position X' Here is my diseqc.conf if it helps you: S19.2E 11700 V 9750 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 99999 V 10600 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S19.2E 11700 H 9750 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 99999 H 10600 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S13.0E 11700 V 9750 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 99999 V 10600 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S13.0E 11700 H 9750 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 99999 H 10600 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S28.2E 11700 V 9750 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 99999 V 10600 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.2E 11700 H 9750 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 99999 H 10600 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.5E 11700 V 9750 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 99999 V 10600 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T S28.5E 11700 H 9750 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 99999 H 10600 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T I guess it comes down to the hard truth that there is no vdr 1.7.x user with C programming skills using a rotor who needs something more than USALS 1.2 Message: 5 Date: Tue, 22 Jun 2010 19:12:16 -0700 From: "Timothy D. Lenz" <tlenz(a)vorgon.com> Subject: [vdr] rotor screen missing stuff To: vdr(a)linuxtv.org Message-ID: <4C216D80.2090500(a)vorgon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I am trying to get my rotor working again. I had been using v0.1.4 with vdr-1.6.0. Now I'm trying to get v.0.1.5 working with vdr-1.7.15. On the rotor page, Postion information no longer shows the sat it matches to, the option to do a scan on the current TP is gone, and the lock and other indicators are gone. Was that all part of the text2skin plugin which I'm not using now? or has the plugin been down graded?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr June 2010