Feel free to submit your feedback to Chevrolet, Subaru, Cadillac, Lexus and Maserati since out of all those vehicles I own, one of which has an aftermarket Pioneer headunit, not a single one uses the "AlbumArtist" field when displaying tracks. They all use Artist, Title and Album. It's a nuisance for me since the Apple devices I use do utilize the Album Artist field. But if I add a track to my library that doesn't have the AlbumArtist field populated and I forget to fill it in, then I get duplicate artists showing on the Artists screen. So it's basically a nuisance for me to have it and just easier to eliminate it altogether. It's not like it's a hard field to repopulate in the future if I really wanted to seeing as how all my music is organized in "Artist\Album..." folders. I could easily tag that field using my folder structure.
There's no way that's true and if it is, then there are some coding issues that need to be addressed. I've tested this multiple times and the results are repeatable every single time. I could upload a screencapture showing the process if need be, but this is very easy to reproduce if you'd like to test for yourself.
Source Files: 88 AAC tracks totaling 1.03GB
- Copy all source files to RAM Disk.
- Drag & Drop all the source files into Mp3tag.
- Select All > View > Extended Tags > Delete AlbumArtist > OK
- I get a "Writing Tag Data" popup with a progress bar and takes ~4 seconds to complete.
- Delete files from RAM Disk.
- Copy all source files back to RAM Disk.
- Drag & Drop all the source files into Mp3tag.
- Actions > Actions (Quick) > Remove fields > AlbumArtist > OK
- I get a "Writing Tag Data" popup that flashes so quick, I actually had to screen record the process because it happened so fast and I wanted to verify that it was the same popup window as before.
I repeated the exact same process above four times in a row and got the exact same results every single time. Using the "Extended Tags" to delete fields is SIGNIFICANTLY slower than using "Remove Fields". Note that I used a RAM Disk to rule out any latency or disk caching. But just to be sure, I even tested the same process with the files copied to an SSD and also on a HDD. My conclusion is that this has nothing to do with caching or anything like that. Feel free to test for yourself and you'll see what I'm talking about.
I tested with both FLAC and AAC files. The results were the same regardless of file type used.