1 In an Action, include an Export using $filename(xxx)
2 In the .mte file, change xxx to yyy
3 Run the Action
Expected: Export output file is yyy
Observed: Export output file is xxx!
It seems Mp3tag is using the $filename() value current at the time the Export dialog box is closed, failing to read it at the time the .mte is actually executed upon the Export.
This is the expected behaviour to respect changes made by the user to the pre-filled output filename (which would be discarded if the filename is build at the time the export is executed).
Yes, after a change in the export script you have to close and re-open the export dialog to refresh resp. to clear the quirky situation.
This is the expected behaviour to respect changes made by the user to the
pre-filled output filename (which would be discarded if the filename is build
at the time the export is executed).
OK... but then I have to say I think it could do a better job. In this case the script's change is blocked even though there is no user's change. This can lead to error and is unexpected because of the hidden change in significance of the script filename.
I suggest the best solution would be to have no blocking - i.e. if/when there's a script change, it goes to the output filename. And when/if there is a user change, it too goes to the output filename.
But Iaccept that probably few use this, and it should be low priority.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.