Hmmmm what can i say to that... it is my passion to change the original as little as possible when processing, so typically when applying a normalize, i do this only in order to fulfill some strict requirement that has been written down to paper and we are contracted to deliver exactly this and that values. E.g. EBU R128 allows +-1db for raw stuff like live and news or such but -+0.3db for films and series. Do you really not have a clear and exact goal to fulfill here?
In case this is only for scientifical interest, i would probably gather some more infos about the "why first pass normalisation is not exact" and probably even come up with a workflow that outputs always guaranteed -12db... Just let me know your goal.
Yeah using variables makes you very mighty
Regarding the some 1.3 build for testing, i fear it is not yet ready for it or better we are not yet ready for it. What you would get is "under construction", so it would not make sense to report any bug that you find because the devs are most likely aware of it anyway... You could not make any difference between stuff that is currently under construction and real bugs. I fear it will take some more months until we are at a point where it makes sense to give it away for testing. Even then we dont yet have any procedure or plan for user testing of betas... it is something we need to work out definitely.
Anyway, if you desperately want to test the first workflow to be able to compare the results to the second one, let me know and i will come up with a patch for processors.a3x which allows you to do so.
