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: m-TAGS component (foo_tags) (Read 165036 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

m-TAGS component (foo_tags)

Reply #125
OK, so the method used to invoke the dynamic titling seems to effectively cause the stream itself to be reloaded in place of the m-TAGS reference.
Dynamic metadata is provided by the decoder of the stream. If the decoder wants to expose the static tags as part of the dynamic tags, it has to explicitly do that.
I wonder if there is a way for the respective first- and third-party developers to work around this, at least as an option.
It should be possible. I think the m-tags component wraps the decoder of the referenced file/stream inside its own decoder. Thus it could enrich the dynamic metadata returned by the stream decoder with static tags.


It does indeed. I will have to look at how dynamic stream tags are implemented in the SDK and see if there is a way to do this "integration"


m-TAGS component (foo_tags)

Reply #127
Awesome!!!! Thank you so much :-)

Please let me know, if there's anything I can do (but I rather doubt it, since I have no experience in Foobar Dev).

m-TAGS component (foo_tags)

Reply #128
I love it when a plan comes together!

m-TAGS component (foo_tags)

Reply #129
I apologize, but I do not understand your first comment.

I am afraid that I cannot improve my English skills in a short time. For me the essential aspect is, that m-TAGS searches for media files independent of the foobar settings (like excluded files). So that comment was something like a summary, not a question.

As for the second one, can you send me some trace? "Does not work" is not too specific. What happens? It does not load at all? Or are some tags broken? I have both XP and W7 computers at home and they all read/write from the same shared hard drive. I have never experienced a problem with the files. Are you editing them manually?

This screenshot shows the problem.
The questionmarks (duration at playlist) are wrong and the properties (lower part of the image, "other") are shown without general.

I have a new album folder with some media files on a W7 computer. I let fb2k/foo-tags create the m-TAGS files on W7. (In this case one tag file for each media file but a single !.tags file has similar effects too later on the XP computer). On that first W7 computer everthing looks fine. Next I copy or move the whole new directory/album-folder (using the W7- PC) to an accessable network directory on a XP computer. Next I copy or move ( using the target XP-PC) the new directory from that place to another place on the same XP PC, where all the media files are stored for fb2k. f2bk is monitoring and finds the new music, but I have the problems like you can see at the screenshot (same image as above). Some of the new entries are shown wrong, but all media are playable.


m-TAGS component (foo_tags)

Reply #131
I apologize, but I do not understand your first comment.

I am afraid that I cannot improve my English skills in a short time. For me the essential aspect is, that m-TAGS searches for media files independent of the foobar settings (like excluded files). So that comment was something like a summary, not a question.


I got it. Yes, m-TAGS ignores the foobar settings, because when you use m-TAGS the foobar settings may very well restrict the allowed files to *.tags, so m-TAGS would not see anything but its own files!

Quote
As for the second one, can you send me some trace? "Does not work" is not too specific. What happens? It does not load at all? Or are some tags broken? I have both XP and W7 computers at home and they all read/write from the same shared hard drive. I have never experienced a problem with the files. Are you editing them manually?

This screenshot shows the problem.
The questionmarks (duration at playlist) are wrong and the properties (lower part of the image, "other") are shown without general.

I have a new album folder with some media files on a W7 computer. I let fb2k/foo-tags create the m-TAGS files on W7. (In this case one tag file for each media file but a single !.tags file has similar effects too later on the XP computer). On that first W7 computer everthing looks fine. Next I copy or move the whole new directory/album-folder (using the W7- PC) to an accessable network directory on a XP computer. Next I copy or move ( using the target XP-PC) the new directory from that place to another place on the same XP PC, where all the media files are stored for fb2k. f2bk is monitoring and finds the new music, but I have the problems like you can see at the screenshot (same image as above). Some of the new entries are shown wrong, but all media are playable.


I think I know what's happening. The hint is that you say that all files play anyway. The key is how the monitor works. When files are moved, the monitor catches the new files as they are added. This means that if the "!.tags" file is copied before some of the media files, then the library will load the "!.tags" file, but it cannot properly resolve all locators within it (becuase the media files are just not there yet). Hence, the "?"'s that you see. There are three solutions:

1) Make sure that the "!.tags" file is the last one copied (not very practical);
2) Touch (i.e. change the date or rewrite) the "!.tags" file after copying all files, so that the monitor re-loads it (still not too practical);
3) Explicitly reload the "!.tags" file, by running "Tagging / Reload info from file(s)" from the context menu, after all files are moved (most practical).


m-TAGS component (foo_tags)

Reply #132
I apologize, but I do not understand your first comment.

I am afraid that I cannot improve my English skills in a short time. For me the essential aspect is, that m-TAGS searches for media files independent of the foobar settings (like excluded files). So that comment was something like a summary, not a question.



I forgot to mention that, as of last month's build, m-TAGS has its own exclusion list, configurable in the advanced preferences.

m-TAGS component (foo_tags)

Reply #133
OK, done. Load the new DLL: http://m-tags.org/foo_tags.dll

Now m-TAGS merges its tags with the dynamic info. Please note that m-TAGS takes precedence, i.e. the dynamic tag is shown if the m-TAGS file does NOT contain that tag.

Let me know if it works.


Works perfect!!!!! Thank you so much!!!! This is just incredible - finally I got my webradio's listed the way I want. 

m-TAGS component (foo_tags)

Reply #134
OK, done. Load the new DLL: http://m-tags.org/foo_tags.dll

Now m-TAGS merges its tags with the dynamic info. Please note that m-TAGS takes precedence, i.e. the dynamic tag is shown if the m-TAGS file does NOT contain that tag.

Let me know if it works.


Works perfect!!!!! Thank you so much!!!! This is just incredible - finally I got my webradio's listed the way I want. 


You are welcome, and thanks for pointing out a behavior that I had totally overlooked.

m-TAGS component (foo_tags)

Reply #135
I think I know what's happening. The hint is that you say that all files play anyway. The key is how the monitor works. When files are moved, the monitor catches the new files as they are added. This means that if the "!.tags" file is copied before some of the media files, then the library will load the "!.tags" file, but it cannot properly resolve all locators within it (becuase the media files are just not there yet). Hence, the "?"'s that you see. There are three solutions:

1) Make sure that the "!.tags" file is the last one copied (not very practical);
2) Touch (i.e. change the date or rewrite) the "!.tags" file after copying all files, so that the monitor re-loads it (still not too practical);
3) Explicitly reload the "!.tags" file, by running "Tagging / Reload info from file(s)" from the context menu, after all files are moved (most practical).

Thank you very much, that seems to be the right analysis!

When I close fb2k before copying and run again after copying everything is fine.

Solution Nr. 3 is more comfortable. The context menu shows  Tagging / create m-TGAS file, I guess you mean Properties / Tools / Reload info.


m-TAGS component (foo_tags)

Reply #136
if you hold shift when you right click, you will see reload info under the tagging context menu.

you can customise the context menu so it appears without having to hold down shift under file>preferences>display>context menu.

and you've already discovered the properties dialog>tools button does the same thing as well.

m-TAGS component (foo_tags)

Reply #137
I think m-tags.org is down again. :-(

m-TAGS component (foo_tags)

Reply #138
Quote
OK, done. Load the new DLL: http://m-tags.org/foo_tags.dll

Now m-TAGS merges its tags with the dynamic info. Please note that m-TAGS takes precedence, i.e. the dynamic tag is shown if the m-TAGS file does NOT contain that tag.

Let me know if it works.


I'd prefer just the opposite. I want dynamic title to be displayed if it's available and m-tag title if the former is missing.

m-TAGS component (foo_tags)

Reply #139
Quote
OK, done. Load the new DLL: http://m-tags.org/foo_tags.dll

Now m-TAGS merges its tags with the dynamic info. Please note that m-TAGS takes precedence, i.e. the dynamic tag is shown if the m-TAGS file does NOT contain that tag.

Let me know if it works.


I'd prefer just the opposite. I want dynamic title to be displayed if it's available and m-tag title if the former is missing.


I won't do that, because then a "hard-headed" input module could "force its own will", practically making m-TAGS useless. You can, however, use $if2(%<dynamic tag>%,%<m-TAGS tag>%) to achieve that, as long as the tags have different names (say "Title" and "M_Title").

m-TAGS component (foo_tags)

Reply #140
Awesome plugin, I was really excited to find something like this.

Does m-TAGS work with masstagger, as long as I don't use XP and run into the utf-8 header issue? I'd like to use it to keep the formatting tagging capabilities of masstagger, but without editing any of my my music files directly.

Thanks!

 

m-TAGS component (foo_tags)

Reply #141
It certainly should work with masstagger, or any other tag editing utility which uses the player's input specific internal tag reading and writing interfaces.

m-TAGS component (foo_tags)

Reply #142
Ah thank you for the confirmation, so far it's working perfectly! Although I did run into the problem referenced (and fixed) here:

!!!!! NEW RELEASE !!!!!

Fixed (hopefully) a bug that prevented resolution of paths on network shared drives.

Also, added the much demanded option to exclude certain kinds of files. The excluded extensions may be separated by commas, colons, semicolons, spaces, or '|'.

Let me know if it works! Thanks to all for the patience.

But sadly I can't find the option to use this functionality to exclude cue files in the creation of the tags files in the preferences dialog, or documentation telling how to do so. Thanks!

EDIT: Found it [File / Preferences / Advanced / Tagging / m-TAGS / m-TAGS creator / Excluded extensions :] thanks for the awesomely powerful plugin, luigi!

m-TAGS component (foo_tags)

Reply #143
Ah thank you for the confirmation, so far it's working perfectly! Although I did run into the problem referenced (and fixed) here:

!!!!! NEW RELEASE !!!!!

Fixed (hopefully) a bug that prevented resolution of paths on network shared drives.

Also, added the much demanded option to exclude certain kinds of files. The excluded extensions may be separated by commas, colons, semicolons, spaces, or '|'.

Let me know if it works! Thanks to all for the patience.

But sadly I can't find the option to use this functionality to exclude cue files in the creation of the tags files in the preferences dialog, or documentation telling how to do so. Thanks!

EDIT: Found it [File / Preferences / Advanced / Tagging / m-TAGS / m-TAGS creator / Excluded extensions :] thanks for the awesomely powerful plugin, luigi!


You're welcome, and the UTF-8 issue should not be an issue at all on XP. I use XP myself.



m-TAGS component (foo_tags)

Reply #144
All has been well in the world of music using m-tag. However there is one thing that I can't seem to figure out... when m-tag generates .tag files for music, it doesn't append the file name as a placeholder for the title in the metadata if it the title is blank (which is fine with me). However, foobar's default behavior for displaying title information when it can't be found in the metadata is to display the file name... which it references as the !.tag file, leaving me with hundreds of ! titles for music that has no metadata. Is there a way to alter this behavior so that m-tag sets a title placeholder for metadata-less music based on the file name?

I noticed that the file names are referenced in the "other properties" category as <@>, but I have no idea how I would append a script in the title column for displaying said information when the title is missing. Something like $if(%title%,%title%,%@%)?

EDIT: Figured it out, just change the title script to $if($meta(title) missing,%title%,$info(@))

m-TAGS component (foo_tags)

Reply #145
Whoops, double post...

Figured it out, this will let you play files without metadata and display all titles correctly (m-tag files with no metadata will have a ! appended to the end).

$if($meta(title) missing,%title%,$if($info(@) missing,$info(@) - !, %filename%))

m-TAGS component (foo_tags)

Reply #146
I think you should be able to just use $if2($meta(title),$info(@) - !)

Keep in mind that $info(@REFERENCED_FILE) contains the full path to the media file, in case you prefer that. If you do not like the "file://" prefix, use $substr().

m-TAGS component (foo_tags)

Reply #147
Nice thank you. So far my foobar experience has been headache free with m-tags, however I would like to accomplish what I think sokeking has done by adding radio stations to my library using m-tags to format the titles. However, when I right click a loaded radio station and generate a m-tags file for it, I get this error:
Code: [Select]
Decoding failure at 0:00.000 (Unsupported format or corrupted file):
"F:\RY\Downloads\#Music\#Radio\!.tags" / index: 1

Honestly I'm at a loss of what to do, when I check the .tags file everything looks in order:
Code: [Select]
[
   {
      "@" : "http://eu1.fastcast4u.com:9300/|0",
      "GENRE" : "JAZZ, FUSION, WORLD",
      "TITLE" : "Dcsoundstream- Music with a mix of Jazz, Fusion, & World",
      "URL" : "http://www.DCSOUNDSTREAM.COM"
   }
]

If anyone could offer some insight on this, I would be extremely thankful. Being able to have all of my webradios listed in my library with custom tags would be wonderful.

m-TAGS component (foo_tags)

Reply #148
Ahh interesting, if I swap my radio URL with the one sokeking's post it works perfectly. No idea why, would the streaming protocol being different break the functionality? I can load both radio stations perfectly from a playlist, but m-tags only opens one.

m-TAGS component (foo_tags)

Reply #149
Weird, I was able to fix this by checking "Only use absolute paths in references" in Tagging > m-TAGs > m-TAGs creator. All is well now, once again, thank you for the awesomely powerful plugin! Being able to tweak my songs to an OCD level of tagging without touching the source file is a dream come true.