Eos 1.4.0 for OS X Now Available...
From the original Analog Industries archive. Some links and images from that era no longer resolve.
If you hit your account in the Audio Damage store, you can grab the Eos 1.4.0 installer for OS X. This installer throws what Apple terms “Standard (32/64-bit Intel)” builds of both the VST and AU. These work in every 64-bit host we could find on the OS X platform, both VST and AudioUnit. The sum total of these are Logic, Cubase 5/6, Reaper, Plogue Bidule, and Studio One, best I’m aware.
In any case, the version number change should force a re-scan, but if you run in to any issues at all, drop me a line via the AD info@ address, or if you have some info that everyone will benefit from, feel free to post it here.
We’re going to do Discord3 and Replicant1.5 next, because they are built with the same framework as Eos, and it should be fairly easy to give them this treatment. We’re going to wait a couple days, though, to make sure this Eos version doesn’t have any problems before we do, though.
And finally, note that if you haven’t updated Eos in the last update round (v1.1.0) then you need to make preparations before using this one. Your existing projects that use Eos won’t break, but the preset manager is somewhat different, and as a result, Eos will return to its default state (the first preset, “This Budd’s For You.”) Also, any presets you’ve created for Eos won’t load. There’s nothing we can do about this, due to a fundamental architecture change internally. So plan accordingly.
15 comments
Chris, I can't get it to show up in Logic 9.1.3 running 64-bit. It scanned as expected launching 32-bit Logic, but no scan and nothing showing up in the AU manager under 64-bit.
Also, is there any way you can get the AD Authorizer app to not send itself to the back of all open windows/apps after its dialog box shows up?
See, that's a good example of a letter that should have been sent to the info@ address. Write me there, and I'll talk you through the steps for getting it recognized.
-CR
Done. Sorry for the bandwidth...
Congratulations (and thank you!) for figuring out the 64 bit issues! The 64-bit AU will be big news for Logic 9 users, as a lot of them refuse to use 32-bit plugins at this point. Which probably has more to do with the wonkiness of the 32-bit bridge than anything else, but hey, it's not like I could code up something better than the bridge...
It's not like Apple could, either.
Seriously, I hope they have a major rewrite in store for Logic, because it is getting to be really fucking hinky.
-CR
after the 64 bit updates the RTAS versions are coming right?
still 32bit here. i haven't booted anything in 64 bit ever. not gonna happen anytime soon for me. still too many apps in 32 bit only. my laptop does 71 tracks reliably w/the logic benchmark test at 32 bit. i don't feel lacking
i've had more logic crashes lately so agree w/the logic is getting hinky comment. i hope the rewrite is in the pipeline as well.
Is that "won't load at all" or "won't load automatically, but by hand everything's ok"?
Sorry to bash in public - but is there _any_ way at all one could load previously created presets? Would it be possible to create a converter for the job? Anything else than would be great.
I haven't been able to test the plugin yet due to several issues, but if I've saved a song in Logic with certain settings, will EOS remember those settings? If not, fuck.
Also, I'd like to know how other plugin manufacturers have cleared similar situations, just out of curiosity.
Email sent.
One thing was left out from my post due to brackets, sorry for reposting of sorts:
... Would it be possible to create a converter for the job? Anything else than (opening the presets in my laptop -> writing down the values -> entering them again on a studio computer) would be great....
Plug-in manufacturers that don't have this problem have uniformly made their own preset mechanisms. Since we're good little boys and use the canonical methods, we (and you) have to pay the price in situations like this.
That said, in a plugin this simple, it's really not that big a deal. Eos only has 12 published parameters. I don't want to get off on a "you kids have it so easy" rant, but in the couple hours (at a couple hundred dollars an hour) it would take to recall a song in a proper studio, just know that each song you worked on had a folder, and in that folder were pieces of paper that had drawings of each effect in the rack. With marks on the paper showing where the knobs were. The absolute best case scenario for a recall was "in the ballpark," even with a total recall console.
All that said, I have the considered opinion that the VST won't be affected in this manner. It's really only the AU.
-CR
I've given up on grasping what 64-bit means to my work. I am super dumb in some areas and this is one of them.
It's like a memory address thing, right?
I have no idea if DP7.2 is 64 bit or not. I don't really understand any of this stuff.
- c
Ha! Reading my own writing: I say "I've given up." And then I ask the question again.
If it helps, I exasperate MYSELF.
(I know it doesn't help.)
- c
DP7.2 is not 64-bit. To answer your question, the main benefit is that the computer itself can have fairly massive amounts of RAM. The biggest (really only, in our world) benefit is that you can have huge sample libraries resident in RAM, without disk streaming.
Pretty much anything else you've ever heard about 64-bit this-and-that is a load of bullshit. There are, as anyone that does audio for a living knows, so many variables in the chain from microphone to the speakers in the listener's hooptie that it is nearly impossible to say that something as prosaic as 64-bit floating point math in a DSP algorithm will have any any measurable effect on the result.
Producers are big fans of minutia, though, and this is something they can grab on to. Also, the various bit bridges go from "mostly works" to "barely works" and we don't like that our products get sent to the back of the bus(s). So we update. And update. And update. And update.
Luckily 128-bit computing is at least a decade away.
-CR
Chad, if I'm mixing a song with 100+ tracks, running a bunch of plug-ins and analog inserts, having Logic address more than 4GB of RAM is a beautiful thing.
I run up against the 4GB max when running Logic 32-bit all the time, so for me, the more plugs I have that run 64-bit, and thus limit the amount I have to use the crapass 32-bit AU Bridge, the happier I am.
Comments are closed on this post.