by MMFrLife » Sun Oct 08, 2017 9:40 am
Thanks, but my question isn't about volume leveling itself, it's about the use of "-99999" to clear the volume leveling field.
I use a clearing batch preset with RegExp Find and Replace add-on and it had that field included (I've since taken it out of
the batch). The batch is intended to do a single sweeping clear of all the fields it includes, whether any of them need it or not,
so I don't have to worry about doing any one of them individually.
It clears the track volume field by using "-99999" to clear whatever is its current state. It seems that when this is done,
it causes a synch problem with that field when applying the Unsynch'd files check.
Isn't "-99999" an MM thing (not an add-on issue)? If so, why do those files not show as synched?
If I reconvert the files to the same specs, it corrects the issue.
As previously mentioned, I've taken that field out of the batch and there is no longer an issue when performing
Unsynch'd files.
Thanks, but my question isn't about volume leveling itself, it's about the use of "-99999" to clear the volume leveling field.
I use a clearing batch preset with RegExp Find and Replace add-on and it had that field included (I've since taken it out of
the batch). The batch is intended to do a single sweeping clear of all the fields it includes, whether any of them need it or not,
so I don't have to worry about doing any one of them individually.
It clears the track volume field by using "-99999" to clear whatever is its current state. It seems that when this is done,
it causes a synch problem with that field when applying the [i]Unsynch'd[/i] files check.
Isn't "-99999" an MM thing (not an add-on issue)? If so, why do those files not show as synched?
If I reconvert the files to the same specs, it corrects the issue.
As previously mentioned, I've taken that field out of the batch and there is no longer an issue when performing
[i]Unsynch'd[/i] files.