Hee hee, a workaround for the workaround! (Thanks for the creative idea, Stevest!)
I came up with the following »Export« which will actually create a BATCH file to tag all three (BPM, ORIGYEAR and LANGUAGE) into the Music Mixer Database:
Export: Batch file for Music IP Mixer Database Update
$filename("C:\Program Files\MusicIP\MusicIP Mixer\mmm.bat")$loop(%_path%)start "MMMExec updating BPM" /wait /B "C:\Program Files\MusicIP\MusicIP Mixer\mmmexec.exe" -set BPM=%bpm% "%_path%"
start "MMMExec updating ORIGYEAR" /wait /B "C:\Program Files\MusicIP\MusicIP Mixer\mmmexec.exe" -set ORIGYEAR=%origyear% "%_path%"
start "MMMExec updating LANGUAGE" /wait /B "C:\Program Files\MusicIP\MusicIP Mixer\mmmexec.exe" -set LANGUAGE=%language% "%_path%"
$loopend()
As you can see, I preferred directly pointing to both the location of mmmexec.exe and the newly created mmm.bat so that everything has a »defined location" and isn’t dependent on PATH variables or the like. The resulting mmm.bat file can be executed either manually or by selecting »Yes« when MP3Tag Export asks you whether the file should be »displayed«. (Most systems have .bat associated with the command processor.)
Important note: Always specify the »window title« parameter with the START command—otherwise Windows will mess up the parameters given to the executed program!
Still, I very much hope for the above requested feature …
EDIT: Please use with care! I just found out that this will presently not function with file paths containing non-ASCII characters. I have written a feature request asking Florian to implement an export file encoding that is compatible with Batch Files.The good thing is: You can still use the scheme—in a way: Answer »No« when asked for displaying the export file, use an editor that can convert ANSI to OEM codepage to edit the generated mmm.bat file, and then execute it manually. — A workaround for the workaround for a workaround … 