Hi,
I'm having a problem, with some projects in Cubase all the automation parameters of ACE are wrong, it's making horrible sounds and patch cables are moving around, because the automation is being sent to all the wrong places I'm guessing the projects were made with an older version of ACE as they are a couple of years old now.
I did a search on the forum and saw that someone else had the same problem with a previous version. If I understand correctly, it seems there is a text file called publicparams, which sets the order of the parameters, but the order is not the same on every version which is what causes the problem. Is there something I can do about this?
Thanks
ACE 1.2 - problem with automation parameters
-
wandering aardvark wandering aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=236919
- KVRer
- 8 posts since 5 Aug, 2010 from forest
-
- KVRist
- 450 posts since 22 Nov, 2005
Urs needs to put a version history up so you can determine what version you were using at that time.
I've just checked the manual and website to see if i could find anything but nothing seems to be there.
I've just checked the manual and website to see if i could find anything but nothing seems to be there.
-
wandering aardvark wandering aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=236919
- KVRer
- Topic Starter
- 8 posts since 5 Aug, 2010 from forest
Thanks for replying and for taking a look for me 
I also checked the manual and website, and found nothing relevant to this, and spent some time searching for the net. I found an alternative publicparams.txt that Urs had linked in a previous thread about this issue, but that didn't help.
My best guess is that the projects were made with v1.0, although it could have been a beta or alpha version. If I could try some previous versions, I should be able to quickly find out which one loads with the correct parameters. Or if I could get the parameter lists of previous versions, maybe I could figure out which parameters the automation should be sent to, and just re route it in my Cubase projects. Although a lot of work, maybe this is the best long term solution, because I'd rather use current version and future updates than be stuck with an older version.
At the moment I just have pages and pages of ACE automation lanes with no way of knowing the correct parameters, so any help/advice will be much appreciated.
Thanks again
I also checked the manual and website, and found nothing relevant to this, and spent some time searching for the net. I found an alternative publicparams.txt that Urs had linked in a previous thread about this issue, but that didn't help.
My best guess is that the projects were made with v1.0, although it could have been a beta or alpha version. If I could try some previous versions, I should be able to quickly find out which one loads with the correct parameters. Or if I could get the parameter lists of previous versions, maybe I could figure out which parameters the automation should be sent to, and just re route it in my Cubase projects. Although a lot of work, maybe this is the best long term solution, because I'd rather use current version and future updates than be stuck with an older version.
At the moment I just have pages and pages of ACE automation lanes with no way of knowing the correct parameters, so any help/advice will be much appreciated.
Thanks again
-
- KVRian
- 1061 posts since 3 Oct, 2011
All I know is when I had a similar problem all automation needed to be moved excactly one lane. No guarantee that'll work for you, but try to se if all or most parameters needs to be reassigned some excact number of lanes, or possibly they'll be in groups where some will need to be moved a certain number of lanes and others some other number of lanes.
If I understood this correctly the issue was caused by inserting new automatable parameters and something slipped up, but from ACE 1.2 on they'll ensure automated parameters should work consistently while any new parameters should be added to the end of the list.
If I understood this correctly the issue was caused by inserting new automatable parameters and something slipped up, but from ACE 1.2 on they'll ensure automated parameters should work consistently while any new parameters should be added to the end of the list.
-
wandering aardvark wandering aardvark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=236919
- KVRer
- Topic Starter
- 8 posts since 5 Aug, 2010 from forest
Hi V-Ger, thanks for your reply.
What you say makes sense, that parameters added near the top of the list would push other parameters down the list, and it sounds like your suggestion could work.
Unfortunately, after reading the whole automation section of the Cubase manual, it seems that this might mot be possible in Cubase 5 since, unbelievably, there is no option to show all used automation lanes for a plugin, both used and unused, in numerical order. Used lanes can be shown all at once, and unused lanes are only shown by adding them one at a time. I can hide all automation and add all lanes one by one, but used lanes are still added first, regardless of numerical order. To make matters worse, they all have abbreviated names with many parameters sharing the same name, eg there are 5 parameters called FMSrc, and seemingly no way to tell which belongs where when they are automated.
I'll read the manual again after a good nights sleep in the hope that I've missed something, otherwise I really hope that there is an easier fix or a more Cubase-friendly solution for this.
Thanks for taking the time to help
What you say makes sense, that parameters added near the top of the list would push other parameters down the list, and it sounds like your suggestion could work.
Unfortunately, after reading the whole automation section of the Cubase manual, it seems that this might mot be possible in Cubase 5 since, unbelievably, there is no option to show all used automation lanes for a plugin, both used and unused, in numerical order. Used lanes can be shown all at once, and unused lanes are only shown by adding them one at a time. I can hide all automation and add all lanes one by one, but used lanes are still added first, regardless of numerical order. To make matters worse, they all have abbreviated names with many parameters sharing the same name, eg there are 5 parameters called FMSrc, and seemingly no way to tell which belongs where when they are automated.
I'll read the manual again after a good nights sleep in the hope that I've missed something, otherwise I really hope that there is an easier fix or a more Cubase-friendly solution for this.
Thanks for taking the time to help
-
- KVRian
- 1061 posts since 3 Oct, 2011
Oh dear, the 
you Cubase users have to go through some times.. 
I'm so happy I made a different choice with FL Studio, it's issues suit me better... 
Good luck with that. Isn't there a Cubase forum where you could try to get some help? If the manual doesn't help much perhaps some experienced users have tricks up their sleeve, if you're lucky.
And you're very welcome
though it possibly didn't take you that much further for now..
you Cubase users have to go through some times.. I'm so happy I made a different choice with FL Studio, it's issues suit me better... Good luck with that. Isn't there a Cubase forum where you could try to get some help? If the manual doesn't help much perhaps some experienced users have tricks up their sleeve, if you're lucky.
And you're very welcome
though it possibly didn't take you that much further for now..