Firstly, thanks for your replies ;-)
On Wed, 2003-04-02 at 23:39, [EMAIL PROTECTED] wrote:
> so for each button on youre remote you'll get something like this in lircrc
> begin
> prog = freevo (obvious)
> button = REMOTE_UP (see /etc/lirc/lircd.conf)
> config = UP (see above, I don't know other commands
> there are)
> end
I had done this using the convert script, however there seems to be 2
errors which had potential to break it..
Firstly, I had left some links empty, so the freevo expect (config) had
a field but the button feild was blank, like this:
begin
prog = freevo
button =
config = UP
end
It looks like this is invalid, if your not using it, leave it out..
Then I had some that looked like this, one that were #'ed out in the
remote.py file ended up this way after the script..
begin
prog = freevo
button = # 1
config = 1
end
This seemed to break it also..
And lastly, to those of you out there trying this to,
If the script creates any buttons that freevo doesn't use (for me it was
Aux1) delete this from the lircrc file also, just to be safe ;-)
So yes, now I too have lirc working for freevo YAY! Next step is to get
mplayer commands working.. From what i've read in the config files, once
mplayer is running, the buttons can be remmapped to do mplayer things
right? Like RIGHT could be mapped to ff? Does anyone have a cheatsheed
of commands that mplayer recieves? I'm sure they'll be in the docs if
not..
Cheers,
Mick
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
