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: foo_custominfo (Read 188137 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_custominfo

Reply #50
Sorry if i'm asking something stupid ,but can this plugin add values besides from the context menues?
(i mean by titleformatting from let's say trackinfo or columns ui playlist column?)
Favourite artist:CD-R
Favourite album:700MB

foo_custominfo

Reply #51
no, that's not possible atm, though i think that custom function for this could be added. i don't see much use for it though, maybe just for the masstagger.

on a sidenote: custom info works perfectly with foo_skip

foo_custominfo

Reply #52
Any updates to this excellent plugin?

foo_custominfo

Reply #53
A little bug:

I created a command that places a skip tag (foo_skip). I wanted to have this command directly in context menu without any submenu so i created following name: "Skip".  But i get a submenu with the name "Skip" that contains a command with the name of an arbitrary track (  )

It seems to me that in current version we have to create submenus in context menu

foo_custominfo

Reply #54
works fine here with these settings:

Display Name: Custom Info/Skip Track
Field Name: SKIP
Value: 1


foo_custominfo

Reply #56
Any chance of adding the custominfo menu items to the keyboard shortcuts list, so we can turn them into hotkeys?

 

foo_custominfo

Reply #57
Any chance of adding the custominfo menu items to the keyboard shortcuts list, so we can turn them into hotkeys?
They should be accessable from the keyboard shortcuts page, just type in custom into the search box and you should find them.

foo_custominfo

Reply #58
Im trying to create an autoplaylist which only shows songs that don't have %rating% tags.

I can get autoplaylist to show if I want tracks with a rating greater than 3 using
Code: [Select]
%rating% GREATER 3
but I can't get unrated ones to show.

I have tried
Code: [Select]
%rating% MISSING
but it returns every track. I then tried
Code: [Select]
NOT %rating% IS ?
which returns nothing.

Any ideas how to do this?


Also could someone show some examples of what these are used for?

Quote
- $cinfo(X,Y). Returns value with field name X and index Y. Similar to $meta(X,Y).
- $cinfo_num(X). Number of values in field X. Similar to $meta_num(X).
- $cinfo_sep(X,Y,Z). Returns all values in field X separated with strings Y & Z as in $meta_sep(X,Y,Z).
- $cinfo_list(X,Y). Returns all custominfo values for current track using Y as a separator between field name and value, and X as separator between field/value-pairs.


foo_custominfo

Reply #60
Use the following to check for the absence of the rating tag field:
Code: [Select]
rating MISSING
Doesn't seem to work, it still bring up every track. Would it make a difference that I am storing the rating using custominfo?

None of the tags I have stored in custominfo work in the autoplaylist.

foo_custominfo

Reply #61
Doesn't seem to work, it still bring up every track. Would it make a difference that I am storing the rating using custominfo?
Yes, it would. Sorry that I overlooked this possibility. In this case try
Code: [Select]
NOT "[%rating%]" IS ?*

%rating% alone would result in a question mark, if the field is not defined, the brackets cause the result to be the empty string in that case, and ?* tests for any string that is at least one character long.

foo_custominfo

Reply #62
Doesn't seem to work, it still bring up every track. Would it make a difference that I am storing the rating using custominfo?
Yes, it would. Sorry that I overlooked this possibility. In this case try
Code: [Select]
NOT "[%rating%]" IS ?*

%rating% alone would result in a question mark, if the field is not defined, the brackets cause the result to be the empty string in that case, and ?* tests for any string that is at least one character long.
Thanks, works perfectly now

foo_custominfo

Reply #63
0.1.2
- bugfix: commands in context menu root were not working correctly (thanks, q-stankovic)


foo_custominfo

Reply #65

0.1.2
- bugfix: commands in context menu root were not working correctly (thanks, q-stankovic)


No! 
When i choose as Displayname "Skip" i get following: Context menu->Skip->Skip

Hmm.. I think it's because you've created the Skip-command before the new version, and foobar uses the context menu path it has already saved with the old version. If this is the case, there are couple of solutions:
1) editing context menu manually (Display -> Context Menu)
2) resetting whole context menu (Display -> Context Menu -> Reset Page)
3) using different display name like "skip" or "Skip " or "/Skip" instead of "Skip"
4) I could update GUIDs for all the commands, but then everyone would have to reconfig their keyboard shortcuts etc.. :/

foo_custominfo

Reply #66
I am wondering if a custominfo for ARTISTS not TRACKS is possible? i.e. a second SQL database for artist entries. Thus if for example U2 are playing and I want to write some custom info, e.g. In biography custom info: "U2 are great" I'd like this to be accessible whenever any U2 track plays.

The reason I want this is to store information such as similar artists, biography, discography etc. To store this in each individual track entry would be quite painful.


foo_custominfo

Reply #68
Can you write in a hook that will cause foo_custominfo to save the custom entries when the Save All button is hit in the configuration pane?  It appears that the only time foo_custominfo commits the changes to disk is when FB2K is closed, which can be quite problematic if FB2K crashes (or the machine) and one has been making lots of custom entries as the songs play.

Alternative to that, could you export the save function up to a level where we can assign it to a hotkey and invoke it when needed?

Thank you in advance.

foo_custominfo

Reply #69
Let me correct myself ...  If one stores the custominfo fields in the FB2K config file, Save All will save them along with the rest of the settings.

If one stores the custominfo fields in another format outside of the FB2K config file, Save All will not save the fields to that separate file.

For the time being, I'm perfectly happy storing my fields inside the FB2K file, however it may be beneficial to have the other formats save at the same time a Save All is called--if that's even possible--I haven't inspected the SDK in some time to see if there is even a way to do this.

Can you write in a hook that will cause foo_custominfo to save the custom entries when the Save All
[...]

foo_custominfo

Reply #70
Somehow when I click on the remove dead entries I only get "Remove dead entries failed. Press cancel to disable foo_custominfo or ok to ignore and continue." Any idea? I use foobar0.9.4 and custominfo 0.1.2 with SQLite DB.

foo_custominfo

Reply #71
Somehow when I click on the remove dead entries I only get "Remove dead entries failed. Press cancel to disable foo_custominfo or ok to ignore and continue." Any idea? I use foobar0.9.4 and custominfo 0.1.2 with SQLite DB.


Same here, but since many fb versions. I think this was only a idea of the author but never implemented. Even doesn't work with txt-file

foo_custominfo

Reply #72
Any plans on adding a custom tag editor?
This would be very useful for files that don't (and should not) support tagging.

foo_custominfo

Reply #73
Any plans on adding a custom tag editor?
This would be very useful for files that don't (and should not) support tagging.

it would be best if this could have been integrated to default foobar's properties dialog (as for example playback statistics are). i have no idea whether there's any way (service) to do so, it should be though ...


Fermion, i have few requests
  • way to remove just one given value from field (in case of multiple values). syntax could be like "-FIELD". this would come handy in case of fields for mood (conbined with buttons in track info panel mod for example) etc.
  • support for album-wide custom tags.

    with the introduction of single column playlist and other components, i would really like to start adding album-related tags without adding them to each track.

    this could work on directory / referenced file basis. if track uses subsong or referenced file, custom info would be linked with that file (and it would be easy to get from given track to this information). in case of no referenced file / subsong, it could use path (without filename) for example.

    i would welcome input from other users / developers on this topic ...

foo_custominfo

Reply #74
Any plans on adding a custom tag editor?
This would be very useful for files that don't (and should not) support tagging.


I was ironically coming to this topic to request something amounting to the same thing, involving a Pokemon GBS emulated audio format no less.  How exactly are custom tags stored in the text file?  If I understand properly, the format in the txt file is:

file://[filename]
0
1
4 [number of characters of the custom tag title]
TEST [custom tag title]
3 [number of characters in custom tag entry]
abc [custom tag entry]

And repeat.

Is this right?

If I want to add title tags to about 30 files which do not support tagging, do I have to create 30 individual context entries in the Custominfo dialog in Properties, or can I just directly add file entries in the txt file without using foobar?