Stm.mitchell

That´s it! Thanks!

There’s loads of great auv3 samplers and granulators on the iOS App Store. Prior to Logic Pro I used AUM. I loved the simplicity of loading them up, recording something into them with the iPad microphone and then routing midi to the instruments to start playing with the recorded samples immediately. Some examples of the apps I’m talking about would be Samplewiz, FRMS, Spacecraft, ELSA etc. How can I achieve something similar (if at all possible) in Logic Pro? If I load the plugins as effects on audio tracks I can’t use the play surfaces, and if I load them on instrument tracks I can’t record into them.

Wow! Thank you Jeff! I have had major issues with Alchemy in particular, but also various other parts of Logic as outlined here viewtopic.php?f=1&t=128953&hilit=alchemy. This workaround makes Alchemy, and Logic in general, snappy again. I wonder what it does exactly, I can't see any difference in colour on my screen?

Thanks for sharing kelvin. I must say I find the knowledge of these so called "Logic experts" at Logic support questionable. You´re not supposed to adjust Alchemy´s parameters while Logic is running? One instance of Alchemy causes a 2016 MBP fans to run at full speed is normal?! I also find it strange that he goes on to tell you it´s because Logic isn´t fully optimised with the new MBP. I´m experiencing the exact same issues you describe, but on a late 2015 iMac. With macOS 10.12.4 now in beta, I hope the issues will be fixed once it goes live.

I got a call back from support today. My case has been closed. He told me engineers are investigating the problem, but could not give a timeline for when a possible fix would happen. I was recommended to run Logic in low resolution mode in the mean time. I must admit I find that slightly provoking, but I´m guessing it´s not a widespread problem so probably very low on their priority list.

Same over here.

I haven't heard anything yet. I was hoping the issue had been resolved in 10.3, unfortunately it´s still the same. The person I spoke to on phone support could confirm the bug on his late 2016 mbp 15". On my iMac Logic and Alchemy works as expected when opened in low resolution mode, it looks terrible though.

I have the same issues on my system, outlined here viewtopic.php?f=1&t=128953&hilit=Alchemy. In addition to what you're mentioning, adjusting all other knobs/parameters in advanced mode is difficult/impossible because of the lag. While Alchemy is open the problem manifests in other parts of Logic as well. Logic meters, resizing windows etc. I have been in contact with apple support, who after having me test various things on my iMac (reinstalling Logic, macOS etc) could confirm the bug on a new (late 2016) MacBook Pro. My case has been "escalated" (not sure what exactly this means). You can try opening Logic in low resolution mode. This works on my system. Doesn't look very good though. The support rep I spoke to recommended using this link http://www.apple.com/feedback/logic-pro.html and letting them know you are affected by the bug. If you are registered as a developer you can also file a bug report at bugreport.apple.com

Just thought I´d give an update to this in case others are having the same issue with Alchemy. I have been on phone support the last two days. First local Apple support here in Norway (who had never even heard of Logic), then directly with Logic support (in Ireland I think?). We´ve been through the basic stuff. Trashing prefs, signing in with an other account, switching audio devices etc. We´ve tried reinstalling Logic, and today we tried reinstalling macOS. Nothing has worked. The only thing we found that remedies the issue is to start Logic in low resolution mode. But that defeats the purpose of getting a high screen resolution Mac... My case has been "elevated", not exactly sure what that means but hopefully it will get sorted out soon. Maybe through an update to Logic? Seems a lot of people are experiencing GUI lag issues with Logic and high resolution monitors. I´ll update again when I hear back from support.

Hi David, all content is finished downloading. I´ve only installed one other plugin so far, Omnisphere. Never had a problem with Omnisphere though. Playing more with Alchemy now; the GUI lag only happens in advanced mode. Audio is not affected. Parameters react roughly .5 seconds after I´ve adjusted them. It´s almost impossible to do fine adjustments because of the lagging. Bummer. Never had problems like this with Logic before.

Got a new iMac 5K and I just finished setting up macOS, and downloading Logic along with all its content. I'm experiencing issues with Alchemy. Whenever I switch it over to advanced mode the gui of Alchemy and Logic itself slows down and becomes sluggish. The other modes work fine. Removing alchemy restores Logic to normal behavior. When in advanced mode turning knobs is almost impossible due to the sluggishness/lag. Has anyone else experienced something similar?

Hit the little cogwheel in the transport display and select "Custom". Try searching for "Division".

Forgive me for bringing this up again, but I´m still struggling and would appreciate some help. Imagine I have 5 tracks with found sound. I use Logic´s arrange page to cut out the parts I want and end up with a bunch of small regions. Now I´d like to load up the regions, with their names intact, in Ultrabeat or Battery to make a drum kit out of them. I have been trying a few different ways, but they all seem very clunky. I can export said regions to new audio files but that gives them generic names like "Audio #1, Audio #2" etc. Another issue I have is if I convert the regions to new audio files and save them in either the project folder, or the new "Package" file, Ultrabeat is unable to see the files?!

I must be getting to used to Live. Thanks for clearing that up

It's been a while since I used Logic but I seem to remember that I could drag and drop regions from the arrange page to VI's. In Logic Pro X I've tried dragging regions to Ultrabeat (using the Drag & Drop preset) and Battery but I can't get it to work. Am I simply remembering wrong