Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 31
  1. #1
    Senior Member
    Join Date
    May 2008
    Location
    Netherlands
    Posts
    852

    "New Music" should be listed by creation/added date, not by modified/changed date

    When browsing "New Music" there are many files that aren't new, but some tags
    maybe have changed by some third party app. These files aren't new and
    shouldn't be listed in "New Music".

  2. #2
    Senior Member Schindler's Avatar
    Join Date
    Nov 2006
    Location
    Switzerland
    Posts
    447
    Yes, only really new Albums should appear there...

    Currently I once a week do copy changed files back from my backup to the server and do a rescan. Then they disappear in new music again..

    I would vote for this that changes in tags do not appear in new music...

    christian

  3. #3
    Senior Member
    Join Date
    May 2008
    Location
    Netherlands
    Posts
    852
    Quote Originally Posted by Schindler View Post
    I would vote for this that changes in tags do not appear in new music...
    You can :-)
    Please vote for bug 17697: "New Music" should be listed by creation/added date, not by modified/changed date http://bugs.slimdevices.com/show_bug.cgi?id=17697

  4. #4
    Babelfish's Best Boy mherger's Avatar
    Join Date
    Apr 2005
    Location
    Switzerland
    Posts
    20,315

    "New Music" should be listed bycreation/added date, not by modified/changed date

    > Please vote for bug 17697: "New Music" should be listed by
    > creation/added date, not by modified/changed date
    > http://bugs.slimdevices.com/show_bug.cgi?id=17697


    Nope. It's a dupe of this... ahm... rather old request:
    http://bugs.slimdevices.com/show_bug.cgi?id=1330

    --

    Michael

  5. #5
    Senior Member
    Join Date
    May 2008
    Location
    Netherlands
    Posts
    852

    Thumbs down

    It's difficult to understand why such basic functionality hasn't been fixed much earlier...

  6. #6
    Senior Member JJZolx's Avatar
    Join Date
    Apr 2005
    Location
    Colorado
    Posts
    11,531
    Quote Originally Posted by verypsb View Post
    It's difficult to understand why such basic functionality hasn't been fixed much earlier...
    I wouldn't call this request basic functionality, or even functionality.

    If you understand how SB deals with New Music, it's not difficult to work with. Don't allow third party tools to alter the modified time. Or if you do, use a 'touch' type of tool to reset the time. For the purposes of New Music, it's not important to reset it to the exact minute and second. Just take all of audio the files in an album and reset their modified date to what it was previously.

  7. #7
    Senior Member
    Join Date
    May 2008
    Location
    Netherlands
    Posts
    852
    Just rename the "New Music" branch to "Changed Music Files" if that's the intended use scenario.

  8. #8
    Senior Member aubuti's Avatar
    Join Date
    Oct 2005
    Posts
    8,825
    Quote Originally Posted by verypsb View Post
    It's difficult to understand why such basic functionality hasn't been fixed much earlier...
    Would it help to understand if you considered that some filesystems (such as Linux) do not store the file creation date anywhere? And that Linux is the OS of choice for most NAS devices, as well as a large share of SBS installations.

    As JJZolx suggested, the behavior you want is easily accommodated by not letting your third-party application update the file modification time, or by using a simple utility to reset the file modification to old-time-plus-2-seconds or something similar.
    Last edited by aubuti; 2011-10-26 at 05:31.

  9. #9
    Senior Member erland's Avatar
    Join Date
    Dec 2005
    Location
    Sweden
    Posts
    11,037
    Both date actually "almost" exists in the database:
    - tracks.timestamp = Modification timestamp the last time file was scanned
    - tracks_persistent.added = Modification timestamp the first time the file was scanned into SBS

    So if the menu would use "tracks_persistent.added" instead of "tracks.timestamp" it would work as I think most people expect and it would also make new/change rescan detect the files correctly since you can safely let the external tagging tools update the modification timestamp properly.
    Erland Isaksson (My homepage)
    Developer of many plugins/applets

  10. #10
    Senior Member
    Join Date
    May 2008
    Location
    Netherlands
    Posts
    852
    Quote Originally Posted by erland View Post
    - tracks_persistent.added = Modification timestamp the first time the file was scanned into SBS
    Does it survive a clear & rescan?

Posting Permissions

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