If you can’t recreate the drop outs, the next step is to dig into your midi data to make sure you're not sending more data into Ableton Live than necessary is the next step. If the CPU usage is still through the roof w/ all peripherals disconnected and only using musical typing, your computer has the recommended specs and you've checked on your Preferences in the tips at the top of this article, this is a strong indication that the issue isn’t midi/hardware related. Unplug your keyboard entirely and use Live’s Musical Typing feature to see if you can recreate the dropouts.We hope Live will eventually allow folks more flexibility over how midi is passed thru or filtered by a given instrument but until then there are some of these unfortunate constraints inherent to the program. A great solution is to use a separate midi controller like the nanoKontrol2, and we like it so much that we have it programmed with a knob to open up the master filter (far right knob). Regarding the mod wheel, we generally just discourage using it as a part of your rig for this reason. It’s how Live handles midi by default and it can cause issues for some, for others it’s not a big deal, and it seems to vary from user to user. It is normal for some data to be sent by these controls that is passed thru to all the instruments. For that we first recommend adjusting your audio buffer settings where possible to reduce the likelihood of the issue. This is also why a sustain pedal press can cause some CPU peaks as well. If you are having an issue with the mod wheel having a CPU spike, this is due to an unfortunate default in Ableton Live that passes midi CC data through to all instruments open in a Set, even when they're inactivated via Chain Selector (as all the bypassed instruments in Sunday Keys are). (Do this at your own risk and always follow best safety practices for downloading files on the internet or opening emails etc.) Also many security/antivirus apps like Norton and McAfee are known to slow down your computer, usually if the auto scan setting is enabled, so you might do some research into that to see if you can optimize that software or temporarily disable it when using Ableton Live. If you have a dual core processor check out the link for CPU optimization. If you are using a PC, there are some good best practices here for running Ableton on Windows: Trim down the Set as you feel the need by removing instruments from the "Instruments Go Here" racks present on each track, just keep in mind that you'll be affecting the layered worship patches as you do.Make sure In/Out Sample rate is 44100 or 48000.You'll want to just test this out on your machine. Adjust buffer size - you'll want the buffer size set to as high as is tolerable.There may be extra, unnecessary settings currently turned on that Ableton is listening to, which is causing the freeze up. Then you should be able to turn on IAC and then turn back on ONLY the exact midi preferences you need on for IAC. If you need to use it, open Ableton Midi preferences and turn “Track” “Sync” and “Remote” off for both input and output for all your IAC instances in Ableton Midi Preferences. If you are having trouble with Sunday Keys for Ableton Live, check out the below troubleshooting tips. You'll need to have 16 GB of RAM to use Sunday Keys, and at least 2.0 gHz processing power.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |