Official Arturia VCollection5 thread

[mcbpete]

I still have to double check my glasses aren't dirty when loading up the Solina, was the original hardware ever this blurry?!

[EnGee]

Does anyone have a problem with Analog Lab 2 (the latest update)?

I loaded Arp2600 and SEM, the latest, and then loaded Analog Lab in Bitwig. While browsing the presets, it began suddenly to be not responsive and in the task manager the memory usage is about 1300 mb!! (Bitwig + Arp2600 + SEM memory usage is about 300 mb only!).

I will test that with Reaper and Studio One, then report here.

In Bitwig I could reproduce it. Analog Lab 2 is the first plugin that brought Bitwig to its knees

Anyway, it is working fine in Reaper 5.211 (version VSTi 2) and Studio One 3.2.3 (version VSTi 3) (both hosts 64bit in Window 10 64bit).

[ke2041]

In Bitwig I could reproduce it. Analog Lab 2 is the first plugin that brought Bitwig to its knees

Thank you for reporting it. We will investigate this.

[ke2041]

Then I later went back in and used the Update Center to get the rest. My guess at this point is that the locations from the global demo installer found on the site were not retained. This would explain why the instruments I was most interested in, are the ones that weren't retained.

That might be the reason indeed. I will check this for future updates.

[Harry_HH]

Does anyone have a problem with Analog Lab 2 (the latest update)?

I loaded Arp2600 and SEM, the latest, and then loaded Analog Lab in Bitwig. While browsing the presets, it began suddenly to be not responsive and in the task manager the memory usage is about 1300 mb!! (Bitwig + Arp2600 + SEM memory usage is about 300 mb only!).

I will test that with Reaper and Studio One, then report here.

In Bitwig I could reproduce it. Analog Lab 2 is the first plugin that brought Bitwig to its knees

Anyway, it is working fine in Reaper 5.211 (version VSTi 2) and Studio One 3.2.3 (version VSTi 3) (both hosts 64bit in Window 10 64bit).

The AL2 is MUCH more demanding for the computer, if you happen to run a DAW laptop which is not really powerful, you are in the trouble. Especially my 32bit Live 9 doesn't like to co-operate with the 5 series/AL2. Slow, freezing, non-responsive.
My Arturia 4 series don't have any of these problems in the same DAW. Luckily I demoed the V 5 series first, because had to skip that, installation was painful,but un-installed it in the same day! Waisted 4 h.

5 series is not for me, I am quite happy with my V ver. 4, maybe I'm in the minority, but I find the 4 series UI much, much elegant than the "pizzabox" ver. 5 UI. The price of the resizable UI was too high, I think.
Even the much praised 5 ver./AL2 preset browser is not very useful to me.


I jump in in the ver. 6 if the Arturia manages implement the resizing AND give us back the elegancy of the ver. 4., + of course new feat.

[EnGee]

Does anyone have a problem with Analog Lab 2 (the latest update)?

I loaded Arp2600 and SEM, the latest, and then loaded Analog Lab in Bitwig. While browsing the presets, it began suddenly to be not responsive and in the task manager the memory usage is about 1300 mb!! (Bitwig + Arp2600 + SEM memory usage is about 300 mb only!).

I will test that with Reaper and Studio One, then report here.

In Bitwig I could reproduce it. Analog Lab 2 is the first plugin that brought Bitwig to its knees

Anyway, it is working fine in Reaper 5.211 (version VSTi 2) and Studio One 3.2.3 (version VSTi 3) (both hosts 64bit in Window 10 64bit).

The AL2 is MUCH more demanding for the computer, if you happen to run a DAW laptop which is not really powerful, you are in the trouble. Especially my 32bit Live 9 doesn't like to co-operate with the 5 series/AL2. Slow, freezing, non-responsive.
My Arturia 4 series don't have any of these problems in the same DAW. Luckily I demoed the V 5 series first, because had to skip that, installation was painful,but un-installed it in the same day! Waisted 4 h.

5 series is not for me, I am quite happy with my V ver. 4, maybe I'm in the minority, but I find the 4 series UI much, much elegant than the "pizzabox" ver. 5 UI. The price of the resizable UI was too high, I think.
Even the much praised 5 ver./AL2 preset browser is not very useful to me.


I jump in in the ver. 6 if the Arturia manages implement the resizing AND give us back the elegancy of the ver. 4., + of course new feat.

I haven't install it in my laptop yet (thanks for reminding me )

With Studio One and Reaper I don't have a problem. My processor for the desktop is i5-4570 which is ok mostly and in general is slightly more powerful than my laptop i7-4700.

Here are the other screenshots of Studio One and Reaper:

[Baptiste Arturia]

FYI Kevin/Arturia,

Some installers are not recalling the VST directory locations, and others are. For instance, the Vox Continental, CS-80, Matrix-12, Solina, and Synclavier definitely did not. I'm pretty sure the Farfisa didn't either.

There are two cases when you reach the VST folder selector in the windows installer :

- If you already have installed the current plugin, it suggests to install the VST at the same location as before
- Else it suggests to install the VST where the last Arturia VST has been installed.

[crisis-at-music]

I still have to double check my glasses aren't dirty when loading up the Solina, was the original hardware ever this blurry?!

That would be also my question... I think the GUI from Solina needs an update with sharp and easy-to-read graphics.

[ENV1]

Very disappointing to see that the minimoog still hasnt been fixed.

I think that pretty much does it then: 10 years and no action despite the fact that it has been reported numerous times...thats ridiculous.

The last version where this stuff worked properly was 1.6 from 2006!


Anyway, i also just noticed that the problem is even worse than i realized. Because its not only VCO3s SawRamps that are modulating VCO1/2 pitch in the wrong direction, in fact the Triangle and Square modulation is reversed as well, i.e. open VCF = low VCO pitch and closed VCF = high VCO pitch. Good luck making original minimoog sounds with that kind of configuration, where the filter closes while pitch goes up and vice-versa.


And...surprise surprise...theres a brandnew bug in that area now too. It screws things up even more than the reversed modulation, and is even more inexcusable because nobody with the least bit of synthesizer experience could possibly miss something so obvious unless they just slap stuff together and never bother to check any of it for proper function. Of course i could report it now, (as i usually do when i find something), but what would be the point. IMO it is pretty clear by now that their focus is firmly on UIs and graphics and preset browsers and whatnot while the functional aspects of the actual synthesizers they purport to emulate matter little to not at all. And im tired of it. Im tired of old bugs celebrating their 10th anniversary while brandnew ones are being introduced to make things even worse than they already were. ARP 2600? Didnt even bother to check this time. Willing to bet that its Saws are still ramping downwards, just as they always were. Never mind the fact that thats not how a real 2600 works...after all who cares as long as the whole thing has a snazzy preset browser and a 'Gigantic' setting for the new 200+ megabytes UI...


OK, i will stop here before it becomes a rant. The point is, ive had enough of that. I will keep my old versions because i already have them, (and yes, IMO their sound and UIs are great), but i definitely wont go for 'updates' that need significantly more harddrive space and RAM only so i can enjoy new bugs in addition to the old ones. It just doesnt work for me.

[BMoore]

Very disappointing to see that the minimoog still hasnt been fixed.

I think that pretty much does it then: 10 years and no action despite the fact that it has been reported numerous times...thats ridiculous.

The last version where this stuff worked properly was 1.6 from 2006!


Anyway, i also just noticed that the problem is even worse than i realized. Because its not only VCO3s SawRamps that are modulating VCO1/2 pitch in the wrong direction, in fact the Triangle and Square modulation is reversed as well, i.e. open VCF = low VCO pitch and closed VCF = high VCO pitch. Good luck making original minimoog sounds with that kind of configuration, where the filter closes while pitch goes up and vice-versa.

Can't replicate that bug here. MiniV v2.
Maybe I'm not doing it right.

[ENV1]

Can't replicate that bug here. MiniV v2.
Maybe I'm not doing it right.

- Enable VCO1, disable the rest
- Set VCO3 Mode to Lo or Lo Mono
- Set Cutoff knob to rightmost position (Filter Open)
- Enable Oscillator Modulation switch
- Enable Filter Modulation switch
- Move Modwheel up to full

Now play a note.

VCO3-SawUp: VCF will open as VCO Pitch goes down.

VCO3-SawDown: VCF will close as VCO Pitch goes up.

VCO3-Triangle: Same as Saws.

VCO3-Square: Same as Saws.

Why: Because the Control Voltage sent from VCO3 to VCO1/2 Pitch is reversed.



And just to let everyone in on the secret (i.e. the lastest bug i mentioned earlier):

In the new version, enabling the Oscillator Modulation switch enables Filter Modulation as well! So if you want your VCO3 to modulate only the other VCOs but not the VCF youre out of luck because it wont be possible.

(But hey, at least the UIs are real big now.)

[exmatproton]

And just to let everyone in on the secret (i.e. the lastest bug i mentioned earlier):

In the new version, enabling the Oscillator Modulation switch enables Filter Modulation as well! So if you want your VCO3 to modulate only the other VCOs but not the VCF youre out of luck because it wont be possible.

(But hey, at least the UIs are real big now.)

[BMoore]

My bad. You are correct, Sir.

[waltercruz]

The Solina V2 doesn't respond to sustain at all? I tried setting the sustain length as described here (https://www.arturia.com/faq/utilization ... nthetizers), with no effect at all.

[vic_france]

The Solina V2 doesn't respond to sustain at all? I tried setting the sustain length as described here (https://www.arturia.com/faq/utilization ... nthetizers), with no effect at all.

MIDI Learning the sustain length slider does work here.. but (as explained in that link) the original Solina didn't have sustain (pedal) at all. So, this MIDI Learn suggestion doesn't suddenly give the Solina a "hold" function (as we've come to expect from CC#64), it mearly switches the sustain length parameter from minimum to maximum (which still fades away eventually )