Eos 1.1.0 Now Available...
From the original Analog Industries archive. Some links and images from that era no longer resolve.
Eos 1.1.0 is now available for download in the AD Store.
New UI. We’ve updated the user interface a touch to match the other recent AD products. Operationally, no change whatsoever.
Windows 64-bit. The Windows installer now installs a native 64-bit VST as well as the 32-bit VST.
All-new AudioUnit. The AudioUnit architecture has been entirely changed to ease future versions, and to fix several bugs existing in the previous AU version.
Those are the major changes. The VST versions are otherwise completely un-changed, and are drop-in replacements for version 1.0.2.
Now, a word about the OS X side of things. Due to some fairly major changes in the way that Apple’s installer maker works between when we pushed 1.0.2 and now, here’s the deal. If you’re installing the OS X version, and you have 1.0.2 already installed, you must delete both the VST and AU prior to installing. If you don’t, you’re gonna gum up your AU cache, and while Live and DP and other AU hosts may be able to deal with things, Logic, being somewhat retarded, will get all confused. If you don’t delete the prior versions, you’re going to spend some time in an email conversation with me getting things un-stuck. If this is the sort of thing that sounds like fun to you, by all means ignore this warning.
ALSO TOO: 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. The VST doesn’t suffer from this problem, on either Windows or Mac.
AND FINALLY: This is only semi-related. I’ve lately noticed a lot of people that use Live as their main DAW, and don’t have Logic at all, who use the AU instead of the VST. All our recent products are built using Sonic Charge’s Symbiosis compatibility layer, and the AU is just a VST with an extra layer of crap on top to make it act like an AU. With commercial plug-ins, it is very rare for the plug to be a true AU. Almost all commercial plugs use some sort of compatibility layer or wrapper to create the AU, and you are nearly always better off using the VST, given the choice between the two.
I imagine that the reasoning behind using an AU in Live is that people think “well, I’m on an Apple. The AU must be better!!!” This is false. The AU is never better. Ever. You might like the preset mechanism more, but as far as Live’s presets go, this is a transparent experience to the user, and thus moot. The only reason you’d have for using an AU in Live is if you want to make presets there and then use them in Logic or DP, or vice-versa. If you don’t do this, use the VST.
So, with that out of the way, go get your new Eos and enjoy!
27 comments
Good to hear, bleen; thanks. This one was fussier than usual.
--Adam
"That company doesn't know shit about fuck about making plug-ins, yet we all have to deal with this ridiculous standard they dreamed up."
(stands up, starts slowly clapping, waits for rest of the audience to join in)
The layout is fantastically usable and non-fat. I do like the contrast and look of D3 and Phosphor more. Low contrast and small fonts are a problem for old people, so I hear.
The reason I use AU's on the rare occasion I open Live; I have a fair number of plugins. My Components folder says 348 items right now (There is nothing about any of the software I use that takes this possibility into consideration, no way to sort, group, etc.).
I spend way too much time trying (and failing) to keep the software I use up to date, and keep it synced between 2 computers. I gave up on keeping the VST's organized a long time ago. It's like Russian Roulette whether a VST is going to work or not for me. Just a couple of days ago I threw out some VST's from the early 2000's I found in there. I had to scrape them off.
bb
Did Apple retain any of the staff from emagic when they bought Logic? I'm still miffed at them for doing that.
@ D' MacKinnon
Yes, the dev team from emagic still exists.
Fascinating. Thank you for explaining the difference between audio units and vsts. A while ago, I had searched everywhere for an answer as to why the two formats exist and which I should generally use on a mac. This sums it up.
ROCKIN'! It's working great here in Logic AND Live.
Good to hear, bleen; thanks. This one was fussier than usual.
--Adam
Wanted to echo comments of tuckmeister22 to CR. Never had a problem with an AU in Live, so I guess ignorance is bliss.
So, obviously this is a day late and a dollar short, as you asked for UI comments last week, but - the low contrast is a real problem, for me anyway. This is a design issue that has been going on for years, but it's gotten much worse of late. Gray on gray on gray is not a scheme for legibility, in my opinion, rather one for eyestrain and headaches. Try this: squint at the box containing the waveform in the oval. Can you tell that the oval has a waveform in it when you do?
Yes.
-CR
I think you must have your screen set up wrong Snuggly.
Or maybe... http://www.colblindor.com/rgb-anomaloscope-color-blindness-test/
- Hugo
I guess I'm GUI-blind, in that 'good enough' is good enough. The old interface was fine, the new one's fine too.
Did I mention that every time I've tried to do Graphic Design the result looked awful?
Oh and here's a question. WHY DUNT THE 64BIT VERSION SOUND BETTERER!?! WHO WHO QUIT ATH+++
I don't think that Audio Units are particularly evil. On the other hand, Logic IS an evil Audio Unit host. I've had AU's work fine in Live and GarageBand, only to give me problems in Logic. For some unknown reason, once Logic loads an Audio Unit into a project, it keeps some weird state of that Audio Unit for the life of that project, which sucks if you are developing that Audio Unit. It must have something to do with preloading things to have projects open up faster, but Logic takes forever to load anyway.
And yeah, Logic is the main reason that people develop Audio Units in the first place, so any issues with Logic end up becoming global Audio Unit issues. Apple doesn't seem to follow their own standards.
Ironically (or not) the plug-ins that come with Logic aren't plug-ins at all, and certainly not AudioUnits, but rather part of the program, in the same way that the channel fader is part of the program.
The only AudioUnits that Apple makes don't even have fucking UIs; they're just the bullshit built-in ones that you have programmatic access to. That company doesn't know shit about fuck about making plug-ins, yet we all have to deal with this ridiculous standard they dreamed up.
Steinberg, on the other hand, at least uses the VST SDK. All Steinberg's plugs are actual VST plug-ins. Granted, most of them only work in Steinberg products, but Steinberg practices what they preach.
Don't even get me started on the ability of $RANDOM_PLUGIN to change a channel from mono to stereo in Logic. What the fuck is that bullshit? We removed that foolishness, and good riddance.
-CR
Everything's good here. Even the "infinite" is now ok in both Logic and Live. Thanks, guys!
Interesting. I didn't realize that so many AU's were made from VSTs but I figured there was some kind of similar process. Otherwise how would so many small indie developers be able to offer different versions of their plugins. Live is my main DAW and I've often wondered whether to use the VST or AU version. As primarily a Mac user, I had assumed that the AUs were more efficient, stable, organic, lower calorie, guaranteed fresh, environmentally sustainable, 0% trans fat, fair trade-friendly, etc... Now I know better :)
Another thing to consider is that since Logic is the main AU host (sorry, DP, and to the 14 people that use Metro) AUs that we make necessarily take the host in to account. For example, Logic has no simple way to send MIDI to an insert effect, so we've just usually left any MIDI capabilities out of the AU, since the main host couldn't use them anyhow.
This doesn't matter as much as you'd think, because Live has a perfectly capable method of assigning hardware controllers to a plug-in's controls, but it's just something to consider. Symbiosis has a MIDI input for effects by default, so our last couple (Replicant and D3) have had the capability, and thus show up, bizarrely, as instrument inserts in Logic should you desire that capability.
-CR
Have to agree with the contrast complaints; it looks like the window is deselected, greyed out in the background.
As they say, "just sayin'."
@msouthard: I wouldn't expect the Automap wrapper to have any significant affect on _audio_ performance. The wrapper shouldn't be doing anything more involved than passing the input signal along to the wrapped plug-in, and passing the plug-in's output back to the host. It's very unlikely that these extra operations will have a measurable increase in CPU load, unless you're using a rather old CPU (and if you're doing that, well, you're gonna have other issues anyway). How well Automap works otherwise: lots of variables involved, obviously. In my limited experience, early versions of Automap didn't work particularly well while the current version (current as of a couple of months ago) seems pretty reliable on Cubase 5 on Windows. I had a fun time using my Remote SL Zero to control all of the knobs in Audio Damage's 914 filter bank, letting me "play" timbral changes in a synthesizer pad by moving the hardware sliders up and down.
And unitard just reminded me that I need to order a Cubase 6 update, sigh. Good to hear that Eos runs in it--thanks for that.
--Adam
What's your take on VST plugs wrapped for Novation Automap? Does that just add another layer of garbage on top that affects performance?
-Mike
The EOS update works and looks great in Cubase 6. Nice job AD (and Steinberg for a change).
@msouthard: I wouldn't expect the Automap wrapper to have any significant affect on _audio_ performance. The wrapper shouldn't be doing anything more involved than passing the input signal along to the wrapped plug-in, and passing the plug-in's output back to the host. It's very unlikely that these extra operations will have a measurable increase in CPU load, unless you're using a rather old CPU (and if you're doing that, well, you're gonna have other issues anyway). How well Automap works otherwise: lots of variables involved, obviously. In my limited experience, early versions of Automap didn't work particularly well while the current version (current as of a couple of months ago) seems pretty reliable on Cubase 5 on Windows. I had a fun time using my Remote SL Zero to control all of the knobs in Audio Damage's 914 filter bank, letting me "play" timbral changes in a synthesizer pad by moving the hardware sliders up and down.
And unitard just reminded me that I need to order a Cubase 6 update, sigh. Good to hear that Eos runs in it--thanks for that.
--Adam
The new Eos UI is more streamlined. The contrast seems easier on the eyes, and it works on both of my computers. All good things.
@Adam: Thanks for the info. I just picked up a nocturn and haven't noticed any issues yet. Playing the 914 sounds like fun, I might have to pick it up one of these days.
=Mike
Good to hear I'm not the only developer who hates this AudioUnit nightmare....
This said, a lot of composers, especially in the movie industry, use Logic.... which means we need to support them too.
Comments are closed on this post.