[size=100]Rich,

This is interesting...with regards to latency, that is! I have experienced [I]the exact opposite![/I]
[size=100]
From the SAC User Manual...

"[I]Using The SAWStudio Links
SAC includes internal links directly to SAWStudio Lite and Full. The SAC Link option is activated from within the SAWStudio app and once a connection link between SAWStudio and SAC has been established, you can now pass data in both directions for recording and playback with SAWStudio using internal shared memory buffers [U]that completely bypass the Windows soundcard drivers. SAWStudio will automatically disconnect from the drivers and use the internal shared buffers to communicate with the outside world through the SAC engine.[/U][/I]" [emphasis mine]
[/size]
MWS is an option to SAW...so SAW would be required.

As a noted, I have used SAW with KONTAKT for use with orchestral strings when performing Vivaldi concertos for guitar and orchestra.[/size]
[LIST]
[*][size=100]Once the [/size][size=100]KONTAKT [/size][size=100]portion [I]has been realized[/I], I will then render the KONTAKT data to a wave file and then dispense with KONTAKT.
[/size]
[*][size=100]However, and this is an important however, [/size][I][size=100]KONTAKT [/size][/I][size=100][I]can still be employed along with SAC for live performance usage[/I].
[/size]
[/LIST]

[quote="mr_es335"][size=100]Rich,

Though SAC can employ the use of VSTi's...I personally would prefer to employ VSTi's in SAW.

Each host application then, can perform the functions for which these host applications were truly designed.

In order to use MIDI - and if I might say..."[I]properly[/I]" - you really should be employing the use of MIDI WorkShop.

If you have been deploying SAC as "the front-end" for SAW...then nothing needs to change on the SAC-Side.[/size]
[LIST]
[*][size=100]And when you really think about this scenario, nothing needs to change on the SAW-Side either.[/size]
[/LIST]
[size=100]And in MWS then, you can assigned whatever MIDI channels you require for whatever VSTi plug-in you are currently employing.[/size]
[LIST]
[*][size=100]I have written somewhat extensively on the use of MIDI devices for use in MSW.[/size]
[/LIST]
[size=100] This all being said, what is it [I]specifically[/I] that you are attempting to accomplish?
[/size][/QUOTE]
I understand what you are saying....it just, to me, the latency seemed to be much better in SAC, using a 64 buffer, whereas in SAW, a buffer of 64 would give me some pops and clicks occasionally. I take it there is no way for Midi workshop to communicate with SAC when linked with Saw.?

[size=100]Rich,

Though SAC can employ the use of VSTi's...I personally would prefer to employ VSTi's in SAW.

Each host application then, can perform the functions for which these host applications were truly designed.

In order to use MIDI - and if I might say..."[I]properly[/I]" - you really should be employing the use of MIDI WorkShop.

If you have been deploying SAC as "the front-end" for SAW...then nothing needs to change on the SAC-Side.[/size]
[LIST]
[*][size=100]And when you really think about this scenario, nothing needs to change on the SAW-Side either.[/size]
[/LIST]
[size=100]And in MWS then, you can assigned whatever MIDI channels you require for whatever VSTi plug-in you are currently employing.[/size]
[LIST]
[*][size=100]I have written somewhat extensively on the use of MIDI devices for use in MSW.[/size]
[/LIST]
[size=100] This all being said, what is it [I]specifically[/I] that you are attempting to accomplish?
[/size]

It’s been a long time since I used virtual instruments in SAC. I loaded a piano on channel one, plays great….loaded some drums from Kontact on channel 2, and both the piano and drums play at the same time from my controller…
How do I assign midi channels to different tracks?

then, can I use the Sac/Saw link with all this?

any videos out there?

thank you.