I feel like OP is being criticized a little bit too harshly. It's not too much to expect from a dev to take care about backwards compatibility.

 

was the compressor on BYPASS?

 

is it so hard to setup a diffrent compressor?

 

That's the point of the post. Tell the people about the backward compability problem with AO plugins, and if you want to keep your setup, don't upgrade. Or if you do upgrade, do it knowing you will have to re-tweak everthing again. People can do whatever they want with this info. Or get mad at me, think it's my fault, say AO is the holy grail of the freebies and live ok with this bugs. But it's a fact: they don't have backward compability and have tons of other bugs. I'm not enemy of tunca, i'm not coming to a internet forum to defame him freely, i'm telling real issues with a company that's in the business as any other. And there are even other issues, which are not the ones i told at the beginning, but other people told on this post.

 

But i got good advices here: "take pictures of your Analog Obsession tweaks and setups for each song you produce, for a real analog experience in the box"

 

I don't use Analog Obsession plugins, so pardon my ignorance here, but does it only break when there's a new major version? Or does it do this after every single update? If the latter, that would really suck. If the former, this isn't too uncommon.. I usually keep multiple major versions of some VSTs like Fabfilter and Arturia, for that reason. But if it breaks projects after every single update (or close to it), then yah, that is pretty ridiculous, but I guess you get what you pay for, or something.

 

This. It was a simple GUI update, the plugin controls were the same, and not was a major update like ozone 8, 9, 10 etc. Regular updates

 

The bugfixes?

 

Cool, did you leave AO a message with feedback? Because complaining in a forum may contribute temporarily to your own satisfaction, but not to the long-term solution of the problem.

 

What kind of satisfaction? could you be more specific? i was thrown dog shit when i posted this thread, even by you. And yes, i talked about the issues with the developer, but he seems to not care about this. This is not a short term issue, its happening for a long time. How's your experience with the company? Do you have any? It seems you are the one who has nothing to talk and get satisfaction (you used this word first) answering random things to a random guy on a forum. I'm not trying to solve the problems of tunca, just trying to aware people of what they can get by upgrading blindly AO plugins. I posted something related to a software dev in the software section. So, whats the deal?

 

Now free ... on Patreon (5,5 each month minimum)
What a joke ...

1 969 ppl
So around 10 K like you said

I remember the time when ppl said "meh..."
And i still do.

Talk about Variety Of Sound Bootsy or
VladG or
TOKYO DAWN LABS
...

That's another level

 

I don't think Analog Obsession is unique here..

I always have a bit of paranoia about updating a plugin, because of changes that might break. TAL Reverb 4 is a great example, it has fucking 5 different versions!! and they all sound different. So I have been forced to pre-emptively name them TAL-Reverb-4v1.dll, 4v2.dll etc.

Same with Blue Cat plugins, an update occurs, do I really care? Will it sound different? Do I have the time to check? At least Blue Cat names his plugins BC Phaser 2, 3, 4, etc. on each update.

This isn't a new thing, sometimes my project's FXP presets only load properly (or at all) with specific DLL versions, so I keep a backup of my entire plugin tree.

I tend to stick to old versions of plugins to avoid all these problems, and I am fine with it, or I simply do tests with old projects after updating to see if problems occur, if I decide to update. I still use an old version of MDE-X.dll because of this fear, plus the issue of Korg Collection requring additional software to run, while my old version needs just one DLL.

So the answer is simple, undo your update, find the old version you used before, and don't bother using his plugins. If the project is important or unfinished, and you MUST use a newer plugin, just try to find a replacement and A/B to match to ensure its achieving a similar result.

I've not tried any of his plugins but I think I downloaded them somewhere... easy to find even them too without giving any money. Not going to complain about donations since it's not anyone's place to say who deserves or not to make a living.

 

Not quite. He gave all for free, updated shitty sounding plugins to sound good, people started loving him for that, became a saint and now earns *decently* a month for the new good stuff.

LALA was shit originally, but v2.1 already sounded very good and better than many paid LA-2A plugins. I'm not sure about this new v3.0 thou. I have no patience for a thorough test, just quickly checked it out and instantly noticed the release time which is now much faster than it was in v2.1 (where it was a little bit too fast already) and much more different than in the original hardware where the dual-release behavior is clearly noticeable and overall it's quite slow. Also if the oversampling should improve something, at least it doesn't show in PluginDoctor either for v2.1 or v3.0.

Edit: Now I read the changelog and see that resizable interface and AAX support should be the only changes in v3.0. But the different release is clearly visible. Now I have to make a thorough test anyway for this, dammit, to see if it's only the GUI that lies while the actual release has stayed the same.

Edit2: After the test I can confirm v2.1 and v3.0 sound totally different, like completely different plugins. The changelog only mentions what has changed in 3.0 compared to the previous release but doesn't tell what the previous version was. Maybe there was something between 2.1 and 3.0 that I have missed...

 

Last edited: Dec 23, 2022

Would you mind sharing those reasons please? I'm curious.

 

Why so passive aggressive? Yes, I use 3 of his plugins from time to time. Without problems, mind you. But I also do not update costantly. Why should I? They work.
I finish my projects, render multi-tracks and stereo out, store backups, and move everything to the NAS. Done. Even if I update, it should not come to such problems. So yes, you are responsible for your system. Don't rely on others.

 

Maybe not pictures, but putting notes in your project is not a bad idea. At some point I got so tired of a plugin not always recalling settings correctly that I made a preset and put the preset name in the track.

 

Wow, I think you're right. LALA 2.1 and 3.0 look completely different. This is a sine wave through 3.0:



And 2.1:



I don't know how LA-2As are supposed to work, but that looks pretty 'wtf' to me.

 

No
Fucking
Way


Well, let's look at the bright side. At least the last version does "something"

 

Serious?

The whole thread was about upgrades related to AO plugins. Why shouldn't you update legit plugins? that's the question you should ask yourself