vdr November 2011

vdr@linuxtv.org

37 participants
45 discussions

Re: [vdr] VDR and Hybrid DVB Cards ( was "HVR 4000 drivers broken - adapter0/frontend1 busy" in linux-media list )
by ian_and_joanna＠talktalk.net 15 Nov '11

15 Nov '11

Hi, I am an HVR4000 owner too. Re: VDR internals I'm no expert but the basic assumption is that all devices are available at all time. This assumption has implications for e.g. timers, epg scans, multi-clients etc. This assumption breaks with the HVR4000. Basic use to watch one channel at a time with VDR switching between T and S devices as appropriate is the most simple case. But a corner case considering wider use-cases of VDR. Practical advice Get a dedicated T or S receiver to be able to receive T and S with vanilla VDR. To exercise the HVR4000 re: integration of multi-frontends may involve a long wait for development. Existing patches There had been some work a while ago reported in this forum (search this forum for something like 'multi frontends'), don't know current status. Regards, Ian. Sent from my HTC ----- Reply message ----- From: "Steffen Barszus" <steffenbpunkt(a)googlemail.com> Date: Tue, Nov 15, 2011 10:52 Subject: [vdr] VDR and Hybrid DVB Cards ( was "HVR 4000 drivers broken - adapter0/frontend1 busy" in linux-media list ) To: "VDR Mailing List" <vdr(a)linuxtv.org> 2011/11/15 Hawes, Mark <MARK.HAWES(a)au.fujitsu.com>: >>What i got from previous discussions on linux-media is, that if the >> device nodes are created within one adapter, an application needs to >> assume that >> the devices can not be used concurrently and needs to close >> one "device node group" before opening the other one. >> > This suggests a constraint in the current design of the way VDR handles > the detection and use of DVB devices in that it cannot handle so called > 'hybrid' cards where two (or more!) frontends are attached via a single > adaptor without restarting VDR and identifying which frontend to use. > > As already mentioned I wish to use both cards on my system and I'd be > interested and happy to help in developing a patch to overcome this > constraint. However I would need some VDR architectural guidance to > suggest how this might be done with minimal disruption to the current > DVB device handling. Any direction would be much appreciated. What i said above is AFAIK more or less undocumented up to now. But it seems to be a consensus between most driver developers now. Yes vdr needs to change to handle this devices properly based on the previous assumptions, i think soneone else can be more helpful than me ;). _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

2 1

vdr-xine-plugin and LATM AAC
by Luis Fernandes 15 Nov '11

15 Nov '11

hello, is there a patch for vdr-xine-plugin to do the repack LATM AAC audio as e-ac3 patch. xine-lib-1.2 already supports and works very well in my recordings with LATM HE-AAC but not live tv. how can I do a debug, has changed on vdr172remux.c / / Set this to 'true' for debug output: DebugPatPmt static bool = true; but does not report anything unusual, just send the audio as an MPEG audio layer 2 (lib: MAD) for xine-ui. just see this: [v] VMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMAMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMbuffered -214.2 frames (v:111.4, a:-214.2) <<<<< DiscontinuityDetected: triggering soft start [v] VMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMAbuffered 56.6 frames (v:86.4, a:56.6) MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMbuffered -35.6 frames (v:146.0, a:-35.6) <<<<< DiscontinuityDetected: triggering soft start [VM] MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMAMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMbuffered 105.9 frames (v:243.7, a:105.9) <<<<< DiscontinuityDetected: triggering soft start best regards

1 0

VDR logs and logwatch
by Kartsa 14 Nov '11

14 Nov '11

Hi Has anyone built a script for logwatch to get VDR messages from the logs? I am not familiar with perl which is mostly used with logwatch scripts. I assume it is possible to use any other language as well but thought that I would ask here if anyone has already a solution :) \\Kartsa

3 6

femon request; historic data
by Torgeir Veimo 13 Nov '11

13 Nov '11

Am wondering if it would be hard to enhance the femon plugin to show a graph of signal quality and correction statistics? Basically, a histogram with STR, SNR, BER and UNC, so that one doesn't have to oogle the screen constantly to see how signal quality changes. Even better if it was possible to trigger such monitoring without the femon display showing. -- -Tor

3 2

No output via xineliboutput with VDR 1.7.21
by Chris Rankin 12 Nov '11

12 Nov '11

> Do you get the red "No Signal" text on black background? No, I get the "xine" splash screen instead. Sometimes with the VDR OSD on it... I am using xine-1.1, BTW. Perhaps this is relevant? > And as someone also suggested, make sure you have xineliboutput set as your > primary device in Settings/DVB. The value should be the amount of your > dvb devices + 1. OK, I'm assuming that you're talking about /etc/vdr/setup.conf here. And although I have PrimaryDVB = 2 in this file, I don't see how this can be seen as setting xineliboutput as my primary device. My xineliboutput configuration is: xineliboutput.Audio.Compression = 100 xineliboutput.Audio.Delay = 0 xineliboutput.Audio.Headphone = 0 xineliboutput.Audio.SoftwareVolumeControl = 0 xineliboutput.Audio.Speakers = Stereo 2.1 xineliboutput.Audio.Surround = 0 xineliboutput.Audio.Upmix = 0 xineliboutput.Audio.Visualization = goom xineliboutput.Audio.Visualization.GoomOpts = width=720,height=576,fps=25 xineliboutput.Decoder.PesBuffers = 250 Cheers, Chris P.S. Can you also CC any reply to me, please? Otherwise my mail client is going to start a new thread on the VDR list.

1 0

No output via xineliboutput with VDR 1.7.21
by Chris Rankin 10 Nov '11

10 Nov '11

> Please see the xineliboutput README for examples on using xine-ui with xineliboutput. > Both vdr-sxfe and xine-ui can act as a front-end to xineliboutput. Not any more though, it would seem. Perhaps xineliboutput has not been maintained? Cheers, Chris

2 1

Re: [vdr] No output via xineliboutput with VDR 1.7.21
by Chris Rankin 10 Nov '11

10 Nov '11

> you must have an output "xineplug_inp_xvdr.so" then, you can play using > xine cmd line: > > xine xvdr://127.0.0.1:37890 FYI, I have been successfully using xineliboutput *for years* with VDR 1.6.x. The *only reason* I felt this worth reporting to the mailing list is because it has all stopped working after upgrading to VDR 1.7.x. YES, I have the xvdr plugin! $ ls -als /usr/local/lib/xine/plugins/1.29/*vdr* 460 -rwxr-xr-x 1 root root 463196 Nov 7 23:29 /usr/local/lib/xine/plugins/1.29/xineplug_inp_xvdr.so Geez! Cheers, Chris

3 2

[PATCH] for cards like Cine-C/T with multiple frontends but only one shared demux/dvr
by L. Hanisch 09 Nov '11

09 Nov '11

Hi, Since the driver doesn't allow to create only the frontend of the desired delivery type, here's a patch for cDvbDevice. If there's no demux/dvr device with the frontend number it looks for one with a lower number. Now it's possible to use "-D 0" for DVB-C or "-D 1" for DVB-T (change device numbers to your setup). Of course the dynamite-plugin can also be used. Just set "dynamite_attach=no" at the unwanted frontend with a udev rule (please look at the dynamite README). It's not really tested, since I have not such a card, but the patch is almost trivial. Feedback is welcome. I hope the dvb/v4l developers will someday agree on a standard layout for hybrid tuners... Regards, Lars.

1 0

vdr-sxfe can't connect
by Damien Bally 09 Nov '11

09 Nov '11

Hello Vdr is launched in the background, but vdr-sxfe can't connect : [1142] [input_vdr] Connecting (control) to tcp://127.0.0.1:37890 ... [1142] [input_vdr] Server not replying [1142] [input_vdr] Can't connect to tcp://127.0.0.1:37890 [1142] [input_vdr] Connections closed. [1142] [vdr-fe] fe_xine_open: xine_open("xvdr://127.0.0.1#nocache") failed Error opening xvdr://127.0.0.1 /var/log/messages seems OK : Nov 5 22:32:09 vdrbox user.err vdr: [1105] starting plugin: xineliboutput Nov 5 22:32:09 vdrbox user.err vdr: [1111] Remote decoder/display server (cXinelibServer) thread started (pid=1105, tid=1111) Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [xine..put] Have CAP_SYS_NICE capability Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Nov 5 22:32:09 vdrbox user.info vdr: [1111] [xine..put] Listening on port 37890 Nov 5 22:32:09 vdrbox user.info vdr: [1111] [xine..put] Listening for UDP broadcasts on port 37890 Nov 5 22:32:09 vdrbox user.debug vdr: [1111] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0^M Server port: 37890^M Server version: xi neliboutput-1.0.90-cvs^M ^M Nov 5 22:32:09 vdrbox user.debug vdr: [1105] [xine..put] cXinelibDevice::StartDevice(): Device started I checked with netstat : vdrbox:/# netstat -nptl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1003/vsftpd tcp 2 0 0.0.0.0:37890 0.0.0.0:* LISTEN 1105/vdr tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1120/X tcp 0 0 :::22 :::* LISTEN 1002/dropbear tcp 0 0 :::6000 :::* LISTEN 1120/X What am I missing ? Thanks for helping. Damien

6 10

No output via xineliboutput with VDR 1.7.21
by Chris Rankin 09 Nov '11

09 Nov '11

Hi, I have just tried installing VDR 1.7.21 (from Fedora RawHide), with the xineliboutput plugin from its git repository. I have managed to get xine to connect to VDR (I think - after I had added 127.0.0.1 to the allowed_hosts.conf file), but I am not receiving any output in the xine window. VDR seems to be processing events from my remote, and the channels all seem to have tuned in too - even the HD ones. But it's no good without either a picture or sound. Does anyone have any ideas, please? Thanks, Chris

4 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2011