"Force preferred tag writing scheme" not being honoured, 1.1.10 tagging problem? |
Please read foobar2000 Tech Support Forum Rules before posting and comply with all the points.
Failure to provide all the information pointed out in the above document in your post is considered wasting other people's time and in extreme cases will lead to your topic getting locked without a reply.
See also: Hydrogenaudio Terms of Service.
![]() ![]() |
"Force preferred tag writing scheme" not being honoured, 1.1.10 tagging problem? |
Jan 11 2012, 10:16
Post
#1
|
|
|
Group: Members Posts: 232 Joined: 28-October 05 Member No.: 25414 |
In advanced tagging settings I have "Write ID3v2.3", "Prefer ID3v2 + ID3v1", & "Force preferred tag writing scheme" all set.
I moved to foobar2000 v1.1.10 a few days ago. Prior to upgrade, I think from v1.1.9, any edit of an mp3 did indeed result in it being forced to v2.3+v1. Certainly this has worked for me for a long time, & it can only be relatively recently that this stopped working. Now, if there is an existing v2.4 tag it is not being forced over to v2.3, although a v1 is added. In long, an edit of any tag content results in the following: CODE Before After v1 v2.3+v1 v2.3 v2.3+v1 v2.4 v2.4+v1 v2.3+v1 v2.3+v1 v2.4+v1 v2.4+v1 [context menu]>Tagging>MP3 tag types...>Override ID3v2 revision will force tags to v2.3, or v2.4, whichever you wish. I'm seeing no errors in the console, just lots of "Properties dialog refresh" & "Properties dialog display refresh". Foobar is reporting itself & all components up to date, with the online troubleshooter finding no dodgy components. The only possible reason it could be at my end is that I'm running foobar under Wine, but that has never affected this before. Is a Windows user able to reproduce my findings? |
|
|
|
Jan 11 2012, 11:33
Post
#2
|
|
![]() Group: Admin Posts: 3229 Joined: 30-September 01 Member No.: 84 |
The "force preferred tag writing scheme" is only relevant to the "preferred tag writing scheme" branch, NOT to "ID3v2 revision and quirks". ID3v2 revision is not changed unless explicitly requested by the user, to prevent data loss from 2.3 vs 2.4 specification differences.
-------------------- This job would be great if it wasn't for the users.
|
|
|
|
Jan 11 2012, 15:45
Post
#3
|
|
|
Group: Members Posts: 232 Joined: 28-October 05 Member No.: 25414 |
Thanks, makes sense. I could have sworn foobar used to force v2.4 down to v2.3 with any edit, but obviously my mistake. I'll continue to use Override from the context menu.
|
|
|
|
Feb 28 2012, 04:13
Post
#4
|
|
![]() Group: Members Posts: 492 Joined: 5-January 06 From: Dublin Member No.: 26898 |
Using the current release (1.1.11) and can't seem to find the "Force preferred tag writing scheme" checkbox that once existed under Preferences > Advanced. Am I missing something or has this option been removed?
|
|
|
|
Feb 28 2012, 04:44
Post
#5
|
|
![]() Group: Members Posts: 3340 Joined: 27-January 05 From: England Member No.: 19379 |
QUOTE (http://www.foobar2000.org/changelog) Cleaned up advanced preferences for MP3 tagging (beta 2) “Force preferred tagging scheme” option gone - use the “MP3 tag types” dialog to convert between different tag types. |
|
|
|
Feb 28 2012, 05:16
Post
#6
|
|
![]() Group: Members Posts: 492 Joined: 5-January 06 From: Dublin Member No.: 26898 |
Ugh, that's unfortunate - I found this option to be quite useful!
|
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 19th June 2013 - 18:51 |