Frequently Asked Questions
Which Operating systems does Museek-Plus run on?
Museek-Plus is known to compile and run on Linux, FreeBSD and OpenBSD. It also runs on OSX (or more properly, Darwin), but Museek's dependencies are not available in Fink for some versions of OSX. All attempts to compile it in Cygwin have met with failure, to our best knowledge. Mucous does work in Cygwin, if pymucipher is compiled, first. Update: As of 11/18/2008, museek+ 0.2 has only been tested on linux. If you're running (or failed to run) it on another platform, please inform us!
Why should I use Museek-Plus? What does it have that other clients don't?
Museek-Plus can be accessed from multiple machines: Museek+ is separated into the backend (or daemon or server, if you prefer), museekd, and the clients, like Museeq and Mucous. This means you can run museekd on one box on your network and run several instances of museeq or mucous from other computers on the network all using the same Soulseek Username.
Low resource usage: If you do not wish to, you never need run museeq or any other client on the same machine museekd is running on.
Looks: Museeq is a QT app. So, if you use KDE, Museeq will fit perfectly into your desktop. If you're not using KDE, you can still theme Museeq to meld with whatever X11 configuration you use.
Speed: The Museek Daemon was written in C++, so it's considerably faster than the Python-based clients, Nicotine and PySoulSeek? who are a bit slower on the GUI front. This means your GUI doesn't need to be a resource waste that slows you down.
X-less: You don't need an X-Server to run museekd. You can use Mucous as a client, instead of Museeq. Or, you could use MuseekControl , if you just want to search, browse and initate downloads.
What about all these dependencies? I've read the INSTALL file, but am still confused.
CMake is the build script that compiles and installs museek-plus. The recommended version is >= 2.6.
GCC 3 or greater is recommended.
SWIG is required for building the mucipher module required by the Python clients: mucous, mulog, and museekcontrol.
libxml++ is a library seperate from libxml, although both are required by museekd.
muscand requires FAM or GAMIN, or it simply will be skipped and not compile.
Where do I find answers to the questions not answered in this FAQ?
You can try the Official Soulseek Forums and the museek chat room on Soulseek.
If you can't login to Soulseek for some reason, try the #slsk-gpl chatroom on Freenode
Who created Museek? Where does Museek+ come from?
Hyriand wrote the Original museekd, musetup, muscan, muscand, mulog.py ,museekchat, musirc.py, museeq, and some other now defunct Python tools.
Since Hyriand stopped active development on museek in 2005, several programmers, including SeeSchloss and daelstorm, wrote patches for museekd and museeq. In April 2006, daelstorm started actively adding features to museeq and later to museekd. Since patches are an less-than-optimal form of distributing software, he began releasing his and other users' changes as Museek-Plus.
In 2007, Hyriand worked on a complete rewrite of museekd (newnet branch). This work has been finished by lbponey in 2008 and released in museek+ 0.2.
Hyriand, the author of Museek, is also the author of Nicotine, another Soulseek client.
How does Museek compare to other Soulseek Clients?
Read the SoulseekClientComparison
What are the changes from Museek in Museek Plus?
Different Themes in Museeq?
Aside from changing your QT theme with qtconfig or your KDE theme with kcontrol, you can change the icons displayed in museeq >= 0.1.9 with Settings->Pick Icon Theme. If you wish to create an IconTheme, read: CreatingThemesForMuseeq?
Is there any way I can help the Museek-Plus project out?
Yes, there is. We Need:
- A decent GTK2 client (Murmur is unfinished)
- Experienced Python programmers to work on other clients.
- Instructions on installing Museek-Plus on OSX, OpenBSD and other operating systems.
- Patches are welcomed!
- Bug reports
- New Museeq theme
How do I get detailed crash information?
gdb is the GNU DeBugger?. It helps us with debugging crashes with museekd, museeq, and other C/C++ applications.
Make sure you give cmake the following option, so debug symbols will be enabled: -DCMAKE_BUILD_TYPE=Debug
cd workdir cmake .. -DCMAKE_BUILD_TYPE=Debug make sudo make install
Now, when you want to debug an application, such as museeq, you'll need start it through gdb.
For example, with museeq, run
gdb museeq or gdb ./museeq/museeq (if you don't want to install museeq, first)
and the type "r"<enter> to run it. When a crash occurs type "bt" <enter> to get the backtrace.
Paste this backtrace along with your bug report.
Please read DevelopingMuseekPlus