Wow. Not sure how I missed that in my testing & setup. I guess that's sometimes the problem with thinking too much. Heh. As a work-around, I ended up using LP to call a script that conditionally killed kinamp or started it. I was happy with it.
After chopping all that down to a cd & a kinamp command, everything works fine.
So it appears that if kinamp is already running and you execute it, it quits regardless of any args you pass it. I should've known it would be so simple. Thanks again fbdev.
3 More questions.
Q1: Have you noticed any problems after using kinamp to pause mplayer for extended periods of time? From watching ps output for a spell, it seems to me like there's no cpu or RAM leakage, but if I could work out a simple enough way for the mplayer/kinamp/launchpad combo to easily remember my place in the current playlist, I'd be happy to shut it all down between sessions.
Q2: All of my music is VBR. So I'm interested in disabling the progress bar, as damn-impressive as it is, to save on battery life. I'm not a developer, but I'm an SA extremely well-versed in BASH who has also played around with modding other open source projects to my liking. I've had a glance at the source for kinamp and was wondering if you could point me in the right direction? How much would I need to change? (I see the progressbar struct.. simple as commenting that out? *grin*) On the other hand, how much would YOU need to change to add a kinamp parameter that disabled the prog bar? (I'm guessing "a lot", since you pass all args on to mplayer.)
Q3: I have lots of music that flows from track to track and sounds silly on a player that doesn't have gapless playback. One of my dreams in rooting my Kindle was that I'd find an mp3 player that could do gapless... Do you know if mplayer has always been bad at gapless music playback or is this a symptom of the way it was compiled for the Kindle?
Thanks for your time fbdev.