The colour-codes are stored as $rgb() values right below the config-section in the globals. However, those are just the primary colors....... the secondary colors (for example, to create the "stripes" in the background) are calculated on-the-fly (so they are not hardcoded). If you need those, then you best bet is some app which allows you to hover your mouse over any part on the screen, and it will then display the colour in hex and rgb. Most webeditors for example have such a function.
- Lyx
Full Version: Navigator-Suite Feedback
QUOTE(Lyx @ Aug 3 2005, 09:47 AM)
The colour-codes are stored as $rgb() values right below the config-section in the globals. However, those are just the primary colors....... the secondary colors (for example, to create the "stripes" in the background) are calculated on-the-fly (so they are not hardcoded). If you need those, then you best bet is some app which allows you to hover your mouse over any part on the screen, and it will then display the colour in hex and rgb. Most webeditors for example have such a function.
- Lyx
- Lyx
Alternatively, you could just take a screenshot and load it into any half-arsed image editor. If an image editor doesn't have a colour picker, it wasn't worth paying for (or downloading).
thanks for the tips, i used Huey 1.9 to pick the colour direct from foobar it doesnt seem to be an exact match (probaly the hue, sat, lue that that software didnt give values for) i would have used the hex number it gave me 323C50 but i seem to remember post saying foobar uses odd hex values so i didnt want to mess around with it as its close enough and even made it readable without me having to change the text colour.
In HTML and CSS (and in most image editors that are aimed at web production) hex colors are represented as RRGGBB. In Foobar the hex colors are represented as BBGGRR. In otherwords, to convert from the hex color the image editor spits out to what Foobar wants, just swap the first two and last two hexadecimal digits (e.g. 408060 becomes 608040). You also have to indicate hex colors by surrounding them with a special character. It is much more straight forward in my opinion to use the $rgb(...) function, although doing so may increase parsing time, I'm not sure.
QUOTE(Lyx @ Jul 3 2005, 04:24 PM)
QUOTE(eliazu @ Jul 3 2005, 11:04 PM)
maybe just do a dividing line?
can add an option to change the singletrack background?
do you agree that the background-color of singletracks arent "fit" to the whole config?
can add an option to change the singletrack background?
do you agree that the background-color of singletracks arent "fit" to the whole config?
How do you add a dividing line without additional tags, like marking the last-track of an album?
I agree its not optimal. But i dont know how to improve it without requiring additional tags(which i do not want to support).
Easy. Just add a top divider if the track is single and the albummode is active. of course that would results in a dividing line for every single track and that may not be what the original poster desires.
QUOTE(JimmyPage @ Aug 15 2005, 04:51 PM)
QUOTE(Lyx @ Jul 3 2005, 04:24 PM)
How do you add a dividing line without additional tags, like marking the last-track of an album?
Easy. Just add a top divider if the track is single and the albummode is active. of course that would results in a dividing line for every single track and that may not be what the original poster desires.
Yup, exactly.
Navigator 1.4.0alpha3 for fb2k 0.9/ui_columns prealpha15 only
changelog:
- sorting by all kinds of playback-statistics works correct now (however, since playcount is not available yet for 0.9, thats kinda useless for now)
- statusbar should now work okay in countries where RTL-languages are used
- many minor fixes and tweaks i dont remember anymore
- includes albummode and singlemode-priority variant
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k or ui_columns, then backup your current configs first! <-
- Lyx
changelog:
- sorting by all kinds of playback-statistics works correct now (however, since playcount is not available yet for 0.9, thats kinda useless for now)
- statusbar should now work okay in countries where RTL-languages are used
- many minor fixes and tweaks i dont remember anymore
- includes albummode and singlemode-priority variant
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k or ui_columns, then backup your current configs first! <-
- Lyx
Navigator 1.4.0 alpha4 for fb2k 0.9/ui_columns prealpha15
changelog:
- album & tracknumber display for singletracks in albummode is now optional
- fixed: typo in the playlistpos.-column
- fixed: tag-based VA-detection should have priority over path-based VA-guessing
- fixed: fileextension-column didn't work
- rewrote column-style code - now fully compliant with the new $set_style() syntax. If there are bugs, please report them.
- full support for ALBUM RATING including sorting-support in albummode(if you click the rating-columnheader in albummode, then it sorts by ALBUM RATING instead of RATING.)
- the singlemode-priority variant now automatically switches to albummode when playing audio CDs.
- misc minor fixes
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
changelog:
- album & tracknumber display for singletracks in albummode is now optional
- fixed: typo in the playlistpos.-column
- fixed: tag-based VA-detection should have priority over path-based VA-guessing
- fixed: fileextension-column didn't work
- rewrote column-style code - now fully compliant with the new $set_style() syntax. If there are bugs, please report them.
- full support for ALBUM RATING including sorting-support in albummode(if you click the rating-columnheader in albummode, then it sorts by ALBUM RATING instead of RATING.)
- the singlemode-priority variant now automatically switches to albummode when playing audio CDs.
- misc minor fixes
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
- ignore it -
Screenshot of Work-In-Progress alpha5
(redesigned hybrid-mode layout in action)
Click to view attachment
(redesigned hybrid-mode layout in action)
Click to view attachment
Navigator 1.4.0 alpha5 for fb2k 0.9beta13+/ui_columns prealpha16+
changelog:
- redesigned hybrid-mode (singletracks in albummode)
- secondary background color does no longer get highlighted when selecting tracks
- replaygain-column can now be shown for both, album- & singlemode
- column-style code rewritten to make use of new ui_columns features: 75% reduction in style-code
- as a result of above: works without columns ui legacy-support
- some minor exotic features dropped
- more code-cleanup and misc minor fixes
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
changelog:
- redesigned hybrid-mode (singletracks in albummode)
- secondary background color does no longer get highlighted when selecting tracks
- replaygain-column can now be shown for both, album- & singlemode
- column-style code rewritten to make use of new ui_columns features: 75% reduction in style-code
- as a result of above: works without columns ui legacy-support
- some minor exotic features dropped
- more code-cleanup and misc minor fixes
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
It would be great if Navigator-Suite could make album info (artist, date, albumgain, format, etc.) appear even if some tracks (namely 1-4) are missing. It is sad to see album-mode messed up simply because I do not have some of the tracks.
QUOTE(elenhil @ Dec 20 2005, 09:28 PM)
It would be great if Navigator-Suite could make album info (artist, date, albumgain, format, etc.) appear even if some tracks (namely 1-4) are missing. It is sad to see album-mode messed up simply because I do not have some of the tracks.
Not possible in a reasonable way with currently available UIs. If you have non-full albums, and want to see all info, then switch to singlemode.
Because this is a general UI limitation, it is the same with every other FCS.
QUOTE(Lyx @ Dec 20 2005, 10:35 PM)
Not possible in a reasonable way with currently available UIs. If you have non-full albums, and want to see all info, then switch to singlemode.
Because this is a general UI limitation, it is the same with every other FCS.
Because this is a general UI limitation, it is the same with every other FCS.
You could always support some weird "fake tracknumber" tags.
Navigator 1.4.0 alpha6 for fb2k 0.9beta13+/ui_columns prealpha16+
changelog:
- fixed tag-mess when disabling tag-guessing
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
changelog:
- fixed tag-mess when disabling tag-guessing
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
QUOTE(anza @ Dec 20 2005, 09:42 PM)
You could always support some weird "fake tracknumber" tags.
Hmm, i've heard about that but never used it - could you explain a bit more how it works? If it can be done with a minimum amount of code, i'd consider it.
QUOTE(Lyx @ Dec 20 2005, 11:27 PM)
Hmm, i've heard about that but never used it - could you explain a bit more how it works? If it can be done with a minimum amount of code, i'd consider it.
Well I think it sould work if you'd just override %tracknumber% with the fake tracknumber tag. I'm not familiar with your code, so I don't know how complex/simple your tracknumber formatting is, but something like $if2(%fake tracknumber%,%tracknumber%) should do it. And I bet you knew that already
But then you'd need to figure what tag people use for the fake tracknumber (if it's even used). Or you could make it configurable.
I think there's an alternative way.
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
QUOTE
I'm not familiar with your code, so I don't know how complex/simple your tracknumber formatting is, but something like $if2(%fake tracknumber%,%tracknumber%) should do it.
Okay, i'll have a look into it at a later time. Tracknumber-detection is currently centralized in the globals. I'm not sure if i will need one or two $if2's or about twenty of them. If its the latter, then it wont happen for 1.4.x.
QUOTE
But then you'd need to figure what tag people use for the fake tracknumber (if it's even used). Or you could make it configurable.
Right, and i'm currently not really in the mood for asking people repeatly for help with something which only they wanted in the first place. Plus, there wont be any configuration - i will not option-bloat the config further with exotic feature.
QUOTE(elenhil @ Dec 21 2005, 10:17 AM)
I think there's an alternative way.
<...>
<...>
If it would be that easy, then someone would have done it already.
Formattings cannot look backwards and forwards - they only see one track at a time and have no "memory". Albummode actually is a dirty hack - current formatting-system was never intended for something else than singlemode.
by the way - known issues of current alpha:
- rg and tagmatrix indicators sometimes are wrong
- possibly a rare glitch in albummode occuring when singlertrack-detection via trackgain is enabled
QUOTE(elenhil @ Dec 21 2005, 11:17 AM)
I think there's an alternative way.
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
As Lyx already said, it is IMPOSSIBLE.
edit: whoa I'm slow today.
Note to self: don't open all the threads in different tabs, or at least refresh them before writing a reply.
On another note regarding album-info...
current longterm-plan looks like this:
1. Finish 1.4.0
2. Abandon 1.x.x line and only do bugfixes for it in the future
3. Start working on 2.0.0 which will among other things do the following:
4. Drop tag-guessing completely and make use of the then possible fb2k 0.9 optimizations - should result in 40-60% reduction of overall code! (yep, that means major speed-gains)
5. Drop comment-display in albummode - should result in about 40-50% less albummode-column code
6. Create a trackinfo-panel formatting to display detailed info about tracks/albums. Should be able to make use of FCS-colorschemes
7. Create a new OSD formatting. Should be able to make use of FCS-colorschemes
current longterm-plan looks like this:
1. Finish 1.4.0
2. Abandon 1.x.x line and only do bugfixes for it in the future
3. Start working on 2.0.0 which will among other things do the following:
4. Drop tag-guessing completely and make use of the then possible fb2k 0.9 optimizations - should result in 40-60% reduction of overall code! (yep, that means major speed-gains)
5. Drop comment-display in albummode - should result in about 40-50% less albummode-column code
6. Create a trackinfo-panel formatting to display detailed info about tracks/albums. Should be able to make use of FCS-colorschemes
7. Create a new OSD formatting. Should be able to make use of FCS-colorschemes
QUOTE(anza @ Dec 21 2005, 09:31 AM)
QUOTE(Lyx @ Dec 20 2005, 11:27 PM)
Hmm, i've heard about that but never used it - could you explain a bit more how it works? If it can be done with a minimum amount of code, i'd consider it.
Well I think it sould work if you'd just override %tracknumber% with the fake tracknumber tag. I'm not familiar with your code, so I don't know how complex/simple your tracknumber formatting is, but something like $if2(%fake tracknumber%,%tracknumber%) should do it. And I bet you knew that already
But then you'd need to figure what tag people use for the fake tracknumber (if it's even used). Or you could make it configurable.
That has to be the supidest thing I've heard! I doubt people who can't be arsed fixing missing tracknumbers could be arsed adding fake tracknumber tags to their files...
QUOTE(elenhil @ Dec 21 2005, 07:17 PM)
I think there's an alternative way.
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
As far as I understand, in Album-mode your code simply uses the row where the 1st track is located for artist, genre, 2nd for title, date, 3rd for format, albumgain, etc.
The problem is that 1-5 album info lines are strictly bound to rows with tracks nn. 1-5. If one of them is missing, one of album infos does, too. The solution, as I see it, is to bind info lines to first five tracks not absolutely (that is _the_ 1st track row, _the_ 2nd track row, etc.) but relatively (that is the first track in a list, which can be tracknumber 02 or else, the second track in a list, which can be tracknumber 03 or 23, etc.).
Impossible. TAGZ (the code behind the config) can only deal with one track at a time. There is no possible way for it to 'see' what tracks are next or previous in the playlist. So the only possible way for it to select the first 5 tracks of an album is using tracknumbers.
QUOTE(Insolent @ Dec 21 2005, 01:32 PM)
That has to be the supidest thing I've heard! I doubt people who can't be arsed fixing missing tracknumbers could be arsed adding fake tracknumber tags to their files...
While i agree that IMHO it is stupid to add weird tags to files just so that a display works, i think you misunderstand the scenario. What they probably meant was not missing tracknumber-tags but incomplete albums.
QUOTE(Lyx @ Dec 21 2005, 10:37 PM)
QUOTE(Insolent @ Dec 21 2005, 01:32 PM)
That has to be the supidest thing I've heard! I doubt people who can't be arsed fixing missing tracknumbers could be arsed adding fake tracknumber tags to their files...
While i agree that IMHO it is stupid to add weird tags to files just so that a display works, i think you misunderstand the scenario. What they probably meant was not missing tracknumber-tags but incomplete albums.
Well, it works both ways. Incomplete albums = missing tracknumbers. If it bothers people that much, why can't they just manually adjust the tracknumbers of the tracks that aren't there so it displays correctly?
...or go get the missing files from the album.
QUOTE(Insolent @ Dec 21 2005, 01:47 PM)
Incomplete albums = missing tracknumbers. If it bothers people that much, why can't they just manually adjust the tracknumbers of the tracks that aren't there so it displays correctly?
Thats even more insane than fake-tracknumber tags - messing up the metadata of files just because of a specific audioplayer-display.
You folks are looking at the issue from a wrong way: it is the DISPLAY's job, to display stuff correctly - not some weird tags. Current fb2k is meant mostly for singlemode.... albummode is a hack and mostly only meant for full albums. It's that simple. This is also the reason why i have so long been reluctant to support hybrid-mode - its the wrong approach to fix the issue. What is needed is not different tags or weird formatting-code, but instead a different UI.
edit: i think i have an idea how to cleanly fix the whole mess without requiring a change how formatting-strings are parsed. I'll propose it to musicmusic later today.
Navigator 1.4.0 alpha7 for fb2k 0.9beta13+/ui_columns prealpha16+
changelog:
- fixed wrong indicators in replaygain-column
- fixed wrong indicators in metadata-matrix
- fixed a rare glitch occuring when detecting non-singletracks via albumgain
- ported various recent FCS-fixes to the copy-string
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
changelog:
- fixed wrong indicators in replaygain-column
- fixed wrong indicators in metadata-matrix
- fixed a rare glitch occuring when detecting non-singletracks via albumgain
- ported various recent FCS-fixes to the copy-string
I am currently only interested in bug-reports, no feature-proposals:
I do already have an TODO-list and my current time-schedule does not allow it to become bigger. Thus, i'm only interested in bugs.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
I'm using Alpha 7, and the comment's are not shown.
Navigator 1.4.0 beta1 for fb2k 0.9beta13+/ui_columns prealpha16+
changelog:
- fixed comments not being displayed
- tracknumbers in format "x/y" are now correctly shown as "xx" in FCS and copy-string
- some additional notes in the how-to
I am currently only interested in bug-reports, no feature-proposals:
Besides of already planned features, i do not intend to add further features to the 1.x.x line of Navigator. After 1.4.0 i will focus on working on 2.0.0 and only do bugfixes for the 1.4.0 line. 2.0.0 however already has a milelong list of planned changes & features, thus i'm not really short on TODO stuff.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
@keytotime: thanks for bug-reporting.
changelog:
- fixed comments not being displayed
- tracknumbers in format "x/y" are now correctly shown as "xx" in FCS and copy-string
- some additional notes in the how-to
I am currently only interested in bug-reports, no feature-proposals:
Besides of already planned features, i do not intend to add further features to the 1.x.x line of Navigator. After 1.4.0 i will focus on working on 2.0.0 and only do bugfixes for the 1.4.0 line. 2.0.0 however already has a milelong list of planned changes & features, thus i'm not really short on TODO stuff.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
@keytotime: thanks for bug-reporting.
I'm using version 1.4.0 beta1
Can you tell me how to get the daily total and last played tabs to work. I dont see anything although i have the tabs enabled.
Also foo_playcount is loaded and works when i put %last_played% and %play_count% in the status bar.
Also thank you for all your work i really like it!
Can you tell me how to get the daily total and last played tabs to work. I dont see anything although i have the tabs enabled.
Also foo_playcount is loaded and works when i put %last_played% and %play_count% in the status bar.
Also thank you for all your work i really like it!
LAST_PLAYED: my fault, will be fixed in next version
PLAY_COUNT(ER): current beta component was made by peter (foobar2000 author) and uses PLAY_COUNT - while all other plugins(and formattings) use PLAY_COUNTER. He is now aware of the incompatibility
FIRST_PLAYED: not supported by current beta playcount-plugin.
Daily plays: requires PLAY_COUNTER and FIRST_PLAYED to be available - else, there would be no way to calculate it.
thanks for reporting this.
- Lyx
PLAY_COUNT(ER): current beta component was made by peter (foobar2000 author) and uses PLAY_COUNT - while all other plugins(and formattings) use PLAY_COUNTER. He is now aware of the incompatibility
FIRST_PLAYED: not supported by current beta playcount-plugin.
Daily plays: requires PLAY_COUNTER and FIRST_PLAYED to be available - else, there would be no way to calculate it.
thanks for reporting this.
- Lyx
Navigator 1.4.0 beta3 for fb2k 0.9beta13+/ui_columns prealpha16+
changelog:
- fixed incompatibility with playcounter plugins which use other storage-methods than tags (this does NOT mean, that the earlier mentioned incompatibilities on the side of the beta playcount plugin are solved - i just fixed what was wrong on my side and thats it)
- nuked beta2 and uploaded beta3: it now should REALLY work as expected :-P
I am currently only interested in bug-reports, no feature-proposals:
Besides of already planned features, i do not intend to add further features to the 1.x.x line of Navigator. After 1.4.0 i will focus on working on 2.0.0 and only do bugfixes for the 1.4.0 line. 2.0.0 however already has a milelong list of planned changes & features, thus i'm not really short on TODO stuff.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
changelog:
- fixed incompatibility with playcounter plugins which use other storage-methods than tags (this does NOT mean, that the earlier mentioned incompatibilities on the side of the beta playcount plugin are solved - i just fixed what was wrong on my side and thats it)
- nuked beta2 and uploaded beta3: it now should REALLY work as expected :-P
I am currently only interested in bug-reports, no feature-proposals:
Besides of already planned features, i do not intend to add further features to the 1.x.x line of Navigator. After 1.4.0 i will focus on working on 2.0.0 and only do bugfixes for the 1.4.0 line. 2.0.0 however already has a milelong list of planned changes & features, thus i'm not really short on TODO stuff.
-> If you upgrade your fb2k/ui_columns/navigator-fcs, then backup your current configs first! <-
- Lyx
my two petty zloty...
I think it was a bad idea to move the info for the hybrid single tracks into the title column. The reason? Now it's harder to spot single tracks at one glance while it's more likely to visually associate them with the previous full album (I know about the solid border-lines). In the same vein I think the "highlight only right side plus album info" is significantly slower than before when selecting tracks with the mouse?
Suggestion in good faith. Revert to single track info in left column, plus dividing lines (plus maybe a slightly different shade for single tracks). Revert selection highlight to full rows (it looks more standard as well IMO).
just feeding back, so.
I think it was a bad idea to move the info for the hybrid single tracks into the title column. The reason? Now it's harder to spot single tracks at one glance while it's more likely to visually associate them with the previous full album (I know about the solid border-lines). In the same vein I think the "highlight only right side plus album info" is significantly slower than before when selecting tracks with the mouse?
Suggestion in good faith. Revert to single track info in left column, plus dividing lines (plus maybe a slightly different shade for single tracks). Revert selection highlight to full rows (it looks more standard as well IMO).
just feeding back, so.
QUOTE(towolf @ Dec 25 2005, 09:18 PM)
I think it was a bad idea to move the info for the hybrid single tracks into the title column. The reason? Now it's harder to spot single tracks at one glance while it's more likely to visually associate them with the previous full album (I know about the solid border-lines).
No matter which way i do it, it will look ambigious. If i do it as it its now, that it looks like being part of the previous album. If i do it as you propose, then it looks like being part of the next album. Reason why it looked less ambigious before was because of the missing borders - but that in turn looks uggly.
Whatever, in a few months, the whole hybridmode-mess will probably be solved anyways by changes in columns ui. So, i consider the current solution a temporary one which looks not too awfull.
QUOTE
In the same vein I think the "highlight only right side plus album info" is significantly slower than before when selecting tracks with the mouse?
Placebo.
The difference in execution-speed is too minimal to be noticed. IF it is noticable, then the new method should actually be faster(older one was more cpu-intensive).
deleted
hi there, congrats for this nice fcs, 
after looking at a few i guess this one will be my choice
altough i made a few mods, iīm no programmer myself... anyway.. i need to take the playlist tabs from the top (btw i'm using old 0.83 foo version) because i use sidebar playlist in album mode and i donīt like to see a 3 rows of playlists at the top of the main window. how can i take thsoe out please?
after looking at a few i guess this one will be my choicealtough i made a few mods, iīm no programmer myself... anyway.. i need to take the playlist tabs from the top (btw i'm using old 0.83 foo version) because i use sidebar playlist in album mode and i donīt like to see a 3 rows of playlists at the top of the main window. how can i take thsoe out please?
this is my favorite fcs, thank you so much lyx.
I've only recently discovered the "DISCNUMBER" tag and have gone through my collection and applied this where needed. However I would like the disc number to be displayed in foobar without having to resort to either putting it within the album name i.e. Name of Album Disc 1, Name of Album Disc 2 etc or putting it in the Comments field. Is there anyway within Navigator to apply the DISCNUMBER tag so that it shows next to the actual album name?
QUOTE(Demonanya @ Mar 6 2006, 10:42 PM)
I've only recently discovered the "DISCNUMBER" tag and have gone through my collection and applied this where needed. However I would like the disc number to be displayed in foobar without having to resort to either putting it within the album name i.e. Name of Album Disc 1, Name of Album Disc 2 etc or putting it in the Comments field. Is there anyway within Navigator to apply the DISCNUMBER tag so that it shows next to the actual album name?
I think navigator uses DISC as its disc number tag.
QUOTE(hedge153 @ Mar 6 2006, 02:01 PM)
QUOTE(Demonanya @ Mar 6 2006, 10:42 PM)
I've only recently discovered the "DISCNUMBER" tag and have gone through my collection and applied this where needed. However I would like the disc number to be displayed in foobar without having to resort to either putting it within the album name i.e. Name of Album Disc 1, Name of Album Disc 2 etc or putting it in the Comments field. Is there anyway within Navigator to apply the DISCNUMBER tag so that it shows next to the actual album name?
I think navigator uses DISC as its disc number tag.
In foobar 0.9 / Navigator 1.4.0b3, DISC is automatically aliased to DISCNUMBER. So no matter if you tag with DISC or DISCNUMBER, both will display correctly.
I dont know if this is also the case for foobar 0.8.3 - if not, then there are no plans to fix it for 0.8.3.
- Lyx
QUOTE(Lyx @ Mar 6 2006, 11:45 PM)
In foobar 0.9 / Navigator 1.4.0b3, DISC is automatically aliased to DISCNUMBER. So no matter if you tag with DISC or DISCNUMBER, both will display correctly.
I dont know if this is also the case for foobar 0.8.3 - if not, then there are no plans to fix it for 0.8.3.
- Lyx
I dont know if this is also the case for foobar 0.8.3 - if not, then there are no plans to fix it for 0.8.3.
- Lyx
No it isn't the case in 0.8.3... isn't hard to fix though Demonanya, just look in globals about 3 quarters of the way down in the detection core section and replace this line:
$puts(album,[$if2(%album%,%venue%)[ - CD%disc%]])
with this one:
$puts(album,[$if2(%album%,%venue%)[ - CD$if2(%disc%,%discnumber%)]])
or simply:
$puts(album,[$if2(%album%,%venue%)[ - CD%discnumber%]])
if you don't want to detect disc at all.
Hi 
When i try to import album mode navigator suite fsc file, last available beta for 0.9 1.4.0b3, i see single mode
I tried with new RC foobar too, same problem.
When i try to import album mode navigator suite fsc file, last available beta for 0.9 1.4.0b3, i see single mode
I tried with new RC foobar too, same problem.
QUOTE(hedge153 @ Mar 6 2006, 03:07 PM)
QUOTE(Lyx @ Mar 6 2006, 11:45 PM)
In foobar 0.9 / Navigator 1.4.0b3, DISC is automatically aliased to DISCNUMBER. So no matter if you tag with DISC or DISCNUMBER, both will display correctly.
I dont know if this is also the case for foobar 0.8.3 - if not, then there are no plans to fix it for 0.8.3.
- Lyx
I dont know if this is also the case for foobar 0.8.3 - if not, then there are no plans to fix it for 0.8.3.
- Lyx
No it isn't the case in 0.8.3... isn't hard to fix though Demonanya, just look in globals about 3 quarters of the way down in the detection core section and replace this line:
$puts(album,[$if2(%album%,%venue%)[ - CD%disc%]])
with this one:
$puts(album,[$if2(%album%,%venue%)[ - CD$if2(%disc%,%discnumber%)]])
or simply:
$puts(album,[$if2(%album%,%venue%)[ - CD%discnumber%]])
if you don't want to detect disc at all.
Fantastic, that works a treat
I can now go back through my music and remove the Disc no's from the comments field.Very many thanks
I have added *-s* to option 'Filter playlists' in collumns config (changed *single*;*-s-*;default;Default to *single*;*-s-*;default;Default;*-s* everywhere where needed), and now when i name playlist with -s all is displayed like -s-, single, def.. and so on, EXCEPT that the albums are separated by line. Why, is this bug or feature? I have searched for -s in many configs(globals, collumns) but havent found anything.
UPDATE: using 0.8.3 ver
UPDATE: using 0.8.3 ver
QUOTE(JoyO @ Mar 22 2006, 05:39 PM)
Why, is this bug or feature?
Since you changed the code, its your bug.
QUOTE
I have searched for -s in many configs(globals, collumns) but havent found anything.
Of course not, you were the one who added "-s" not me - so why should "-s" be in the globals?
Navigator relies in multiple places on playlistname-patternmatching, columns as well as globals. If you want to change the behaviour, then you need to change the coresponding code in both, globals AND columns - however, you're on your own....... i do not provide dev-support for "mods".
__________________________
On a different topic, i'll release 1.4.0 final during the next 2 weeks - but not much will change compared to current beta, except of inline-tagediting support for *some* (not all) columns.
- Lyx
That was just strange coz there is no -s- string in globals, the same -s, but they work different way, so i thought it was a feature. Anyway, its actually useful so no need to play with it
And one more thing: what do You think about making tag-matrix displaying in different way(color?) if for example one specific track of the *album* has other tag then others (like year or different comment)? But this may be diffficlut in implementation or not wanted by many, only idea i got how to incorporate this, is to generate colors from tags (change letters to numers) and the difference will be visible. But the problem will be not to make it too flashy, and still make the diffs visible. This would make proper tagging much easier.
And one more thing: what do You think about making tag-matrix displaying in different way(color?) if for example one specific track of the *album* has other tag then others (like year or different comment)? But this may be diffficlut in implementation or not wanted by many, only idea i got how to incorporate this, is to generate colors from tags (change letters to numers) and the difference will be visible. But the problem will be not to make it too flashy, and still make the diffs visible. This would make proper tagging much easier.
QUOTE(JoyO @ Mar 22 2006, 08:04 PM)
That was just strange coz there is no -s- string in globals
There is. Either you deleted it or you missed it when searching.
QUOTE(JoyO @ Mar 22 2006, 08:04 PM)
And one more think: what do You think about making tag-matrix displaying in different way(color?) if for example one specific track of the *album* has other tag then others (like year or different comment)?
Impossible because currently formatting-strings cannot look ahead or behind. When the design for a track is "drawn" then the code has no knowledge about the other tracks.
- Lyx
I solved for me problem whith playback statistics in next way.
Before I stop use 8.3, then change in datebase (not in files) last_layed on past_played (masstager is very good for this job).
Then load all datebase to one playlist and save it.
Start 9.0 and clear media library, then load previous playlist and close foobar.
Then start foobar and restore path of media library, close afoobar again. Now whe have new media library file.
In columns Total played I change code to
//%play_counter%'x'
//$get_global(standard_color_low)' total'
$if(%play_counter%,
$add(%play_counter%,%play_count%), %play_count%
)
In column Last played I change code to
$if(%last_played%,
$puts(last_played,%last_played%)
$puts(lastplayed_d-2000,$add(
$mul($substr($get(last_played),3,4),365),
$select($substr($get(last_played),6,7),0,31,59,90,120,151,181,212,243,273,304,334),
$substr($get(last_played),9,10)))
// calculate days since last play
$puts(days_since_last_play,$max(0,$sub($get_global(system_d-2000),$get(lastplayed_d-2000))))
// last played
$ifgreater($get(days_since_last_play),30,$left($get(last_played),10),
$ifgreater($get(days_since_last_play),1,$get(days_since_last_play)days ago,
$ifgreater($get(days_since_last_play),0,yesterday,
$get_global(special_color)' - today - '
)))
$char(9)$get_global(standard_color_low)$substr($get(last_played),12,16),
$if(%past_played%,
$puts(last_played,%past_played%)
$puts(lastplayed_d-2000,$add(
$mul($substr($get(last_played),3,4),365),
$select($substr($get(last_played),6,7),0,31,59,90,120,151,181,212,243,273,304,334),
$substr($get(last_played),9,10)))
// calculate days since last play
$puts(days_since_last_play,$max(0,$sub($get_global(system_d-2000),$get(lastplayed_d-2000))))
// last played
$ifgreater($get(days_since_last_play),30,$left($get(last_played),10),
$ifgreater($get(days_since_last_play),1,$get(days_since_last_play)days ago,
$ifgreater($get(days_since_last_play),0,yesterday,
$get_global(special_color)' - today - '
)))
$char(9)$get_global(standard_color_low)$substr($get(last_played),12,16),
)
)
Before I stop use 8.3, then change in datebase (not in files) last_layed on past_played (masstager is very good for this job).
Then load all datebase to one playlist and save it.
Start 9.0 and clear media library, then load previous playlist and close foobar.
Then start foobar and restore path of media library, close afoobar again. Now whe have new media library file.
In columns Total played I change code to
CODE
//%play_counter%'x'
//$get_global(standard_color_low)' total'
$if(%play_counter%,
$add(%play_counter%,%play_count%), %play_count%
)
In column Last played I change code to
CODE
$if(%last_played%,
$puts(last_played,%last_played%)
$puts(lastplayed_d-2000,$add(
$mul($substr($get(last_played),3,4),365),
$select($substr($get(last_played),6,7),0,31,59,90,120,151,181,212,243,273,304,334),
$substr($get(last_played),9,10)))
// calculate days since last play
$puts(days_since_last_play,$max(0,$sub($get_global(system_d-2000),$get(lastplayed_d-2000))))
// last played
$ifgreater($get(days_since_last_play),30,$left($get(last_played),10),
$ifgreater($get(days_since_last_play),1,$get(days_since_last_play)days ago,
$ifgreater($get(days_since_last_play),0,yesterday,
$get_global(special_color)' - today - '
)))
$char(9)$get_global(standard_color_low)$substr($get(last_played),12,16),
$if(%past_played%,
$puts(last_played,%past_played%)
$puts(lastplayed_d-2000,$add(
$mul($substr($get(last_played),3,4),365),
$select($substr($get(last_played),6,7),0,31,59,90,120,151,181,212,243,273,304,334),
$substr($get(last_played),9,10)))
// calculate days since last play
$puts(days_since_last_play,$max(0,$sub($get_global(system_d-2000),$get(lastplayed_d-2000))))
// last played
$ifgreater($get(days_since_last_play),30,$left($get(last_played),10),
$ifgreater($get(days_since_last_play),1,$get(days_since_last_play)days ago,
$ifgreater($get(days_since_last_play),0,yesterday,
$get_global(special_color)' - today - '
)))
$char(9)$get_global(standard_color_low)$substr($get(last_played),12,16),
)
)
QUOTE
Impossible because currently formatting-strings cannot look ahead or behind. When the design for a track is "drawn" then the code has no knowledge about the other tracks.
I know, but what about the colors "taken"/generated from tag values?
QUOTE(pIv @ Mar 23 2006, 04:09 PM)
I solved for me problem whith playback statistics in next way.
Before I stop use 8.3, then change in datebase (not in files) last_layed on past_played (masstager is very good for this job).
Then load all datebase to one playlist and save it.
Start 9.0 and clear media library, then load previous playlist and close foobar.
Then start foobar and restore path of media library, close afoobar again. Now whe have new media library file.
In columns Total played I change code to
.... Lot of code ....
Before I stop use 8.3, then change in datebase (not in files) last_layed on past_played (masstager is very good for this job).
Then load all datebase to one playlist and save it.
Start 9.0 and clear media library, then load previous playlist and close foobar.
Then start foobar and restore path of media library, close afoobar again. Now whe have new media library file.
In columns Total played I change code to
.... Lot of code ....
I've used this code, but it only gives me last played 'today'...
Can someone explain to me how comes???
If you played any song with foobar 9, then last_played was set to date of playing (today).
If song not played yet with foobar 9 - it must have tag past_played only and do not have last_played tag (you can see in properties) from previous version 8.3. That means - create past_played based on last_played and then delete last_played tag. ( Only then save playlist and inputs in foobar 9).
On my PC that works very good.
I am sorry for my bad English.
If song not played yet with foobar 9 - it must have tag past_played only and do not have last_played tag (you can see in properties) from previous version 8.3. That means - create past_played based on last_played and then delete last_played tag. ( Only then save playlist and inputs in foobar 9).
On my PC that works very good.
I am sorry for my bad English.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.