Finally EOS updates to 64-bit!!

[samsam]

OK, so I've gone onto AD's blog and it says this:

"If you open a previous project that had the AudioUnit version instanced, 1.1.0 will instance fine. However, the settings will revert to the default preset ("This Budd's For You.") This is due to a change in the preset structure in the AU version. Plan accordingly. "

So, what does "plan accordingly" mean? I've been using the AU in Live (which Chris now says is pretty dumb behaviour, Chris, mate, wish you'd said that sooner) so in my case, before I ever update to this version, would I have to go though every instance I've used of EOS in a tune since I bought it, open up the VST, copy the settings from the AU, delete the AU, repeat for every other instance in the song?

I'm missing a point here, right? I'm way off the mark and don't have to do anything near as time consuming as what i've just speculated, right?

[Cordelia]

Did Audio Damage fix the problem with their plug-ins and REAPER?

Sorry, didn't hear anything about that. What problems?
Been using EOS in Reaper 3 and Reaper 4 Alpha for a few months now, never had problems with the combination?

Glad to hear it works OK.

I'm talking about this problem:

http://forum.cockos.com/showthread.php? ... dio+damage

I never saw an official post from AD, maybe I missed it.

No, AD refuses to deal with it. Justin coded me a patch in just a few minutes that has worked well, both to help me out and, I think, to prove that his understanding of the issue is clear, and to prove in code that the fault lies with AD. I don't know if his patch will continue to work in future versions of Reaper, so I've stopped upgrading. I've also bought my last AD plugin, I'm guessing.

Whatever. When I think of the money I've spent on software plugins, I mostly want it all back.

Anyway, much happiness, big hugs all around for AD's (first??) successful 64bit plugin. What a big day!

[Mercado_Negro]

Hi Cordelia,

Thanks for your input. Yesterday I contacted AD via e-mail and Chris Randall told me that they switched to the new version of VSTGUI and they haven't heard of problems since then. The plug-ins that should be free of problems are Discord3, Axon, Phosphor, Replicant, and Eos. If you ever update your plug-ins please let us know your findings

Cheers

[Cordelia]

Hmmm. So possibly it would be worth it to me to update Eos. I hope in time all AD plugins are updated with the new VSTGUI.
Thank you for the information!

Edit: It's unclear to me- is the Eos update 64bit only? Is there an updated 32bit version?

[Funkybot's Evil Twin]

Did Audio Damage fix the problem with their plug-ins and REAPER?

Sorry, didn't hear anything about that. What problems?
Been using EOS in Reaper 3 and Reaper 4 Alpha for a few months now, never had problems with the combination?

Glad to hear it works OK.

I'm talking about this problem:

http://forum.cockos.com/showthread.php? ... dio+damage

I never saw an official post from AD, maybe I missed it.

No, AD refuses to deal with it. Justin coded me a patch in just a few minutes that has worked well, both to help me out and, I think, to prove that his understanding of the issue is clear, and to prove in code that the fault lies with AD. I don't know if his patch will continue to work in future versions of Reaper, so I've stopped upgrading. I've also bought my last AD plugin, I'm guessing.

Whatever. When I think of the money I've spent on software plugins, I mostly want it all back.

Anyway, much happiness, big hugs all around for AD's (first??) successful 64bit plugin. What a big day!

Justin also posted the patch in the forums. Now to be fair, if Justin coded a patch that fixes it, I'd ask, "how does that prove it's an AD bug?" In fact, I'd say that indicates the opposite. The problem, if I remember correctly is that Reaper doesn't support some framework that's not common to a lot of plugins, but is also supported by every other host.

[Funkybot's Evil Twin]

Edit: It's unclear to me- is the Eos update 64bit only? Is there an updated 32bit version?

Yes, the updated 32 bit version just uses the new GUI.

[Cordelia]

Great, thanks.

[lightsfadelow]

AmpliTube has 64-bit in the works. Expect it this quarter!

Any ideas about T-Racks 3 DeLuxe?

No firm date yet, it will have to come after upcoming product launches, so still a ways off. But it is on the radar.

Sigh...

I guess it will be another year or two before I use t-racks again.

[samsam]

OK, so I've gone onto AD's blog and it says this:

"If you open a previous project that had the AudioUnit version instanced, 1.1.0 will instance fine. However, the settings will revert to the default preset ("This Budd's For You.") This is due to a change in the preset structure in the AU version. Plan accordingly. "

So, what does "plan accordingly" mean? I've been using the AU in Live (which Chris now says is pretty dumb behaviour, Chris, mate, wish you'd said that sooner) so in my case, before I ever update to this version, would I have to go though every instance I've used of EOS in a tune since I bought it, open up the VST, copy the settings from the AU, delete the AU, repeat for every other instance in the song?

I'm missing a point here, right? I'm way off the mark and don't have to do anything near as time consuming as what i've just speculated, right?

If any other OS X/Live/AU users are reading this:

I emailed Chris and his advice was no need to update for the moment but to get older projects ready for any future update, a good idea would be to replace all instances of AUs in songs with VSTs.

[todd_r]

Justin also posted the patch in the forums. Now to be fair, if Justin coded a patch that fixes it, I'd ask, "how does that prove it's an AD bug?" In fact, I'd say that indicates the opposite. The problem, if I remember correctly is that Reaper doesn't support some framework that's not common to a lot of plugins, but is also supported by every other host.

Thats not true, alot of other plugins use gdi+ and dont crash, the AD plugins crash as they dont 'unload' it properly, it only doesnt show up in other hosts as they use gdi themselves, whereas reaper uses its own graphics library.

[Funkybot's Evil Twin]

Thats not true, alot of other plugins use gdi+ and dont crash, the AD plugins crash as they dont 'unload' it properly, it only doesnt show up in other hosts as they use gdi themselves, whereas reaper uses its own graphics library.

Again...doesn't sound like this is entirely AD's fault here. Why is Reaper the only host not using GDI?

My point: there's obviously steps both companies could take to resolve this. AD's already going 64-bit, which addresses the problem. And Justin already coded up a patch to support the effected AD plugins. I just think all the blame going to AD is a little unfair.

[todd_r]

...doesn't sound like this is entirely AD's fault here...

Well its not entirely, if irc it's actually a bug with the vst sdk they are using, but still it's a bug with the plugin and not the host

... Why is Reaper the only host not using GDI?..

It's just MS's built in graphics library, any programme is free to use it or a third party, or, as in cockos case, write their own(LICE). They did this because they wanted something faster/lighter and cross platform...

"Just a bit more technical context.

This is not a question of "Reaper choosing not to support GDI+". If a plugin wants to use GDI+, it can do so in the normal way. Plenty of plugins do use GDI+ properly.

The bug here is that these particular problem plugins apparently use GDI+ but don't unload it properly. The audiodamagefix.dll that Justin supplied does nothing but load GDI+ and never unload it.

Justin's dll essentially introduces a new (generally benign) bug that cancels out the plugin's bug. Which is why Justin wrote that the fix is "otherwise pointless and generally bad form."

I know that for most people this whole business probably just sounds like tiresome blame-passing, which is a bummer."

[Brian @ IK Multimedia]

AmpliTube has 64-bit in the works. Expect it this quarter!

Any ideas about T-Racks 3 DeLuxe?

No firm date yet, it will have to come after upcoming product launches, so still a ways off. But it is on the radar.

Sigh...

I guess it will be another year or two before I use t-racks again.

Just to reiterate and clarify, when I said "a ways off" that simply meant most likely not until the early part of next quarter.