![]() I just read your post and the good replies to it. MPD is also a text based app that is interesting and fits my goals, but again it "runs all the time."Īre there things I'm missing? Is a "runs all the time" server app OK.ie low power, low server overhead? Is Ampache usable for my goals? How? Any ideas? I've considered using Twonky for music as well as video (works fine for streaming video), but I've read comments that it is clunky for music compared with firefly. I don't like the idea of "always running" maybe OK for and office, but seems weird for my situation. I could install this on my client desktop, and connect it to music living on the server, but then wouldn't I have to install Ampache on ALL my client machines? Mopidy is text based, but runs the playlist w/o ever stopping but local player can cut in and exert some control.as I understand. Ampache seems like a nice solution, but it is web based and I loath turning the server into an X machine. So I started reading but have become more confused. 2) Next I tried forked-daapd (a current fork of firefly), but this requires compiling (pulling in massive packages), is hard to configure, but the bottom line is, "I couldn't get it to work." ![]() If I could find a solution to "make" firefly compatible with the new architecture short of recompiling it, I would happily accept it. But the old plug is 32 bit architecture and the new server is 64 bit, and firefly (mt-daapd) doesn't like this and isn't working. I really liked this solution, it is not too hard to install and configure, and there is a "local" web interface, like CUPS has. What I've tried: 1) Install old mt-daapd (which I've been running nicely on the old plug server). The server will also do duty as a file server, print server, and video server.so no separate machine for the music server. ![]() Here are my goals: 1) the music server and music collection live on the server, players are on client machines - so no elaborate set up on the client machines 2) set up on the headless server as simple as possible - no X here, only CLI 3) Server OS is debian stable, so the music server must be compatible (some music servers are entire OSes). ![]() The new server is a mini-ITX, much more robust than the old sheeva plug, but like the plug, it is headless (no GUI running) All works fine, BUT my equipment is all old (7-8 years +) so I'm replacing it all. My music lives on a hdd attached and mounted on the "plug." My main local machine runs Mint and uses rhythmbox which recognizes daapd servers. I set up firefly (mt-daapd) to serve music and Twonky for video. I have a home network with 4+ machines and a headless server, which is a "plug" computer running debian stable. Lots of articles on this, but not sure what fits my situation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |