Right, but why didn't the assignments go away, after I made sure they were not assigned in the SAC settings?

I guess there must have still been some channel strip setting I wasn't noticing - maybe at the input source setting - that didn't clear until I purposely selected all the channel groups and cleared them with the menu choice.

Still got a long way to go.

I'm just happy that you helped out today, Bob.
Thanks!

Well you said you had a midi keyboard that is no longer being used... if it was usb, then it was creating midi ports that you may have had assigned and when you removed the keyboard you also removed those ports which were still assigned.

Bob L

In SAW, Do I have to close Midi Workshop in all the f-keys, or see if I have an older f-key saved with no midi workshop views?
Tried clearing all inputs, outputs and returns and saving as a default template, as in SAC. But still get the single warning when opening SAW64.

AHA! Got it just now!
I had to clear the midi device options in Midi Workshop (separate from SAW main settings choices)!!
I'd forgotten that tidbit from when I first struggled to set up midi in SAW at the beginning of that project.

So, the SAW puzzle is resolved.

As is the SAC puzzle, but without revealing a cause.

Checked all settings in both programs and saved prefs to file (as I always do) and also to default (as always).
I also made sure the mixer in SAC was cleared of synth plugs (AGAIN), even disabled those channels, saved the session, saved mix template and made it the default.
At least now SAC opens without the synths plugged in after saving the new default mix template.

But I just tried closing the session (File/Close Mix Session) and nothing happens. If I try to go live, SAC crashes.

This is all in the 64bit versions, by the way - haven't tried in 32bit yet.

However, I just tried clearing all input, output and return channels (all have to be cleared by group, which I find curious, even though Select ALL was my first right-click choice).
Saved this as a new session, mix template and default... and I was able to go live in this blank session.

THIS seems to have cleared up the going live and warning message issues.

So, problem solved, but no cause discovered.... still scratching my head for a reason, so I might clean up the old sessions and not need to reroute and label everything from scratch (minus the midi stuff).
Unfortunately, I started using SAC64 just as I started using the softsynths and keyboard. So all SAC64 mix sessions have some form of the midi routing configured.

NO solution for SAW yet - Still get the message every time I open it.

Look in the SAC Options and SAWStudio options for the Midi Device and Sync Device setup options.... make sure they are set to none if you want o not use midi at all... otherwise, make sure they are only set to active midi/usb ports and that any port being used should only be addressed once and not diplicated in the other SAC or SAW setups.

Once configured properly, make sure to save the default preferences from the File menu so it stays that way every time you start the programs.

Bob L

I hope somebody can help with this one.
"Midi in Device driver is currently not available"

I get this message 3-4 times when starting SAC and when closing it. It's not only a big annoyance, but also crashing SAC when I try to go live.

This is on a desktop pc (win10 pro) and being used as a front end to SAW, once in awhile, but not currently.
I also get this message at least once every time I open SAW.

The thing is, I had a keyboard connected via USB for a few months, while working on a project and it was fine.
Used SAC as a front end to SAW and was able to monitor and record sounds just great.

The project is finished and now I'm just using SAW to work on other editing/mixing projects that don't require midi, or the keyboard.
The keyboard has been disconnected from the pc and moved out of this small mixing room.

I don't need MIDI right now and I'm really tired of getting this message.
I opened SAC today to try some unrelated ideas and that's when I discovered that I get this message multiple times on each opening and closing of SAC. Add to that the crash any time I try to go live.

I take it the problem is not SAC, but a Windows issue, from what little I've found online about getting rid of the problem.

Does anybody know how to resolve this issue?