hwatt

PLEASE IGNORE. simple mistake. 'Cycle On' in recording settings needed to be set to 'Merge' DOH

Hi. I have a summing stack set up for my drums (using Battery 4) with each pad in Battery outputting to separate channels. I can play the full kit on my midi keyboard, no problem. However, when I hit record, and try and record a HiHat track over the pre-existing kick track (43:35 in YouTube video) it creates a duplicate track instead of merging with the pre-existing recording. I've tried changing the recording settings, I don't know what I'm doing wrong. Are my recording settings wrong? (see photo) Cheers

hey, sorry for the insanely late reply. ok, I will try this when and if I come across this issue again.

Hi, I will try to keep this short and concise. So, I have a guitar track. It's a 4 bar loop. It repeats throughout various sections of the composition. I just cut the last 1/4 note section of the loop during a particular part of the song (the break), and reversed the audio of this particular section. It's now reversed that particular section of the loop but for every instance of the loop on that track! I hope that makes sense. It's essentially copied that procedure and applied it to every single bit of recording on that track. I have no idea how to fix it. I've tried 'undo' but it doesn't seem to want to go back on the procedure. What I did was the following: 1. Cut out the particular section of the loop 2. Double clicked, and clicked on file in audio editor. 3. Click functions, and click 'reverse' Logic Pro X 10.16.1 Apple Mac Mini (Late 2012) Please help!

I feel your pain. It's been how long since this OS update?! And still no remedy for this issue. Ridiculous. I don't know if you've already tried this, but I've found sometimes you can open one of these problematic projects by doing the following: 1. Open an empty project 2. Turn Core Audio Off (logic - preferences - audio) 3. Open the problematic project 4. Turn core audio back on 5. If it works, you can go ahead and close down the empty project and work within the problematic project. Also, another way is simply opening a project you know works, then trying to open the problematic project. This has worked for me in the past.

Hi, I recently bought Native Instruments - 'Battery 4'. Forgive me if I'm asking a dumb question, but I'm unsure of the best way to import my third party drum packs. It seems to me that Battery Kits come as .nbkt files? Is there a tidy way of importing .Wav or Mp3 folders/files? I have already tried this - Select User, then from the drop down arrow I clicked edit - preferences - library - user. I then clicked Add and imported a selected drum pack. However, when I rescanned, all it had done is take each .Wav file from the folder and many subfolders and put them in the Battery User - Samples folder. I need them neat and tidy, sorted in to their relevant folders. What's the best way of doing this? Cheers. Logic Pro X (10.6) Mac Mini (Late 2012) macOS 10.15.7 Catalina

Sorry for the late reply. Will do. Cheers!

Just so other people know, my question regarding my AU Cache folder was answered. Unfortunately this did not fix anything relating to the topic of this thread.

Hi mate, Quality. I managed to access it through your method and have moved it in to my library folder for easier access. I deleted the cache and opened up Logic, it rescanned everything but unfortunately I still can't open certain projects supposedly due to some third party plug-ins. Cheers

Wow, I've opened up a can of worms here...I had no idea this was happening to other people. It is a very frustrating issue, and one that doesn't seem to have any remedy. So far I've located 4-5 plug-ins & 1 Instrument that my 'Logic X' no longer accepts (but only on certain projects). In response to the aforementioned - I also remember doing the trick of opening a project that you know works, and then opening a cursed project. But like @amnestic, this also stopped working for me and would end up crashing Logic entirely. What's strange is I can open up a new project and use these "problematic" plug-ins (such as the Mini V). As @amnestic mentioned earlier the crashing seems to begin at a significant stage of development in the project. I honestly have no clue what's going on, but I'm currently in the process of contacting the plugin developers and hoping their technicians can locate the problem. I noticed today that I do not have an Audio Units Cache folder anywhere on my Mac. Does anybody know why this may be?

Hi, Came here to say I just discovered I have exactly the same issue. The 'Mini V' by Arturia is causing a particular project to crash and so I got in touch with Arturia and they suggested I reset my audio unit cache and that I delete the following files - 'com.apple.audiounits.cache', 'com.apple.audiounits.sandboxed.cache'. I went through the steps they laid out for me, and cannot find the relevant files anywhere. Anyone know how to make them reappear? I'm unsure if this is related but every time I open up Logic it has a scanning process where it scans my Audio Units. It's been doing it for years and I have no idea how to stop it. I kind of just got used to it, and nearly always click on 'abort scan', but would be good to get that fixed. Cheers! Logic X 10.15.1 Mac OS Catalina 10.15.7

Ahh right ok. Luckily the project in question is still in its early stages of development. I'll remove the components of each 3rd party plugin and add them back in a few at a time. Cheers!

Hey, Thanks for the reply. So, I moved all my AU components to my desktop, and I've slowly been adding them back in to their logic folder. I don't really understand what's going on but the project that for some reason doesn't like SPL Transient Designer anymore, now works, so long as the SPL TD component file remains on my desktop (so that plugin is out of use for now). The problem seemed to be fixed, and I was able to open other projects successfully, however, I've tried opening up a recent project I made and it crashes but doesn't give an explanation, it simply states "Logic Pro X quit unexpectedly"...it's so frustrating. I have no idea why this particular project is crashing. Any suggestions on what it may be? Cheers

No problem

Hello, Since updating my OS to 10.15.6, I am unable to open a lot of my projects without Logic crashing entirely. It usually says it's due to a specific plugin (see attached photos). I've literally never had any issues with some of these plugins, like the SPL Transient Designer, this is the first time this particular plugin has flagged up as causing an issue. I've had the "Logic Pro X quit unexpectedly while using the WaveShell3-AU plug-in" message a few times. Other times it has crashed with no explanation. It's incredibly frustrating. I can open up Logic fine, I can even open up a new project via my chosen template. It's strange because the "SPL" message I received today was for one of the projects that up until now has opened for me, and so I've been working on that for the last few days, and today it decided it doesn't like the SPL Transient Designer anymore. Please help! Mac Mini (Late 2012) macOS Catalina 10.15.6 Logic Pro X - 10.15.1