Is 2C's Aether REALLY worth it? (the answer is: yes, certainly)

[kelldammit]

Ltz,
Look in your plugin folder, and make sure the aether folder (and the folders within it) is not "read only". once you fix that, and enter the s/n, it should "take".

the installer seemed to work great here (vista32)...had issues with the last one (had to manually install).

kell

[Lotuzia]

Ltz,
Look in your plugin folder, and make sure the aether folder (and the folders within it) is not "read only". once you fix that, and enter the s/n, it should "take".

the installer seemed to work great here (vista32)...had issues with the last one (had to manually install).

kell

Yesssssssssssssssssssss It workedddddddd

You're my heroe of the day Kell

Thanks a lot !

LtZ

[Lenticular]

I ran a normal installation of the update & all my user presets were erased as well.

[ozmoz2008]

had issues with the last one (had to manually install).

kell

Same here, but the new installer seems to work fine in 32bit and 64. In 64bit before I was seeing the 32bit plug, probably a mistake I did, but now everything is fine.

I had to write my serial again though.(I did a repair too)

Good job on the installer Andrew & co!

[Andrew Souter]

I ran a normal installation of the update & all my user presets were erased as well.

Thank's for the update. The only thing that is a bit annoying is that with every update one has to re-enter the serial no. But that's just a minor issue.

This SHOULD not happen. The installer is designed to preserve both User Presets, and Authrorizaiton status so that you SHOULD NOT need to re-enter SN and you SHOULD keep your user presets.

However, sometimes users have some weird nebulous disk-permission (read only) stuff going on, and this can interfere with the installer.

From the README:

========================================================
1.1 Installation on Mac OS X
========================================================
UPDATING FROM 1.5.0: You can update your current 1.5.0 installation by running the 1.5.1 installer. The authorization settings and user presets are preserved, however we strongly recommend to backup you user presets before launching 1.5.1 installer. You can find user presets here:

/Library/Application Support/2C-Audio/Aether/Presets/user.

Note: plug-in settings are not preserved, so please enter your desired settings on the Info page upon updating to 1.5.1.

========================================================
1.2 Installation on PC/Windows
========================================================
UPDATING FROM 1.5.0: You can update your current 1.5.0 installation by running the 1.5.1 installer. The authorization settings and user presets are preserved, however as an extra precaution, we strongly recommend to backup you user presets before launching 1.5.1 installer. You can find your 1.5.0 user presets in your VST Plug-ins folder under

/2C-Aether/Presets/user.

Note: plug-in preferences and settings are not preserved, so please enter your desired settings on the Info page upon updating to 1.5.1.

And I am updating the Readme again to put at the very top:

NOTE 1: If you are updating from a previous version of Aether, the Aether installer is designed to preserve any User Presets that you have previously created. However, occasionally user' disk-permission settings interfere with the installer's ability to read or write to the User Presets folder. Because of this, if you have created critical User Presets that you wish to preserve, we STRONGLY ADVISE THAT YOU MANUALLY BACK UP YOUR USER PRESETS BEFORE RUNNING ANY UPDATES. Please see below for instructions.

[Sampleconstruct]

Thank's for the update. The only thing that is a bit annoying is that with every update one has to re-enter the serial no. But that's just a minor issue.

This SHOULD not happen. The installer is designed to preserve both User Presets, and Authrorizaiton status so that you SHOULD NOT need to re-enter SN and you SHOULD keep your user presets.

However, sometimes users have some weird nebulous disk-permission (read only) stuff going on, and this can interfere with the installer.

Well it happened with both updates and other users are experiencing the same so even if it should not happen it does happen, but re-entering the serial wasn't so hard

[Adrian Earnshaw Music]

I just upgraded to the latest version and got a similar problem regarding the file error during installation. I am on windows 7 64 bit.

On retrying I noticed that if you navigate to the folder you want to install Aether it will add a \ after the file path:- ie:- C:\Plugins\Aether\. For some reason the install script insists on adding another \ after it so in effect it is trying to install to C:\Plugins\Aether\\ which is of course an invalid path. The simple thing to do is navigate to the folder you want to install it to and then delete the \ in the install file path dialog box, so your file path reads C:\Plugins\Aether, and it should install okay without the file errors.

Hope I've explained this okay

Adrian

[jbraner]

Win 7 x64, upgraded from 1.5.0 to 1.5.1

It puts the presets into a completely different folder! Should I copy my old factory presets to the one?

It put the presets etc under c:\program files. I uninstalled and reinstalled and told it to use the VST folder as the "shared" folder (I've only installed the 64 bit VST plugin) but it still uses a different path.

So now I've got presets in two different places. I guess I'll just merge the two, but that's strange behaviour for a minor (version) update.

EDIT: And if you try to re-install a preset pack, it tells you that Aether isn't installed!

[kelldammit]

This SHOULD not happen. The installer is designed to preserve both User Presets, and Authrorizaiton status so that you SHOULD NOT need to re-enter SN and you SHOULD keep your user presets.
However, sometimes users have some weird nebulous disk-permission (read only) stuff going on, and this can interfere with the installer.

heh. "nebulous permissions" just sounds so...dirty!
it just seems like the installers do blanket replacements of the folders in question, which is obviously the way to go for updates or even fresh installs. if that's what's going on, could the installer just ignore the user folder if one is already present? if a user folder isn't present, it could just create one then...
i don't so much mind having to reenter the serial, as i'll take all the karmic boosting i can get! all of the installers have done this to me as well, as well as the "permissions" thing. no great shakes, really, but perhaps the settings.spt file (if present) could be ignored as well?

it is always sound policy to back up prior to updating (i always save copies of any preset files within the relevant project folders, too...i've been burnt by lost presets before). perhaps that should go in bold as step 1 of the update procedure
at any rate, good work! overall, the new installer does seem to work much better than the last couple and of course, thanks for the update! it IS much appreciated!

@Ltz - you're welcome! 1.5.1 would crash for me too, but that was due to some of the folders not being created by the installer (manual install was the workaround). i'd hazard the guess that it may have been your problem as well, especially since your v1, and 1.5.1 installs worked right out of the gate.


kell

[Andrew Souter]

File/folder/resource structure is basically completely different in 1.5.1 compared to 1.5.0 on Windows at least (and there are a lot of changes on OSX also).

Things are now organized in a similar way as on OSX. We have a shared company folder in /Program Files/ (like in /Application Support/ on OSX). This stores all the important stuff. And is shared for all hosts, so that you don't have to maintain 3 sets of presets, preferences, etc...

Then we have only "shells" in the various host plug-in folders (VST 32, VST 64, RTAS... for now, and maybe more later). These basically tell the host "hey, load stuff from our shared company folder"...


This should all be transparent to users and there SHOULD really be no need to know this as a user... But if you previously did a manual install for 1.5.0 and/or moved things around, and/or used custom folder locations for various things... it is possible this could confuse our new installer I suppose.

The new structure is MUCH better. All resources are shared. All files are saved on one static place. All user files are in a known location now. So going forward it is MUCH better.

It was actually a pretty massive amount of low-level work to restructure things this way. But it way needed for RTAS, and it is better/easier as people transition between 32bit and 64bit hosts also.

[Andrew Souter]

EDIT: And if you try to re-install a preset pack, it tells you that Aether isn't installed!

Preset Expansions have new installers now too.

If you need to re-install these, please "reorder"

0) Go here:

http://www.galbanum.com/shop/product_in ... ucts_id=77

1) Select the preset expansion(s) you ordered previously from the drop down menu(s)
2) Add this update to your shopping cart and proceed to the checkout page
3) On the checkout page enter the following coupon code and click on Redeem:

AetherExpansionsReDownload

This will change the price to $0.00. There is no cost and no payment info is required.

[jbraner]

This should all be transparent to users and there SHOULD really be no need to know this as a user... But if you previously did a manual install for 1.5.0 and/or moved things around, and/or used custom folder locations for various things... it is possible this could confuse our new installer I suppose.

I didn't do anything "funny"
I just installed everything normally and that's where it put the presets, freq profiles, skins etc. It put them in folders "level" with the VST folder. Now it installs the presets, freq profiles etc etc to a different place - and you have two sets - in two different places. *that* will lead to confusion.

The new structure is MUCH better. All resources are shared. All files are saved on one static place. All user files are in a known location now. So going forward it is MUCH better.

It's debatable whether it's better. Some developers use \program files, some use \program files(x86) (so the 32 bit version can see them) some use \users\username\appdata and some use the folder that the plugin is in (like you used to).

They all think their way is better
All we are is confused - especially when the paths change from version to version.

Preset Expansions have new installers now too.

Ahh thanks.

I guess I'll reinstall with the shared stuff under \program files and reinstal my preset pack again...

[Andrew Souter]

There is only one correct folder location for all presets, resources, etc. now:

Win (new): .../Program Files/2C-Audio/Aether/...
OSX (same as previous): .../Application Support/2C-Audio/Aether/...

One Folder to rule them all, One Folder to find them,
One Folder to bring them all and in the DAWness bind them
In the Land of 2C-Audio where the Aethers lie...

One Folder to rule them all...

This is much easier to manage and keep track of...

[jbraner]

This is much easier to manage and keep track of...

Unless the user chooses a different location.

[Andrew Souter]

This is much easier to manage and keep track of...

Unless the user chooses a different location.

Heretic! Burn him!