![]() I'd say roughly 40% of the time no note data is recorded. It's definitely in record mode-the control strip changes color to red, the record button is active, the track in question is record-enabled, and indeed a MIDI region is being created. So: Logic is clearly receiving MIDI data, because it's producing output. It seems that it more reliably records the data if I start recording at the beginning of the project, but it frequently fails even under those conditions.Īlso: I can hand-enter MIDI note data in the piano roll interface without issue. (I don't think the problem is related to any particular software instrument since I've been able to reproduce it using Logic's native instruments, drum kits, and sample libraries contained in Native Instruments' Kontakt sample player.) And sometimes it will record the note data. Obviously it's receiving the data, because the software instrument on that track is producing output. ![]() In fact, with the metronome set to do a one-bar pre-roll, Logic starts creating the region in the preroll.īut, even worse, it often (but not always) doesn't actually record the MIDI note data. But lately, I've noticed this rather bizarre dysfunction where Logic simply will not record MIDI data that it's clearly receiving, since the software instrument being controlled is clearly producing audio.Īs a guitarist/bassist, I don't often record MIDI note data, but in my experience, when you're recording MIDI note data, Logic doesn't start creating a region until it receives the first note-on information. I've recorded numerous MIDI regions with it without difficulty. I recently purchased an Akai MPK249, which is a pretty nice keyboard controller. Odd MIDI Recording Bug I suspect this issue is unique to my setup, since I haven't seen any analogous reports, but here goes: I have never in 20+ years had to go online here to post bugs but these are big ones that might underline a more serious flaws in the new version. So I am hoping someone from Logic who has the power to fix these problems will do something here. The more reports they get in this direction, the higher the chance this gets fixed again by Apple. This worked perfectly fine before with the Virus TI OS 5.1.7 and other 10.4 releases of Logic Pro X, so at this point we can only recommend to report this to Apple's support. We have reports that something in this regard broke in the very latest Logic Pro X release from Apple. I contacted Access about this issue and this is their response: Used to work fine in previous Logic versions. I have to mouse the knob on the plugin to record any automation which renders the desktop unit useless. The knobs will control the plugin but no automation is recorded. Now I noticed that my Access Virus TI will control the plugin but Logic will not record automation any more from knob moves on the desktop unit. I have to quantize the regions separately or go into note editor. Midi info is un-quantized when played into Logic even if the dialog box is set to a quantize value. Latest version of Logic 10.4.6 Serious Midi/Automation Flaws First I noticed that setting the quantize in the dialog box on the arrange page does not work. I've made a screen capture of this behaviour to try and demonstrate what I'm talking about. Working, as exoected when disconnecting the midi interface on the Knob on the software) while all the other knobs and faders stopped That the "rogue" knob still acts weird (affecting another unrelated Tried disconnecting the interface on Logic's environment, andĬonnecting it to a midi monitor, to see what happens. ![]() I contacted Arturia's support, and they kindly guided me through resetting the definitions on the Kelyab and on the plugins.Īt the end of the process, i.e following Arturia's suggestions, I still get one knob not working properly. In Logic however, some of the knobs stopped controlling the corresponding knobs on screen. Standalone, or either as an AU or a VST inside Ableton Live, everything Things further, it should be noted that when launching Analog Lab V as a (5) included, I started experiencing problems. Was working perfect for me with Analog Lab 4, but recently, afterĪrturia released the new version of the V Collection, with Analog Lab V Keylab Essential, and especially the meta-plugin, the Analog Lab. Very intuitive and a lot of fun to control the Arturia plugs with the I have Arturia's V Collection and also the Keylab 61 Essential. This one is a bit complicated to explain, but I'll try.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |