despotify?

Hi

Instead of porting not so useful ports I have an idea.

Lets try to port despotify

http://despotify.se/

@LiveForIt

Great idea. Let us know when you've done it.

@xeron

I'm way to lazy

Ok I try...

@LiveForIt

Cool! it is also for XBMC!! I'll add it to my XDBC machine!

Mmm but i don't undestand, what's that ??

@LiveForIt

A program we really need! I hope you can port it.

@samo79

Its library + clients for Spotify. Cleints are mostly do that: search and play music.

The only problem which i see for now: all normal clients are : gtk, qt and java. One which (maybe) will works for us : simply text-mode client (i.e., not so cool).

Let's hope that LiveForIt can port the main library + simply client, so, someone can write a reaction based client later (which for me looks a bit hard too, because its almost the same as write new gui-based player :) )

@kas1e

Maybe a plugin for TuneNet?

@kas1e

Ah ok, maybe as cha05e90 say we can make a plugin for TuneNet, it seems the quick solution to me

@cha05e90

I don't think its possible to make this in to a TuneNet plugin, unless you make changes to TuneNet.

TuneNet GUI does not have a option to login and search for music.

TuneNet can search for radio thats not the same.

Anyway I have no idea how TuneNet does what it does, Its easier for me to make new application.

Spotify is quite a cool app actually. Are the guys at Spotify still operating under a 'invite only' scheme or is it widely open now so that anyone can get into the craze?

@kas1e

Quote:

Well this applications are the easiest to port, also it should be easy to redirect output and input to a Reaction GUI.

@LiveForIt

Maybe bean would be interested in adapting tunenet to support spotify.

@LiveForIt

+1

@spotUP

Sounds like a good suggestion to me.

@LiveForIt

Yea, please do! I actually downloaded the source but never got around to look at it. I'm also not good at porting. I might be arsed into making a GUI though if someone ports the library stuff.

If the library wants to be stand-alone for some reason perhaps the GUI could be stand-alone too and communicate through TCP/IP. That would be cool, and makes it a lot easier to split the job between the porter and the GUI maker. It also makes it extremely easy for someone else to make a different GUI without having to compile the library.

@Deniil

Might need some help on audio (AHI support) I don't know.

The GUI part I do my self, if I get there.

Quote:

I think about using a message port, that way the TCP/IP stack does not need to enabled.
I have used pipe: before but it sucks big time.

@xeron

Ok I'm getting this errors?


sndqueue.h:10:31: error: vorbis/vorbisfile.h: No such file or directory
sndqueue.h:31:3: warning: #warning "Unknown endian - Assuming little endia
sndqueue.c: In function 'shortsleep':
sndqueue.c:27: warning: implicit declaration of function 'nanosleep'
sndqueue.c: In function 'snd_reset':
sndqueue.c:37: warning: implicit declaration of function 'ov_clear'
sndqueue.c: In function 'snd_get_pcm':
sndqueue.c:460: error: 'OggVorbis_File' undeclared (first use in this func
sndqueue.c:460: error: (Each undeclared identifier is reported only once
sndqueue.c:460: error: for each function it appears in.)
sndqueue.c:465: error: 'ov_callbacks' undeclared (first use in this functi
sndqueue.c:465: error: expected ';' before 'callbacks'
sndqueue.c:466: error: 'callbacks' undeclared (first use in this function)
sndqueue.c:474: warning: implicit declaration of function 'ov_open_callbac
sndqueue.c:486: error: 'vorbis_info' undeclared (first use in this functio
sndqueue.c:486: error: 'vi' undeclared (first use in this function)
sndqueue.c:486: warning: implicit declaration of function 'ov_info'
sndqueue.c:493: warning: implicit declaration of function 'ov_read'
sndqueue.c:499: error: 'OV_HOLE' undeclared (first use in this function)
sndqueue.c:521: warning: implicit declaration of function 'ov_time_tell'

@LiveForIt

you need the vorsbis library. You can download it from os4depot

@afxgroup

Thanks.