Tiny Core Extensions > TCE Talk

MPD - time for an update?

<< < (2/10) > >>

b1ackmai1er:
So if these are the available options for MPD... What options should be compiled in?

########### MPD CONFIGURATION ############

Archive support:
        (-bzip2) (-ISO9660) (-ZIP)
Client support:
        (+IPv6) (+TCP) (+UNIX Domain Sockets)
File format support:
        (+AAC) (-C64 SID) (-FFMPEG) (+FLAC) (-FluidSynth) (-GME) (+libsndfile)
        (-MikMod) (-MODPLUG) (+MAD) (-MPG123) (+MP4) (+Musepack) (+OggFLAC)
        (-OggTremor) (+OggVorbis) (+WAVE) (+WavPack) (-WildMidi)
Other features:
        (+libsamplerate) (+inotify) (+SQLite)
Metadata support:
        (-cue) (+ID3)
Playback support:
        (+ALSA) (+FIFO) (+File Recorder) (+HTTP Daemon) (+JACK) (+libao) (+OSS)
        (-OpenAL) (-OS X) (-Pipeline) (+PulseAudio) (-Media MVP) (-SHOUTcast)
        (-Solaris) (-WIN32 wave)
Streaming encoder support:
        (+FLAC) (-LAME) (+Ogg Vorbis) (-TwoLAME) (+WAVE)
Streaming support:
        (+CURL) (-Last.FM) (+MMS)

????


donquixote2u:

--- Quote from: b1ackmai1er on August 20, 2010, 03:24:41 AM ---So if these are the available options for MPD... What options should be compiled in?

--- End quote ---

erm - you've lost me there, b1ackmai1er!  are you taking a poll on what most people want in MPD, or just what is needed to compile it at all?  if the latter,  the doco says "The only requirement is you must compile with at least one audio output, and one decoder"

for example I have experimentally built for my use a version that plays only mp3s to OSS output with optional mp3 streaming via the mpd internal server;

 that only has OSS and lame as  tc dependencies (ie no ogg, vorbis, flac, etc) and if I left out the streaming it wouldnt even need lame.

This wiki list was helpful; http://mpd.wikia.com/wiki/Dependencies   

hope this helps!  ;D

TaoTePuh:
@b1ackmai1er
Is there a particular reason why your extension (mpc) loads mpd as a dep and starts it? On a client computer that is not necessary, right?

donquixote2u:

--- Quote from: TaoTePuh on August 21, 2010, 02:25:44 PM ---@b1ackmai1er
Is there a particular reason why your extension (mpc) loads mpd as a dep and starts it? On a client computer that is not necessary, right?

--- End quote ---

Tao I am unaware that mpc has any remote capabilities, being just a local cli for mpd, so the mpd dependency is valid, but please correct me if I am wrong.

However when it comes to mpd, I wonder if ANY dependencies should be listed? Surely the y are only dependencies if and when they are required according to the mode that mpd is configured for?  e.g. if I want to play mp3s to OSS without streaming, there would be no dependencies required for the current version as it is compiled?   

IMHO there should just be a list of modal dependencies in the info.

TaoTePuh:

--- Quote ---Tao I am unaware that mpc has any remote capabilities,
--- End quote ---

Of course ...


--- Code: ---tc@box:~$ mpc playlist --host 192.168.252.137 --port 6600
2raumwohnung - Da sind wir
2raumwohnung - Ich weiss warum
2raumwohnung - Ich und Elaine

--- End code ---

BTW: Yesterday I built ncmpcpp and it is now available in the repo. Although it is slightly larger then mpc, but can also much more.

For this I have also built libmpdclient as an extra extension. So you can take this part out of your mpc extension and instead use libmpdclient as a dep.


--- Quote ---e.g. if I want to play mp3s to OSS without streaming
--- End quote ---

Have you already tried out "moc"?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version