Liquid EDGE wrote: ↑Sun Nov 28, 2021 4:01 am
I’m not entirely sure how you work with scope. But I have scope and my daw on the same computer. The daw replaces all those things you say. So no real problem untill they get fixed, as an alternative is just sitting side by side with scope.
Both,- SCOPE and DAW on same computer but also SCOPE/XITE w/ laptop standalone and for the time being, also a 32Bit Scope system standalone.
But all that is some effort maintaining all the systems and I´d wish everything included in actual SCOPE worked on only one machine, 64Bit and together w/ native VST apps.
When playing just only keys, I prefer SCOPE standalone because there´s no latency and devices talk MIDI PrgChanges.
Scope synths and samplers are good (enough) in addition to hardware keys while native VST introduces the "roundtip" ASIO latency and f##kin´Windows USB-MIDI jitter.
Especially VST3 devices most often don´t respond to MIDI PrgChanges anymore and if they do, you have to deal w/ workarounds like "MIDI banks",- something you have to plan and organize before you can select patches via MIDI at all.
The more different things are combined, the more incompatibility problems come up !
When I play a hardware keyboard/workstation and trigger VST via MIDI, there´s always a "flam" like delay between the hardware keyboard´s sound and the VST generated one.
P. ex. layer a Kurzweil PC3 VA sound w/ Scope/XITE Profit-5 or such,- both is tight, fat and "in your face".
Playing keys for me is more important than recording and mixing.
I made my money as a player, not sound engineer and I play keys at home a lot.
And if it´s allowed to dream,-
I´d wish it worked on Linux and/or Mac Silicone M1X in future to get rid of Microsoft sooner or later.
A portable and powerful new Mac Mini together w/ XITE-1 in a small rack would be ideal for everything,- studio, gigs, jams,- Apple Logic and Mainstage included.
Bud