After reading some posts about 5 sounding different than 4, I decided to fire them and do a side by side... one thing however that is disturbing is that 4 patches can not be loaded into 5!! I see the post though from Kevin at Arturia... so that's good... in fact, it's vital... how can you release updates to existing plugins and exclude supporting the previous versions patches???Kevin [Arturia] wrote:aMUSEd wrote:Kevin why can't I import my SEM bank into the new version? - I have my own bank (SEMBlance) and 3 other third party banks I need to use. It just doesn't recognise the format for banks or individual presets.
For the moment, the legacy factory & user presets won't be compatible with the new plugins versions.
But we are currently developing a preset converter in order to make your patches from the legacy versions compatible with the new plugins.
This app should be available in the forthcoming weeks/months.
Kevin
I know this converter "should be available in the coming weeks/months"... but can you please make it sooner? This to me is a major almost deal-breaker issue. I've never heard of such a thing - an update to an existing product with completely no support for previous patches. bizarre.
I have learned that in this world of software plugin tools, there is basically nothing you can assume from developers. for example, just because one dev offer license transfers, you can't assume another dev will. however, I just assumed that 5 would support 4 patches. that to me just seems like it should be in the top 10 list of priorities. I am dumb founded by the idea that they are not supported. I guess you just can't assume anything with these software devs. if an update comes out for an existing plugin, don't assume you can use your own patches. a new low!
