David Nahmani Posted December 16, 2021 Share Posted December 16, 2021 Unless it appears in a change log as fixed, it is not fixed Actually there have been many bug fixes that were not listed in any release notes. The most helpful thing you can do if you encounter this issue again would be to share a project where this happens so we can reproduce the issue and even possibly forward it directly to the Logic team if we can reproduce it. Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 16, 2021 Share Posted December 16, 2021 Thanks again, David. In addition to that, the original bug is *obviously* fixed as I can reproduce it 100% in 10.4.8, but exactly 0% in 10.6.1. But I'm repeating myself... Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 16, 2021 Share Posted December 16, 2021 How would having a project help? - I can't see how A video might - maybe I'll make one Having a project might help to understand the cause. And thanks in advance for a video! Might clear things up, I hope. Quote Link to comment Share on other sites More sharing options...
facej Posted December 16, 2021 Share Posted December 16, 2021 NB It has been my experience over many versions of Logic that the Normalize Region Gain function will make no adjustments to regions that have a level of 0.0 (like many normalized tracks one might get). The regions just stay at 0.0. If you adjust the gain of the underlying audio file and reduce it by a tiny amount (no longer 0.0) the Normalize Region Gain will adjust. Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 16, 2021 Share Posted December 16, 2021 NB It has been my experience over many versions of Logic that the Normalize Region Gain function will make no adjustments to regions that have a level of 0.0 (like many normalized tracks one might get). The regions just stay at 0.0. If you adjust the gain of the underlying audio file and reduce it by a tiny amount (no longer 0.0) the Normalize Region Gain will adjust. That is exactly the bug that is fixed in 10.6.1 already, so I'm wondering if you still experience it (as from your signature your're on 10.6.3 already)? If so, an example project - or steps how to reproduce this - might help, also to clarify what Cocker reports. FWIW I can not reproduce this in 10.6.1 or later versions. Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 16, 2021 Share Posted December 16, 2021 Here's two videos to show the difference between 10.4.8 and 10.6.1 1 Quote Link to comment Share on other sites More sharing options...
facej Posted December 16, 2021 Share Posted December 16, 2021 I haven't run in to any tracks shipped to me with 0.0 levels, so hadn't realized the "no change" bug was fixed. As I watch your video, number 2 in particular, I can't quite see what is wrong. After Normalize Region Gain the Gain field in the region inspector should have the offset value that is applied to assure the peak gain of -6. I have no expectation that any of the gain offsets will be the same on a region to region basis. Are you expecting the Gain value for the region will be -6 for the region? or that the gain adjustment will be the same for each region? Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 16, 2021 Share Posted December 16, 2021 I haven't run in to any tracks shipped to me with 0.0 levels, so hadn't realized the "no change" bug was fixed.As I watch your video, number 2 in particular, I can't quite see what is wrong. After Normalize Region Gain the Gain field in the region inspector should have the offset value that is applied to assure the peak gain of -6. I have no expectation that any of the gain offsets will be the same on a region to region basis. Are you expecting the Gain value for the region will be -6 for the region? or that the gain adjustment will be the same for each region? Nothing's wrong in the second video. That's from 10.6.1 (the fixed version). I thought that was clear from the GIF's name. In the first video, recorded from 10.4.8, the "Clipped" regions (which definitely peak at 0.0dB) don't change their gain, even though I used a level of -6dB for Normalize (so a clipped region should end up at -6 dB region gain) So maybe you could try and check with a file with a peak level of 0.0 dB if the bug is fixed for you as well? Quote Link to comment Share on other sites More sharing options...
JakobP Posted December 16, 2021 Share Posted December 16, 2021 Fwiw, it works fine here, so seems it was fixed in 10.5... 1 Quote Link to comment Share on other sites More sharing options...
Nola111 Posted February 15, 2022 Share Posted February 15, 2022 I hate to have to revive this thread once again, but I am now having issues with Normalize Region Gain as well. I am on 10.7.2. Just so there is no ambiguity around what one person assumes this function should be doing vs reality - I watched this video: and that is exactly how I'm expecting NRG to work, yet it's not doing so in the test I'm running. To keep it simple and remove as many variables as possible, I am using just one track with one region on it. It's a kick drum track - before applying any gain normalization, the track is peaking around -30dB (fader set to unity) - I attempt to apply Normalize Region Gain with the algorithm set to Peak, and the target set to -18.0. The result - the gain does change, but the peak value is -22.0?? So it seems to be off by 4dB. If I set the target of NRG to -14.0, well then I get my desired peak of -18.0. I don't understand why this is happening. Why doesn't it work the way it works in the video and just give you what you ask for ? What I'm experiencing isn't as far off as what others in this thread have experienced (where there is no effect at all), but I can't argue with the fact that something about this functionality isn't doing what we would expect it to do. Note that I tried using all three options for Affect, and they all yield the same result. Quote Link to comment Share on other sites More sharing options...
polanoid Posted February 15, 2022 Share Posted February 15, 2022 (edited) Did you try and (destructively, so better use a copy of the file) normalise the file in the Audio File Editor, to ensure the peak is really -30dB? (In Functions-> Function settings... set Normalize Peak at -30db, then Normalize - if I'm thinking correct it should leave the file unchanged then) Edited February 15, 2022 by polanoid Quote Link to comment Share on other sites More sharing options...
Nola111 Posted February 15, 2022 Share Posted February 15, 2022 Hi Polanoid - good to see you hop back in here - I have not tried that, but I certainly will give it a shot and see what I come up with. Thanks! Quote Link to comment Share on other sites More sharing options...
polanoid Posted February 15, 2022 Share Posted February 15, 2022 Hi Polanoid - good to see you hop back in here - I have not tried that, but I certainly will give it a shot and see what I come up with. Thanks! Note that I edited my post, my first proposal was much too complicated Quote Link to comment Share on other sites More sharing options...
Nola111 Posted February 15, 2022 Share Posted February 15, 2022 polanoid said: Note that I edited my post, my first proposal was much too complicated Sounds good, thanks. I'll report back my findings - I will say however that I've now experimented with ALL tracks in my session, and for all of them, if I use NRG and put in a peak -14db, they all peak at around -18db. Very odd. Quote Link to comment Share on other sites More sharing options...
Cocker Posted February 16, 2022 Share Posted February 16, 2022 Did you try and (destructively, so better use a copy of the file) normalise the file in the Audio File Editor, to ensure the peak is really -30dB? (In Functions-> Function settings... set Normalize Peak at -30db, then Normalize - if I'm thinking correct it should leave the file unchanged then) 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 Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 16, 2022 Share Posted February 16, 2022 Polanoid is talking about the Audio File Editor; The functions you use there are "destructive"... Quote Link to comment Share on other sites More sharing options...
Cocker Posted February 16, 2022 Share Posted February 16, 2022 Polanoid is talking about the Audio File Editor; The functions you use there are "destructive"... 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 Quote Link to comment Share on other sites More sharing options...
JakobP Posted February 16, 2022 Share Posted February 16, 2022 You still seem to be talking about the Audio TRACK Editor, not the FILE editor. In the edit window/pane, click the tab "File" to get to the Audio File Editor. Quote Link to comment Share on other sites More sharing options...
Cocker Posted February 16, 2022 Share Posted February 16, 2022 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 Quote Link to comment Share on other sites More sharing options...
polanoid Posted February 17, 2022 Share Posted February 17, 2022 Did you try and (destructively, so better use a copy of the file) normalise the file in the Audio File Editor, to ensure the peak is really -30dB? (In Functions-> Function settings... set Normalize Peak at -30db, then Normalize - if I'm thinking correct it should leave the file unchanged then) This is exactly the same operation Nola111 is already describing No. Quote Link to comment Share on other sites More sharing options...
polanoid Posted February 17, 2022 Share Posted February 17, 2022 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 What I was proposing was a way to find out what the real peak of the audio file is, using the Audio *File* editor, in case you don't trust the (nondestructive) Normalize Gain function for whatever reason. Also, the Audio File editor will not "only normalise to 0 dB". You can set the peak level it normalises to in the Audio File Editor menu, Functions -> Function Settings... dialog. Quote Link to comment Share on other sites More sharing options...
benwaddi Posted May 9, 2022 Share Posted May 9, 2022 On 12/14/2021 at 12:20 PM, Cocker said: 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 About 5 months later, seems like this issue is still relevant in logic pro, it happened to me just now and also happened to a classmate a few days ago. HOWEVER if ^⌥G didn't work, ⌥⇧P would work. At least, that's what happened in my experience. ⌥⇧P opens the "Selection Based Processing" menu which has a normalization feature within it. It's just a slightly different menu where you can do more than normalization. However, you cannot chose between RMS and peak normalization and you can't set the target, but I'm guessing it's peak normalization with a target of -1 dB. Quote Link to comment Share on other sites More sharing options...
polanoid Posted May 10, 2022 Share Posted May 10, 2022 (edited) 13 hours ago, benwaddi said: About 5 months later, seems like this issue is still relevant in logic pro, it happened to me just now and also happened to a classmate a few days ago. HOWEVER if ^⌥G didn't work, ⌥⇧P would work. At least, that's what happened in my experience. ⌥⇧P opens the "Selection Based Processing" menu which has a normalization feature within it. It's just a slightly different menu where you can do more than normalization. However, you cannot chose between RMS and peak normalization and you can't set the target, but I'm guessing it's peak normalization with a target of -1 dB Please attach a screenshot of the settings you enter in the dialog box that pops up when you use the ^⌥G key command. I have not found Logic behaving incorrectly regarding this command yet. The normalization happening in "Selection Based Processing" is not the same because it is destructive, it doesn't use Region Gain. Which Logic version are you using? Edited May 10, 2022 by polanoid Quote Link to comment Share on other sites More sharing options...
matchewy Posted December 2, 2022 Share Posted December 2, 2022 I was having this same issue too (10.7.5). Only way I could get around this..... :: drum roll :: instead of entering the target level value via the keyboard, I used the little arrows next to the value and then it finally worked. 1 Quote Link to comment Share on other sites More sharing options...
MrDarcy Posted December 24, 2022 Share Posted December 24, 2022 On 12/2/2022 at 11:30 AM, matchewy said: I was having this same issue too (10.7.5). Only way I could get around this..... :: drum roll :: instead of entering the target level value via the keyboard, I used the little arrows next to the value and then it finally worked. I have been stuck on this issue for the past hour and this is the only solution that worked for me, very strange, but yes, when i manually use the mouse to enter the desired DB, it works! when i type in the desired number, it does not. Funny. 1 Quote Link to comment Share on other sites More sharing options...
rAC Posted December 25, 2022 Share Posted December 25, 2022 Have you logged this with Apple? Quote Link to comment Share on other sites More sharing options...
polanoid Posted December 25, 2022 Share Posted December 25, 2022 On 12/2/2022 at 4:30 AM, matchewy said: I was having this same issue too (10.7.5). Only way I could get around this..... :: drum roll :: instead of entering the target level value via the keyboard, I used the little arrows next to the value and then it finally worked. After entering the target level via keyboard, you can also press the Return key to make Logic use the entered value. The bug, it seems, is that the entered value is not taken over when you simply enter it and then click "Apply". Easy to work around though. Quote Link to comment Share on other sites More sharing options...
Steve Kudlacek Posted February 14 Share Posted February 14 (edited) I read quite a few threads on this site, most of them are helpful. This thread was far too long and filled with an embarrassing amount of unnecessary banter for zero reason. i too have experienced this same problem of late. And I appreciate the people who were attempting to be helpful… Edited February 14 by Steve Kudlacek Incomplete Quote Link to comment Share on other sites More sharing options...
polanoid Posted February 14 Share Posted February 14 2 hours ago, Steve Kudlacek said: I read quite a few threads on this site, most of them are helpful. This thread was far too long and filled with an embarrassing amount of unnecessary banter for zero reason. i too have experienced this same problem of late. And I appreciate the people who were attempting to be helpful… Could you describe what happens exactly (e.g., which settings do you use for Normalize Region Gain) so people can help you better? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.