Cocker

You end up at the same place more or less. It will only normalise to 0 dB which in practice is no different from normalising using the track tab and you can still manually adjust gain by +/- 30 dB in the inspector

Yes and you are both wrong in the case of the Normalise Gain parameter Drag in an audio file or record a new one Open it in the Editor Apply Normalisation to 0dB for the sake of argument (you cannot normalise above 0) Now select the region and inspect it in the region inspector Edit: Actually you can normalize above 0dB if you use LUFS - but it doesn't destructively alter the waveform and you can still use the inspector to return to the original gain This will tell you how much gain was added to normalise to 0dB and you can adjust it even further from here If it was destructive - you would be able to adjust beyond clipping and not go back In simple terms the Normalise Gain function just adjusts the region gain via the parameter in the region inspector You still need to flatten or bounce to a new file to make the changes permanent

This is exactly the same operation Nola111 is already describing Physically navigating to the Normalise Gain function will not make any difference over using the keyboard shortcut - they lead to the same menu item The Normalise Gain function is also non-destructive by its very nature - you can continuously change the gain of any region at any time It only becomes destructive if you bounce to a new version of the file or consolidate it to a new one

See for yourself https://support.apple.com/en-ie/HT203718 the bug was reported two years ago in the thread It doesn't appear in any change log

Unless it appears in a change log as fixed, it is not fixed Details on how to reproduce it provided several times over at this stage The bug I'm describing matches the one the thread is about - how could it possibly be a different bug? That you can't find it just means that you just haven't encountered it yet How would having a project help? - I can't see how A video might - maybe I'll make one

I've explained at least twice how to reproduce it and so have others much earlier on in the thread In case you missed it several times already - you select multiple audio regions in your project - use the: Ctrl+option+G shortcut - choose: Individual Regions, Peak and whatever Target Level you like and click "Apply" What this shortcut should do is analyse the peak amplitude within a region and normalize that region to the Target amount you specified set in the Normalize Gain dialogue box. It does do this but it also often bugs out and randomly doesn't normalize some regions You have to use it an awful lot and repeatedly to encounter it I wasn't expecting the bug to be fixed. I wasn't looking for help either. I was simply pointing out that it was still a bug two years after this thread was published

Check the title of the thread or did you forget what we were talking discussing in the first place?

You didn’t discover it as a bug in 10.6.1 because even in my own experience it’s completely random. You could easily have spent hours trying and found nothing except confirmation of your own preconceptions Just because you didn’t find it does it mean it’s not there Absence of evidence is not evidence of absence

Yes I use it hundreds of times a day If it helps I have noticed that it happens most when I have split one region into two or more separate regions I can highlight these regions - hit the shortcut - select individual regions - Target level: 0 dB Quite often it will only normalize some of the highlighted regions - which I then have to go back and do manually Always check !

Yes of course I meant to say 10.6.1 - how completely absurd (and rude) of you to question whether I can count What makes you think everybody runs a system that supports the most current versions of Logic ?? My work mac does not run anything later than Catalina and therefore LPX 10.6.1 is the most recent version I can avail of currently The settings are correct - Affect: Individual Regions - does not always affect individual regions You obviously don't use it a lot, but I do and in certain cases it randomly doesn't affect some of the selected regions So it has probably worked for you the one time you had tried but that is not how you find a known bug - by trying to replicate it once Try using it hundreds of times a day - you will probably find it is still a bug even in latest versions of Logic The likelihood is that if it was a bug two years ago and is still a bug in 10.6.1 - well then it is probably a bug in 10.7.2

Two years later... I've encountered the same issue in Logic 10.6.1 Key command [ctrl+option+G] You should be able to auto normalise any number of selected regions to a set level but it works only on some random regions but not others You then have to go find the regions that it didn't work on and adjust these manually in the region inspector Still not fixed - It's a niche issue that barely anyone would notice but it's still there Most logic users I've met do not even know this key command exists - it would be amazing if it worked as expected

No. None. It's a work computer. Several of them in fact. No trace of Steinberg anywhere This is still ongoing as of now. Every once in a while a .mre file turns up in the same location and with the same name as my bounced audio

At work I bounce audio to a Network drive Recently and quite at random a .mre file has been showing up alongside my bounced audio Has anyone else experienced this or know how to stop it? Running latest Logic version

Not a new feature. Happens when there's no Prelisten audio object on track 256. Check the Environment window and look for the Prelisten track that should have the solo-safe enabled when that track exists. If you don't have one you have to create it, otherwise it will show up on every highest number track you create. Or you enable it by Control clicking the Solo button. The Logic basic new template has it. New in so far as the old keyboard shortcut I used to disable it was completely changed and the default way in which it was implemented was also changed

Ah ok. Thanks. This solo-safe is obviously a new feature of the mixer then. I use Logic at work. The computer auto updated over the weekend.