MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
Nightingale Forums - Library order?

Nightingale Forums

Full Version: Library order?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Currently the Songbird library is sorted like this:
Artist (A-Z) -> Album (A-Z) -> Disc Number -> Track Number -> Track Name
I proposed that it be changed to:
Artist (A-Z) -> Release Date -> Album (A-Z) -> Disc Number -> Track Number -> Track Name

This would mean that your library is order with albums under artist in release order rather than alphabetical.
With Vorbis Ogg you wouldn't really need the "Album (A-Z)" as you can add the full release date not just the year (Which is currently not supported in Songbird)
I reported this to the Songbird team but they seem to not even want to consider this sort of change. What about in Nightingale will we see this sort of thing? (and support for full release dates for Vorbis Ogg)
See bug report here: http://bugzilla.songbirdnest.com/show_bug.cgi?id=23052
I like it.
Sounds good.
This can be changed with this:
Code:
--- nightingale/components/property/src/sbPropertyManager.cpp~    2012-02-15 10:34:11.538437812 +0000
+++ nightingale/components/property/src/sbPropertyManager.cpp    2012-02-15 11:07:21.165597478 +0000
@@ -522,6 +522,10 @@
   NS_ENSURE_SUCCESS(rv, rv);

   //Sorting by artist will sort by artist->album->disc no->track no->track name
+  rv = artistSecondarySort->AppendProperty(NS_LITERAL_STRING(SB_PROPERTY_YEAR),
+                                         NS_LITERAL_STRING("a"));
+  NS_ENSURE_SUCCESS(rv, rv);
+
   rv = artistSecondarySort->AppendProperty(NS_LITERAL_STRING(SB_PROPERTY_ALBUMNAME),
                                          NS_LITERAL_STRING("a"));
   NS_ENSURE_SUCCESS(rv, rv);

And you then need to export your ratings with the ratingfile extension, turn off music folder monitoring, remove all music from your library then turn on music folder monitoring and import your ratings back in. I'm not sure why it can't resort without all this but it doesn't.
This is updated for the 1.11 branch:
Code:
--- nightingale/components/property/src/sbPropertyManager.cpp~    2012-02-15 10:34:11.538437812 +0000
+++ nightingale/components/property/src/sbPropertyManager.cpp    2012-02-15 11:07:21.165597478 +0000
@@ -567,7 +567,12 @@
   rv = artistSecondarySort->SetStrict(PR_FALSE);
   NS_ENSURE_SUCCESS(rv, rv);

-  //Sorting by artist will sort by artist->album->disc no->track no->track name
+  //Sorting by artist will sort by artist->year->album->disc no->track no->track name
+  rv = artistSecondarySort->AppendProperty(
+                              NS_LITERAL_STRING(SB_PROPERTY_YEAR),
+                              NS_LITERAL_STRING("a"));
+  NS_ENSURE_SUCCESS(rv, rv);
+
   rv = artistSecondarySort->AppendProperty(
                               NS_LITERAL_STRING(SB_PROPERTY_ALBUMNAME),
                               NS_LITERAL_STRING("a"));

And you then need follow the instructions above to rebuild your library.
No the method hasn't changed here's a link to the file in the github repository
http://github.com/nightingale-media-play...anager.cpp

You need to download the source code, modify the file above then compile the source.
I'd rather it be an option you can set the ordering in...make it variable for the user, not a static default.
Unfortunately my programming skills don't extend to adding it as an option to the gui, also I have no idea how I'd go about forcing ngale to rebuild the library if you turn the option on or off.
Sounds like a small project, If I got time I will look on how to make this an option.
You wouldn't build the lib, you'd just have a function that toggles between the options that the frontend can manipulate...
Pages: 1 2