ReplayGain

[golke53]

In dbpoweramp there are 2 options for replaygain: 1. "replaygain apply" and 2. just replaygain. I have always been double cautious not to do the apply thing because this would have changed the files instead of just adding tags.
I did create always both, Album and Track in the same conversion.
After the recoding I have always checked the replaygain tags with mp3tag and could conclude that if the tags were written the run was mutually exclusive to the apply function (unless dbpoweramp has a major bug, I don't believe). A way to check is to just do a recode with the same settings twice and then the tags in the 2nd run would be big time different from the first. This has not been the case so far.

Your example of just above 5 minutes for 500+ files I cannot match but my PC is not the fastest. I always do rewrite to the same location instead of creating a copy on a new folder. In theory it should be faster since it uses my 4 CPU cores simultaneously but while the conversion runs I can observe that most of the time 2 of the 4 processes are in a wait state, probably waiting for the tag write to disk which requires an exclusive lock on the disk track(s) in question.

The 10 seconds per song appears a bit too much. For 500 this implies 5000 seconds devided by ,, hmm 4 cores means 1250 seconds or a bit more than 20 minutes. I just tested a batch with 400 of alreaded recoded records and it took 10 minutes. Sure the software does recalculate the gains but the tag values in both were the same. All that looks fine.

I am now on dbpoweramp rel. 17 and 3 years ago it may have been rel. 14 or 15 and therefore I have no way to prove anything unless I downgrade the software. But that is not worth the effort for the handful of exotic tag values that were easy to correct and not difficult to find.

The new options in dbpoweramp regarding DSP setting make a lot of sense to me and even in the batch processing I found a new option that would allow to skip the "finish" message which has not been the case before. It happened often in the past that the process did not come to conclusion even after all files were done but the process was stuck in a state named "finalizing DSP effects". In that situation all I could do was to cancel and then the backout of all previous changes took place and lasted, and lasted.
I assume the problem was not only my single user problem and so the Illustrate guys invented this new option.

Good talk mate. Thanks for engaging.