Mike Janney wrote: ↑
Tue Jul 27, 2021 10:32 am
gentleclockdivider wrote: ↑
Tue Jul 27, 2021 10:03 am
anoise wrote: ↑
Tue Jul 27, 2021 9:18 am
Thanks for the reply and clarification. I was not aware of the validation process and all that is involved. It is clear now. I'm sure the next version will be more polished.
Regarding the "Improve emu", maybe it should be grayed out/not clickable when it is not in use, in a certain engine/VCO configuration. Same with every knob to reduce confusion.
I was assuming that ABL3.2.2 and ABL3.3.0 engine 2 are the same, as another user above me, but this is false, they don't match, I did some quick checking.
ABL3.3.0 is a different plugin, right? If this is true, than naming it ABL4 would have been more appropriate.
It's confusing to say the least .
Abl 2 and 3 were two different plugins .
Due to popular request abl2 is now also in 3.3.0, but 3.2.2 is not .(model 2 does not sound like 3.2.2)
So this either a bug or a pretty weird decision .
We have updated the engines in every release since 1.0. If that's weird to you then I guess our company is weird, like the Wonka chocolate factory or something. We did have a lot of requests to bring the ABL2 engine back so we did that. We brought distortion back with that. So far the overall response seems to be good with the new engines, with a few confused or critical posts like here on kvr.. But all feedback is valid and good, and I appreciate it..!!
I ran some checks again to see if there was any muffling going on between the versions and I didn't manage to replicate that yet. I will do some more investigating tomorrow..
Edit: read the thread again more closely. model 2 does not try to replicate ABL3.2.2.. And model 3 is not specifically for 3.3.0. I do see how that would be confusing now, it really didn't cross my mind as versions tend to be more a technical thing to enumerate the plug-ins.. Now that I see that, I'm not sure how to fix it. We could add the 3.2.2 engine back under model 2 and perhaps rename that model to something else??
No hard feelings , I am just sharing my experiences
Let me summarize , abl 3.2.2 added the following new features :
-vcf trim ,-bass -and higpass , when improved emu was turned off , bass and vcf trim were greyed out = logical .
This is not the case anymore in abl 3.3 , bass knob is always active so it's not clear what the improved emu knob actually does
Also 3.3 in model 2 mode , (improved emu off ) treble knob does nothing , while in model 3 it does ( regardless improved emu switch position )
This are the first points of confussion
Second point of confusion , the 3.2.2 engine is not ported over while the abl 2.0 engine is .
If/when abl 4.0 arrives , the abl 3.2.2 will be ported over except 3.9 ..due to popular demand
Listen ,Abl is the finest emu out there and I applaud your decades long passion of perfecting it's sound in software ( I even remember your freebee) , but just excluding a fine engine (3.2.2 ) while including a decade old one ( yeah popular demand -distortion bla bla ) just feels like a really strange move .
Abl 2 was still avaibale as a separate plugin , It makes no sense to include it in a superior plugin like abl3 .
As it is now , abl 3.3.0 is like an umbrella project (models come and go )
Just bring back 3.2.2 improved emu mode in 3.3
Keep up the good work