Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Sep 2006
    Posts
    4

    Problems restoring TrackStat statistics

    I have just updated slimserver to version 6.5.2 - 12069 and TrackStat to 1.38.

    My music is stored as flac images with external cue sheets.

    When I restore statistics in TrackStat the last track in the albums are not restored!

    I have looked into the slimserver database as well as the TrackStat backup file and found that urls differs :-(

    The end point given for the last tracks differs meaning that the urls are different so no statistics restored.

    Example Urls:
    Database: file:///D:/Sound/MusicFlac/Norah%20Jones/Feels%20Like%20Home/Norah%20Jones%20-%20Feels%20Like%20Home.flac#2597.09333333333-2784.01333333333

    Backup file: file%3A%2F%2F%2FD%3A%2FSound%2FMusicFlac%2FNorah%2 520Jones%2FFeels%2520Like%2520Home%2FNorah%2520Jon es%2520-%2520Feels%2520Like%2520Home.flac%232597.093333333 33-2784.02557823129

    Except for the xml emcoding the only difference is the endpoint.

    Has anybody else experienced this? Do you have any suggestions/fixes?

    Best Regards,
    Silver

  2. #2
    Senior Member erland's Avatar
    Join Date
    Dec 2005
    Location
    Sweden
    Posts
    10,318
    Quote Originally Posted by Silver View Post
    The end point given for the last tracks differs meaning that the urls are different so no statistics restored.

    Except for the xml emcoding the only difference is the endpoint.

    Has anybody else experienced this? Do you have any suggestions/fixes?
    I haven't seen these kind of urls with the end point stuff before, I guess it has something to do with the cue sheet usage.

    What does the end point stuff after ".flac" represent and when will it change ?
    Will you get different endpoints every time you rescan ?

    The only fast solution I can see is to edit the TrackStat backup file so it has the same endpoint values, but I realize that it might be a bit of work if you have a lot of albums.

    The xml encoding stuff should differ between the xml file and the real url, so that is not a problem.
    Erland Isaksson (My homepage)
    (Developer of many plugins/applets (both free and commercial).
    If you like to encourage future presence on this forum and/or third party plugin/applet development, consider purchasing some plugins)
    You may also want to try my Android apps Squeeze Display and RSS Photo Show
    Interested in the future of music streaming ? ickStream - A world of music at your fingertips.

  3. #3
    Junior Member
    Join Date
    Sep 2006
    Posts
    4
    First of al thanks for you quick answer erland, as well as your fantastic work with slimserver plugins. I love them and has used them for a long time, until now without problems.

    Quote Originally Posted by erland View Post
    I haven't seen these kind of urls with the end point stuff before, I guess it has something to do with the cue sheet usage.

    What does the end point stuff after ".flac" represent and when will it change ?
    With flac images a CD is stored as 1 big file/song. The points after flac describes where the individual tracks start and end (....flac#trackStart-trackEnd

    Quote Originally Posted by erland View Post
    Will you get different endpoints every time you rescan ?
    No they should never change. I have not seen them change until the last update of slimserver and plugins and no they do not change on rescan. After thinking about it I guess it must have more to do with the slimserver scanner process than the TrackStat plugin.

    Quote Originally Posted by erland View Post
    The only fast solution I can see is to edit the TrackStat backup file so it has the same endpoint values, but I realize that it might be a bit of work if you have a lot of albums.
    Well fast and fast manually updating 600-700 CD's is going to take a looong time. I might be able to write a program that patches up the xml file.

    I will first of all try to determine if the problem is related to the specific version of slimserver.

    /Silver

  4. #4
    Junior Member
    Join Date
    Sep 2006
    Posts
    4
    Just a short follow-up. It turned out to be a problem with slimserver not trackstat. Slimserver detects the last end point of flac images different from previous versions.

    I had been thinking of splitting my images to single tracks anyway so that ended up being what I did.

    Now my collection is split in tracks and tagged using musicbrainz for unique ids. Hopefully the future will prove this easier to manage.

    /Silver

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •