You are here: Home » Topic » svn-1695, nslu2, unslung 6.8 + itunes 7.4.3.1: Duration ???

svn-1695, nslu2, unslung 6.8 + itunes 7.4.3.1: Duration ???

FireFly Media Server (formerly mt-daapd) Firefly Media Server Forums Firefly Media Server Nightlies Feedback svn-1695, nslu2, unslung 6.8 + itunes 7.4.3.1: Duration ???

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #1861
    jheinitz
    Participant

    Hi,

    I just upgraded my instance of mt-daapd to svn-1695 on my NSLU2 using unslung 6.8. All fine so far, but when I connect from iTunes (ver. 7.4.3.1) I can see all songs, but the duration is set to “continuous” (In German: Kontinuierlich). After selecting a song and pressing the play button, the duration is displayed correctly. The above is true for most of my AAC files. All of my MP3 files are displayed correctly.

    Is this more an itunes issue or a firefly thing?

    Best regards

    Jens

    #13125
    fizze
    Participant

    That has to do with transcoding. As firefly has to transcode the aac files, it doesn’t know the duration before it actually transcodes those files. That happens when you actually play a song.

    Grüsse nach Hamburg 🙂

    #13126
    rpedde
    Participant

    @jheinitz wrote:

    Hi,

    I just upgraded my instance of mt-daapd to svn-1695 on my NSLU2 using unslung 6.8. All fine so far, but when I connect from iTunes (ver. 7.4.3.1) I can see all songs, but the duration is set to “continuous” (In German: Kontinuierlich). After selecting a song and pressing the play button, the duration is displayed correctly. The above is true for most of my AAC files. All of my MP3 files are displayed correctly.

    Is this more an itunes issue or a firefly thing?

    Best regards

    Jens

    I’d like to see one of those, if you don’t mind. Can you email me one (a short one, if possible, or even a truncated one) at [email protected]?

    #13127
    jheinitz
    Participant

    @fizze: Grüsse aus HH zurück 🙂

    If it has to do with transcoding, why is the duration displayed for some AAC files even for those I have not played yet?

    @ron:

    I’m going to send you a file in the next couple of days. Hope to do so on the weekend.

    Regards

    Jens

    #13128
    rpedde
    Participant

    @jheinitz wrote:

    @fizze: Grüsse aus HH zurück 🙂

    If it has to do with transcoding, why is the duration displayed for some AAC files even for those I have not played yet?

    @ron:

    I’m going to send you a file in the next couple of days. Hope to do so on the weekend.

    Regards

    Jens

    k… like fizze says, sometimes I don’t get the length right because with transcoding I have to guess. But usually I guess *something*, even if it’s not exact.

    So a file that exhibits the problem would be good.

    – Ron

    #13129
    jheinitz
    Participant

    Hi Ron,

    I have sent you a small file by email. This one is ripped of the CD using itunes 6.x or 7.x a while ago. Hope that you are able to reproduce. If not, please let me know.

    Have a nice weekend.

    Cheers

    Jens

    #13130
    jheinitz
    Participant

    Hello,

    today I performed the Full Scan and I have a strange result:

    1.) Only a very few files show “Continuous” in itunes. That’s the good part.

    2.) All (really ALL) songs are shows in itunes as Type “AAC File (Removed)” or “MPEG Audio File (Removed)”

    Here is the section of the Full Scan from the Log:

    2007-10-29 20:19:05 (00000400): Rescanning database
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:19:22 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:21:10 (00000400): Bad aac file: atom length too short searching fo
    2007-10-29 20:26:33 (00000400): Starting playlist scan
    2007-10-29 20:26:38 (00000400): Updating playlists
    2007-10-29 20:26:39 (00000400): Scanned 5729 songs (was 5729) in 454 seconds

    What’s wrong here?

    Best regards

    Jens

    #13131
    jheinitz
    Participant

    Hello!

    STOP!!! I’m sorry for causing confusion. I had a few “bad” songs in my repository. These did not play at all, but the rest is fine. The only strange thing is that the type of the file is still shown as “AAC File (Removed)”. Even after removing the songs3.db file and restarting the server.

    Best regards

    Jens

    #13132
    rpedde
    Participant

    @jheinitz wrote:

    Hello!

    STOP!!! I’m sorry for causing confusion. I had a few “bad” songs in my repository. These did not play at all, but the rest is fine. The only strange thing is that the type of the file is still shown as “AAC File (Removed)”. Even after removing the songs3.db file and restarting the server.

    Best regards

    Jens

    Really? It literally says “aac file (removed)”?

    hrmph. that’s strange. Wonder what that is?

Viewing 9 posts - 1 through 9 (of 9 total)
  • The forum ‘Nightlies Feedback’ is closed to new topics and replies.