Re: New on Xite-1
Posted: Wed Dec 03, 2025 12:22 pm
hey!
regarding x64 OS and XTC - it can work (latest scope version is v5.1, in v7 it's completely broken / taken away) but it will crash randomly on plugin load due to the fact that this stuff comes from 32bit era and behaves as if all you have is 32... and sometimes gets resource addresses from above that, refers to them in a wrong way and makes it all crash - or so i imagine.
Steinberg - Steinberg sucks due to inventing VST2 standard and then abandoning it. For example, Samplitude and Sequoia support VST2 and 32bit VST plugins natively even in newest versions. Avoid new steinberg DAWs if you can, or try luck with them an jbridge.
regarding XTC plugins not appearing - Scope installer can be very wonky depending on Windows version it's installing to - it fails to copy some files, copies some others, sets the permissions wrong, and all that shit. Make sure you actually have them where needed.
i'd advise keeping just multifx-s and multifx-m plugins in your \vstplugins\scope\ and then loading everything within them - then it's just these two "empty" plugins for the DAW to scan, not 100 which takes a long time to initialise one by one and is a big risk to catch a crash after poking some unlucky one.
XTC project file - you mean you opened it in scope? that's a cool thing with it - one might adjust xtc project to one's liking (like routing something somewhere), save it, exit and leave it alone. when you want to use xtc, don't open scope, it will all happen automatically in background when you add scope vst in your daw.. if you have scope open while opening daw, it will prevent xtc from working!
regarding x64 OS and XTC - it can work (latest scope version is v5.1, in v7 it's completely broken / taken away) but it will crash randomly on plugin load due to the fact that this stuff comes from 32bit era and behaves as if all you have is 32... and sometimes gets resource addresses from above that, refers to them in a wrong way and makes it all crash - or so i imagine.
Steinberg - Steinberg sucks due to inventing VST2 standard and then abandoning it. For example, Samplitude and Sequoia support VST2 and 32bit VST plugins natively even in newest versions. Avoid new steinberg DAWs if you can, or try luck with them an jbridge.
regarding XTC plugins not appearing - Scope installer can be very wonky depending on Windows version it's installing to - it fails to copy some files, copies some others, sets the permissions wrong, and all that shit. Make sure you actually have them where needed.
i'd advise keeping just multifx-s and multifx-m plugins in your \vstplugins\scope\ and then loading everything within them - then it's just these two "empty" plugins for the DAW to scan, not 100 which takes a long time to initialise one by one and is a big risk to catch a crash after poking some unlucky one.
XTC project file - you mean you opened it in scope? that's a cool thing with it - one might adjust xtc project to one's liking (like routing something somewhere), save it, exit and leave it alone. when you want to use xtc, don't open scope, it will all happen automatically in background when you add scope vst in your daw.. if you have scope open while opening daw, it will prevent xtc from working!