v3.066 does not sound the same as before

[Teksonik]

This is obviously not right... What happened?! Very concerned about this...

It might help Lennard if you explained exactly what the point you're trying to make in that graphic.

[flounderhouse]

This picture obviously looks very buggy, most notably, every destination param is mapped to "ampEnv A attack".

I have not yet saved an ableton project that looks like this. This is because I noticed the sound difference right away and began contacting this forum. The only thing I've done is open old projects and close them without saving. The only time I ever saved something after the update was when I saved the sylenth preset and emailed it over.

Because of this, I'm hoping that if I instead launch these Ableton projects with the old version of sylenth installed, I can have my music back.

If for some reason you'd rather not give out old versions of sylenth to a customer, or perhaps this can cause more problems or something, I'd consider sending you one of my whole Ableton projects as it was saved before the sylenth update.

[Teksonik]

But that seems like an Ableton issue not a Sylenth 1 issue. What does Sylenth have to do with Ableton mapping ? How could a Sylenth update change Ableton Mapping ?

Have you updated Ableton Live recently ?

Anyway I'm sure Lennard will be along shortly.

[flounderhouse]

Yes, Teksonic, i was a little hasty in posting the graphic. Lennard asked for what parameters were being automated and so when I tried to check in the project I saw this. I was not trying to automate "ampEnv A attack" eight times over with the same macro knob.... this is surely why it sounded so glitched out in that one song, and also what would cause erratic behavior.

[flounderhouse]

No, I'm 100% sure this issue only arose after a sylenth update. No other updates were done at that time. Not by me anyway, however, I'm seeing in my ableton preferences that "automatic updates" are switched on... not yet sure if ableton happened to update that very same night without my noticing.

[Teksonik]

I don't use Ableton Live so forgive my ignorance but I'm not understanding how Sylenth or any plugin for that matter could change settings that were made in Live whether it's AmpEnv A Attack Time or whatever parameter.

But I have used quite a few other DAWs and I can't figure out how any plugin could change settings or mappings in the DAW project but again maybe I'm just ignorant of the way Live works. It's never happened in any of the DAWs I've owned.

[flounderhouse]

I agree with what you are saying--why would the ableton data change? I've been assuming that it isn't, and I'm hoping that fact will help narrow down just what the problem is. It's gonna be somewhat confusing to look at this picture if you are not familiar with Ableton's macro knobs. I'll briefly explain:

- The bottom-left eight knobs are the macro knobs that you wiggle or automate.
- The bottom-right area (currently highlighted in purple) are sylenth parameters. (multiple sylenth param destinations can be chosen per macro knob).
- The top has a list of all these sylenth parameters where you can program the minimum or maximum value that sylenth will take on when the macro knob is fully-counter-clockwise or fully-clockwise respectively.

***To reiterate, the issue with this picture is those stylenth parameter destinations are not the same ones I originally chose.

[e-crooner]

Thanks Teksonik. And thanks e-crooner. We are still unsure whether its an issue for all Mac users, or just for the older OS versions. I'm considering upgrading my OS. Its free. But I'd rather not cause I like my current one, and everything else works great.

I'm not sure how close we are to a solution, but to buy time, I'm still eager to get hands a download link for the old v3.054. But would it even install correctly? The last thing I wanna do is permanently lose sound design work.

That said, lets move forward in finding a permanent solution for v3.066.

Lennard, I assume you are not easily able to recreate the problem. Instead, I think it'd be useful to show you exactly this aforementioned erratic behavior in an ableton project. I was thinking I'd record a pair of tracks simultaneously--one being midi loop containing recorded knob automation, and the other being its resulting audio. Its alot of effort to try and explain here what happens. But if you heard what I heard, and saw the automation causing it, it might provide insight.. Let me know what you need from me and I'll knock it all out in one go!

Probably not a good idea as your Ableton 9 will not be supported by the latest Mac OS:
https://www.sweetwater.com/sweetcare/ar ... ility-list

[e-crooner]

I think the only changes concerning the envelopes are the new menu options for copying envelope setting to other envelopes. Can it have to do with that?

[Lennard]

Hi, can you please send the project file through wetransfer (or anything similar) to our support email? Then I'll have a look at it.

[flounderhouse]

Ok I sent an entire project folder over via weTransfer. Be sure to read the notes that accompany each of the three uploads! My ableton projects are messy--fair warning! At least everything is labeled... You are probably still missing several samples so hope that doesnt bother you. Don't hesitate to let me know if you need anything else from me!

Thanks to everyone for your help and ideas on this!

[Lennard]

Thanks, that was helpful! It seems there was a problem with the automation parameters in the AU version of v3.066. I've found the cause and fixed it in v3.067. You can download the updated version from your account page.

This problem occured only in the AU version on Mac, not in the VST or AAX versions.

[flounderhouse]

Lennard, you are my hero. WE ARE BACK!!!!