I've got a project I completed using an instance of ACE 1.0, which had 3 parameters automated...
Now that I've got ACE 1.1 installed, I've reopened that project to do a couple things, and it seems that 3 different parameters are now being automated on that instance of ACE...
Going back to ACE 1.0 fixes the problem - the correct parameters are now being automated
Whatever changes have been made under the hood, projects that were made with ACE 1.0 are having issues when ACE 1.1 is installed, at least on my system:
Ableton Live 8.2.5
OS X 10.6.8
Any help here? Is this something that has been changed permanently? Is there a fix that will allow projects that were saved with ACE 1.0 to operate correctly with ACE 1.1? I'm all for bugfixes, but when bugfix updates end up breaking old projects like this, it is such a frustrating process to go through...
ACE 1.1 - automation changes breaking old projects
-
- KVRian
- 607 posts since 23 Jun, 2005
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
To further illustrate the problem, here is a screenshot of the ACE instance in question, with ACE 1.0 installed... these are the correct parameters that should be being automated:
If I install ACE 1.1 and then re-open the same project, here are the incorrect parameters that are being automated (instead of the correct ones shown above):
If I install ACE 1.1 and then re-open the same project, here are the incorrect parameters that are being automated (instead of the correct ones shown above):
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Please check you have this file:
MacHD/Library/Application Support/u-he/com.u-he.ACE.publicparams.txt
If not, please download it from here and let me know if it eases the problem:
http://www.u-he.com/downloads/ACE/com.u ... params.txt
(I need to check if the Mac Installer has got it...)
Thanks,
Urs
MacHD/Library/Application Support/u-he/com.u-he.ACE.publicparams.txt
If not, please download it from here and let me know if it eases the problem:
http://www.u-he.com/downloads/ACE/com.u ... params.txt
(I need to check if the Mac Installer has got it...)
Thanks,
Urs-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Thanks for the quick reply Urs:
- The file you mentioned was not present in that location, so it looks like it wasn't included in either the 1.0 or 1.1 installer.
- After downloading the file and putting it in the location you mentioned, it seems to have complicated things even further... when opening the same older project I mentioned in my original post, the ACE parameters which appear with automation are again incorrect, but they are different again:
These 3 parameters show up as long as that TXT file is in the location you mentioned (both for ACE 1.0 and ACE 1.1) So this creates further complications and doesn't really fix the problem at all. There are now 3 different sets of conditions, each of which produces a different combination of automation parameters:
1) ACE 1.0, TXT file not installed - this produces the intended combination of automation parameters (because the project was originally created under these conditions)
2) ACE 1.1, TXT file not installed - this produces an incorrect combination of parameters
3) ACE 1.0 or 1.1, TXT file added - this produces a second incorrect combination of parameters...
- So what is the solution here? Is it possible to perhaps create a workaround version of the TXT file that remaps the parameters to the same order as scenario 1 above (i.e. as if ACE 1.0 were installed and the TXT file didn't exist in the correct location)?
- The file you mentioned was not present in that location, so it looks like it wasn't included in either the 1.0 or 1.1 installer.
- After downloading the file and putting it in the location you mentioned, it seems to have complicated things even further... when opening the same older project I mentioned in my original post, the ACE parameters which appear with automation are again incorrect, but they are different again:
These 3 parameters show up as long as that TXT file is in the location you mentioned (both for ACE 1.0 and ACE 1.1) So this creates further complications and doesn't really fix the problem at all. There are now 3 different sets of conditions, each of which produces a different combination of automation parameters:
1) ACE 1.0, TXT file not installed - this produces the intended combination of automation parameters (because the project was originally created under these conditions)
2) ACE 1.1, TXT file not installed - this produces an incorrect combination of parameters
3) ACE 1.0 or 1.1, TXT file added - this produces a second incorrect combination of parameters...
- So what is the solution here? Is it possible to perhaps create a workaround version of the TXT file that remaps the parameters to the same order as scenario 1 above (i.e. as if ACE 1.0 were installed and the TXT file didn't exist in the correct location)?
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Sheesh... you're right. Two parameters slipped in unnoticed and moved most parameter indexes by 2. Dunno how that could happen as I ran specific tests, but still it happened 
Please delete the publicparams file and try this version:
http://www.u-he.com/downloads/ACE/ACE111MacInstall.zip
We will make this a hotfix and release it asap, after a week or so of testing.
Urs
Please delete the publicparams file and try this version:
http://www.u-he.com/downloads/ACE/ACE111MacInstall.zip
We will make this a hotfix and release it asap, after a week or so of testing.
Urs-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Thanks so much for the quick response Urs 
Already finished in the studio for the day but will test this in the morning & post back here
Already finished in the studio for the day but will test this in the morning & post back here
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Just tried the 1.1.1 hotfix version, and it seems as though it still has the same problem as the 1.1 release - the automation parameters that show up are the same as I experienced with the 1.1 release:
So at the moment it seems that the problem isn't fixed
So at the moment it seems that the problem isn't fixed
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
Now that's weird then... does it say ACE 1.1.1 when you open a new instance? Hmmm... gotta see what the installer does...
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Actually it all looks good now... I think I must have accidentally had both 1.1 and 1.1.1 in my VST folder at the same time, and Ableton must have defaulted to using the 1.1 version when I opened the project...
1.1.1 appears to have solved the issue! Thanks heaps for the help on this Urs!
1.1.1 appears to have solved the issue! Thanks heaps for the help on this Urs!
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Just a quick observation Urs - since I've installed 1.1.1, the synth shows up in my Ableton plugins list as "ACE1" rather than "ACE"... is that part of the changes made in this version?
-
- KVRer
- 9 posts since 12 Oct, 2006
Joining in. I just purchased my copy of ACE, downloaded v1.1 from the u-he website, and it totally fuxxed up my work, previously done on v1.0... automation of the VCF1 cutoff changed to Input (as the OP mentioned), and when I changed it back to control VCF1 cutoff, it stopped playing all together..
I just went back to 1.0, and everything's fine.
I just went back to 1.0, and everything's fine.
-
- KVRian
- Topic Starter
- 607 posts since 23 Jun, 2005
Hi Urs, sorry to resurrect this thread but I'm having some issues...
I'm going back to the same old project I mentioned in my initial posts in this thread... I ended up using v1.1.1 of ACE as you posted earlier in the thread, and it worked fine while it lasted.
Time's moved on and I'm now using build 1391 (the latest public beta) and Live 9.0.1 64bit, and this old project won't play back properly now because the automation is broken again.
v1.1.1 didn't have a 64bit VST2.4 version so I tried jbridge, but it won't work with it for some reason... loading the project using v1.2 (build 1391) of ACE leads to the automation not playing back properly, and looking at the parameters being automated by Ableton, it's the same old problem of the same incorrect parameters that I posted about way back then:
Any workarounds?
I'm going back to the same old project I mentioned in my initial posts in this thread... I ended up using v1.1.1 of ACE as you posted earlier in the thread, and it worked fine while it lasted.
Time's moved on and I'm now using build 1391 (the latest public beta) and Live 9.0.1 64bit, and this old project won't play back properly now because the automation is broken again.
v1.1.1 didn't have a 64bit VST2.4 version so I tried jbridge, but it won't work with it for some reason... loading the project using v1.2 (build 1391) of ACE leads to the automation not playing back properly, and looking at the parameters being automated by Ableton, it's the same old problem of the same incorrect parameters that I posted about way back then:
Any workarounds?
-
- KVRAF
- 1888 posts since 13 Aug, 2011 from Berlin
Hi mustgrove,
thanx for that detailed report. I can reproduce it here. The only workaround that I see is to downgrade until we have a version with a fix for this, sorry.
thanx for that detailed report. I can reproduce it here. The only workaround that I see is to downgrade until we have a version with a fix for this, sorry.
-
- u-he
- 30192 posts since 8 Aug, 2002 from Berlin
double answer here too
Actually, as it turned out later last year, the culprit was a mishap in one unfortunate 1.0.x update - the fix we gave mustgroove never went official and wasn't ever posted in our downloads.
All he needs is the same com.u-he.Ace.publicparams.txt as his 1.1.1
The current beta of ACE has identical parameter setup as ACE 1.0, and the official 1.1 versions we had on the website.
Cheers,
Urs
Actually, as it turned out later last year, the culprit was a mishap in one unfortunate 1.0.x update - the fix we gave mustgroove never went official and wasn't ever posted in our downloads.
All he needs is the same com.u-he.Ace.publicparams.txt as his 1.1.1
The current beta of ACE has identical parameter setup as ACE 1.0, and the official 1.1 versions we had on the website.
Cheers,
Urs