I think to remember that in SC2 I was able to use one of the 2 versions doing the same things, but in SC3 it seems to me that the 2 versions are different, in my Bitwig Studio at least
Today I tried to create a looper-based project, so I found 3 chords by ear on my axe, then I asked SC3 VST to decipher it, but the Audio input of my audio card was unavailable
After some vain try I dropped SC3 Audio in a track and the Audio input of my audio card reappeared
Is it how SC3 is supposed to work?
Each version only for different uses?
And I had another issues then, because I was unable to D&D in SC3 VST the 3 chords recognized by SC3 Audio: I had to D&D them in my desktop, and only after in SC3 vst
Is it how SC3 is supposed to work?
No D&D of chords?
I found that if I D&D Scaler 3 VST in a Bitwig track, the track is seens as an Instrument track: this is why I cannot see the audio routing and I cannot use the Audio Detect option
If I convert the Instrument track in Audio track I can see the audio routing, and I can have the audio detected
Nevertheless, I cannot use this converted Audio track to drive other MIDI tools because it is an audio track, YUK!
Clearly, converting again the Audio track in an Instrument track doesn’t fix the issue
The only way to go on in my workflow is exporting the chordset from Scaler 3 Audio, putting Scaler 3 Instrument in another track, then importing the chordset: quite a cumbersome procedure
