Re: [vdr] Impact in cDevice::GetDevice
> This impact algorithm has evolved over time and is a very fragile thing.
Looks like only people have very deep insight in this algorithm should
change it.
> For alternate channel, wouldn't it be better to try all possible
> channels one after the other until one succeeds? I would not expect
> GetDevice to return a device for a different channel than requested.
I have two different solutions in mind.
The first one:
Modify the cDevice::GetDevice method. It returns a device able to
provide the same "semantic" channel as requested ("semantic channel" =
channel with the same programme).
Modify the cDevice::SetChannel method. If the requested channel
couldn't be provided by the device, the method will try to provide the
configured alternatives one.
Pros: The user have the epg and the original channel number on the osd
Cons: Modifies the methods in an unexpected way. Plugins and other
parts of the vdr doesn't work anymore.
The second one:
When pressing CH+/- or selecting an channel directly (via 0-9) and the
selected channel is not available, switch the channel explicit to an
alternative one. (explicit = also display the channel number and the
epg of the alternative channel).
Pros: After switching to the new channel, the vdr is in a clean and
consitent state.
Cons: The vdr has switched to complete another channel when using CH+/-.
Checking for timer conflicts won't work correctly in both ways
(without changes), because this algorithm doesn't know about
alternative channels. But it would be much easier to implement this
when using the second approach.
Cheers, Rainer
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video & audio, etc.
>> If you can find a modeline what your output is currently using you can >> use online services to check framerates it provides. > "xvidtune -show" prints the current modeline, but the refresh rate > calculated from it will not be the same as the actual rate. My used modeline is (1080p60) $ xvidtune -show -display :0.0 "1920x1080" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Which compiles to 60Hz output on theory level at epanorama calculator. If it is 60.001Hz because of clock Inaccuracies the TV will synch to it, no problem. As I use my VDR's X-output only for TV-based web browsing with randon youtube/vimeo. However I am now at office, so I cannot use "get-edid" to read all modelines TV is announcing for PAL-modes/timings. And how Nvidia is altering the proposed timigs as horizontal synchs must be at multitude of 8 (so you cannot have f.ex resolution 1924x1080). - Jori smime.p7s Description: S/MIME cryptographic signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Impact in cDevice::GetDevice
Am 24.08.2010 07:57, schrieb Rainer Blickle: > in the method cDevice::GetDevice the device with the least impact is > searched (the block with "imp <<= x; imp |= "). For calculating the > impact (higher value = bigger impact) some "facts" are used. The most > prio fact is "prefer the primary device for live viewing", the least > prio is "prefer CAMs that are known to decrypt this channel". > > Does anyone know why the facts are ordered in this way ? This impact algorithm has evolved over time and is a very fragile thing. Its quite difficult to oversee all consequences these rules have, and they're not completely bug-free either, see for example [1] and [2]. Part of the problem is that the whole priority system is not very consequent: Live view on primary devices leaves the device with 0 receivers attached like its unused, live view transferring to output devices has priority -1 but is treated like priority Setup.PrimaryLimit, re-tuning live-view to a different channel disconnects a stream with same priority while timers cannot disconnect streams with same priority, and so on. I think, if my proposed change [2] gets applied, some of the impact rules may be even superfluous, but I'm not very sure. In the end, changes to the impact algorithm often resulted in unexpected side effects in the past. For alternate channel, wouldn't it be better to try all possible channels one after the other until one succeeds? I would not expect GetDevice to return a device for a different channel than requested. Cheers, udo [1] http://www.linuxtv.org/pipermail/vdr/2010-July/023202.html [2] http://projects.vdr-developer.org/issues/show/10 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Automatic shutdown / restart of VDR
Am 24.08.2010 12:10, schrieb Lari Tuononen: > I've managed to get the waking-up working properly, and also so that > VDR will shutdown at night after the last timer has stopped, but if > there is a timer in the morning and it wakes computer up, VDR also > shuts down the computer, which is something I do not want. If a shutdown command is provided, and MinUserInactivity is set to 0, then VDR will never switch to non-interactive mode by itself, and thus never shuts down automatically. It does however allow to manually shut down. If VDR then wakes up close to a timer, it starts non-interactive, stays in that mode until the end of the timer, and shuts down again. The user can switch to interactive (by any key press) or to non-interactive (by pressing power button once). You want two different things: A timer ending 'at night' should shut down VDR, a timer ending 'at day' should keep VDR running, even if there's no sign of user interaction. Possible solutions: - Abort the shutdown script at day time (your distro may provide some hook script mechanism) - If VDR wakes up at daytime, issue a harmless key press via svdrp to switch to interactive. - Maybe some plugin like the exec plugin can be used to modify the behavior of VDR. Plugins generally have the possibility to keep VDR awake at certain times (like, for example, the whole day) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VGA2SCART: circuit diagram with audio pins
On Tue, 24 Aug 2010 16:07:43 +0200 Matthias Fechner wrote: > wow, that are interesting news. > Does it means I can buy a Atom board with an ION2 chip on it and can use > the VGA connector to connect my old TV till I buy a new LCD and use then > HDMI? It depends on whether the Ion2 can generate the modelines you need. You'll have to check around for that. I expect most people buying new hardware like this would already have an LCD TV by now, so the info could be hard to find :-(. -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VGA2SCART: circuit diagram with audio pins
Hi List, Am 23.08.10 15:26, schrieb Tony Houghton: [1] http://crashme.cx/vdr-portal-picts/VGA_SCART_RGB_NEWER.png wow, that are interesting news. Does it means I can buy a Atom board with an ION2 chip on it and can use the VGA connector to connect my old TV till I buy a new LCD and use then HDMI? Bye, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
I tried the patch with git plugin, now it works fine.. I'll try it with your version later. :) 2010/8/24 Ville Skyttä : > If you do, be sure to test the vdr-dxr3-0-2 branch, and see if you need to > apply patches/vdr-dxr3subtitlehack.patch to your VDR. You may also want to > check if that patch/hack has any effect on subtitles when used with the git > version of the plugin. -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Automatic shutdown / restart of VDR
Hi! I've been trying to play with different settings around nvram-wakeup and vdr. My idea of the working setup would be: * VDR will shut down the computer ONLY when it is told so with the power-key (so VDR will continue recording if there is a timer active or coming in next few hours) * VDR will wake up if timer is to record and computer shut down * VDR will not shutdown automatically I've managed to get the waking-up working properly, and also so that VDR will shutdown at night after the last timer has stopped, but if there is a timer in the morning and it wakes computer up, VDR also shuts down the computer, which is something I do not want. Settings in setup.conf: MinEventTimeout = 120 MinUserInactivity = 0 So the question is: Which settings should I have to get the functionality I like? Best Regards, Lari Tuononen ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
On Tuesday 24 August 2010, Luca Olivetti wrote: > En/na Teemu Suikki ha escrit: > > OSD is working 100% except for the subtitles. To me it looks like it > > is the subtitle font rendering that is bugged, sometimes you can see > > "unfilled" letters where there's only the white outline and inside is > > transparent.. This might be VDR bug actually, I have no idea where the > > rendering takes place? > > You could try the cvs version from sourceforge If you do, be sure to test the vdr-dxr3-0-2 branch, and see if you need to apply patches/vdr-dxr3subtitlehack.patch to your VDR. You may also want to check if that patch/hack has any effect on subtitles when used with the git version of the plugin. A known problem currently in the vdr-dxr3-0-2 branch at least when used with VDR 1.6.0-2 (haven't tested 1.7.x versions) is that DVB subtitles appear too early. I plan to do something about that (this was discussed on the dxr3 plugin mailing list) and then release 0.2.11. > (though I don't know if > Ville committed the latest changes I made, which, IIRC, showed a message > for h264 encoded channels). Yep, that's in. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
En/na Teemu Suikki ha escrit: OSD is working 100% except for the subtitles. To me it looks like it is the subtitle font rendering that is bugged, sometimes you can see "unfilled" letters where there's only the white outline and inside is transparent.. This might be VDR bug actually, I have no idea where the rendering takes place? You could try the cvs version from sourceforge (though I don't know if Ville committed the latest changes I made, which, IIRC, showed a message for h264 encoded channels). Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
Ah so the muted digital audio is normal then. :) I'm moving this VDR machine to different room anyway, where I will be using analog audio, so no real problem there. OSD is working 100% except for the subtitles. To me it looks like it is the subtitle font rendering that is bugged, sometimes you can see "unfilled" letters where there's only the white outline and inside is transparent.. This might be VDR bug actually, I have no idea where the rendering takes place? -- Teemu Suikki http://www.z-power.fi/ its waiting in my local git > repository. I hope I can find some hours this week > to commit patches and improve some broken stuff. > > I think it would be also a good idea to start some unit testing to fix > broken OSD outputs. This would improve the situation much > more, as the OSD is quite a complex construct and I could close some > open bugs in the tracker. > > Alsa output does not support digital audio at the moment... but I will > bring back OSS - which supports digital and analog output. > > greets > -- > Christian Gmeiner, MSc > > > > 2010/8/24 Teemu Suikki : >> Hi, >> >> thanks a bunch! This looks a lot more promising now. I have perfect >> picture and OSD, but there is no sound? >> >> It might be due to the fact that this new dxr3 plugin seems to use >> ALSA? My older installation used OSS. I'm using the digital audio >> output, I have nothing in the analog outputs so I can't be sure if >> it's outputing something there. But I have selected "digital output" >> in dxr3 plugin setup. >> >> Also subtitles seem to bug a little, there's a lot of garbage on top >> of the text, and sometimes the texts appear in top left corner, not in >> bottom like they should. >> >> -- >> Teemu Suikki >> http://www.z-power.fi/ >> >> .4.5 and dxr3plugin 0.2.6 for years now, with no real problems. For some reason I decided to try the recent versions. :) VDR 1.7.15 and dxr3plugin 0.2.10. >>> >>> Did you choose the buffer-and-sync-rewrite branch [1]? It's working >>> fine for me with vdr-1.7.15. >>> >>> >>> >>> - jan >>> >>> [1] >>> http://projects.vdr-developer.org/projects/plg-dxr3/repository/show?rev=buffer-and-sync-rewrite >>> >>> ___ >>> vdr mailing list >>> vdr@linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >>> >>> >> >> >> >> -- >> Teemu Suikki >> http://www.z-power.fi/ >> >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
Hi, thanks for your feedback - I have some commits waiting in my local git repository. I hope I can find some hours this week to commit patches and improve some broken stuff. I think it would be also a good idea to start some unit testing to fix broken OSD outputs. This would improve the situation much more, as the OSD is quite a complex construct and I could close some open bugs in the tracker. Alsa output does not support digital audio at the moment... but I will bring back OSS - which supports digital and analog output. greets -- Christian Gmeiner, MSc 2010/8/24 Teemu Suikki : > Hi, > > thanks a bunch! This looks a lot more promising now. I have perfect > picture and OSD, but there is no sound? > > It might be due to the fact that this new dxr3 plugin seems to use > ALSA? My older installation used OSS. I'm using the digital audio > output, I have nothing in the analog outputs so I can't be sure if > it's outputing something there. But I have selected "digital output" > in dxr3 plugin setup. > > Also subtitles seem to bug a little, there's a lot of garbage on top > of the text, and sometimes the texts appear in top left corner, not in > bottom like they should. > > -- > Teemu Suikki > http://www.z-power.fi/ > > .4.5 and dxr3plugin 0.2.6 >>> for years now, with no real problems. For some reason I decided to try >>> the recent versions. :) VDR 1.7.15 and dxr3plugin 0.2.10. >> >> Did you choose the buffer-and-sync-rewrite branch [1]? It's working >> fine for me with vdr-1.7.15. >> >> >> >> - jan >> >> [1] >> http://projects.vdr-developer.org/projects/plg-dxr3/repository/show?rev=buffer-and-sync-rewrite >> >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> >> > > > > -- > Teemu Suikki > http://www.z-power.fi/ > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Impact in cDevice::GetDevice
Good Morning, >From what I recall of discussions held on this list the reasons are based on, >in no particular order :), First - initial basic common sense then an iterative process involving - satisfaction of common corner use cases - satisfaction of problem use cases - keeping most people happy most of the time - keeping some people happy some of the time i.e. a can of worms. I am sure others can provide a more insightful technical response. Ian. On 24 Aug 2010, at 06:57, Rainer Blickle wrote: > Hi, > > in the method cDevice::GetDevice the device with the least impact is > searched (the block with "imp <<= x; imp |= "). For calculating the > impact (higher value = bigger impact) some "facts" are used. The most > prio fact is "prefer the primary device for live viewing", the least > prio is "prefer CAMs that are known to decrypt this channel". > > Does anyone know why the facts are ordered in this way ? > > Why ?: > > At the moment i'm developing a patch providing alternative channels. > An alternative channel is a channel providing the same programme as > the original channel, but with another receiving technique (like DVB-T > instead of DVB-C). My alternative technique is analoge (via pvrinput). > For this, i introduced a new fact "programme is received from an > alternative channel". Therefor i have to define the priority of this > new fact regarding the impact. So i'd like to know more why the prio > is as it is. > > Regards, Rainer > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
Hi, thanks a bunch! This looks a lot more promising now. I have perfect picture and OSD, but there is no sound? It might be due to the fact that this new dxr3 plugin seems to use ALSA? My older installation used OSS. I'm using the digital audio output, I have nothing in the analog outputs so I can't be sure if it's outputing something there. But I have selected "digital output" in dxr3 plugin setup. Also subtitles seem to bug a little, there's a lot of garbage on top of the text, and sometimes the texts appear in top left corner, not in bottom like they should. -- Teemu Suikki http://www.z-power.fi/ .4.5 and dxr3plugin 0.2.6 >> for years now, with no real problems. For some reason I decided to try >> the recent versions. :) VDR 1.7.15 and dxr3plugin 0.2.10. > > Did you choose the buffer-and-sync-rewrite branch [1]? It's working > fine for me with vdr-1.7.15. > > > > - jan > > [1] > http://projects.vdr-developer.org/projects/plg-dxr3/repository/show?rev=buffer-and-sync-rewrite > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
