Are you by any chance running Azslow's control surface plugin? Just out of interest. EDIT - ps I opened a thread over at the Arturia forums and someone from the company was looking into it with me, but it was working on their test machines so he couldn't really help. Since then, I've had a few people ask me how to map it to their analog lab and. But after a reboot, it went back to the previous behaviour. Arturia was kind enough to send me their Keylab 61 Essential MIDI controller. And it worked, so I thought it was fixed. I don't know what I did differently - the only thing I can think of is that I updated Azslow's plugin (which I use to interface between Sonar and two old control surfaces - a NI Kore and an Alphatrack). TO make this even stranger, it DID work - once. I have to manually go in and link each knob in analog lab to the Minilab MK2 knobs and I. Which is the knobs do not work automatically upon opening an instance of Analog Lab 2 vst. It works fine in standalone OR (and this is my workaround for the moment) sub-hosted in NI's Komplete Kontrol. I just purchased a Minilab MK2 which I absolutely love, however Im having one single problem with it that Ive been troubleshooting. It loads and looks normal, and I can load patches and change controls and so on, but it's unresponsive to either MIDI input (which works with anything else I load, and I'm very far from a beginner with this stuff, so I'm quite positive it's not mis-routed or anything) or mouse clicks on its own keyboard. But the Analog Lab 2 - that's what I'm seeing here as well. Can't speak to your SEM latency, unless it's just that - latency, possible ASIO settings or whatever. You're the first person I've encountered with the same experience as me. In the standalone VST outside of FL Studio, the tone adjustment pads work fine, but within FL12 they do not.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |