vdr November 2010

vdr@linuxtv.org

59 participants
41 discussions

VDR & Multiple frontends
by Eddi 25 Jul '15

25 Jul '15

Hi, I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use multiple frontend. So I get: /dev/dvb/adapter0/demux0 /dev/dvb/adapter0/demux1 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/dvr1 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/net1 The bus of the two frontend is shared, isn't possible to get access to both frontend simultaneously, so I get an -EBUSY error by trying accessing frontend1 if frontend0 is in use. VDR doesn't support yet the second frontend, and it try to get exclusive access on both frontend on start, so the second frontend is inusabile. Vdr should probe for multiple frontend at start, and access frontend only on channel change. Please can someone give me an help to wrote a patch for this issue? Best Regards, Eddi

4 21

vdr xine-lib eac3
by zaverel 10 Jul '12

10 Jul '12

hello your second patch doesn't work : no sound on eac3 channel if you want there is a sample of vdr hd-eac3 recording here: http://dl.free.fr/ew4rJddM8 103mo else , i don't know what mailing-list is the more indicate for debuging the vdr or xine-dev mailing-list ?

7 38

[ANNOUNCE] noad-0.7.1
by the Noad 01 May '12

01 May '12

Hi, there is a new version of noad at http://noad.heliohost.org This Version handles also TS-Recordings. Greetings theNoad

7 10

VDR-1.7.16 doesn't respect valid dvb device frequency ranges
by Andreas Brachold 03 Mar '12

03 Mar '12

Hello, Any current vdr doesn't respect valid dvb device frequency ranges. Here on a EPG-Scan it's generate many messages on syslog, like : DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) DVB: adapter 0 frontend 0 frequency 177500000 out of range (470000000..860000000) Any of my three DVB-T devices have different frequency ranges, and the primary device can't receive VHF-channels. frontend 0:0 frequency range 470000000..860000000 frontend 1:0 frequency range 51000000..858000000 frontend 2:0 frequency range 177000000..858000000 Therefore i attach a simple patch to check provided frequency ranges of used dvb-t device driver. Andreas

2 1

[ANNOUNCE] vdr-pvrinput
by L. Hanisch 17 Sep '11

17 Sep '11

Hi all, The plugin for integrating analog MPEG2 cards by Hauppauge (et al.) into the vdr has a new home. http://projects.vdr-developer.org/projects/show/plg-pvrinput It's adapted to the latest changes of vdr (>= 1.7.13). For older versions the plugin-param-patch is still needed. Take a look at the README to adjust your channels.conf to the matching syntax of your vdr. http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/README http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/HISTORY I think, it's stable enough to be tested by you. :-) Use the new home page for documenting bugs you encounter. A short changelog: - the generated TS now contains valid PAT, PMT and PCR packets so streaming with streamdev-server now works in TS mode. The used PIDs are the same as in the TS of cx18 cards, so the vdr will not alter them in mixed environments. vpid: 301+101=2 ; apid: 300 ; tpid: 305 - the Hauppauge HD PVR is now supported but uses different PIDs as the cx18/ivtv cards. vpid: 4113+4097=27 ; apid: 0;4352 - for radio channels no more video packets are sent. If you use a PVR350 as output device make sure you have a recent version of the pvr350-plugin which generates black video on its own. - if you use a PVRUSB2 make sure you have the latest driver otherwise you can see occasionally no picture after a channel switch. The corresponding patch of pvrusb2 will be integrated in kernel 2.6.34. - if you experience stuttering video on switching channels you can tweak some buffers with some parameters in the setup.conf (stop your vdr before editing, of course) pvrinput.ReadBufferSizeKB = 64 // size of buffer for reader in KB (default: 64 KB) pvrinput.TsBufferSizeMB = 3 // ring buffer size in MB (default: 3 MB) pvrinput.TsBufferPrefillRatio = 0 // wait with delivering packets to vdr till buffer is filled up to x% If the default values don't make you happy, please report working values for your setup. Please report also your used input and output devices. The latest versions of w_pvrscan and wirbelscan supports the new vdr 1.7.13 syntax if you don't want to change your channels.conf by hand. http://wirbel.htpc-forum.de/w_pvrscan/index2.html http://wirbel.htpc-forum.de/wirbelscan/index2.html Here's the announcement in the vdr-portal: http://www.vdr-portal.de/board/thread.php?threadid=95389 Have fun! Lars.

2 4

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, two channels don't have HD versions.. I can't see anything in dmesg or the vdr log which causes a problem. As an aside, a scan using w_scan to create a kaffeine channels.conf file on that adapter, doesn't find anything on that frequency. Am I getting interference from something? Any ideas?

4 17

[Patch] Make RGYB buttons customizeable
by Oliver Schinagl 07 Apr '11

07 Apr '11

Hey all, Ever had the trouble that your remote's color navigation key weren't the same as VDR's? Well I wrote this patch the past 4 hours which lets you configure them. By doing so, the order of the buttons in the menu changes depending on whatever you tell it to. So finally that remote can match whatever is displayed on screen. This only works for the classic and st-tng skins, as those are supplied with VDR. The Skin needs to support this feature. If there is no skin support, the setting simply gets ignored by that skin. Since only the order of the buttons in the skin are being changed any plugin configuration will be independent from this change. What I mean is that, when a plugin has configured blue to take you straight to the photo gallery, the blue button will still do this, no matter where it is on the remote. If the plugin however used the blue key to fast forward, because it is the right most key, and thus made sense logically there, it will no longer when you move the keys around. Practically, this will boil down to a handful of plugins depending on location which imo is a little weird anyway :) Also, I patched it on a Gentoo box using the latest 1.6 ebuild they have so line numbers may be a little off in the patch due to various patches Gentoo may apply. It's the only dev. box for VDR I have so forgive me on that. I'm looking forward to the review :) Oliver

6 27

priorities in streamdev
by Rainer Blickle 13 Mar '11

13 Mar '11

Hi everybody, i have a question regarding the streamdev plugin. I have 2 tv cards, both gets accessed with the pvrinput plugin, but the problem i have would be the same with dvb devices. I also watch TV on the PC with the two cards. I have another pc (laptop) with vdr installed. There i installed the streamdev-client plugin. When switching the channel on the laptop with the up/down keys, the live picture gets interrupted with a black screen for about half a second. My wife doesn't like this very much. I had a look into the source code and found following: - The receiver of the pc has the priority 0, the receiver of the streamdev-server 1. - When switching with the up/down keys, the streamdev-client sends an "PROV"-Message to the streamdev-server. The streamdev-server tries to get a device (Method cServerConnection::GetDevice). The Receiver of the "old" streamdev-channel is still receiving. - The Method cServerConnection::GetDevice calls cDevice::GetDevice. The priority in the function call is 1. In the cDevice::GetDevice method the devices gets iterated, calling on each device the method cDevice::ProvidesChannel. Because the priority property of this call is 1, the "old" receiver of the streamdev-server has also a priority of 1 and the live-receiver has the priority of 0, the only device which can provide the channel is the device of the live-tv. - In the latter of the method cDevice::GetDevice the live-receiver gets detached via "d->DetachAllReceivers". Later in the code of cServerConnection::GetDevice, if the Method cDevice::GetDevice doesn't return a device, the current receiver gets detached. In my infrastructure this doesnt happend because the live receiver will nearly always gets detached ( The only exception is when a timer records). To prevent this, i changed the code in that way that the streamdev-receiver gets detached before calling cDevice::GetDevice). Is the detaching of live-tv an known issue or is this a feature ? Should have the live tv receiver a priority greather than streamdev-receiver ? If so, the live-tv wouldn't get detached ? Regards, Rainer

6 20

Include Path in Makefile (VDR >=1.7.15)
by Joachim Wilke 29 Dec '10

29 Dec '10

I'm just wondering, if there has happened a mistake in updating the Makefile in VDR 1.7.15. The HISTORY file states: "Include paths are now added instead of overwriting INCLUDES in the Makefile" However, in the Makefile changes: -INCLUDES = -I/usr/include/freetype2 +INCLUDES ?= -I/usr/include/freetype2 Shouldn't that be += instead of ?=. In my case, my IDE sets INCLUDES with some custom stuff. Therefore the Makefile does not touch INCLUDES any more and I get an error. -- Best Regards, Joachim.

4 6

CAM auto resetting - feature request??
by Simon Baxter 27 Dec '10

27 Dec '10

Hello My v 1.6.0 system has 2x Alphacrypt multi-CAMs. Occasionally one of the CAMs seems to "crash" and if I go into Setup > CAM one of the CAMs changes from "Alphacrypt" to "CAM Ready" - and will no longer decrypt channels. I then correspondingly get a bunch of timer conflicts, as 1/2 my CAM resources have vanished. Only ever one CAM fails, never both. I rectify this by selecting the CAM, and then hitting "reset" (sometimes a couple of times) - and it comes back. Unless I go into the Setup > CAM menu, I'm unaware that the CAM has "crashed". My request is...... Is there a way I can either 1)Automatically reset a CAM if it falls into this state or 2)Be notified, by generating a console/kernel message, so I can know to come in and fix this. Any ideas?

7 20

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2010