QUOTE(upNorth @ Apr 18 2006, 09:38 PM)

As I see it, complete albums, incomplete albums and single tracks, all floats into each other. So, if you want to solve it without tracknumbers and custom tags, I also take it you don't want to rely on directory structure/naming?
Do you care to elaborate?
I think you misunderstood how it would work - lets asume the following contentgroup-pattern:
%album artist%%album%%discnumber%
The entire playlist is now scanned for this pattern. Subsequent tracks with identical pattern-result are considered to form one contentgroup. Thus, the entire playlist gets split into individual contentgroups, based on the above pattern.
Lets asume we only have album artist(AA) and album(A) tags..... our playlist looks like this:
#1 AA=slowdive, A=Souvlaki
#2 AA=slowdive, A=Souvlaki
#3 AA=lanterna, A=Elm Street
#4 AA=slowdive, A=Souvlaki
#5 AA=slowdive, A=Souvlaki
#6 AA=lanterna, A=Elm Street
#7 AA=lanterna, A=Elm Street
#8 AA=lanterna, A=Elm Street
The contentgroups for the above playlist will then look the following way:
Legend: contentgroup_id/contentgroup_index/contentgroup_total(tracks in group)
#1 (1/1/2)
#2 (1/2/2)
#3 (2/1/1)
#4 (3/1/2)
#5 (3/2/2)
#6 (4/1/3)
#7 (4/2/3)
#8 (4/3/3)
formatting-strings now get CONTENTGROUP_INDEX and CONTENTGROUP_TOTAL accessable and can use them like TRACKNUMBER and TOTALTRACKS - except that this time, it works independently of the real tracknumbers of tracks.
Untagged files are a different beast, but that can probably be solved with an advanced pattern-string as well.
If you understood the above, then you will notice that not just singletracks are identified automatically, you can even move tracks around the playlist freely - split up albums and move them around, add just one track of an album to the playlist, whatever...... everything works - you can now freely move tracks around the playlist without caring at all about "proper order"..... and the playlist-display automatically adjusts to it. It now works the way as it is supposed to work.
- Lyx