Notices

oscp (0.9.76) stable; urgency=low

* limit data sent to remote (from vbr codecs)
* ignore invalid volume sent by remote
* fix: some more shoutcast quirks
* fix: some audiocards support only one frequency

oscp (0.9.75) stable; urgency=low

* fix: another shoutcast quirk

oscp (0.9.74) stable; urgency=low

* fix: segv.

---
fixes ahoy! also, there is a new oscp-remote-gtk bundled, so you might want to check if it works better than pygtk version. also builds for linux and windows are updated on sf page. also there is a mingw64 build of oscp-remote-gtk, so right now you can use it on windoze without the need for pygtk (its standalone 10MB pkg)

oscp (0.9.77) stable; urgency=low

* added oscp-remote-ncurses
* bundled libsidplayfp and updated SID songlenghts db to hvsc66
* bundled stsound and fixed build bug. now .ym files play again
* fixes and new ui mode (hippo) in oscp-remote.py. inspiration: https://nils2.files.wordpress.com/20...ippoplayer.gif , on pc it looks like this: http://i.imgur.com/o3984M6.png
* initial silence trimmer (enabled in: gme)
* ncurses: fixed list post bug
* added keybinding to return to currently playing file, default '?', you might want to edit your ~/.oscp/oscp.conf and oscp-remote.conf files to reassign it (which is good idea, because you might be missing some keybindings due to upgrades)
* network links can now also be played as other types (than just libav types)
* added to dynamic build: zzlib, gme, libav, xmp, wildmidi, adplug
* bundled flod
* add version to dlog init

oh, and btw. oscp-remote.py now launches oscp automatically when host is 127.0.0.1 and it doesnt find running core

Impressive update! oscp-remote-ncurses FTW.

Maybe I shouldn't ask this, but any hope for a sailfsh port?

@dameceno: unfortunatelly i dont have any SF device, so can't work on it there. unless there is some sdk similar to the fremantle's one (ie. vm image with emulator and sdk set up)

@dameceno:
if you want to do a quick test, there is a chance that n900's version could work (oscp by design has as few dependencies as possible). please download latest package from http://repository.maemo.org/extras-d...n-free/o/oscp/ and check if it installs? also, anyone with sf device wanting to help, please join #maemo irc channel on freenode and poke me directly. it's much easier than forum

@KotCzarny I have no n900 device, and Sailfish uses rpm packages therefore there is no way it can install on my Jolla 1. There are SDK for Sailfish out there have never needed them, let me try and grab a download link for you if I can

https://sailfishos.org/wiki/Applicat...K_Installation

Available for windows and linux with a full documentation. I can only be on freenode later in the evening when I am back from work, but would gladly help anyway I can

Since the last update I'm having problem killing the core from oscp-remote on n900. It just restarts and starts playing the last saved song. I'm now killing it from the terminal but would be nice to be able to use oscp-remote. What is the best way to kill the core?

And on a similar topic. Is there a way to not start with the last played song? I want oscp to just start and will then manually select the song. To be honest I've never really figured out how and when the song to start with is saved and it has been the same for some time now.

um, are you sure you are using the right button? if you press the 'gears', it's spawn-local-core. nearby button (X or power symbol, depending on iconset) should be sending QUIT command to core. as for last played song, if core dies for some other reason it might not be able to save current dir (ie. if you kill it instead of sending QUIT command, so maybe you were killing it all the time instead of quitting core?). and since i dont remember it misbehaving, so if you keep having troubles with it, please join irc to have it debugged (forum is a bit slow to communicate). also, you might consider not quitting core at all, because in stopped state it consumes no resources (other than some ram, which would be happily swapped out when not in use)

Works like a charm when I use the right button. Can't understand how I missed that. To my defence I usually leave oscp running, starting/stopping it more at the moment to test maebble.