The previous version had more flexibility to use multiple instruments simultaneously (but that version is no longer available to buy). Plus, they changed the multi-instrument split-keyboard functionality from Analog Lab 4 to V. Some of the cons are that Arturia plugins are a generally tad slower to load than many other plugins (probably due to their heavily bitmap-centric GUI design (even on an SSD) and they also have to communicate with the separate Arturia Software Centre licence manager).Īrturia's synths can be quite CPU-hungry too. The pros are that there are loads of very usable sounds in Analog Lab.
Are you by any chance running Azslow's control surface plugin? Just out of interest.As an owner of Arturia Pigments and Arturia V Collection 7 & 8 (which include Analog Lab 4 and Analog Lab V). 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. But after a reboot, it went back to the previous behaviour. 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. It works fine in standalone OR (and this is my workaround for the moment) sub-hosted in NI's Komplete Kontrol. 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.
0 kommentar(er)
