Hmm, it just occurred to me that perhaps Freevo is reading the joystick and sending mplayer commands, AND mplayer itself may be reading the joystick - and doing bad things. I'll have to investigate that a bit more. (Isn't it amazing how problems can be worked through by writing a rant to other people? ^_^)
Pin pon!! Didn't take long to fix. I needed to add -nojoystick to MPLAYER_ARGS_DEF in freevo_config.py, and all the weirdness went away. The PAUSE button even resumes, as well, so I don't need that bound PLAY button. ^_^
Perhaps this option should be used by default in Freevo, since it's a safe assumption that mplayer run from Freevo should be using Freevo's Joystick smarts, not its own?
I'd still like to see better analog stick functionality some time... ^_^
-- . Trevor Phillips - http://jurai.murdoch.edu.au/ . : Web Technical Administrator - [EMAIL PROTECTED] : | IT Services - Murdoch University | >--------------------------------------------------------------------< | On nights such as this, evil deeds are done. And good deeds, of / | course. But mostly evil, on the whole. / \ -- (Terry Pratchett, Wyrd Sisters) /
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
