FireFly on DNS-323 and Flac files

FireFly Media Server Firefly Media Server Forums Firefly Media Server Setup Issues FireFly on DNS-323 and Flac files

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #1755
    Anonymous
    Inactive

    I’ve had FireFly server running on my Windows Home Server machine serving two SoundBridge M1000s and everything has worked just fine. I’ve ripped all my CDs to flac-files and FireFly (“Roku-version” = svn1359) has AFAIK made a server-side conversion and transcoded .flac music to wav and sent it to the SBs.

    Now I wanted to dedicate WHS to pictures, videos, home folders and automatic backups and bought D-Link DNS-323 NAS for music. I’ve managed to install FireFly (v. svn-1498) as a standalone application and get it running but i’ve bumped into a couple of serious problems:

    – when I browse music in SB, I can see only the songs but not artists or albums. The song names are strange, for instance like this: x 01 Blues Before Sunrise.flac. In song info all songs have duration of 10:00.0 (!?). When I try to play them, I get message “This music format is not supported” and in mt-daapd.log there in is an error message “(0010d803): Write error: Broken pipe”

    – Firefly in DNS-323 (= Linux) doesn’t recognize scandinavian alphabets. In mt-daapd.log file there are error messages like “Invalid UTF-8 in /mnt/HD_a2/Flac/Essi Wuorela/Valo/03 Uusi kevät.flac”.

    I’ve tried MP3s and they play just fine and I can browse them normally. I’ve compared mt-daapd.conf files in both FireFlys and I just couldn’t figure out, what’s wrong! Something to do with ssc_prog and ssc_codectypes, I guess but what?

    As you can guess, I am a novice in Linux skills.

    #12685
    rpedde
    Participant

    @A.E. Neuman wrote:

    I’ve had FireFly server running on my Windows Home Server machine serving two SoundBridge M1000s and everything has worked just fine. I’ve ripped all my CDs to flac-files and FireFly (“Roku-version” = svn1359) has AFAIK made a server-side conversion and transcoded .flac music to wav and sent it to the SBs.

    Now I wanted to dedicate WHS to pictures, videos, home folders and automatic backups and bought D-Link DNS-323 NAS for music. I’ve managed to install FireFly (v. svn-1498) as a standalone application and get it running but i’ve bumped into a couple of serious problems:

    – when I browse music in SB, I can see only the songs but not artists or albums. The song names are strange, for instance like this: x 01 Blues Before Sunrise.flac. In song info all songs have duration of 10:00.0 (!?). When I try to play them, I get message “This music format is not supported” and in mt-daapd.log there in is an error message “(0010d803): Write error: Broken pipe”

    – Firefly in DNS-323 (= Linux) doesn’t recognize scandinavian alphabets. In mt-daapd.log file there are error messages like “Invalid UTF-8 in /mnt/HD_a2/Flac/Essi Wuorela/Valo/03 Uusi kevät.flac”.

    I’ve tried MP3s and they play just fine and I can browse them normally. I’ve compared mt-daapd.conf files in both FireFlys and I just couldn’t figure out, what’s wrong! Something to do with ssc_prog and ssc_codectypes, I guess but what?

    As you can guess, I am a novice in Linux skills.

    Sounds like the version you have wasn’t compiled with flac support. You’ll need the libvorbisfile and libflac libraries, and it has to be configure with –enable-flac to be able to read flac metadata.

    Not sure where that build came from, but that’s the issue. Did you build it yourself? Could you recompile it with flac support?

    — Ron

    #12686
    Anonymous
    Inactive

    I installed the precompiled package dns_323_firefly_svn_mt-daapd-svn-1498_pa1.tar.gz in the howto:firefly – DNS323Wiki page in Standalone – The Easy Way => “tried to get over the fence where it is the lowest” 🙁

    So the next step would be to try FireFly in Standalone mode in the same page, but first I have to familiarize with crosscompiling and other weird terms to me!

    #12687
    rpedde
    Participant

    @A.E. Neuman wrote:

    I installed the precompiled package dns_323_firefly_svn_mt-daapd-svn-1498_pa1.tar.gz in the howto:firefly – DNS323Wiki page in Standalone – The Easy Way => “tried to get over the fence where it is the lowest” 🙁

    So the next step would be to try FireFly in Standalone mode in the same page, but first I have to familiarize with crosscompiling and other weird terms to me!

    Ah, but what an opportunity to learn a new skill. 🙂

    I think that on the 323, the easiest way is to get unslung working, then you can use the pre-built nightlies packages and all the optware stuff.

    #12688
    Anonymous
    Inactive

    Isn’t it for Linksys NSLU2? Do they have same processors?

    I’ve been thinking to get a Slug too, just for toy purposes and practising.

    #12689
    rpedde
    Participant

    @A.E. Neuman wrote:

    Isn’t it for Linksys NSLU2? Do they have same processors?

    I’ve been thinking to get a Slug too, just for toy purposes and practising.

    Nope, it works on a bunch of different systems. Including a version that runs on the 323, I’m almost sure.

    Google around for “optware” on the 323. That’s the packages for unslung that are ported to other architectures.

    — Ron

    #12690
    Anonymous
    Inactive

    I had the same issues – moving from slug to a dns 323. Finally after searching around I found this thread:

    http://forum.dsmg600.info/t1897-Firefly-package-(with-flac).html

    and Firefly is now working like a charm 🙂

    #12691
    Anonymous
    Inactive

    Yes, I noticed the same thing a couple of weeks ago and the version has been running in my DNS-323 ever since without any trouble.

    Excellent job!

    AEN

Viewing 8 posts - 1 through 8 (of 8 total)
  • The forum ‘Setup Issues’ is closed to new topics and replies.