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

Re: External Tags

Reply #250 –
The new APIs apparently don't currently play well together with components made with the pre-1.4 SDKs. There are similar problems with foo_wave_seekbar. These require fixing in the core and will be working in the next beta.

Re: External Tags

Reply #252 –
There's a new version of the component out to go with the today released foobar2000 1.5 beta 10. Stream metadata and album art now work.

Re: External Tags

Reply #253 –
Here's a new problem with 1.5.2 update: foo Dynamic Range stops work reporting it can't open scanned file. It may be also because of I'm having installed alot of plugins, exceeding file handles pool or something so. Back to external tags 1.5.1 and the problem is gone. I'm using foobar 1.4.6 stable if it's not compatible already.

Re: External Tags

Reply #254 –
Looks like a bug in the core that was just fixed in the beta series. Peter mentioned the bug was introduced with 1.4 series. All components made with old SDK fail at using decoders.
I'd recommend upgrading to foobar2000 v1.5 even if it's beta. External Tags no longer has to do hacky things to work there and it has quite a bit of other improvements too. No reason to avoid it.

Re: External Tags

Reply #256 –
Peter confirmed the 1.4.6 issue is the same bug that affected the earlier foobar2000 v1.5 betas. But there was a workaround so I released a new version with one.

Re: External Tags

Reply #257 –
Just updated to 1.5 beta 10 and External Tags is "cookin' with Crisco", thanks Case.

Re: External Tags

Reply #258 –
Alot of problems with foobar 1.5 beta. Updating tags on DSD files directly is not possible because of error Could not update tags (this was possible directly with version 1.46 stable). Then making external tags and change them via properties dialog, works. But again whenever applying changes to tags made by 3rd party plugin (RG-scan, Masstager etc.), I get again this error. External Tags aren't taken into account but tags always are written directly. Surprisingly External Tags (reader) isn't listed in decoders list at all. Is that intentional?

Re: External Tags

Reply #259 –
It may ber related to this issue https://hydrogenaud.io/index.php/topic,118068.0.html. Spontaneously the plugin seems to stop read/write external tags.  Installed version is 1.5.3.

/edit: Confirmed. Back to foobar stable + ET 1.5.1, Both Reader and Writer appear among decoders, which is IMO proper function.

Re: External Tags

Reply #261 –
Aah, I had to miss that, thanks for notifying. Now testing new foobar with lastest plugin and hopefully things will sort out.

Re: External Tags

Reply #262 –
@Case:  IMO it would be a good idea for the Track Info Filters/External Tags box to come checked by default after the initial installation of External Tags?  Easy to miss this otherwise.

Re: External Tags

Reply #263 –
I agree but Peter made it an opt-in feature. Hopefully we can convince a change for 1.5 final

Re: External Tags

Reply #264 –
Hi, currently having a meltdown, not sure where to start or if this is a good place to post considering the number of issues happening simultaneously. (if moderators would like to move this message elsewhere feel free)

I recently started using External Tags for *everything*, that's including MP3s, FLACs, WMAs and other formats that already have robust tags (won't go into why right now.) Also enabled the tag<->stats synchronization if that matters and manually wrote all the stats to external tags this morning.

Everything seemed fine, until spontaneously today in the last hour or so, I noticed certain files/formats suddenly lost their tags completely - principally WMA,  XA, IDSP and some other lesser known formats. I've tried reloading the tag info for those, but it does nothing, just completely blank. Tried removing the .tag files from their respective directories and reloading info - still blank, the WMAs definitely have internal metadata but it's not being read. I've literally just noticed while typing this that those formats in particular (I think?) and maybe other formats are now not playing *at all* in foobar2000. So the tag loss seems symptomatic of something greater going on. To be clear, here are a couple of the messages I've seen when attempting playback:

Code: [Select]
Wave cache: generic IO exception (Unexpected subsong index) for "D:\Dave\Music\G\George Benson - A Foggy Day.wma" / index: 1
Code: [Select]
Opening track for playback: "D:\Dave\Music\GameCube\Sonic Gems Collection\history.adx" / index: 1
Unable to open item for playback (Unsupported format or corrupted file):

Watching the foobar2000 console just shows lots of tag reading messages with no errors that I can see. Progressively, all of my external tags are being dropped as foobar2000 is re-reading my library and failing to load them, plus as soon as I access a file they disappear/revert to internal tags of course... foobar2000 is hanging constantly and sometimes crashing too while this is going on but that could just be due to media library activity, All kinds of crazy stuff is going on. I am sat here watching my "Faves" playlist decrease in number as the tags are being disappeared.

Thinking it might be a hard drive failure I checked my music drive for errors - nothing reported. Also checked my Windows 10 harddrive where fb2k is installed - also no errors reported. And I've also tried playing problematic WMAs in Windows Media Player where they're fine, and haven't yet noticed any file access problems elsewhere - my photos still pen in photo viewer, etc etc. This seems like a foobar2000-centric issue, but the weird thing is how it seems to have struck totally at random without even being closed or re-opened.

I'm not sure what else to tell you but this is very concerning... I'm hopeful that External Tags is the sole cause of the problem but it seems far more cataclysmic and External Tags is just one of many components biting the dust? Please help if you can & suggest things for me to try! I'd like to just restart my computer and go from there but not sure what will happen after that, and in my haste I'm now undergoing a full backup of my Music directory. sorry for my very disjointed and verbose post... Thank you!

Re: External Tags

Reply #265 –
You don't mention a single version number. Your problems could happen if you for example used foobar2000 v1.4.x and non-latest version of the component.
I recommend using the latest foobar2000 v1.5 beta version and the latest version of the component. Make sure you manually enable the component on the new foobar2000 under Preferences -> Tools -> Track Info Filters.

Re: External Tags

Reply #266 –
Very sorry about that Case,.. I was panicking and not thinking straight.
I've updated to the newest fb2k beta and External Tags 1.5.3, and have manually enabled it.

I tried accessing a few files I knew to be otherwise non-problematic formats and those picked up their External Tags again, which is very reassuring, but tag reading still isn't working for e.g. WMAs. They are playing (again), but not fetching metadata from the tag files, nor are they defaulting to their internal metadata. (Also attempting to load an XA crashed the application/foo_adpcm.)
The difficulty for me as a layperson is that it's unclear the extent to which this is an interaction with External Tags or indeed has zero relevance to you/your software, due to the simultaneous nature by which things went horribly wrong.

I can't do any other testing for the time-being as I'm currently reloading tag info for my entire library, which is enormous and will take hours to complete ~ I'll report back later. Thanks.

Re: External Tags

Reply #267 –
Is VGMStream somehow higher in your decoder priority list than the core player's WMA input? VGMStream does claim to support .wma files, will play them (and downmix them to 16 bits per sample), and has absolutely zero support for their tags.

VGMStream also defaults itself to going straight to the bottom of the input priority list, for the express reason that it has several colliding file type extensions, and has very bad support for those generic file types.

Re: External Tags

Reply #268 –
No decoder should affect the external tag behavior with the new system. Hopefully @iridescentaudio can provide some more info to figure out what is the problem with the WMAs.

While doing some WMA testing I noticed a bug with the new system - "Edit file tags" doesn't edit file tags but external.

Re: External Tags

Reply #269 –
All right, I am mostly back to normal, and my hard drive is probably fine. External tags are working for all but a small, specific minority of files - actually just WMA bothers me now. One major reason why I began using them for everything yesterday is precisely because of wanting to avoid such volatility with foobar2000 playback statistics and tags moving forwards.

A common theme with most of the remaining problem files is that %SUBSONG% is >0 (I see in the changelog that subsongs have been a concern in the past) and that they are either streamed formats that are related to vgmstream and adpcm components (which I have reinstalled), or they are WMA. In any case the external tags aren't working so I've removed all of them. Other game audio formats that use subsongs work, though I did have to manually intervene with some subsong'd foo_openmpt/module formats (I just deleted/recreated the external tags.)

Quote from: kode54 on
Is VGMStream somehow higher in your decoder priority list than the core player's WMA input? VGMStream does claim to support .wma files, will play them (and downmix them to 16 bits per sample), and has absolutely zero support for their tags.

That would seem to explain the problem as yes, it was... I've moved foobar2000 WMA decoders to the top of the list and VGMStream to the bottom, deleted all WMA external tags and restarted foobar2000 at least twice, but I'm still unable to reload internal tag info from WMAs. I generated the external tags yesterday, likely whilst VGMStream was erroneously reading WMA, and even though the .tags are deleted, I can't refresh from the internal metadata to recreate them - has foobar2000 somehow memorised their blank state? (though if this was the case I might expect to see an internal APEV2 flag...)

Also what I have noticed is that this only applies to WMAs where %CODEC% is reported as Windows Media Audio 2, which all have a reported %SUBSONG% index of 1.
Those were producing an Unexpected subsong index error upon playback too but I think they are playing ok since fixing component priorities (time will tell.)
Where %CODEC% is reported as WMA (which have %SUBSONG% 0), they play fine, and tags internal or external work as expected, basically zero problems.

I had more written up going into more detail for other formats that I was going to post in a new thread, feeling it may not be relevant to external tags. Might post about that later, but one thing at a time.

Any other information that you'd like me to provide please let me know.

Re: External Tags

Reply #270 –
Thanks for the extra info. If the subsong index for the playlist entry differs from the subsong stored in the external tag the metadata there will be ignored. Sounds like kode54 was correct about the decoders if they have different subsong indexing.
You may need to remove the files from the media library or playlist and re-add them to get them to use the correct subsong numbers. After that if external tags are still missing re-create the tags.

Re: External Tags

Reply #271 –
Quote from: Case on
You may need to remove the files from the media library or playlist and re-add them to get them to use the correct subsong numbers.

This fixed the remaining files ~ huge relief, I'm back to 100% external tags with knock-on-wood zero problems, and I've learned a few things too, so thank you very much (to both of you.) While I hadn't mentioned it I was experiencing the same problem with Rdos AdLib (RAW) files as well, where I'd mistakenly generated external tags whilst decoders had been incorrectly configured and so were persistently being flagged as RAW Little Endian audio. Before removing their external tags, they were playing in that format as well (ouch my ears) so that was going to be my next question. I'll know better for the next time something like this happens, and not immediately assume my drives are imploding.

Re: External Tags

Reply #272 –
I think I made a weird problem for myself.

On fb2k v1.4.6, updated external tags, some decoders, masstagger. Foobar starts crashing on startup.
I find disabling foo_external_tags stops the crashing. I downgrade to the some old version of external_tags I had downloaded (1.0.3?)
I decide to update foobar to v1.5 beta instead. I update external_tags again. It doesn't crash again.

Now, a large amount of my files don't have their tag files read in the library (my autoplaylists are all incorrect). However, when the file is actually playing it displays the external tag fine, it shows on the playlist, item details, etc, but the library doesn't seem to do anything with the data, and then it stops displaying the tag file data when playing a different file.

When I edit the external tag data it rewrites it in a slightly different structure but then it is read properly. If I try changing the properties directly it overwrites the tag file.
Removing/readding the files from the media library doesn't change anything. I could try just adding/removing junk fields to all files to force the external tag rewrite but that seems risky...

Re: External Tags

Reply #273 –
Have you:

1.  Updated Foobar to 1.5 beta 10?

2.  Then, updated to External Tags 1.5.3?

3.  In Foobar Preferences/Tools/Track Info Filters made sure that the new box for "External Tags" is checked?

Re: External Tags

Reply #274 –
Yeah, everything is already updated and checked. I noticed the rewritten tag file really isn't different except the order of tag fields is moved around sometimes.