Notices

i've pressed the buttons as follows: next song, previous, volume up, down, pause, resume, pick a call.

mapped next/prev and pause (i think), resume and pick-a-call aren't showing, unless it's too early in the morning for me, and volume is probably handled internally by bt, so i prefer not to touch it. as always, grab the file, configure and test. if you want buttons to do anything else, just change the functions they call (they are set in handle_hsb() and available functions are further down the file)

@saponga: and? did it work?

Sorry, i didn't test yet because i'm at work and my headphone is at home. I'm a bit confused because looks like you've changed only the remote.py file, at least at the time i've saw the sourceforge early in the morning and i actually don't use that file at all. I just call the oscp-n900-PA bin from terminal and it just works. Sorry. I'm a noob and have no clue weather is possible to make the headphone's keys work without that remote.py or not.
Thanks again.

ahm, yes, i only changed it in remote, because it's more touch friendly than console version on n8x0/n900. just try it, you might like it. especially it now can spawn/close oscp-core via button. i've added example .desktop files (put them to /usr/share/applications/hildon/) then you can have icon directly on your n900's desktop

if not i'll see how much work would be needed to add dbus support to core

updated binaries with current wildmidi branch (fixes silence at the start/end)

update: fixed a bug where tcp listen was only enabled with daemonize mode (thx to totalizator for spotting it) now you can use ncurses interface AND pygtk gui from another machine at the same time. also is my player so good that no one has any issues or nobody bothers to report their experiences? if you like it, spread the word, if you don't, tell me why, if you find a bug, tell me too

Alritey ...feedback?
want more people using it?
put it up in extras - devel or testing
pump it... get it in extras...
if you think about it...
it appears the evolution of a sub-community is such that when a new device/ platform comes out..it attracts many who are adept and new...they quickly all become masters and then move on to the next available device when it appears (excepting a few ...) ...
then comes (for lack of a better term) the next generation of users for that device / platform ...that are new...with alot of research already done in writ in the forums for study ...but few actual people (who still use said devices and platform) around to help....
we have some of the greatest stuff ...
but the learning curve may be cliff steep in some examples...
with few or no one to help.
For a more direct example...How many would be afraid to try something new if it were easy to install...less daunting...intimidating...or confusing.
For example...look at the simplicity of installing easy debian.
If it weren't that easy... fewer would have tried it ..fearing they would screw up their devices somehow.
And hence fewer would be using it.
That is the short and simple of it.
I'm not saying that the best way to get new or established members to use stuff is to dumb stuff down for them...belittling people's intelligence is not the aim.
But if it seems (from say ...the perspective of the noob ) a brain-eating,time-consuming herculean effort to understand how to do something and implement it.
More oft than not the new member will pick the quickest most understandable and easiest method and / or service first before the more complex one.

My advice...
Get it into extras.
Get it into the application manager.
Then it's highly visible and people will be perpetually seeing it as an alternate player when they surf through the app man trying to figure out what to try next.
Half the battle's won then.
The easier to install and run the better.
Especially for new people.
Just my opinion.

@endsormeans, good, i'll move the 'make a .deb' to the top of the todo. i just wanted to polish it before so people won't stumble upon not working software on install. expect package today/tomorrow!

ps. it seems there is no freepats package for diablo, or i'm looking wrong? i'll make one too in such case

Ah grand.
My lucid moment of sanity must have made sense.

Y'know even if a program doesn't function initially (the way the developer would like)...I know it hasn't stopped me from hunting and investigating why and trying to find the answer to get it to work.
And it never stopped me from attempting at a later date to try again.
It's just that unless one has time, the desire to hunt through the posts on the forums, an insatiable curiosity and an overwhelming desire to try something off the beaten track that may or may not work. ..(which is cool and exciting method to find stuff btw...)
Then having it accessible in the app man is the way to go.
The more people using it...the more likelihood and the quicker people find those odd little hiccups or bugs that can identified and rectified...the sooner it is optimally working.

hum...yea .. I can't say that in my time I've run into the freepats package for diablo to be able to deny your suspicions. Better safe than sorry if it's needed.