vdr August 2008

vdr@linuxtv.org

53 participants
62 discussions

Recommended xine settings for Arte HD ?
by Gregoire Favre 13 Sep '08

13 Sep '08

Hello, I am a big fan of Arte, and I would like to watch it in HD. Aug 15 13:18:42 vdr vdr: [24729] receiver on device 2 thread started (pid=3246, tid=24729) Aug 15 13:18:42 vdr vdr: [24730] TS buffer on device 2 thread started (pid=3246, tid=24730) Aug 15 13:18:42 vdr vdr: [24728] cVideoRepacker: operating in H.264 mode Aug 15 13:19:08 vdr vdr: [24729] buffer usage: 70% (tid=24728) Aug 15 13:19:08 vdr vdr: [24729] buffer usage: 60% (tid=24728) Aug 15 13:19:08 vdr vdr: [24729] buffer usage: 70% (tid=24728) Aug 15 13:19:08 vdr vdr: [24729] buffer usage: 60% (tid=24728) Aug 15 13:19:08 vdr vdr: [24729] buffer usage: 70% (tid=24728) Aug 15 13:19:09 vdr vdr: [24729] buffer usage: 80% (tid=24728) Aug 15 13:19:10 vdr vdr: [24729] buffer usage: 90% (tid=24728) Aug 15 13:19:10 vdr vdr: [24728] clearing transfer buffer to avoid overflows Aug 15 13:19:10 vdr vdr: [24729] buffer usage: 0% (tid=24728) Aug 15 13:19:10 vdr vdr: [24728] TS continuity error (7) Aug 15 13:19:10 vdr vdr: [24728] TS continuity error (2) Aug 15 13:19:10 vdr vdr: [24728] TS continuity error (14) Aug 15 13:19:10 vdr vdr: [24728] cVideoRepacker: operating in H.264 mode How could I avoid those errors which make me loose the sound and have glitches ? In my .xine/config I have : audio.device.alsa_front_device:default engine.performance.memcpy_method:libc gui.dropped_frames_warning:0 gui.experience_level:Master of the known universe gui.panel_visible:0 gui.panel_x:700 gui.panel_y:550 .version:2 video.processing.ffmpeg_choose_speed_over_accuracy:1 video.processing.ffmpeg_skip_loop_filter:all video.processing.ffmpeg_thread_count:2 I use count 2 because I have a core 2 duo. grep -i xine /etc/vdr/setup.conf xine.autoPrimaryDeviceMode = autoPrimaryDeviceOn xine.image16:9.zoomX = 100 xine.image16:9.zoomY = 100 xine.image4:3.zoomX = 100 xine.image4:3.zoomY = 100 xine.interactWithEitScannerMode = interactWithEitScannerOff xine.modeLiveTV.monitoringDuration = 4 xine.modeLiveTV.monitoringMode = monitoringOnce xine.modeLiveTV.prebufferFrames = 6 xine.modeLiveTV.prebufferHysteresis = 6 xine.muteMode = muteIgnore xine.osdGammaCorrection = 123 xine.osdMode = osdBlendScaledHQ xine.transparencyMode = transparencyOn xine.volumeMode = volumeChangeHW And I start xine with : #!/bin/bash killall xine > /dev/null &> /dev/null killall -9 xine > /dev/null &> /dev/null #XINE="xine -V xxmc -A alsa --no-logo --borderless --geometry +0+0 --post vdr_video --post vdr_audio -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1" XINE="xine -V xv -A alsa -f --no-logo --geometry +0+0 --post vdr_video --post vdr_audio -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1" VDR="vdr:/var/vdr/xine/stream#demux:mpeg_pes" #VDR="vdr:/tmp/vdr-xine/stream#demux:mpeg_pes" if [ -z "$1" ]; then $XINE $VDR > /dev/null &> /dev/null & else $XINE $1 > /dev/null &> /dev/null & fi sleep 4 && sudo renice -18 -p `pidof xine` > /dev/null &> /dev/null & I have svn ffmpeg and hg xine-lib-1.2. Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre

7 30

vdr-1.5.18 subtitles issue
by matthieu castet 10 Sep '08

10 Sep '08

Hi, I tried subtitle features and I saw some problems (I am using vdr-1.5.18 with softdevice and streamdev). First auto channel update is need : there no way to save subtitle pid in channel.conf. I haven't info about this on the manual and it takes me some time how to make it works. Next osd behaviour is weird : as soon as subtitle is started, when it will refresh it will mess up with other osd. For example if I start subtitle and then go to the menu, the menu will be clear by subtitle refresh, but I am still in menu mode. Next, why like audio aren't there an entry in main menu for showing current subtitle tracks ? The only way to know that is to use keymacro with Subtiles key, but that could be hard to map it with remote with few keys. Finally I have the impression that the subtitles synchronisation isn't good. Thanks, Matthieu

5 8

new rolloff paramemter in channels.conf for vdr 1.7.0
by Goga777 07 Sep '08

07 Sep '08

Hi As Manu explained me it's not possible to set manually rolloff/FEC for stb0899. that's why I'm wondering - what for need the new roll off (parameter O) parameter in channels.conf ? Only for reading the current state of roll off in demod ? (0,35% is default for dvb-s/s2 BPSK, QPSK, 8PSK) Is work really ? Goga

2 2

Failed to read channels.conf after adding transponder
by Udo Richter 06 Sep '08

06 Sep '08

Hi Klaus & list, Today I had an unexpected parse error in my channels.conf, in this line: Test Feed;Test Feed:10920:hC56M2O0S0:S19.2E:22000:0:0:0:0:0:1:1063:0 The line was added by automatic transponder scan yesterday. The 'bug' of this channel is that the SID (4'th last) is 0, triggering tChannelID::Valid() to be false. By now, the channel is announced correctly like this: Test Feed;Test Feed:10920:hC56M2O0S0:S19.2E:22000:601:0:0:D02,1815:20351:1:1063:0 The core problem however is that the channel was added without completely checking validity first. Adding a check for Valid() to cChannels::NewChannel() probably solves this issue. (not tested) Until this is fixed, its probably a good idea to disable channel updates for VDR systems that run mostly un-monitored. (Holiday season is near!) Cheers, Udo

12 24

new dvb api ?
by Goga777 06 Sep '08

06 Sep '08

http://linuxtv.org/pipermail/linux-dvb/2008-August/028313.html

4 3

Re: [vdr] [linux-dvb] DVB-S2 / Multiproto and future modulation support
by Oliver Endriss 30 Aug '08

30 Aug '08

Steven Toth wrote: > Regarding the multiproto situation: > > A number of developers, maintainers and users are unhappy with the > multiproto situation, actually they've been unhappy for a considerable > amount of time. The linuxtv developer community (to some degree) is seen > as a joke and a bunch in-fighting people. Multiproto is a great > demonstration of this. [1] The multiproto project has gone too far, for > too long and no longer has any credibility in the eyes of many people. > > In response, a number developers have agreed that "enough is enough" and > "it's time to take a new direction", for these developers the technical, > political and personal cost of multiproto is too high. These developers > have decided to make an announcement. > > Mauro Chehab, Michael Krufky, Patrick Boettcher and myself are hereby > announcing that we no longer support multiproto and are forming a > smaller dedicated project group which is focusing on adding next > generation S2/ISDB-T/DVB-H/DVB-T2/DVB-SH support to the kernel through a > different and simpler API. > > Basic patches and demo code for this API is currently available here. > > http://www.steventoth.net/linux/s2 > > Does it even work? Yes > Is this new API complete? No > Is it perfect? No, we've already had feedback on structural and > namingspace changes that people would like to see. > Does it have bugs? Of course, we have a list of things we already know > we want to fix. > > but ... > > Is the new approach flexible? Yes, we're moving away from passing fixed > modulation structures into the kernel. > Can we add to it without breaking the future ABI when unforseen > modulations types occur? Yes > Does it preserve backwards compatibility? Yes > Importantly, is the overall direction correct? Yes > Does it impact existing frontend drivers? No. > What's the impact to dvb-core? Small. > What's the impact to application developers? None, unless an application > developer wants to support the new standards - binary compatibility! > > We want feedback and we want progress, we aim to achieve it. > > Importantly, this project group seeks your support. > > If you also feel frustrated by the multiproto situation and agree in > principle with this new approach, and the overall direction of the API > changes, then we welcome you and ask you to help us. > > Growing the list of supporting names by 100%, and allowing us to publish > your name on the public mailing list, would show the non-maintainer > development community that we recognize the problem and we're taking > steps to correct the problem. We want to make LinuxTV a perfect platform > for S2, ISDB-T and other advanced modulation types, without using the > multiproto patches. > > We're not asking you for technical help, although we'd like that :) , > we're just asking for your encouragement to move away from multiproto. > > If you feel that you want to support our movement then please help us by > acking this email. > > Regards - Steve, Mike, Patrick and Mauro. > > Acked-by: Patrick Boettcher <pb(a)linuxtv.org> > Acked-by: Michael Krufky <mkrufky(a)linuxtv.org> > Acked-by: Steven Toth <stoth(a)linuxtv.org> > Acked-by: Mauro Carvalho Chehab <mchehab(a)infradead.org> > > * [1]. Rather than point out the issues with multiproto here, take a > look at the patches and/or read the comments on the mailing lists. Guys, I don't like the way you do this. ;-( Why didn't you propose this API when we reviewed multiproto? Meanwhile there are applications (vdr, others?) which implement the multiproto API. As I am not willing to spend a single minute of my time with API wars, I will ack this API only if the multiproto developer and the users agree with this approach. Oliver -- ---------------------------------------------------------------- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ----------------------------------------------------------------

2 1

vdr-restarts after upgrade
by Oliver Joa 30 Aug '08

30 Aug '08

Hi, i recently upgraded my vdr to version 1.6.0. Now my vdr restarts every some minutes when recording: Aug 4 12:17:21 video1 vdr: [3688] frontend 1 timed out while tuning to channel 1, tp 111836 Aug 4 12:17:43 video1 vdr: [3694] ERROR: video data stream broken Sometimes it is working, and sometimes it restartes every minute. A friend of me had the same problem when recording ARD. He upgraded his kernel to 2.6.26 and now it works for him. I also tried 2.6.25.9 and 2.6.26.1, but it does not work. I don't think that it is a problem of temperature, because it also happens suddenly after cold startup. The system is running now for some years, with regular software-upgrades. I use Debian-Etch. Any Idea? Olli

6 8

how to find out the crash of vdr
by Goga777 30 Aug '08

30 Aug '08

Hi I have vdr 170 + cvs xineliboutput + external svn ffmpeg + hg xine-lib-1.2 during of watching some hdtv channels I have crash ffmpeg/xine-lib with this errors [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]B picture before any references, skipping [h264 @ 0x8706aa0]decode_slice_header error [h264 @ 0x8706aa0]no frame! [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]mmco: unref short failure [h264 @ 0x8706aa0]number of reference frames exceeds max (probably corrupt input), discarding one [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 1, 10.1, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 2, 22.2, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 2, 22.6, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 3, 38.5, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]warning: first frame is no keyframe vdr: osdflush: n: 1, 9.5, timeout: 0, result: 0 [h264 @ 0x8706aa0]warning: first frame is no keyframe [h264 @ 0x8706aa0]Internal error, picture buffer overflow Aborted How can I track this errors for good bug-report to ffmpeg developpers ? It's seems need to use the gdb. Is it right way ? http://xinehq.de/index.php/developer Q: How do I run xine in gdb? A: First make sure you have a debug build. You can either run xine from gdb or attach to an already-running process: Running xine from gdb: $ gdb xine (gdb) handle SIG32 noprint nostop (gdb) run Attaching to a running xine process: $ gdb xine `pidof xine`

1 0

[ANNOUNCE] vdr-sudoku-0.3.1
by Thomas Günther 30 Aug '08

30 Aug '08

Hi! There is a new version of the Sudoku plug-in. Download: http://toms-cafe.de/vdr/sudoku/vdr-sudoku-0.3.1.tgz Changes since version 0.3.0: - Corrected English language texts: Great font/digits -> Large font/digits (thanks to Ville Skyttä for reporting this). - Updated Finnish language texts (thanks to Ville Skyttä). - Updated Italian language texts (thanks to Diego Pierotto). This plug-in generates Number Place puzzles, so called Sudokus, and let you solve it. A Sudoku puzzle consists of 9 x 9 cells subdivided into 9 regions with 3 x 3 cells. The rules are simple. There have to be the numbers from 1 to 9 in every row, column and region. In the beginning some numbers are given. These cells are painted with cyan background color. The aim of the puzzle is to find the missing numbers. There is only one solution of a Sudoku puzzle. See the project's homepage for details: http://toms-cafe.de/vdr/sudoku/ Tom

1 0

two new open HDTV channels on Astra 19,2E
by Goga777 29 Aug '08

29 Aug '08

Simul HD;IRT:11361:hC23M5O35S1:S19.2E:22000:6410:6420=deu:0:0:11140:1:1011:0 EinsFestival HD;ARD:12422:HC34M2S0Z0:S19.2E:27500:11601+1601:1602:0:0:28396:1:1201:0

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr August 2008