RealSkyDiver Posted September 17, 2011 Share Posted September 17, 2011 I'm currently dealing with a huge Logic bug. Basically whenever I listen to a project I hear a remnant of some reverb from a part that I previously listened to and I can't find a way to get rid of this. That makes a clean bounce completely impossible since there will always be that annoying reverb-remnant at the begining of the track that's not suppose to be there Link to comment Share on other sites More sharing options...
ski Posted September 17, 2011 Share Posted September 17, 2011 Start your track one measure before the actual start of the song, then stop immediately. You may hear a burst of reverb or other artifact. Let it die out. Then repeat the procedure one or more times until you no longer hear any artifacts at the top. Then bounce as normal. Link to comment Share on other sites More sharing options...
RealSkyDiver Posted September 17, 2011 Author Share Posted September 17, 2011 Yeah I did that but isn't there a fix for this? A DAW like Logic should not have this bug if even FL Studio doesn't struggle with it. Link to comment Share on other sites More sharing options...
ski Posted September 17, 2011 Share Posted September 17, 2011 This has been an ongoing problem with Logic for YEARS. My personal feeling is that the developer doesn't think it's a high-enough priority to fix. Or maybe they've tried, but found that the problem is unfixable but they just haven't bothered to communicate that to end-users. From reading posts and articles and blogs online by some 3rd party developers whose wares sometimes bear the brunt of user frustration with this problem, Apple points the finger at them, and they turn around and point the finger at Apple. Not sure what you can do other than write to Apple/Logic feedback and complain. And if the reverbs in question are 3rd party plugins, write to the developer. In the meantime, you have a workaround, as much of a PITA as it is. Oh, and you are not alone. So maybe there's a little solace to be taken in that. Link to comment Share on other sites More sharing options...
RealSkyDiver Posted September 17, 2011 Author Share Posted September 17, 2011 Thanks for the write up. I'm currently experience that problem with the play-engine by EWQL. Link to comment Share on other sites More sharing options...
ski Posted September 17, 2011 Share Posted September 17, 2011 I'm getting the same behavior with Play, fwiw. The only thing I can say is that overall, this behavior we're talking about is better than it was. Compared to running 3rd party plugs on my old system ( G5 PPC, 10.5.8 ), there's a 1000% improvement, but that the problem exists at all makes me (us) go Link to comment Share on other sites More sharing options...
fader8 Posted September 17, 2011 Share Posted September 17, 2011 Compared to running 3rd party plugs on my old system ( G5 PPC, 10.5.8 ), there's a 1000% improvement, Glad to hear Apple improved their end of it. That still doesn't let the 3rd party plug-in developers off the hook. They still need to respect the audiounitreset call, which flushes the plug-ins own buffer.. If they don't, then the ball is squarely in their court. RealSkyDiver, this old thread will give you some background on this problem. http://www.logicprohelp.com/viewtopic.php?t=43306 Link to comment Share on other sites More sharing options...
shivermetimbers Posted September 17, 2011 Share Posted September 17, 2011 http://www.logicprohelp.com/viewtopic.php?p=365396#365396 Link to comment Share on other sites More sharing options...
Jordi Torres Posted September 17, 2011 Share Posted September 17, 2011 http://www.logicprohelp.com/viewtopic.php?p=365396#365396 Logic Porridge...healthy! J. Link to comment Share on other sites More sharing options...
camillo jr Posted September 17, 2011 Share Posted September 17, 2011 Yup, oooold problem. I suspect that fixing it would maybe cut into Logic's famed CPU efficiency. My workaround is to play about 3 seconds from after the last region in the song before every bounce. A while back someone suggested hitting play twice in quick succession over a non-region area would clear the buffer but that hasn't worked for me. I'd be happy if apple implemented a simple purge button right in the GUI, if CPU efficiency was at issue or any other thorny coding problem. AND / OR, making the purge function a part of the bounce, so that it would happen automatically. I could live with the occasional reverb blip while I'm working if that was in place. Link to comment Share on other sites More sharing options...
ski Posted September 17, 2011 Share Posted September 17, 2011 That still doesn't let the 3rd party plug-in developers off the hook. They still need to respect the audiounitreset call, which flushes the plug-ins own buffer.. If they don't, then the ball is squarely in their court. Hey Fader8, Wondering if you could shed some light on why plugin developers wouldn't implement that call. And here's why I'm asking... Looking at the preponderance of the evidence -- innumerable reports of 3rd party plugins exhibiting this problem -- it would appear that there's something about Logic that makes it difficult for so many plugin developers to implement such a call. Otherwise they'd do it, yes? No? Discuss! Link to comment Share on other sites More sharing options...
fader8 Posted September 17, 2011 Share Posted September 17, 2011 Hey Fader8, Wondering if you could shed some light on why plugin developers wouldn't implement that call. And here's why I'm asking... Looking at the preponderance of the evidence -- innumerable reports of 3rd party plugins exhibiting this problem -- it would appear that there's something about Logic that makes it difficult for so many plugin developers to implement such a call. Otherwise they'd do it, yes? No? Discuss! Because Logic is the only DAW that actually requires it. So apparently it gets overlooked until enough Logic users complain about it. It's not difficult to implement, at least not in the original authoring of the plug-in, but some developers are pretty stubborn about going back in and making a change like that. Particularly if they haven't documented their work well. Or the guy that originally coded it didn't document anything and he no longer works there! It's up to each plug-in to flush its own buffer. Apple's code can't reach into the plug-ins code and do that. It can only send the instruction to do it and depend on the plug-in to flush the buffer in response. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.