Arturia Forums

V Collection - Legacy versions => Solina => Solina Technical Issues => Topic started by: andyr1960 on December 04, 2014, 11:51:31 am

Title: Ensemble Modulation Speed
Post by: andyr1960 on December 04, 2014, 11:51:31 am

While I applaud Arturia's new Solina, I have to say that the ensemble modulation sounds off kilter - the high LFO is just too fast, it should be around 6/7Hz and maybe not as pronounced.

I owned a Solina for many years, and it certainly didn't sound this "wobbly".

I don't mean to nit-pick, everything else about it is perfect.

Title: Re: Ensemble Modulation Speed
Post by: martinl on December 16, 2014, 08:42:40 am

I completely agree with the above post. I would even say, that the current ensemble mode makes the SolinaV unusable. The sound is far from what it should be. The freebie "ESline" from Elektrostudio (although getting the envelopes wrong) comes MUCH closer to the ensemble sound.

I hope Arturia will fix the ensemble (possibly exposing the speed and depth parameters of the two LFO's in the OPEN page).

Martin

Title: Re: Ensemble Modulation Speed
Post by: andyr1960 on May 29, 2015, 05:01:39 am

At last, the problem has also been noticed by a very respected journalist, in this months Sound on Sound.

Gordon Reid mentioned that the 3 phase chorus effect was the only thing letting it down. I'm now hoping that Arturia will address the problem.

Title: Re: Ensemble Modulation Speed
Post by: ben arturia on June 01, 2015, 03:29:02 pm

Thank you all to take time to report this issue.
We will investigate further to check if we've made a mistake here.

Title: Re: Ensemble Modulation Speed
Post by: martinl on September 03, 2015, 01:00:03 pm

Quote from: ben arturia on June 01, 2015, 03:29:02 pm

Thank you all to take time to report this issue.
We will investigate further to check if we've made a mistake here.

Hi there, just wanted to ask whether there is any news on this?

Title: Re: Ensemble Modulation Speed
Post by: ben arturia on September 03, 2015, 04:06:30 pm

Hi martinl,
This problem is referenced here. We will try to fix this in a future update.
Sorry for the inconvenience.