Hope you did a fresh install with X3, otherwise you may get false bug issues further down the line.  A fresh installed would mean uninstalling the X2 program and reinstalling X3, otherwise you're still riding on some X2 settings in the X3 program.

kday
Hope you did a fresh install with X3, otherwise you may get false bug issues further down the line.  A fresh installed would mean uninstalling the X2 program and reinstalling X3, otherwise you're still riding on some X2 settings in the X3 program.

come on, knowing the history with previous updates this is way too dangerous. i certainly won't uninstall a productive x2a for x3 where all problems are yet to be discovered.
 
these versions need to run in parallel like all previous ones used ...

I would not uninstall previous Versions.
I think there is no need.. there is not a large amount of disk space taken up by the remaining programs and also no loss of previous plugins etc.
I would like to be able to go back and mix old Projects in the future.
 

I meant if you were using an upgrade version of X3 that required X2 to load. Because if your X2 became corrupted and you haven't discovered that yet, then you layered an X3 upgrade on top of an old X2, then you possibly got a buggy X3.
 
All software companies tell you it's better to first uninstall a previous version of the program before installing the new one, to eliminate possible conflicts or incompatibilities over time. 
 
But if it's the full version of X3 then you probably don't have to uninstall the X2 program. But if X3 decide to share some of X2 files, it's a possibility that corrupted shared files could affect X3. Old data doesn't always remain 100% corruption free over time from constant use.
 
For me it's extremely important that I "Clean your registry" once a day and that's before recording tracks or installing programs or plugins in X3 or X2, otherwise you may still run into false positive bug issues from possible previous corruption. 
 
I've had several bug issues, then ran the "Clean Your Registry" program and many bugs disappeared.
 
Re-loading old projects and songs always faces the possibility of a corruption over time, either the program or the file becomes corrupted from new overwrites with new bug kinks.
 
I've had the V-Vocal program that just didn't work, then I re-installed the X2 program and everything just started back working from the fresh install. Sometimes even the program itself won't load correctly from a fresh install, it's a long process to re-install the program but it may fix a lot of issues that only you and nobody else has a problem with.
 
If your program is corrupted in areas, but it still works, if you ever reinstall the program all the files saved on the program at that time may not necessarily work when you do a new or fresh install. 
 
A daily registry cleaning is always your best friend on a recording program that requires constant writes and deletes. Many of the takes and recording could be worth a million bucks to just omit doing a daily registry cleaning.
 
Just an extra thought....
 
 
 
 
 
 
 
 
 
 

Sonar doesn't work like that. Each install is standalone. It asks if you want to migrate preferences, and of course they both share the same plug in folders, but that's it.
 
That said, I suspect that the Channel Strip Mapping XML file does come under the shared preferences. I've had exactly this problem with previous versions. The solution is to spend an hour or so re-programming it knob by knob using ACT learn. So not completely broken, but, let's call a spade a spade, shoddy work from Cake.
 
Really, Cakewalk should be doing this kind of minimum compliance test, and aren't doing. I can understand not developing it further, that's fine, but this kind of thing is just neglectful.

I think I need to have closer look at what is inside those XML files because my ACT settings won't stick and get lost whenever I close Sonar (had reported that, was re-directed to support who could not reproduce) - in fact, none of these files ever change when I map ACT ... but that is still X2a
 
Anyway, pls Dyonight share details if you get this sorted out (as your problem also started in X2)

Oh man. I had that (changes not sticking), and worked out a fix, but I can't remember what it was. As soon as I do, I'll let you know.

So when you save and load Channel Strip file settings, you're saying the ACT Mapping isn't retained?
 
ACT Mapping for the Channel Strip Control Box and Audio Channel Strips seems like it would be saved when you save the Project file.
 
I don't think Channel Strip Mapping Files are considered shared preferences. I always thought that Preferences are usually for console OS settings built into the program, and ACT Channel Strip files are for storing settings for Add On plugins and programs that are not necessarily included in the program in which ACT deals with half or most the time. 
 
Have the VS-700 ever loaded ACT file settings, I can load Channel Strip settings from the saved file in the same way I saved them.
 
I thought any ACT Channel Strip Box settings are retained for controlling plugins would be saved too? Is this not true?
 
I know when I save a Project file every setting including ACT Mappings were or supposed to be retained, are they not being retained?
 
 
 
 
 
 

Well if they dont get saved... please share Your xml files :-)
 

Hi guys!
 
Sorry, I really don't want to hijack this thread with issues unrelated to X3, but since the ACT mapping thing came up, we might as well try to sort it out before the real X3 issues (if there are any ) start showing up ...
 
I did consult the manual to be clear on what to expect:
 
To edit the default ACT mappings (X2 manual, p. 1235)
[...] use ACT Learn Mode button [...] bla bla bla [...]
 
Any assignments you keep are saved automatically as soon as you disable the Learn button. These assignments are global, so they are the same for every project.
 
Well, this just never happens on my DAW. I can remap, but have to redo everytime I reopen Sonar. 
 
You can use ACT with any automatable plug-in. You can create your own mappings by using the ACT Learn button, but because ACT Learn mappings are stored in XML files, you can also import XML data that contains predefined parameter mappings for certain plug-ins.
 
xml files on my DAW never change after editing ACT. I appears as if this only happens in RAM, but is never dumped to any file ...
 
These predefined parameter mappings provide generic "best guess" assignments between the controls on your surface, and the parameters in the plug-in, which gives you a starting point that you can customize by using the ACT Learn process. The import feature makes it easy for users to share data, and will also allow you to download incremental updates when new plug-in mappings become available.
 
I searched again but could not locate any ACT setting default files or updates ... maybe that's just the way it used to be in 8.5.3 ...
 
If you import ACT data for a certain plug-in, and you have already mapped some of the parameters in that plug-in, for each already-mapped plug-in, a dialog box asks you if you want to overwrite that plug-in's mapping. This lets you protect any parameter mappings that you've already done. To see if any new ACT XML files are currently available, check the support pages at www.cakewalk.com.