Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Navigator-Suite Feedback (Read 361523 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Navigator-Suite Feedback

Reply #350 –
Quote
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.
[a href="index.php?act=findpost&pid=374362"][{POST_SNAPBACK}][/a]

I used this code in my own fcs... Are there any dependencies???
'Cause if I use the Navigator-fcs it works fine...

Navigator-Suite Feedback

Reply #351 –
When you masstag your playback-stats of your files to the 0.9 playcount-plugin by peter, and modify all the navigator-code which makes use of those values...... then be aware that you will have to do it all again, once the "real" playcount-plugin(by kl33per) is updated for 0.9. This is because kl33pers playcounter-plugin uses the agreed upon tag-standards(last_played, first_played, play_counter), while the current 0.9 playcount-plugin by peter uses different tags.

Its of course your choice what you want to do - however, i recommend to NOT use the current 0.9 playcount-plugin and instead wait for the "real" playcount-plugin by kl33per to be updated - then, you wont need to do any masstagging, wont need to change navigator, and will have your playback-stats tags in a future-safe scheme.

- Lyx
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #353 –
Is there possibility, beside Performer, and Conductor, to see some other tags, like  Composer, Location or Opus? Is it hard to modify code for that?

Navigator-Suite Feedback

Reply #354 –
Quote from: Oby on
Is there possibility, beside Performer, and Conductor, to see some other tags, like  Composer, Location or Opus? Is it hard to modify code for that?

whops, sorry for the late reply.

First, i will only support standard-tags or quasi-standard tags (like composer, conductor, etc.), but not exotic schemes like location or opus.

Second, i have no plans to add composer to the albummode-display. This is because i consider 1.4.0 mostly finished and at its end-of-life.

My (longterm, dont hold your breath for it) plans for 2.0 - after certain features have been added to Columns UI - is to drop albummode AND singlemode completely. Instead, there will be "one displaymode to rule them all". Also, secondary info like publisher, conductor, etc. will be moved out of the FCS and instead be moved into a trackinfo-panel display. This trackinfo-panel display can then carry as much info as one desires, without running into space-problems.

So, if you want to have your mentioned tags in the current albummode display, then your only choice will be to do it yourself.

- Lyx
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #355 –
Quote from: ArtMustHurt on
how come if i have the default name of my playlist it looks like this:


Why if the playlist name is default does NAV assume singles mode? Can I change this behavior?

Navigator-Suite Feedback

Reply #357 –
Quote from: acedriver on
Quote from: HiFiRE on

Why if the playlist name is default does NAV assume singles mode? Can I change this behavior?

removed Default and default from filtered playlists


I tried this and it results in weird display problems: the grey vertical border between the album mode column is 2px wide instead of 1px and the title & length column doesn't show the grey horizontal border between albums.

Navigator-Suite Feedback

Reply #358 –
Quote
Why if the playlist name is default does NAV assume singles mode?

Because incoming files can be anything - full albums as well as single files - thus, for the average user, the incoming playlist will be a "mixed playlist". No, there is no builtin support to turn it off.

Quote
removed Default and default from filtered playlists


As already stated numerous times in this thread (the last time one page back), you can NOT change playlistname-recognition by simply messing around with the keywords in the column-code. No, there is no support from my side to change it (if you must have it, then you'll need to find out yourself which parts of the column AND globals code needs to be changed).

Easiest way to avoid default-recognition would be to change the default name for incoming files in the foobar-preferences.

- Lyx
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #360 –
1.4.0 final released

Changes since the last beta:
- added full support for the recently standardized STYLE-tag
- added basic support for inline-metadata editing
- misc changes to the how-to docs
- no longer hosted at dano's FCS site, because it doesn't accept 0.9 FCS's.

Download and additional info in the first post of this thread:
http://www.hydrogenaudio.org/forums/index....showtopic=31509

This marks the end of the 1.x.x line of Navigator - i will only do bugfixes from now on.

New features will appear in Navigator 2.0.0 to be released someday in the future (yes, no ETA at all). Since 2.0.0 will be a complete redesign almost from scratch, feature proposals which asume an 1.4.x style workflow will be useless. Radical and avantgardistic ideas are welcome as long as they are reasonable. However, 2.0.0 is a long way of, so i cannot give any definitive answers to proposals - i will however read every proposal and consider it.

- Lyx
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #361 –
thanks!

Navigator-Suite Feedback

Reply #362 –
Awesome work, Lyx.

Navigator-Suite Feedback

Reply #364 –
Oh, By the way. That serves as a good question after looking at the changelog again, What are the list of standard tags? (aside from normal ones such as artist, title, etc).

Navigator-Suite Feedback

Reply #365 –
@Lyx - how/where is the style tag displayed?

My flac files have a genre tag i.e. Rock and a style tag i.e. Hard Rock, Soft Rock etc but using the albumlist view the style tags don't seem to be showing up.

Navigator-Suite Feedback

Reply #366 –
Quote
What are the list of standard tags? (aside from normal ones such as artist, title, etc).

ID3v1: http://en.wikipedia.org/wiki/ID3v1
FB2k recommended tag-standards: http://www.hydrogenaudio.org/forums/index....showtopic=31530

Hmm, DISCNUMBER is supported as well, but not mentioned in the first post - i'll add it.

Quote
Lyx - how/where is the style tag displayed?

In singlemode, there is a style-column which can be enabled. In albummode it happens in the albummode-column automatically.
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #367 –
There seems to be no STYLE support in any of the configs, when I search the fcs files after %sty nothing is found.
Maybe you can check the uploaded file again?

Navigator-Suite Feedback

Reply #368 –
Quote from: dano on
There seems to be no STYLE support in any of the configs, when I search the fcs files after %sty nothing is found.
Maybe you can check the uploaded file again?

Weird, i will check later - breakfast for now........ thanks for informing.
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #369 –
1.4.1 uploaded

Something went wrong with the 1.4.0 packaging so that STYLE wouldn't work. I have no clue why, but it should be okay now.
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #370 –
There is a display problem when the STYLE field is long, it consumes the whole first line in the album mode column.

Navigator-Suite Feedback

Reply #371 –
Damn, i someway suspected something like this to happen.

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)
I am arrogant and I can afford it because I deliver.
 

Navigator-Suite Feedback

Reply #372 –
Thanks for that link, Lyx.

Looks like style is not something i'd use, as i dont tag my files to that of an extermity ;]

By the way, which is preferre between DISC\DISCNUMBER, and ive seen other being used - are they supported? (SINGLETRACK, TOTALTRACKS)

Navigator-Suite Feedback

Reply #373 –
Quote from: ChaosBladE on
By the way, which is preferre between DISC\DISCNUMBER

I'm not 100% certain about this, but if i remember right, DISC is aliased to DISCNUMBER. So both are the same and it doesn't matter which one of them you use.

Quote
and ive seen other being used - are they supported? (SINGLETRACK, TOTALTRACKS)

SINGLETRACK is supported - i just dont like to show off with it, because i consider it to be an ugly solution (optimally, the display should be able to detect singles without the need for exotic tags).

TOTALTRACKS is unnecessary to display albummode correctly, because Navigator does not depent on knowing the last track of an album. I may however consider using TOTALTRACKS to detect singles(this is not implemented yet). It would be very easy to add(just a 3min job), so the next version will probably treat tracks with TOTALTRACKS=1 as singles.
I am arrogant and I can afford it because I deliver.

Navigator-Suite Feedback

Reply #374 –
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.