Am 13.02.2015 um 01:28 schrieb René:
>
> On 13.02.2015 01:22, Joerg Riechardt wrote:
>> start softhddevice suspended: ./vdr -P'softhddevice -g 1920x1080 -s'
>> resume softhddevice: svdrpsend plug softhddevice RESU suspend again:
>> svdrpsend plug softhddevice SUSP Jörg
> Thanks! I'll try this out.
Hi,
I am trying to setup my new vdr using an intel hd graphic device.
Could you please post a working config for xineliboutput?
MfG.
Halim
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> At yavdr we use this feature to start X and vdr in parallel and attach
> softhddevice when X is ready.
> And you can restart X when softhddevice is detached.
Do you happen to know approx. how much startup time is saved doing this?
___
vdr mailing l
On 14.02.2015 19:53, VDR User wrote:
>> At yavdr we use this feature to start X and vdr in parallel and attach
>> softhddevice when X is ready.
>> And you can restart X when softhddevice is detached.
>
> Do you happen to know approx. how much startup time is saved doing this?
Another case wher
14.02.2015 23:17, Lucian Muresan kirjutas:
On 14.02.2015 19:53, VDR User wrote:
At yavdr we use this feature to start X and vdr in parallel and attach
softhddevice when X is ready.
And you can restart X when softhddevice is detached.
Do you happen to know approx. how much startup time is
Am 14.02.2015 um 19:53 schrieb VDR User:
>> At yavdr we use this feature to start X and vdr in parallel and attach
>> softhddevice when X is ready.
>> And you can restart X when softhddevice is detached.
> Do you happen to know approx. how much startup time is saved doing this?
>
We have no time
>We have no times for this isolated feature of starting X and vdr
>parallel, because we do more.
>We don't use lircd, but eventlircd, because eventlircd has not to wait
>until the remote devices are ready, so the vdr don't need to wait for
>them too.
>Many current dvb tuners need long time to get
