XXHighEnd

Hey Peter,

I wanted to normalise some selected music overnight but it did not work out as expected. I received an error and the process stopped and waited until I click on OK...

This means that I have to monitor the process and have to click the message before it proceeds.

Any idea how it can show me the errors on a created list and skip that track/album without stopping the progress?

Bert

Bert, that could be a tough one;

A message like this exists in many more types and they spring from somewhere far under the hood and should not occur when all lis right, but they do because it just *is* not all right (meaning : that can't be, sure also not for myself here).
The only "solution" in such cases is eventually knowing what kind of messages can occur for a specific (automated !) procedure (which should go all automatic) which next can be a. captured so they are not shown and b. are turned into Log Entries which can be observed afterwards for the same messages and data they apply to.
Good example for past changes in the same realm is the copying of albums or obtainment in Galleries; you could go crazy from the many iterations it took before all was error free (and the data just *is* erroneous in such occasions). But slowly though certainly with enough data to pass through such function finally all messages occurring could be eliminated and turned into Log Entries. And indeed, now I can press a button at night and the next morning all will have been done. Well, not quite, because all which couldn't be done wasn't obviously. And don't you think I will ever sit down to correct the data.

At least I agree that this doesn't quite "work";
First thing to do is that I normalize all my own albums, so probably I will run into all the messages which can popup.

Sorry for the too long story.
Peter

I am used to that...  :)

Another one related... if the normalisation was interrupted (user or fault) will it check for already normalised albums?

Bert

Yes. So it will sort of skip them (goes way faster over those done already.

Peter


PS: But I will apply the run on my own albums hopefully soon, so maybe wait for that (and eliminating hopefully all the possible messages).

Peter,
most albums are processed without problems. For the albums with error message we (Bert and I) found that this happens when the Normalisation is started through the Library panel (selecting the album, rightclick etc.). However, when starting to play the same album with Normalisation activated, all goes well and no error occurs. Hope this helps.

I also noticed that Normalisation does not work for WAV tracks that have been converted from m4a format. But this is a different issue.

Cheers,
Eric

Hey Eric, super.

Can you send me two of these from m4a converted tracks ?
Thanks,
Peter

After all albums are Normalized using a certain album as reference it would be convenient if all work not has to be done again if I another album is going to be used as reference.

Is this the case or do we need to re-normalize all albums again?

Bert

Bert,

I didn't check it really, but Normalizing with another album as the reference won't matter for the generated data. What will (or should happen I think) is that when you set another album for reference, the difference between your set Volume and the created Volume (at the right side) will change. But all in linear fashion (so if one album's generated Volume is now 1.5dB higher, all the others should be 1.5dB higher as well).
Just try it ?

And regenerating the data isn't even possible at this moment, unless you delete the XXAnalysis.dat files.

Regards,
Peter

Cool, if it does not matter for the generated XXAnalysis.dat files then its okay and the normalized process does not have to be repeated.

I can then also play any Album brought and normalized by others using my own reference.

Bert