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: 1.0 beta6 (and earlier) - console issues (Read 4133 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

1.0 beta6 (and earlier) - console issues

Hello,

I've been using console for a while and want to report some issues. They're confusing, maybe worth looking at.

While applying tags to some songs, I receive the following.
[blockquote]Multiple ID3v2 tags encountered
Multiple ID3v2 tags encountered
ID3v2 parsing failed: Invalid frame name
ID3v2 parsing failed: Invalid frame name
[/blockquote]If it's possible, there should be also file name with path, so I know which files are affected.

---
[blockquote]Location not parsable: "G:\Music\Metal\Asgaard\Asgaard - [2001] Ex Oriente Lux\temp-39D436D54FBC9724D8C7FD47972541B7.tmp", reason: Unsupported file format
Location not parsable: "G:\Music\Metal\Baptism\2005 - Morbid Wings Of Sathanas\temp-F66517130E1223E21B93BA3F0564BDEB.tmp", reason: Object not found
Could not query file attributes for "G:\Music\Metal\Astarte\1998 - Doomed Dark Years\temp-54629FDD32BE6857B8A5C38FAAED8B16.tmp", reason: Object not found
Location not parsable: "G:\Music\Metal\Bathory\2003 - Nordland II\temp-A1CCF17000A7DFD3CFAEB06F275084B9.tmp", reason: Object not found
Could not query file attributes for "G:\Music\Metal\Bathory\2003 - Nordland II\temp-A1CCF17000A7DFD3CFAEB06F275084B9.tmp", reason: Object not found
[/blockquote]
They are MP3 songs, they play OK, they also display proper tags. Once I tag them, they appear to be 'repaired' in the sense they don't show this message next time I re-tag them.
But I don't know which object is not found, what does it mean that proper MP3 file is of unsupported file format, what file attributes is it talking about (OS info or what?) and so on ;-)

Thanks!

1.0 beta6 (and earlier) - console issues

Reply #1 –
It can't play .tmp files, something created those, they're not .mp3-files.
Windows 10 Pro x64 // foobar2000 1.3.10

1.0 beta6 (and earlier) - console issues

Reply #2 –
Quote from: Andreasvb on
It can't play .tmp files, something created those, they're not .mp3-files.

Normally they are MP3 files, but I suppose foobar creates these TMP files for a brief moment while tagging. It's even more confusing than I thought ;-)

Thanks.

1.0 beta6 (and earlier) - console issues

Reply #3 –
Quote from: chojrak on
Normally they are MP3 files, but I suppose foobar creates these TMP files for a brief moment while tagging. It's even more confusing than I thought ;-)

Your assumption is correct. tmp files also are created during converting process.

This error messages in foobar's console come from the Media Library's automatic folder watching.

To avoid that hints add *.tmp as file type to be excluded in Preferences / Media Libray.
This is HA. Not the Jerry Springer Show.

1.0 beta6 (and earlier) - console issues

Reply #4 –
Quote from: Robertina on
To avoid that hints add *.tmp as file type to be excluded in Preferences / Media Libray.

That's nice workaround, thanks!
However media library should not take these files into account, knowing that they may be not fully written, and that they'll disappear momentarily.

So the only request remains - to add file names to "Multiple ID3v2 tags encountered" and similar messages.

Thanks very much for your help!
 

1.0 beta6 (and earlier) - console issues

Reply #5 –
was this console issue ever looked into further?

i'm starting to see the "Multiple ID3v2 tags encountered" in the console running v1.0.1 beta 1.  this is the first time in 3 years of using foobar i've seen this exact console message.

I would like to locate the offending files, but can't seem to figure out a way.

46k+ tracks in my library; i just rescanned the major portion of my library and found about 132 of 42,9760 with the "Multiple ID3v2 tags encountered" listed in the console, but no way to locate them.

i just moved about 20GB's of files around over the weekend using the file ops plugin, so i'm hoping the these multiple tags errors are not coming from some sort of bug in the plugin.

[edit-correction on error count]
Quote from: chojrak on
Quote from: Robertina on
To avoid that hints add *.tmp as file type to be excluded in Preferences / Media Libray.

That's nice workaround, thanks!
However media library should not take these files into account, knowing that they may be not fully written, and that they'll disappear momentarily.

So the only request remains - to add file names to "Multiple ID3v2 tags encountered" and similar messages.

Thanks very much for your help!

1.0 beta6 (and earlier) - console issues

Reply #6 –
There is no "console issue".

The "Multiple ID3v2 tags" messages are usually caused by broken Windows tagging. Microsoft shell extensions do not support ID3v2.4, but they display ID3v1 tags fine. So when somebody changes any tag in Explorer, it takes the ID3v1 tag, modifies it and saves as a new ID3v2.3 tag, before the existing ID3v2.4 tag. The result is two ID3v2 tags one after another.

I think detection and workaround for this problem has been added in some semi-recent version, that might explain why you haven't seen it before.
Full-quoting makes you scroll past the same junk over and over.