kdubb1234

Hi all, I want to record the six channels in a BreakTweaker pattern onto six audio tracks in Logic in one pass – not one track at a time. I was told by iZotope that you could accomplish this by command+clicking the record button for every audio track you wanted as part of the pass, but command+clicking on record does not engage record for multiple tracks simultaneously. Is this possible in Logic Pro X? I know you can do it in Ableton Live and Protools and it sounds like you should be able to do this in Logic? Does anyone know of a way to actually get this to work in Logic? Thanks for your help.

Hello all, David I'm not seeing where the Audio File Editor Undo History is within Logic. Can you direct me to where that might be? Atlas, if by cold-reboot you mean powering off the computer and turning back on, I do that daily. What would you gain from doing a cold-reboot (if it is something other than what I just referenced)?

Funny, I mentioned earlier that I'm also part of another thread involving Kontakt and Logic and in re-reading JonParadise's response, it triggered something that I referenced in the other thread. I'm still noticing these extreme file sizes occurring with Logic Pro – files that have very little content in them. I just rebuilt a song after Logic kept crashing trying to access Kontakt 5. I upgrade to Kontakt 6 (knowing that it would not solve this particular issue) and start the long, arduous process of trying to recreate some of this content but now with using Kontakt 6. A week of working without incident and now Kontakt 6 is involved with the Logic files no longer opening. The interesting part is (and this is what Jon touched on) when I look at the size of the Logic file it is reading 5x the size of the previous iteration – over 200 MB! I can't think of any reason why a file with no audio tracks and only one instance of Kontakt 6 and one instance of BreakTweaker being over 200 MB in size! Unfortunately, this has been typical with my exposure to Logic so far. I've adjusted my Undo History and continue to use the Clean Up option but this is bordering on craziness! I like some of the features in Logic but I may have to abandon this software and go back to Pro Tools and/or Performer so I can actually get some songs finished.

Hi, I'm on OSX 10.13.6 - High Sierra. Not planning on upgrading at the moment. I did reluctantly upgrade to Kontakt 6 also. It didn't solve the problem as I knew it wouldn't because the songs are accessing Kontakt 5. I went through the process of rebuilding one of the songs using Kontakt 6 and now after about a week of working, the newest rebuild is no longer opening and the error message is involving Kontakt once again! ("Logic Pro X quite unexpectedly while using the Kontakt plug-in"). What I'm also noticing again is this issue with Logic file sizes bloating to these incredible amounts. This new song is 5x the size of the previous iteration. There is only a few tracks in this song so far – no audio tracks other than one reference track. The only thing else in the file is one instance of Kontakt 6 and on instance of BreakTweaker. This file is reading over 200 MB and there is absolutely nothing in it that would justify a file size that large - even a file size of 40 MB for something with this minimal amount of content is extreme, but it has been a consistent, typical result with my exposure to Logic so far. Pro Tools and Performer are producing much smaller file sizes with comparable content. Curious if this recurring file-bloat issue might be part of the problem but there definitely seems to be some link to Kontakt and Logic not wanting to playing nice together. I may have to abandon Logic and go back to using the other DAWs at my disposal so I can actually get some work done.

Thanks for the replies. The problem is I have songs built using Kontakt 5 and they will not open. I'm looking for a solution so that I can access those songs that are still accessing Kontakt 5. Something is going on with Kontakt 5 interacting with Logic. I'll reach out to Native Instruments again and see if they have any additional information that will solve this issue. If I find out anything I'll report back. And any other thoughts you all can provide on solving this particular issue would be most welcome. Thanks all.

Hey guys, I've been out of the loop for while but saw this notice. Yeah, I did address the backups and that helped some. Also using the clean up option within Logic helped but the files are still large, especially compared to similarly sized projects in the other DAWs that I am using. I have not tried the Undo History option yet. I will as soon as I can get Logic to launch again (a new issue involving Kontakt from Native Instruments. I've posted this in a different thread but mentioned it because Jon made reference to Kontakt). I'll respond with results once I get the other new issue resolved. Thanks all.

Hello, Logic Pro X 10.4.4 is crashing with Kontakt 5 as part of my system A little history: I just installed a new 2TB SSD hard drive and 96 GB of RAM and started using an external hard drive for most of my Kontakt 5 Libraries, where I was not using an external drive before. I had to reinstall all of the plugins and was using the latest version of Native Access when doing so. Logic and Kontakt 5 worked briefly and then things went south. I've troubleshooted and narrowed it down to Kontakt being the issue. When I remove Kontakt 5 from my system, Logic launches. When I introduce Kontakt 5 it crashes. And, after Logic tries to launch for a lengthy period of time I get the alert that "Logic Pro X quit unexpectedly while using the Kontakt 5 plug-in". I have a query into Native Instruments also because there is another issue occurring. When Logic was launching at the beginning, and when trying to add sounds into an instance of Kontakt 5 I kept getting the prompt "Kontakt 5 is too old to load this file. Please update to the latest version." This same message also appeared when working in the stand-alone version of Kontakt 5 (and I did initialize Kontakt 5 in stand-alone mode first after reinstalling before trying to open in any DAW). I'm not sure what's instigating the issue - is it Logic or Kontakt 5? I do know that things were working fine before I updated to Logic Pro X 10.4.4. Using an external drive for my Kontakt libraries is new in my workflow. Kontakt 5 itself is still on my external drive however. I'm not sure if this would have anything to do with the issues that are occurring but thought I should mention it. I've had to uninstall everything Kontakt and i also decided to uninstall Logic Pro X in an attempt to eliminate corrupt preferences as being the cause. Has anyone heard anything further with Kontakt 5 and Logic Pro X 10.4.4 not being compatible? I'm still waiting to hear back from Native Instruments after checking off all of the troubleshooting options they suggested.

Hello, thanks for the reply. If by cold reboot you mean shutting down the computer (and not just logging off) and then restart, I do that daily. I'm running iOS 10.13.6 and Logic Pro X v.10.4.2. I'll take a look at the Troubleshoot Rundown list that you provided to see what I may or may not have done already. Appreciate this information.

Hello LPH, I am noticing that my Logic Pro X files are saving large – and actually starting out quite large especially when realizing that there is no midi or audio data saved in them. When Creating A New File: - Saving file as Folder, not a Package - File has 10 blank tracks in it; created from a template - No audio or midi data added to the file yet - File saves at 656 KB Add one Kontakt 5 Plugin to an insert and save: - File size jumps to 1.1 MB Add 2 instruments to the Kontakt 5 instance: - File size jumps to 4.5 MB - There is still no midi or audio data saved in the file Add a second instance of the Kontakt 5 plugin: - File size jumps to 6.2 MB - There is still no midi or audio data saved in the file I’ve read that each save doesn't overwrite the project file but instead renames the last project file to a backup version, and saves a new file. So, every time you save you are adding an extra project file (up until the max autosave entries number). I was attempting a new workflow with Logic using one instance of Kontakt 5 as a multi-timbral instrument, attempting this approach with the explicit purpose of keeping the file size down. What is also worrisome is that my song files are corrupting and I'm losing work. I’ve had to rebuild this particular song from scratch twice now with the same result of the file bloat and the file corrupting where it would not open. I’ve also tried importing the corrupted files content into a new session and every attempt at recovering the file in this manner created just another corrupt session. I was in the middle of attempting a third try and thought better of it. I’m not sure if the file corruption is connected to file bloat or to the introduction of Kontakt 5 into my workflow. The files were responding without incident until I started using Kontakt 5 but I'm not sure if I should post another thread to discuss this Native Instrument and Logic Pro issue? I’ve since started working with Digital Performer again until I can solve this issue. I was also made aware of the Cleanup option within Logic’s Project Management that aids in reducing the file size but the overall file bloat issue is still problematic. Any ideas? Could this have anything to do with needing to do a clean install of the operating system? Reformatting the hard drive to get rid of disk fragmentation, perhaps? I’m about to do a clean install but thought I’d try this post before proceeding. Thanks.

Hi all, I forgot to update the progress of this post. I did try creating a new, empty session and everything worked as expected when doing so – even with the 3rd party plug-ins. I went back to the original project and was also working. Not sure why after so unfortunately I can't impart anything of benefit here to help anyone who may have also run across this issue. I appreciate all the help in trying to solve this issue though. Thanks.

Thanks David, I'm going to try this right now!

Hello, I'm noticing that if I have a track with multiple takes on it that I can no longer access the Fixed Velocity function. It grays out with any track that has multiple takes. If the track has only one take, I can select Fixed Velocity (under Functions > Midi Transform > Fixed Velocity) but if a track has multiple takes on it this option grays out. Is this a bug or is there some logic I am not aware of as to why this would work in this manner? I'm trying to set the velocities on a Kick and I want to keep all of the takes. As I was about to submit this I did notice that if I select all takes within the track by selecting at the layer level, that it will allow me to then access Fixed Velocity but this effects ALL takes within the track. I would think that I would be able to select the take that I want to effect and not have to select all takes. Any ideas?

Hi all, thanks again for the responses. David/Waterandwax, The F Grand 278 is definitely velocity sensitive. I'm online know with the makers of Substance to get some information on that because that may not be velocity sensitive and hopefully I can respond back with some insight on those. I just ran tests in Digital Performer – recreating the same scenario – and the F Grand 278 is working as expected. I can adjust velocities, I can click on notes in the Midi Editor (Piano Roll) and they sound so I can hear them as I edit them, etc. The process should work pretty much the same way in Logic. So there's either a bug in Logic with regards to 3rd-party plugins or I am doing something seriously wrong. I've even gone back to review tutorials that illustrate how the Piano Roll works in Logic but it's just not working with these plugins. Is there something about 3rd-party settings having to be "in sync" with Logic settings? Does that make sense to anyone? I'll have to do some more research on that. Atlas/Waterandwax, the Midi Routing appears to be correct. Output gives you a dropdown where you can set the midi channel. This has to coincide with the setting on the Logic track. I've done that. And yeah Waterandwax, things are sounding on playback without any issues which seems to confirm that midi is set properly. Altas, when you adjust the velocities in Logic you get visual confirmation as the color of the note changes – moving into the red spectrum as you increase velocity and into the blue spectrum as you decrease velocity. I get that visual confirmation and I can see the velocity changing in the velocity slider as well. And the Midi In button is enabled but that wouldn't cause the issues that I'm experiencing from the tutorials I've been reviewing. I've run this also with Midi In not engaged as well with the same issues occurring.

Hello, thanks for the responses everyone. A friend mentioned trying to use a Logic-native patch to see if the problem still existed. When using one of the Logic's own sounds (in this case the Classic Electric Piano patch), everything works as expected. I can click on the midi data that was recorded and it generates a sound so that I can hear as I edit the note. I can use the Velocity tool and the velocity adjusts. And David, to your question, I was using several 3rd-party plugins. One was Substance by Output through their Kontakt Player and the other was using F Grand 278 by MOTU through their MachFive3 Sampler. And yes, the issue still persists in a new, empty project. I'm not sure how to attach that file though. Several friends have mentioned experiencing similar issues when trying to use 3rd-party plugins with Logic. Erik, I have checked the Region Inspector. And the settings look like the screen capture you provided (expect Mute is not engaged). I am not seeing anything related to the Velocity parameter that allows it to be set to "fixed". I do see this option available however with the Dynamics parameter but it is not set to "fixed". It is set to 100%. I can hit play and what was recorded plays/sounds as was recorded. The issue is when trying to edit the data. When I click on recorded notes in the Piano Roll Editor I should hear those notes sound and they aren't sounding. I should be able to adjust their velocities and Logic is not allowing me to do that. But with this latest test, the issues appear to be occurring with 3rd-party plugin sources. I also work with Digital Performer and I'm not witnessing these issues in that DAW.

Hello, I’m attempting to edit midi data within the Piano Roll and the notes aren’t responding to any velocity changes that I make. I’m also noticing that when I click on any of the midi data in the editor that they don’t produce a sound either. When clicking on a key on the virtual keyboard however that is producing a sound as expected. I think this might be tied in to with why I can’t adjust the velocity of the midi data either? Midi In and Midi Out are both engaged. Changing the velocity of a note with the Velocity Tool also appears to be functioning properly (the color changes and the velocity amounts are adjusting) but there is no audible difference in the velocity of the sound. I've tried changing patches/plugins to make sure the sound source itself was velocity sensitive and the results are the same – the notes all sound with the same velocity as was recorded with. I saw another posting online that mentioned making sure that velocity was not set to “fixed” in the Region Inspector but set it to “100%” instead. I’m not seeing the same configuration in the newest version of Logic and not seeing anything labeled as "fixed". One other thing that I noticed: if I marqueé-select the midi notes in the editor window that they then produce a sound like expected – but not all of them, only some of them. Clicking on them no, but marqueé-selecting some of them, yes. I also switched to the Step Editor and tried selecting midi notes in that mode. Similar results - some sounded and some didn't. Any help would be appreciated.