2C-Aether Reverb
-
- KVRian
- 698 posts since 21 Jan, 2009 from Every damn place
I installed it and it works great...I chose to remove the old version to do a little clean up on my VST library, but other that having to reauthorize I had no issues. All my old projects had no issues either. Just simply a Great, Great reverb.....
A+
A+
agent
Ableton-Moog-Spectrasonics-Native Instruments-Propellerhead-CamelAudio-LennarDigital-2CAudio-Renoise-Korg-JoMoX-MOTU-PeterTools-FXpansion-IK Multimedia-Fabfilter-Vinyl/Tape
Ableton-Moog-Spectrasonics-Native Instruments-Propellerhead-CamelAudio-LennarDigital-2CAudio-Renoise-Korg-JoMoX-MOTU-PeterTools-FXpansion-IK Multimedia-Fabfilter-Vinyl/Tape
-
- KVRist
- 243 posts since 16 Nov, 2007 from Spain
Same here.. Only installed Audio Unit however.rexlapin wrote:Hi Andrew,
I picked up Aether when it was first released and have been running it in
Tiger (10.4.11) all this time with no problem. However, after downloading
the new update it no longer works in Live 7/8 .
Hd
- KVRAF
- 2621 posts since 12 Sep, 2008
If you have x.4.11 issues, can you send me an email to:
suport at 2caudio dot com
?
suport at 2caudio dot com
?
-
- KVRAF
- 4265 posts since 21 Oct, 2001 from my bolthole in the south pacific
Andrew - coupla suggesions bro.
This process could be a little slicker.
I had to reauthorise even when I installed the new version over the old. Also your key had to typed in - no pasting from the clipboard like I do with many others. If I have the key open in text file in Notepad I have to make my host a minimal sized window so that Notepad doesn't disappear behind the host (due to lost focus) as soon as I enter the first digit into your authorisation screen. Allowing pasting of the whole code solves this at a stroke. Native Instruments and IKMM etc allow this.
This process could be a little slicker.
I had to reauthorise even when I installed the new version over the old. Also your key had to typed in - no pasting from the clipboard like I do with many others. If I have the key open in text file in Notepad I have to make my host a minimal sized window so that Notepad doesn't disappear behind the host (due to lost focus) as soon as I enter the first digit into your authorisation screen. Allowing pasting of the whole code solves this at a stroke. Native Instruments and IKMM etc allow this.
- KVRAF
- 2621 posts since 12 Sep, 2008
This "should" not be true. You "should" not have to reauthorize. What OS specifically?egbert wrote:I had to reauthorise even when I installed the new version over the old.
This is part of our Karma security system. This gives people five times to decide not to steal from us. It's our way of asking "are you sure you want to damage your karma"? Thieves have to confirm this decision 5 times, and well then the damage is done...egbert wrote:Also your key had to typed in - no pasting from the clipboard like I do with many others. If I have the key open in text file in Notepad I have to make my host a minimal sized window so that Notepad doesn't disappear behind the host (due to lost focus) as soon as I enter the first digit into your authorisation screen. Allowing pasting of the whole code solves this at a stroke. Native Instruments and IKMM etc allow this.
You can cut and paste one field at a time. We feel this system is much less obtrusive than the alternatives which all employ stronger and more authoritarian copy protection schemes which all carry their own set of hassles...
-
- KVRAF
- 4265 posts since 21 Oct, 2001 from my bolthole in the south pacific
That 5 part paste thing really isn't much help. Every time you go back and forth from your key source (eg from your text file in Notepad) to your Auth screen your Notepad instance is going to disappear. This means I have to screw around resizing my Cubase window nad my Notepad window which is spread over two large monitors before and after I run your authorisation. I didn't complain about doing this on first install but if this is going to be necessary for every point update then it is clearly a waste of customers' time and goodwill. Personally, if I had built this baby, I wouldn't want anything to distract my paying customers from the stellar product I had produced.
Updates shouldn't kill authorisations and entering codes should be a piece of cake.
Updates shouldn't kill authorisations and entering codes should be a piece of cake.
-
- KVRian
- 806 posts since 1 Sep, 2008 from US
Updated mine, didnt ask me to reauthorize. I think he meant if you want to uninstall before updating, then you'll have to do so.egbert wrote: Updates shouldn't kill authorisations and entering codes should be a piece of cake.
- KVRAF
- 2621 posts since 12 Sep, 2008
Right. Exactly. If you instal the update WITHOUT manually uninstalling the previous version, it SHOULD NOT ask you to reauthorize.softska wrote:Updated mine, didnt ask me to reauthorize. I think he meant if you want to uninstall before updating, then you'll have to do so.egbert wrote: Updates shouldn't kill authorisations and entering codes should be a piece of cake.
I see someone mentions Windows 7. That is not tested, so I can not say what happens on it. But for OSX and WIn XP and Vista, you should NOT have to reauthorize with this update, UNLESS you manually delete the previous install by choice (which is not needed).
- KVRAF
- 2621 posts since 12 Sep, 2008
you should have received an email last night giving the info. please email support at 2caudio dot com if you have not received itganymede wrote:Where is the update? Do you just install the new demo?
-
- KVRAF
- 4265 posts since 21 Oct, 2001 from my bolthole in the south pacific
I didn't uninstall 1.00 - I installed 1.01 over it on WinXP and had to reauthorise. If this is not how it was meant to go it is conceivable that the new location is different in some detail from the first install. I have two separate partitions - one for system and one for apps. The VSTplugins path I used was the same but perhaps the installer path is different.softska wrote:Updated mine, didnt ask me to reauthorize. I think he meant if you want to uninstall before updating, then you'll have to do so.egbert wrote: Updates shouldn't kill authorisations and entering codes should be a piece of cake.
Ideally, an installer should look in the registry or whatever and then offer your current install location for the plugin as the first option. Plenty of installers don't offer the current path though - eg PSP installers don't but for example NI and Voxengo do and I always appreciate the fact that they get these little details right. One of the more tedious things that can happen is that you install the new version in a slightly different location and then finding that your host still sees the earlier version and loads it instead of the updated version.
-
- KVRian
- 895 posts since 1 Apr, 2005
Hi Andrew,
I just wanted to give this information. On the other hand, I thought there wouldn't be to much difference to Vista x64. Anyway, we will see it soon, when the final is on retail.
Cheers,
LiteOn
I'm not upset for it.Galbanum wrote: I see someone mentions Windows 7. That is not tested, so I can not say what happens on it. But for OSX and WIn XP and Vista, you should NOT have to reauthorize with this update, UNLESS you manually delete the previous install by choice (which is not needed).
Cheers,
LiteOn
-
- KVRist
- 147 posts since 27 Jun, 2009 from Solar System
Just received it.Galbanum wrote:you should have received an email last night giving the info. please email support at 2caudio dot com if you have not received itganymede wrote:Where is the update? Do you just install the new demo?
-
- KVRist
- 204 posts since 14 Aug, 2008
regarding the installer.
the installer looks into the registry. if it finds previous installation it goes through full installation path. after the installation the vst path to which plug-in has been installed in remembered in the registry.
if the previous version is detected, then installer goes to update installation mode. in this case the new plug-in files are installed into previous installation location keeping user settings intact.
Regards,
Denis (2C-Audio)
the installer looks into the registry. if it finds previous installation it goes through full installation path. after the installation the vst path to which plug-in has been installed in remembered in the registry.
if the previous version is detected, then installer goes to update installation mode. in this case the new plug-in files are installed into previous installation location keeping user settings intact.
Regards,
Denis (2C-Audio)
