Sure—you can set the id3v23 config variable and then invoke something like `beet write -f` to update the tags.
To import without autotagging, use the -A flag. > On Jan 15, 2017, at 5:48 AM, Karcsi Kolbasz <[email protected]> wrote: > > Interestingly I was trying to figure out what was wrong with my tags knowing > I have my config set to use 2.3. > > Last night I stumbled upon issue 1903, which alligned perfectly with my > issue. I did a mass import of my entire library with that version and now > all my tags are incorrectly 2.4. > > So, the real issue is, what can I do? Is there an easy way with beets to > convert from 2.4 to 2.3? I have seen other tools that can do this, but I > don't know what that will do to my beets DB. > > My other thought was if beets can't do it and using another tool breaks the > DB, is there an easy way to rebuild the DB where beets just reads my files > and tags without trying to do any matching, since some things need manual > identification and the last thing I want to do is retag my entire library > since it takes time doing the manual identification. > > Or option 3 is move forward with an empty DB, after fixing them, but I want > to avoid that with hopes beets can do it all for me. > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
