JMH

Hi there. I'm setting up a second studio and looking to clone my mac pro rig so both studio computers are identical and can open sessions on both rigs. I've been reaching out to colleagues and getting a difference of opinion on the cloning process. Some are saying I can clone all my samples data drives using super duper etc, but for the main macintosh HD I should do fresh installs of all of the sample libraries manually. Others are saying I can do a clone of the macintosh HD as well, and assuming the file directories are all the same and the hardware is the same on both rigs, the sample libraries should all open correctly. Anyone have any insight on this? Obviously the clone option for Mac HD would be simpler, but seem like manual reinstalls would be safer? Thanks.

Thanks Cliff, that's reassuring to know K5 is working for you in Monterey/Logic. Can I ask what version of Logic and K5 you're running?

Hey guys, does anyone know if Kontakt 5 still works in MacOS Monterey within Logic Pro? The current compatibility report from NI is that only Kontakt 6 is officially supported in Monterey, but not sure if that means K5 is a total no-go or what. In my case, with 15 years totaling hundreds of sessions and a 500+ track template in each session of mostly K5 instances (or Vienna Pro linking to K5 instances), the lack of K5 compatibility would mean I wouldn't be able to open any of these projects ever again, which obviously would be an impossible situation for my business and a non-starter, as I assume it would be for most everyone in music/pro audio. Since the OS police essentially force you to upgrade every so often, it would seem incomprehensible/devastating if NI/Apple didn't provide for K5 compatibility ongoing to allow continued access to existing/historical sessions. Any info/clarity appreciated!

Thanks Atlas, I did read that thread. It talks about the standard Logic workarounds to free up ram (freezing tracks, BIP, and removing instruments entirely) , but doesn't answer the question of what is Logic's max usable ram amount, and why does it have that limitation in the first place. I used to think it was somewhere around 40GB but I got 46GB loaded directly in Logic today before it crapped out.

I should mention my Logic ram buffer is set to 512. Any lower, like 256, and I get performance artifacts due to CPU single core spiking. It really is frustrating that Logic's RAM limits and core mismanagement are so behind the other DAWs. It's almost like they designed Logic for non-pro users or something. I've considered shifting to Cubase many times because of this. Anyway that's the Logic buffer setting. Wondering if messing with the Kontakt global preload buffer would have any effect?

Hi, I have 64GB of RAM and tend to use all of it in my larger orch sessions. This usually involves about 25-30GB loaded in Logic and the remaining 35-40GB loaded outside logic (on the same computer) in VE Pro. However, I'm currently working in a session with no VE Pro sidecar that has 46.5GB loaded directly into Logic and Logic is acting like it's at capacity, even though I still have 10+GB of headroom left unused in system RAM. If I try to load one more instrument in Kontakt the session hangs until I force quit or it will just crash. So the question is, what is Logic Pro's hard limit on usable RAM and why can't it make use of all of your physical RAM, like other applications can? Or is this a Kontakt issue? Extremely frustrating that in this day and age we're still dealing with RAM limitation of any kind. Spent $10k on a computer loaded with RAM that Logic won't let me use.. Thanks.

Thanks again for you time. Hmm...the .mid file in finder is called "AXP_1m03_v3_Dead Batteries_011018Pix.mid" however this is different from the names of the several midi regions/tracks within the file. The file has about 10 or so midi tracks/regions each with their own name. Those names are the region names from the original Logic session, but as you see they seem to get cut off after x number of characters in the midi file.

Hi David, not sure what you're asking. You mean the physical length of the midi region not being long enough to hold x amount of text characters? This isn't an issue in the regions in logic (you can zoom in or out and change how much you can read on a given region, but it doesn't change the actual text in the region name. Not sure if that's what you're asking?

Hi Having an issue where the full text of the region names I'm writing in Logic are getting truncated (erased) when exporting as midi file In the first image you see a lengthy region name describing to my orchestrator what the aleatoric effects are doing. The second image is the midi file exported from the same region. As you see most of the detailed description in the midi region is obliterated. I've tried exporting several times, making sure the full text of the region is visible when exporting, etc. No dice. Seems like bug. Thanks.

Thanks for your responses. Just keeping things on thread for a minute, so nobody knows why my screenset 1 arrange window was suddenly transformed into a 2000 bar christmas tree of empty automation regions when using smart tools to automate a volume change on a single track? Pretty sure that's the definition of "buggy." MusiKLover, thanks for your explanation on using Controller Assignments vs. Smart Controls. One thing you didn't mention is that you need to be in the plugin window and select the plugin parameter there, in order for "Learn Controller Assigment" to be automatically populated with the correct param. I wasn't able to get to this option the way you describe it (by selecting the parameter in the track dropdown menu in arrange). Overall, this is a simpler option than smart controls, but unfortunately it still requires that you use track automation vs. MIDI CC. MIDI CC is superior as it writes directly to the region, not track, does not require that you constantly enter and exit automation mode, does not require that you constantly turn track from "read" to "touch," does not require that you toggle "display off" if you need to edit regions, etc, and is always 100% glitch free, as opposed to track automation which, in my experience, has been inconstant and buggy as described earlier. So using Midi CC is faster, requires fewer annoying and workflow-slowing steps, and always works. It also doesn't require that you bypass your hardware controller's settings. For example, I've programmed 5 sliders on my Kurzweil to specific MIDI CCs, as I use a lot of proprietary VIs that have been programmed to respond to these CCs. Being forced to assign one of those faders to control a parameter in a synth which does not respond to Midi CC, by way of track automation controller assignments as you describe, forces Logic to no longer acknowledge that hardware fader's original MIDI CC output. To put it another way, Logic hijacks the fader, for the purpose of a single parameter, and no longer allows it to control the broader range of parameters that responded to its original MIDI CC. If you delete the controller assignment, you can see the MIDI CC info being metered in Logic once again, when moving the fader. It seems appropriate that MIDI-driven VI's such as software instruments should respond to MIDI CC as they traditionally have (Kontatk, Spectrasonics, etc maintain this functionality). Many VIs programmed to respond, for example to CC11, and others. Using track automation to control these parameters feels unnecessarily clumsy and cumbersome, and very much like an awkward workaround. Track automation seems appropriate for traditional applications like level mixing audio, but not for programming midi, which has traditionally been an in-region, streamlined, lean, elegant, and powerful process when using CC. With Logic's ability to assign any parameter, it seems a glaring omission that they didn't also include an option to assign those parameters to MIDI CC instead of just track automation.

Hi David, thanks for responding. Honestly, I can't imagine any scenario where viewing two thousand bars of empty regions labeled "automation" across all tracks would be desirable, useful, or in any way helpful. I'm mystified as to why that viewing option exists at all, and more importantly, how it popped up on my screen without a single keystroke, apart from recording a volume change using smart tools. Your saying "works as expected" is bit of a head scratcher. 'Opening main window' does open a new window, but without any of the settings I use, so it's like opening an empty project and I have to reset all of the GUI elements like the SMPTE view, beats bars etc, as well as global track configurations. At any rate, thank you for verifying that this was just a viewing issue and the music itself was unaffected. viewtopic.php?f=1&t=123996&p=633642#p633642 As I mention in this older thread, using smart controls to control track automation (rather than being able in Logic to assign parameters to MIDI CC, as Kontakt or Omnisphere can do by simply right-clicking a param), is extremely buggy and inconsistent. Tracking VI automation data in realtime results in incorrectly drawn curves that then need to be manually redrawn, defeating the purpose of recording them in realtime in the first place. Sometimes the smart control fails to modulate the parameter at all, and you need to move your controller fader a bunch of times until the smart control "catches" and starts responding again. Very frustrating and unacceptable in a professional setting. It's gotten to the point that I've stopped using a lot of VI synths that aren't in Kontakt just because the parameter control is so bad using Logic's smart tools.

Hi, Smart controls never work right. That is, assigning a plugin parameter to a fader via smart controls. But this is insane. In this case I assigned a Zebra synth output parameter to a smart control knob. Set track to "touch" and recorded a single volume setting. At which point Logic proceeded to create "automation" regions covering every single track in my session for nearly 2000 bars! Screenshot below. Anyone ever see anything like this? Session still plays normally, but I can't see the actual regions anymore. Thanks.

Thanks Volov, the keyboard wasn't set up for any multi layers or velocity dependent zones. According to Kurzweil, the issue is the keybed in the SP5-8. When a key is struck very hard, the spring in the keyed can cause the a second erroneous attack at slightly lower velocity. It is a terrible design flaw and the recommendation is to not buy a SP5-8. Astonishing that Kurzweil would sell these units knowing of this defect. Anyway, if I can prevent anyone from buying a SP5-8 I've done my service.

Thanks Eric. Playing a single middle C very hard results in the double notes. Single stroke. As you see the two notes are different velocities, different duration, and different attack time. So I guess it's the keyboard, but I've never heard of this specific issue, at super high velocity only causing this. i.e. this is not the fairly common issue of every note being doubled identically (time, duration, velocity) as a result of midi being exported from the controller on two separate midi channels or ports. This issue only occurs at REALLY high velocity. As in as hard as you can play. Thanks for posting that helpful app, any further thoughts are greatly appreciated. have an email into Kurzweil as well, will see if that yields a response.

Is anyone else dealing with this? If playing a note at high velocity Logic creates two midi events for the note you play, one very short at 127 velocity and another at the actual duration you played it and slightly less velocity. This issue does not occur for any notes played at not high velocity. Screenshot below, perc hits played hard and this is the result. Doubled notes on top of each other. And they cancel each other out sometimes during playback. Terrible. You have to go back and find the small notes and delete them one by one. Thought it might be aftertouch from my controller so I disabled aftertouch but same result. The issue started around Logic 10.2. Also using a new Kurzweil SP5-8 controller, but never had this issue with my Kurzweil PC2x so assuming it's not the controller. Any thoughts appreciated. Thanks.