vdr

vdr@linuxtv.org

2 participants
6731 discussions

Patch to put disk usage back in main & recording menus (vdr-1.7.28) for text2skin/anthra
by VDR User 24 Jun '12

24 Jun '12

Hi. I was wondering if anyone has a patch that puts the disk usage back into the title of the main & recording menus when using the anthra (anthra_1920_OSE to be exact) with text2skin? After the following change in vdr, there's no way to know how much free space is on my recording drive without manually checking outside of vdr, and that's very inconvenient. - The disk usage is no longer automatically added to the title of the main and "Recordings" menus. This has always been a mekeshift solution and it is now up to the individual skin if, where and how it wants to display this information. A skin can use the new cVideoDiskUsage class to implement such a display. For compatibility, the default skins "Classic VDR", "ST:TNG Panels" and "Text mode" (i.e. curses) have been changed to behave like before. Other skins may want to display the disk usage in totally different ways. Thanks

2 2

Plugin for MHEG (BBC RedButton service)
by John Williams 21 Jun '12

21 Jun '12

Hello, I have adapted the standalone "redbutton" program (http://redbutton.sourceforge.net/) into a plugin for VDR. This allows me to view the "Redbutton" data service broadcast by the BBC. This is a preliminary version of the plugin and it is not robust enough for general use, but if anyone would like to experiment with it, the source code can be downloaded from http://pond-weed.com/redbutton/ Regards, John Williams

6 8

Collecting semantic channel meta data in a way to be useful for VDR
by Henning Pingel 18 Jun '12

18 Jun '12

Hi, I posted in the discussion "RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C" yesterday and mentioned that my little project Channelpedia could be helpful in this regard. But because my approach is more targeting the necessary semantic meta data that would be necessary for those advanced features, I would like to explain my ideas in a different thread. When I started to work on Channelpedia my goal was to offer a website where different VDR channel lists of different DVB providers could be easily stored, sorted and regularly updated in an easy way. The main audience were new VDR users who often are overwhelmed by the amount of channels offered by their DVB source (in particular satellite sources). Technically, Channelpedia is a PHP web application that uses a sqlite database and offers to upload channel data and retreive channel data in different ways (static generated HTML pages + a small RESTful JSON interface). Channelpedia is not a VDR addon and not a VDR plugin. The coding is completely independet from VDR and it can't be plugged into VDR in any way. Now that there are a couple of different DVB providers in the Channelpedia database, I thought it would make sense to additionally collect semantic meta data for channels in a provider independent way. This semantic data can be gathered and stored in Channelpedia, but in the end it should be easily exportable from Channelpedia. For example in a single textfile, so that this textfile could be used by VDR plugins (or even VDR core) for lookups. The basic idea is that this textfile has a certain structure (could also be XML or JSON) and that anybody could create this data file by typing it all down manually. But Channelpedia on the other hand could create this file in an automated way so that it is rarely necessary to maintain that file manually. At this time, Channelpedia collects some of this meta data only for channels relevant for German language countries (due to the amount of work involved I have limited it to German channels for now). I will now give an example of the kind of metadata I would like to collect per channel: All this metadata below is not specific to one single DVB provider. Instead it should be usable for any provider (C,T,S,I,...) that offers the respective channel. * Country/countries where the organization is based that offers the channel (problems might arise with cooperations: 3sat is a joint effort of Germany, Austria, Switzerland) * Primary region of the audience: Where does the indended audience live? Which language do they speak? * Website URI of the channel (Wikipedia page of this channel + the website of the organization) * Type of channel (Kids entertainment, Music, Crime, Sport, ....) * Channel logo resources for this channel that can be found on the web * List of existing EPG web services (that offer an XML based epg for this channel) * Existing channel variants with the completely the same or nearly the same epg: - Time-shift-versions (+1, +2, +24): List of other channels that have the same epg but a timeshift offset - Regional variants (BBC 1 London, BBC 1 Oxford, ... / WDR Aachen, WDR Köln, WDR ....): List of other channels that share 95% of the EPG but have "regional windows" - Quality/Bandwidth variants (SD, HD, different bitrates, DVB-T offers less quality in Germany compared to SD via DVB-C/S): List of channel alternatives that offer a higher or lower picture quality) - Reference to root channel (the "root" channel is the predecessor of all other variants) * CA-status: This channel regularly changes from FTA to scrambled or is permanently scrambled. * Which pay-TV packages / platforms have got this channel in their portfolio To store all this metadata for a channel, the channel needs a unique ID that is different from the technical unique ID that VDR uses internally (Source-NID-TID-SID, for a more detailed explanation of this ID please read VDR man page). The technical IDs of VDR are only used to identify a channel within the channels.conf of one VDR user and his active DVB providers. But we need IDs that are able to identify channels across different providers. Therefore we have to make them up ourselves, based on their channel name. I want to call them Channelpedia IDs for now - short: CPID, to make it easier to talk about them. But the NID-TID and SID still remain very important. If we put all the NID-TID-SID data into the metadata too, we can use them to automatically assign a channel in a channels.conf to a CPID. Regarding German channels, the DVB-C sometimes reuse the same NID-TID-SID of the channel on satellite. This means that we can hope that we don't have to store as many variants of NID-TID-SID in the metadata as there are providers out there. I guess this metadata collection can never be complete or completely accurate, but even if it doesn't contain all those channels out there it could still be very helpful for VDR plugins. Example: I create a searchtimer using epgsearch and epgsearch is able to look up all channel siblings in my local channels.conf that share the same EPG with the channel that I have currently selected. Now, epgsearch could give me choices: "Do you want to record the HD version of this channel? Is SD quality good enought? etc." Further infos: <http://channelpedia.yavdr.com/> Demos: <http://channelpedia.yavdr.com/gen/de_uniqueIDs2.html> <http://channelpedia.yavdr.com/gen/de_uniqueIDs.html> (JSON files available for auto-assignment) German language thread: <http://www.vdr-portal.de/board1-news/board2-vdr-news/111607-announce-entwur…> Regards, Henning

2 2

RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C
by Ludi 18 Jun '12

18 Jun '12

Hello, Some time ago, I started a discussion in german on the VDR forum about making the VDR more friendly for users that are simultaneously using different sources to receive channels: http://www.vdr-portal.de/board16-video-disk-recorder/board8-vdr-grundlagen/… I am going to explain the problem, when receiving channels from two different sources by using the second german public channel named ZDF: Suppose a user is receiving the channel ZDF by dvb-s and dvb-t. For the VDR, these are two different channels, and it probably is not a bad thing that the VDR differentiates between them because these channels might be of different quality (different data rates, etc.). However, as both sources name these channels often the same way, it is not easily possible to differentiate between the two channels in the VDR OSD, which is particularly annoying for the timers, one of the main VDR features. Currently, I work around this problem, by setting the VDR to not update channelnames and manually adding a suffix to the channelnames in the channels.conf. So, to use the example above and differentiate between the two channels, they could be renamed to ZDF-s and ZDF-t (or ZDF.s and ZDF.t, or...). In practice, I only only rename the channelnames of the source with the smallest number of channels; I know that the channelnames without suffix are those from the other source. @ Klaus Do you think that you could add an additional option to one of your next VDR releases, like "Add suffix about source to channelnames"; I could imagine such an option next to the "Update channels" option in the DVB section of the Setup in the OSD of the VDR. Since the information is already in the channels.conf for every channel, I assume, that it will not require huge changes to the VDR code to use channelnames-source (or something similar) instead of only the channelname in the channelname field of the channels.conf, when the corresponding option is active. In case, I am missing something, I would also like to ask everybody reading this to let us know, if for any reason, the idea about replacing the channelnames with channelname-source cannot work. There are of course also other solutions, like adding a system to the VDR allowing the user to indicate to the VDR, that both ZDF channels (to continue with the example above) are only variations of the same channel; the VDR could thus only show one of the two channels in his channellist (hd channels could also be seen as another variation of the channel); a priority system would be required to indicate what variation of the channel to use for recordings,... Restarting the discussion about how to best handle the simultaneous reception of more than one source is on my ToDo list since I started that thread in the german forum. Unfortunately, I did not have the time to do it until now, and probably will not have the time to do it seriously in the near future. Moreover, since I got the idea about simply adding the information about the source to the string of the channelname, I decided to ask for it, instead of waiting for something, that would probably require a long time to get designed and implemented. Cheers, Ludi

11 32

Re: [vdr] RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C
by Martin 17 Jun '12

17 Jun '12

And what about adding the satellite position to the source name? Martin 2012/6/17 <vdr-request(a)linuxtv.org> > 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 it is more specific > than "Re: Contents of vdr digest..." > > > Today's Topics: > > 1. Re: RFE: Make VDR more friendly when using combinations of > DVB-S, DVB-T and DVB-C (Klaus Schmidinger) > 2. Re: RFE: Make VDR more friendly when using combinations of > DVB-S, DVB-T and DVB-C (Klaus Schmidinger) > 3. Re: RFE: Make VDR more friendly when using combinations of > DVB-S, DVB-T and DVB-C (Luca Olivetti) > 4. Re: RFE: Make VDR more friendly when using combinations of > DVB-S, DVB-T and DVB-C (Ludi) > 5. Re: RFE: Make VDR more friendly when using combinations of > DVB-S, DVB-T and DVB-C (Klaus Schmidinger) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 17 Jun 2012 12:48:20 +0200 > From: Klaus Schmidinger <Klaus.Schmidinger(a)tvdr.de> > To: vdr(a)linuxtv.org > Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations > of DVB-S, DVB-T and DVB-C > Message-ID: <4FDDB5F4.8040109(a)tvdr.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 17.06.2012 00:13, Marx wrote: > > I use VDR mainly via www frontends, but I agree that there is need to > tell VDR what to do with channels from different tuners. For example > detection of recordings collision doesn't take into account that channels > are from two different sources (two different tuners). It also doesn't > understand that > > it's possible to record simultanoesly from the same transponder. Vdr > itself allow for all of it, but module which analyse collisions should be > much more flexible. We also sometimes have the same channels in SD and HD > which has different name but they differ only in quality. > > I can imagine that it should be easily possible to teach colision > detection module that some devices can record at once, also that it's > possible to record multiple streams form the same transponder. > > But it would be also great if we could virtually join some channels and > tell recording module that they are the same channel, so they for example > share EPG (it's possible now via plugins, I know). It should be possible to > tell which one should be picked at first if we record from such virtual > > channel. Collision module should advice for example "record from SD > version of channel because it's on the same transponder that second > recording we have planned" or "move this recording from DVB-S card to DVB-T > card because DVB-S card records at the same time from another channel". > > I can give example: polish channel TVP 1 is available from Hotbird as > (1) SD version, (2) HD version. It's also available in DVB-T as (3) SD > version and (4) HD version. I have this channel also available in (5) old > good analogue version. It's probably also available from Astra, and from > local > > provider of DVB-C. > > The core VDR doesn't have these features, yet, but I'm planning on looking > into these after version 2.0. > > Klaus > > > > ------------------------------ > > Message: 2 > Date: Sun, 17 Jun 2012 12:50:59 +0200 > From: Klaus Schmidinger <Klaus.Schmidinger(a)tvdr.de> > To: vdr(a)linuxtv.org > Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations > of DVB-S, DVB-T and DVB-C > Message-ID: <4FDDB693.1020803(a)tvdr.de> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 17.06.2012 09:26, VDR User wrote: > > On Sat, Jun 16, 2012 at 11:47 PM, Henning Pingel > > <henning(a)henningpingel.de> wrote: > >> Hi, > >> > >> As some of you might already know, I'm working on a way to > >> semi-automatically assign unique channel IDs to channels of different > DVB > >> providers. As I currently don't have time to explain it in detail > today, I > >> will just post some links and join this discussion later on when I have > more > >> time to sit down and explain stuff. ;-) > > > > Why not just patch VDR so it cycles through channels that use the same > > channel number. No bothering with sql databases& dependency, no > > altering the real channel numbers, no real pain that I can think of. > > For example, say you have 3 different sources using the same channel > > number: > > > > channel 100, dvb-s > > channel 100, dvb-t > > channel 100, dvb-c > > > > You tune channel 100 from your remote, it tunes 100 dvb-s. Press 100 > > again and it tunes 100 dvb-t. And again, 100 dvb-c. And again, loop > > back to 100 dvb-s. Also, instead of having to enter the channel number > > to cycle through them, maybe just use different keys (skip +/-, > > ffw/rew, some other keys) to cycle. If there's only one of that > > channel number, the cycle keys don't do anything. > > > > I like this idea far better than adding an sql dependency to VDR and I > > see no reason why the above would be difficult to implement or use. If > > I'm missing something, please let me know. > > Well, first of all: there will be no SQL dependency in the core VDR ;-) > > Once version 2.0 is finished, I'm planning on dealing with the "same > channel > from multiple sources" problem. > > Klaus > > > > ------------------------------ > > Message: 3 > Date: Sun, 17 Jun 2012 13:09:24 +0200 > From: Luca Olivetti <luca(a)ventoso.org> > To: VDR Mailing List <vdr(a)linuxtv.org> > Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations > of DVB-S, DVB-T and DVB-C > Message-ID: <4FDDBAE4.2090105(a)ventoso.org> > Content-Type: text/plain; charset=ISO-8859-1 > > Al 17/06/12 12:50, En/na Klaus Schmidinger ha escrit: > > > Well, first of all: there will be no SQL dependency in the core VDR ;-) > > That's a pity, because channels.conf would be a perfect candidate for > being an sqlite table. > (Note that I said "sqlite", not "sql", but since sqlite uses sql it would > allow for the more adventurous to substitute it for an heavy-weight > database like postgresql or mysql). > Bye > -- > Luca > > > > ------------------------------ > > Message: 4 > Date: Sun, 17 Jun 2012 14:00:39 +0200 > From: Ludi <ludi113(a)hotmail.com> > To: VDR Mailing List <vdr(a)linuxtv.org> > Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations > of DVB-S, DVB-T and DVB-C > Message-ID: <BLU0-SMTP3102EF5DC657CF686CD410E8F90(a)phx.gbl> > Content-Type: text/plain; charset="US-ASCII" > > On Sun, 17 Jun 2012 12:44:06 +0300 > Tony Houghton <h(a)realh.co.uk> wrote: > > > I think having VDR (optionally) show something like "(T)"/"(S)" next > > to the names is the best idea, but I also like the idea that it > > somehow understands that they can be considered as identical. > > That was the core of my idea: let's simply enhance the names of the > channels with an indication to its source, so that people are able to > distinguish the source of the channels with the same name. This would > allow people with more than one source of reception to more easily > bridge the time until a full solution is available. > > And if the enhancement of the channelnames could be made in a place, > where also the plugins could see it without modifications to the > plugins, it would be even better. But I understand Klaus being > reluctant to change the names directly in the channels.conf. > > Cheers > > > > ------------------------------ > > Message: 5 > Date: Sun, 17 Jun 2012 14:16:53 +0200 > From: Klaus Schmidinger <Klaus.Schmidinger(a)tvdr.de> > To: vdr(a)linuxtv.org > Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations > of DVB-S, DVB-T and DVB-C > Message-ID: <4FDDCAB5.2030006(a)tvdr.de> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > On 16.06.2012 16:53, Ludi wrote: > > Hi Klaus, > > > > First of all, thanks for your reply and for taking the problem into > > account. > > > > On Sat, 16 Jun 2012 15:32:11 +0200 > > Klaus Schmidinger<Klaus.Schmidinger(a)tvdr.de> wrote: > > > >> On 15.06.2012 17:17, Ludi wrote: > >>> Hello, > >>> > >>> Some time ago, I started a discussion in german on the VDR forum > >>> about making the VDR more friendly for users that are > >>> simultaneously using different sources to receive channels: > >>> > http://www.vdr-portal.de/board16-video-disk-recorder/board8-vdr-grundlagen/… > >>> > >>> I am going to explain the problem, when receiving channels from two > >>> different sources by using the second german public channel named > >>> ZDF: > >>> > >>> Suppose a user is receiving the channel ZDF by dvb-s and dvb-t. For > >>> the VDR, these are two different channels, and it probably is not a > >>> bad thing that the VDR differentiates between them because these > >>> channels might be of different quality (different data rates, > >>> etc.). However, as both sources name these channels often the same > >>> way, it is not easily possible to differentiate between the two > >>> channels in the VDR OSD, which is particularly annoying for the > >>> timers, one of the main VDR features. > >>> > >>> Currently, I work around this problem, by setting the VDR to not > >>> update channelnames and manually adding a suffix to the > >>> channelnames in the channels.conf. So, to use the example above and > >>> differentiate between the two channels, they could be renamed to > >>> ZDF-s and ZDF-t (or ZDF.s and ZDF.t, or...). In practice, I only > >>> only rename the channelnames of the source with the smallest number > >>> of channels; I know that the channelnames without suffix are those > >>> from the other source. > >>> > >>> @ Klaus > >>> > >>> Do you think that you could add an additional option to one of your > >>> next VDR releases, like "Add suffix about source to channelnames"; I > >>> could imagine such an option next to the "Update channels" option in > >>> the DVB section of the Setup in the OSD of the VDR. > >>> > >>> Since the information is already in the channels.conf for every > >>> channel, I assume, that it will not require huge changes to the VDR > >>> code to use channelnames-source (or something similar) instead of > >>> only the channelname in the channelname field of the channels.conf, > >>> when the corresponding option is active. > >> > >> I'd rather have the channels.conf entries keep the names that are > >> broadcast in the SI data. I wouldn't want to add a "source" suffix > >> there. > > > > I understand your concerns. > > > > I assumed that changing the names in the channels.conf would be the > > best in order to make also the plugins and other software use the > > names+source for free. Moreover, since the channels.conf can be > > constantly updated, I thought that it would not really matter, because > > the names without source could be restored in the channels.conf by > > simply disabling the new option and configure the update setting to > > also modify the channelnames. I was not aware that there was a > > standard for the broadcasting of the channelnames; but it does not > > surprise me either now. > > > >> However, I could imagine adding a function like > >> > >> cString cChannel::NameWithSource(void) > >> > >> which would return things like > >> > >> ZDF (DVB-T) > >> ZDF (DVB-S) > >> > >> or, shorter, > >> > >> ZDF (T) > >> ZDF (S) > >> > >> and using that function instead of the Name() function at the > >> appropriate places. > > > > If I get you right, that means that if the user activates the new option > > (I assume that you will make it optional, since most people > > probably use only one source and do not have the problem), the VDR uses > > the NameWithSource() method instead of the Name() method. > > > > But what does this mean for the plugins? I am particularly thinking at > > the plugins related to the timers, like the epgsearch and the live > > plugin. Will they have to be adapted or will they also show the > > name+source if the new option is enabled? > > > > Concerning whether to use the longer or the shorter version of the > > name+source, I would choose the shorter version to not increase chances > > of the new name not fitting in the OSD. Thus: > > > > ZDF (S) > > ZDF (T) > > ZDF (C) > > After sleeping over this for a night I tend to follow your idea of using > modifed > names directly, thus having them appear everywhere. > > I won't change these names in channels.conf, though (this file shall always > store what comes from the broadcaster - provided it is enabled in the > setup). > I'll rather > > - Make a setup option to "Show channel names with source" (default is > "no"). > - Modify cChannel::Name() and cChannel::ShortName() to optionally > append the source character (A, C, S, T, I, ...) to the channel name > in the (short) form mentioned above. > > The attached patch implements this (i18n stuff left out for brevity). > Please give it a try. > > @Ludi: BTW: in order to give you credit in VDR's HISTORY/CONTRIBUTORS file > I'll > need your full name. > > Klaus >

1 0

How to make bug report
by Marx 15 Jun '12

15 Jun '12

Hello I have four DVB cards: DVB-S2: -Pinnacle PCTV SAT HDTV 452E PRO USB (main kernel support) -Terratec Cinergy S2 USB HD v.2 -Prof Revolution DVB-S2 8000 PCIe DVB-T: -AF9015 noname USB (main kernel support) on AMD Brazos platform (Asrock E350M1) with Debian (lately with 3.4 kernel). While I could be able to make all of them working via different drivers (media-build, patches, vendor drivers, Igor Liplianin's repo, yavdr dkms package etc) none of this card works stable (unlike Twinhan PCI I had previously). Prof hangs system, Pinnacle doesn't work with DVB-S2, Terratec records streams partially unplayable, AF9015 stops working after and hour or so etc. Often I see errors of I2C subsystem. While I'm in process of testing it on different hardware (laptop) I would like to know if it's good place to write about dvb drivers bugs. Or maybe should I write directly to developer? or write bugs in Debian/kernel bugzilla or sth similair? How to properly report bugs? What kernel should I use, which driverset? What logs to attach (kernel.log)? how to enable debug options (if needed)? I think it's rather unusual all of cards doesn't work, so I suspect that there can be something wrong with my system. Maybe you, as skilled developers, can direct me what can be wrong, what can I test? Marx

1 0

VDR 1.7.28, xineliboutput 1.0.7: Using local frontend gives `No protocol specified`
by Paul Menzel 15 Jun '12

15 Jun '12

Dear VDR folks, somehow I am not able to get the local frontend to work. Debian Sid/unstable is installed with $ dpkg -l vdr vdr-plugin-xineliboutput libxineliboutput-sxfe […] ii libxineliboutput-sxfe 1.0.7+cvs20120609.1902-1 Local X-Server frontend for the xineliboutput plugin ii vdr 1.7.28-1 Video Disk Recorder for DVB cards ii vdr-plugin-xineliboutput 1.0.7+cvs20120609.1902-1 VDR plugin for Xine based sofdevice frontends and I try to get the local frontend working but it fails. $ sudo -u vdr vdr -P"xineliboutput --local=sxfe --video=auto --audio=alsa --remote=none" No protocol specified No protocol specified No protocol specified Unfortunately I do not know what the problem is as this is the command mentioned in `README` of `xineliboutput`. Usage examples (VDR plugin) If no arguments are given, both X11 and framebuffer frontends are tried. First working frontend is used with best available video driver. Complete list of available command-line arguments can be obtained with "vdr --help". Only local frontend, X11/Xv video, alsa audio: vdr -P"xineliboutput --local=sxfe --video=xv --audio=alsa --remote=none" Thanks, Paul

2 2

Skystar USB HD + VDR + Astra 23.5E 11817 V / 8psk,fec=5/6
by N. D. 13 Jun '12

13 Jun '12

Hi, Since recently I have been using Skystar USB HD with my vdr box. However I have some strange issues with 11817V on Astra 23.5E. Femon reports that there is a lock and sound comes but the image is completely garbled. I am starting to suspect that there might be something wrong with the driver, because I have no trouble with the other transpoders. Maybe it is the combination of fec=5/6 and 8psk on the said transponder that is the reason for this. Other transponders with fec=3/4 and 8psk are OK. The same setup with an HVR-4000 works fine. Kernel: 3.3.4 VDR: 1.7.27 Could someone who owns a Skystar USB HD and has access to Astra 23.5E share his experience? Is this a driver issue a problem with vdr or is my card faulty? If someone would be kind enough to test this with his/hers hardware, there is a FTA channel on the problematic transponder: Planeta HD;SatelliteBG:11817:VC56M5O35S1:S23.5E:27500:1001=27:1002=@3:0:0:5410:3:3206:0 Any help would be greatly appreciated. ----------------------------------------------------------------- Гражданска отговорност – Цените на компаниите http://www.sdi.bg/onlineInsurance/?utm_source=gbg&utm_medium=txtLink&utm_co…

2 1

VDR tuning
by Marx 11 Jun '12

11 Jun '12

What can be wrong if I can tune chanel with szap, but I can't it watch via streamdev because VDR can't tune it? Is it driver fault? Marx

5 11

dvbdevice.c
by Wolfgang Rohdewald 09 Jun '12

09 Jun '12

in vdr-1.7.28 without patches while browsing the log I found Jun 9 05:28:08 server vdr: [13569] frontend 1/0 timed out while tuning to channel 1877, tp 212713 Jun 9 05:28:40 server vdr: [13569] frontend 1/0 regained lock on channel 14, tp 110743 so frontend 1 regained a lock it never had. That seems like a consequence of the fact that LostLock is only a local variable in cDvbTuner::Action, so it cannot be reset when the channel changes also, I wonder about this code sequence in dvbdevice.c: switch (tunerStatus) { ... case tsLocked: if (Status & FE_REINIT) { ... else if (tunerStatus == tsLocked) { at the "else if", how could tunerStatus not be tsLocked? -- Wolfgang

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr