Hi,
Torgeir Veimo wrote:
> Sorry for the noise.. Reattaching to the screen instance I instantly
> realized that the cause was an erroneous video out parameter..
why not using mplayer.sh?
It is a shell script that has some additional features.
Bye,
Matthias
--
"Programming today is a race bet
On 6 Oct 2008, at 23:41, Torgeir Veimo wrote:
> /usr/bin/screen -dmS vdr /usr/local/bin/runvdr 2>&1 >| /tmp/
> vdrlog.txt &
Sorry for the noise.. Reattaching to the screen instance I instantly
realized that the cause was an erroneous video out parameter..
--
Torgeir Veimo
[EMAIL PROTECTED]
On 6 Oct 2008, at 19:00, André Weidemann wrote:
> Hi,
>
> Torgeir Veimo wrote:
>> The mplayer plugin doesn't work when I start vdr from inittab. It
>> works ok if vdr is started from the console.
>>
>> I've seen hints that $USER and $HOME need to be set, but setting
>> these
>> in my startup sc
Hi,
Torgeir Veimo wrote:
> The mplayer plugin doesn't work when I start vdr from inittab. It
> works ok if vdr is started from the console.
>
> I've seen hints that $USER and $HOME need to be set, but setting these
> in my startup script doesn't change anything.. Anyone got any idea
> what'
En/na Torgeir Veimo ha escrit:
> The mplayer plugin doesn't work when I start vdr from inittab. It
> works ok if vdr is started from the console.
Maybe it needs a console to work?
I side stepped the problem by running vdr inside a screen session, so it
has a console and I can attach to it when
The mplayer plugin doesn't work when I start vdr from inittab. It
works ok if vdr is started from the console.
I've seen hints that $USER and $HOME need to be set, but setting these
in my startup script doesn't change anything.. Anyone got any idea
what's missing?
Also, it would be an idea
