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 ca

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 h

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 situatio

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

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 id

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

[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

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/

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

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

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

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 devic

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) $ x

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 > Ge