I see. I do believe a tag is needed to recognize single tracks though.

I see it like this: A single track can be each of the following: has no tags at all (bad?), has no tracknumber  or album tag, and has all standard tags (artist, album, track, title, maybe even genre and date).

How could you make a correct guess with all three 'modes' without an extra tag? esp. in the latter case.

How do you propose to fix it? Truncate it, or move it into a seperate line just for style? (the latter one means less space for other metadata when displaying albums with a low amount of tracks)

For the moment I'd truncate it.
But I can also image having it in a sperate line because I don't use performer or conductor tags.
Maybe you could offer a way to choose what extended tags are displayed?

Quote from: ChaosBladE on 2006-04-18 18:41:00

I see. I do believe a tag is needed to recognize single tracks though.

I see it like this: A single track can be each of the following: has no tags at all (bad?), has no tracknumber  or album tag, and has all standard tags (artist, album, track, title, maybe even genre and date).

How could you make a correct guess with all three 'modes' without an extra tag? esp. in the latter case.

Go to the columns_ui thread and search it for the keyword "contentgroups"-

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?

 ALBUMMODE-DECISION
// ===================================
// singlemode priority
// $if($or($strstr($lower(%_playlist_name%),album),$strstr($lower(%_playlist_name%),-a-)),
// $puts(albummode_active,1),$puts(albummode_active,2))

// albummode priority
$if($not($or($strstr($lower(%_playlist_name%),single),

// ===================================
// MY STUFF - pIv
// ===================================
$strstr($lower(%_playlist_name%),-s-),$stricmp($lower(%_playlist_name%),default),$strstr($lower(%_playlist_name%),radio))),
// ===================================

$puts(albummode_active,1),$puts(albummode_active,2))

// autorating
$repeat($get_global(symbol_rating),$get_global(auto_rating))
$get_global(special_color2)
$repeat($get_global(symbol_rating),$sub(5,$get_global(auto_rating)))

// ===================================
// MY STUFF - pIv
// ===================================

$puts(auto_rating,$ifgreater($num(%play_counter%,3),24,5,
$ifgreater($num(%play_counter%,3),12,4,
$ifgreater($num(%play_counter%,3),6,3,
$ifgreater($num(%play_counter%,3),3,2,
$ifgreater($num(%play_counter%,3),0,1,
0))))))

$set_global(auto_rating,$get(auto_rating))

// ===================================

I think thats just the new look of the single mode in album mode...

Hey Lyx!

When I add next item to "default" playlist - http://10.1.0.22:8888/Dinamit

in column "Title & Length" I see "Dinamit    N/A".


If I add this item in another playlist (in my case it's name is "Radio"), I see in this columns "[unknoun variable]  - Dinamit  N/A".

I solve this problem next way - in Global script add check name  playlist on "radio"

Code: [Select]

 ALBUMMODE-DECISION
// ===================================
// singlemode priority
// $if($or($strstr($lower(%_playlist_name%),album),$strstr($lower(%_playlist_name%),-a-)),
// $puts(albummode_active,1),$puts(albummode_active,2))

// albummode priority
$if($not($or($strstr($lower(%_playlist_name%),single),

// ===================================
// MY STUFF - pIv
// ===================================
$strstr($lower(%_playlist_name%),-s-),$stricmp($lower(%_playlist_name%),default),
$strstr($lower(%_playlist_name%),radio))),
// ===================================

$puts(albummode_active,1),$puts(albummode_active,2))

My second sugession - add autorating column

with all due respect to lyx, i don't see why half of the screen would be neglected in single track mode. And the separation between each track make it looks like it's "cramped".

// is your custom-theme a dark-theme? (0=no, 1=yes)
$puts(theme_dark,1)

// foreground colors
$puts(standard_color,$rgb(255,255,255))
$puts(special_color,$rgb(70,115,170))
$puts(playing_color,$rgb(55,80,108))
$puts(borders_color,$rgb(19,52,102))

// background colors
$puts(bg_color,$rgb(70,115,170))
$puts(bg_color2,$rgb(55,80,108))

// various symbols used in display
$puts(symbol_rating,▀)

Its a nice cool blue type scheme, lemme know what you think. :)

// is your custom-theme a dark-theme? (0=no, 1=yes)
$puts(theme_dark,1)

// foreground colors
$puts(standard_color,$rgb(255,255,255))
$puts(special_color,$rgb(70,115,170))
$puts(playing_color,$rgb(55,80,108))
$puts(borders_color,$rgb(255,255,255))

// background colors
$puts(bg_color,$rgb(70,115,170))
$puts(bg_color2,$rgb(40,58,77)

// various symbols used in display
$puts(symbol_rating,▀)

Looks okay now.

Would you mind if i do some minor adjustments and afterwards add it to the next release? (I'm also willig to add it if you do not wish any modifications from my side. You decide.).

_____________________________________________

If anyone has any bugs to report, then please do so in the coming days. I'd really like to get 1.4.x bugfree and "finished".

- Lyx

// is your custom-theme a dark-theme? (0=no, 1=yes)
$puts(theme_dark,1)

// foreground colors
$puts(standard_color,$rgb(255,255,255))
$puts(special_color,$rgb(255,172,1))
$puts(playing_color,$rgb(55,80,108))
$puts(borders_color,$rgb(255,172,1))

// background colors
$puts(bg_color,$rgb(70,115,170))
$puts(bg_color2,$rgb(30,50,75))

// various symbols used in display
$puts(symbol_rating,?)

%title% $tab()$rgb(70,115,170,30,50,75).:$rgb(255,255,255,255,255,255)$num(%size%,$len(99999))$rgb(70,115,170,30,50,75):. $tab()%length%

Consider these ideas for a release. I've added VA - to my VA albums that didn't already have it.

i think your second pic is because u are using the composer tag or producer tag, it does that i have noticed...

i am sure lyx will give you a more official explanation though