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: SQL Tree: Custom Tagging Question(s) (Read 2304 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

SQL Tree: Custom Tagging Question(s)

Trial and error is a fine principle for creative endeavors, but I figure if someone’s already gone through the motions of mastering a certain skill, why not limit the number face-palms and use the benefit of their experience…
Details:
Foobar2000 v1.3.1
+/- 75,000 ripped flac files

User experience: Trying to learn, presently in the gray area between very limited & totally ignorant. I've googled a lot of questions that have since been answered in this forum, and figured the questions here are probably a lot longer than the correct answers.

Issue: There are about 75 custom Vorbis comments [tag fields] I need to add to my audio files. Several questions have surfaced.

1. With the "Default preset" option in Display -> Columns UI, do those 75 custom tags have to be added 7 different times, over and over again, in the following (Preference) places?
  • Display -> Default User Interface -> Playlist View: Custom Columns
  • SQL Tree -> MediaLibrary table (to enable custom views)
  • SQL Tree -> Playlist table (to enable custom groups & columns)
  • Properties -> Tools -> Add New Field -> FIELDNAME [OK] (to enable entry of tag data in the properties dialog window)
  • Tools -> Tagging -> Quick tagger (to enable entry of tag metadata via properties/tagging)
  • Tools -> Text Tools -> Quick Copy Commands (to enable tag field export to csv files)
  • Display -> Columns UI -> Playlist view / [Columns] tab
  • I’ve entered the 75 desired %tags% manually into those first 2 places, noticing whatever custom tags were established did not carry over to the other places listed above. Is there a less time intensive way of copying the fields from one place to the other? [/i]

    2. What is the difference between a TFExpression (text) and Tag (text) in the SQL Tree's MediaLibrary and Playlist table? Should custom tags be set up as a TFExpression with the expression set up as [%tag field name%] – or set up as a tag? (Assumed the former).

    3. Once those tags fields are established, is there a way to sort the Metadata field names into a more logical order - or should careful consideration be made into which order I "add new fields..."

    4. Why are custom tag field names written in UPPERCASE? I assumed it was to make them stand out from Foobar2000's pre-configured fields, but "Comments" is in normal case and that tag that is not listed in their Metadata fields list was I assume was created/established by freedb.



    Thanks in advance
Neither an audiophile, nor album snob. Why do ratings threads always have someone saying they don't believe in rating music?
Record Label Icons: 600x600 pngs appropriate for any color background:
freeimage.host/johnbuck/?list=images&sort=name_asc&page=1

SQL Tree: Custom Tagging Question(s)

Reply #1
First of all, these questions are posted in the wrong forum as there are related to SQL Tree, which is a 3rd party component.

Quote
Trial and error is a fine principle for creative endeavors
There is a help file available for SQL Tree via the context menu.

1. You don't need to add any custom tag manually as TFExpression. They should be added as Tag and this can be done in one run by clicking on "Add defaults". Besides this there is no relation between the columns you define for the ColumnsUI playlist view and the fields you define for SQL Tree.
2. The MediaLibrary table queries the media library, while the Playlist table queries all playlists. The content of the playlist is not necessarily completely included in the media library.
3. No, but I don't see any need to sort them in a logical order.
4. The fields you define for SQL Tree are case insensitive and they are only used for building queries. Choosing reasonable column labels for the queries will result in not exposing them to the UI.

SQL Tree: Custom Tagging Question(s)

Reply #2
First of all, these questions are posted in the wrong forum as there are related to SQL Tree, which is a 3rd party component.
Sorry, I didn't realize SQLite tree is an independent component.
1. You don't need to add any custom tag manually as TFExpression. They should be added as Tag and this can be done in one run by clicking on "Add defaults". Besides this there is no relation between the columns you define for the ColumnsUI playlist view and the fields you define for SQL Tree.
That's quite a relief, thanks!
2. The MediaLibrary table queries the media library, while the Playlist table queries all playlists. The content of the playlist is not necessarily completely included in the media library.
That too makes sense, thanks.
3. No, but I don't see any need to sort them in a logical order.
4. The fields you define for SQL Tree are case insensitive and they are only used for building queries. Choosing reasonable column labels for the queries will result in not exposing them to the UI.
Thanks. I belatedly found & used BenB's instructions in a similar General Forum thread

Thanks for your considerate and clear reply.
Neither an audiophile, nor album snob. Why do ratings threads always have someone saying they don't believe in rating music?
Record Label Icons: 600x600 pngs appropriate for any color background:
freeimage.host/johnbuck/?list=images&sort=name_asc&page=1