Reasons Not to Save Projects 32/64/32 Bit

[sjoens]

Or maybe it's a conflict between Sonar and CbB when saving.  Most of you know better.  But there's always one who's gonna do it anyway. 

Open 32 bit Sonar project 1.cwp in CbB and save it as 2.cwp.  Now it's a 64 bit project.  Open 2.cwp in 32 bit Sonar and save it again as 3.cwp.

3.cwp is now corrupted.  Even tho newer features can be lost in translation, the basics should be intact.  Right?

Maybe not...

1. In one project the outputs got crossed and the Inspector is confused what to display for output:

Inspector:  Here Onyx 2 is being displayed as Onyx 1 and Onyx 1 is MIA.

Console View:   Here the correct output is showing activity.  In another instance the right meter showed activity even when the left output was selected.

 

 

Edited December 16, 2023 by sjoens

[OutrageProductions]

It's well known that opening an older format file in a newer application and then saving it (using defaults) will convert it to newer file format, and regressing from there is foolhardy.

[sjoens]

Now we I know why. 

[Starship Krupa]

Like looking for reasons not to take your horse and buggy out on a modern freeway: how many do you need?

[sjoens]

But it's fun???

It happens since I have a lot of old projects.  Also why I keep 32 bit apps installed.  Just need to keep them away from CbB.