Hello there.
 
I'm running the latest version of Sonar Platinum (Oct 2016 update). I've just started having a problem where the bus assignments I make in a project are not saving. In my system I have two Delta 1010 cards, each with 8 in/outs.
 
If I set a bus to card #2, pair 1/2, save the project, close the project and reopen, the bus is assigned to card #1, pair 1/2.
 
Is there anywhere to control saving/not saving bus assignments? If so, I can't find it in the preferences. Or might it be a bug? I've used Sonar for many years and don't recall it ever behaving like this.
 
Thanks,
 
Dave

Try saving your set up as a Screenset.
Set up everything the way you want it set (with your buses) then simply lock the Screenset / Save the project.
This should indeed save your settings.
 

Hi Chuck,
 
Thanks for the suggestion. I tried locking a screenset and saving the project, but when I reopen it, the bus assignments are again changed back. 
 
I can't find a way to get the bus assignments to "stick". Any thing else that might cause this? It's really a pain to keep having to reset bus assignments when opening any project now.

I got it working today. For posterity, in case anyone else runs across this issue, here is what I did:
 
In my case, I have two Delta 1010 IO cards, each with 8 analog ins/outs for a total of 16 analog in/out. When installing the driver, it seems there are ports exposed called Delta "Delta multi 1/2, Delta multi 3,4, etc." and ports "Delta 1/2, Detla 3/4, etc.". 
 
Under preferences/devices, I just unchecked all of the "multi" ports, saved, exited, restarted Sonar, and now it seems bus assignments are remaining after stopping/restarting Sonar. Sonar by default has all of them checked. Maybe there was some conflict and "multi" would work fine as long as the non-multi was unchecked. I haven't test this yet. 
 
Things that didn't work/matter:
 
1. Rebooting
2. Saving config with a screen set (they don't save bus assignments from what I can tell)
3. Reordering the card connectors on the host machine (1 to 2 and 2 to 1).
4. Running as administrator
 
So.....YAY! This annoying issue has been resolved for me.