Hi!
Am 02/12/2015 um 03:38 PM schrieb René:
[...]
I have finally got time to migrate xineliboutput to softhddevice, but
Just for the curious: Why did you move from xineliboutput to
softhddevice? Are there any major advantages?
From my experience the client-/server-setup (vdr-sxfe) of xinel
Am 15.02.2015 um 07:57 schrieb cedric.dew...@telfort.nl:
>
>> 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
>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
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
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
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
> 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
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.
On 13.02.2015 00:02, René wrote:
On 12.02.2015 17:27, VDR User wrote:
Rather than treating a symptom, why not try to figure out the root
cause of your freezing and address it there?
That is of course the best solution, but i still would prefer an option to
reload/restart a frontend instead of
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. Hopefully a sequence of SUSP and RESU after a
fr
Am 13.02.2015 um 00:02 schrieb René:
On 12.02.2015 17:27, VDR User wrote:
Rather than treating a symptom, why not try to figure out the root
cause of your freezing and address it there?
That is of course the best solution, but i still would prefer an option
to reload/restart a frontend instead
On 12.02.2015 17:27, VDR User wrote:
Rather than treating a symptom, why not try to figure out the root
cause of your freezing and address it there?
That is of course the best solution, but i still would prefer an option
to reload/restart a frontend instead of having to restart vdr..
René
Rather than treating a symptom, why not try to figure out the root
cause of your freezing and address it there?
On Thu, Feb 12, 2015 at 6:38 AM, René wrote:
> Hi,
>
> First of all i want to thank Klaus for VDR. Vdr has been now "part of my
> life" for roughly 10 years, and i can't imagine myself
13 matches
Mail list logo
