mandoplan

bump

Thanks Atlas, yes I've checked both of those places and have deleted everything that was there and reset everything to no avail. Perhaps I'm not looking in the right spot? Here's a quick video: It would appear that the plugin is "intercepting" the Midi inputs for C2 - F2 and that those keys are mapped to Patterns A - L in Cthulhu but I can't find out where the hell those patch assignments are stored to delete them. Again, I've tried uninstalling Cthulhu and have reset preferences in Logic Pro. And to answer your last question, I use the learn mode to map parameters to buttons, like most noobs. I more than likely accidentally hit some keys with the Learn mode activated, but I don't remember doing that at all.

I'm running Mainstage that's getting it's BPM from a Logic Pro session using Audio MIDI setup, with a number of loopback instances running inside mainstage. The global BPM is syncing wonderfully, however the metronome in Mainstage is not syncing to the Logic Pro X metronome, and as a result the 1 is in an indeterminate place when starting loops in Mainstage. I'm aware of Dewdman's Plogue Bidule workaround detailed here: viewtopic.php?t=139278 , but I'm wondering if there's maybe a scripter fix for this that will get the metronomes in perfect sync? I'll do the Bidule route if I must, but it seems like someone with more Javascript knowledge than me might be able to get the 2 metronomes talking. Maybe a scritper instance on the Metronome channel in MS that forces the MS metronome to get it's reference for the 1 from Logic?

Okay so I feel like a total noob here, but I'm stumped on this and hope someone can help. I'm experimenting with Cthulhu (loving it!) and am running into an issue on one of my machines. Long story short, in attempting to map a parameter within the plugin, I somehow managed to map Letters to a parameter that is normally numbers, and they're all linked to Key on the keyboard (instead of a slider as intended). It's currently reading as A - L in the automation window. Here's the thing, I CAN'T FIGURE OUT HOW TO UNDO IT. I've deleted Cthulu entirely and reinstalled, and I've also deleted the Logic Pro plist file, all to no avail, the erroneous mapping continues. Any ideas as to where I might locate this mapping so as to delete it? CMD +L doesn't work, I've deleted it there already. I hope this is clear in the way I'm explaining it.

That worked well David, thank you! That gives me the ability to slide through the patterns, so it's not a step through, but certainly manageable. Curious if you have any thoughts on how I might step from pattern to pattern?

Hey hey, so I'm working with Cthulu in Logic Pro X, trying it out. One of the things I'd like to be able to do is assign the pattern letter selection to a button, so I can step through different arp patterns when performing live. I've found the automation parameter I'm looking to affect, but I haven't been able to figure out how to map a pattern letter (See below) to either the transport controls or to an individual button on my Keylab 61 Mk1. Patterns A, B, C, D, E each step up in the increments seen in the attached image when the button is clicked in the Cthulu interface window, any tips to map these same steps to a series of buttons?

BUMP on this one? Dave did you get any answers here? I'm having a similar issue

Thanks for that. I don't use a lot of ChromoVerb (I'm a Vallhalla Room fanboy but I HAVE pinpointed an issue with DrumLab in Kontakt 5. So I know what plugin's likely causing it, but my issue is that this problem is new. I've never had to deal with this because my machine is pretty powerful, which leads me to believe that maybe there are some bugs to work out on the Logic Pro app side?

This. I've been tracking on a 12 core machine for YEARS in Logic without ever experiencing any overload issues and in the last 2 weeks it seems to be happening all the time. Any solutions you've come up with? I've been through the check list, no luck and now the project won't allow me to save any changes to it without beach balling on me.

Thanks fellas, sorry for the delay in replying. David the reason I think I'm missing something is because I'm not seeing an option to delete the Keylab as a control surface in the window when I click through as you suggested (see screen shot above). I bypassed control surfaces and that did the trick, so you're correct in your assessment of my issue. But I can't for the life of me figure out how to reset control surface custom keys I've programmed. Should I delete the preferences file maybe?

Thanks David, appreciate the feedback. Should I scan for new devices? I feel like I'm missing something in your instructions.

I'm having an issue with a key on my new keyboard, the Arturia Keylab 61 (MK 1). Key 25 does not play a note at a certain Octave range. At first I thought it was my keyboard, but I think it's something in Logic? It only happens when I try to play a certain Octave range, and when I change the Octaves it plays find. Exhibit A: SOLVED I deleted the preferences file under ~/Library/Preferences/ and deleted the file named com.apple.logic.pro.cs.

Hello everyone, I'm shooting a music video at 60 FPS on a 23.98 timebase. I want to speed the track up to 250% of it's original speed in order to get slo motion, yet still time synced performance shots. Is there a way to time stretch based on my exact percentage in logic pro x? I know I'll probably get some artifacts in the audio file, which really isn't a big deal. Here is the chart I'm using for my frame rate conversion (ie where i get the 250% from) Using a 24p timebase, for the following frame rates, adjust the song speed to: 12 fps: make song last 1.956x longer by stretching it to 51.1% speed 18 fps: make song last 1.333x longer by stretching it to 75.0% speed 20 fps: make song last 1.226x longer by stretching it to 81.6% speed 22 fps: make song last 1.067x longer by stretching it to 93.7% speed 26 fps: make song last 0.907x as long as normal; play it at 110.25% speed 30 fps: make song last 0.800x as long as normal; play it at 125% speed 32 fps: make song last 0.747x as long as normal; play it at 133.87% speed 36 fps: make song last 0.672x as long as normal; play it at 148.81% speed 48 fps: make song last 0.498x as long as normal; play it at 200.80% speed 60 fps: make song last 0.400x as long as normal; play it at 250.00% speed

Director and Editor here, when selecting music for a video edit we look for music that has multiple crescendoes per track. The more "ups and downs" a track has, the better. We also look for tracks that don't have abrupt endings. I analyze waveform first when selecting a song from a stock site for a video project (we use APM at my place of business, GASP), if the waveform is all one height with no peaks or valleys, I know I'm looking at a track that's going to be tricky to use for creating buildup and release in my edit. So if you make a track that has some variance throughout, with a smooth ending that hangs and is easy to cross fade out, you're setting your client up for success. If your client isn't prepared to edit music a little bit you should have a talk with the editor . Good luck!

It worked great, thanks!