Unique 'last used' settings for Match Loudness and Batch Process
My workflow uses Match Loudness to generate WAVs and Batch Process afterwards to generate MP3s. But they share the same 'last used' settings as each other, so I have to change back to MP3 every time I use Batch Process, and change back to WAV every time I use Match Loudness. Can they have their own 'last used' settings memory?
1
vote
Eddie Adams
shared this idea