LiquidEDGE Xite tips. How to avoid annoying stuff!
Posted: Mon Nov 14, 2016 5:33 am
UPDATED with 64bit extras, all still stands for 32bit and applies to 64bit as well with extra about 64bit.
So i did a bug/fact sheet type thing for my studio so as not to get caught out in the future and have a handy piece of a4 paper in there to reference to explain work arounds to bugs and explanations to things that seem slightly "illogical". Most of the information has come from planetz users and http://www.hitfoundry.com/archives/ (which is packed full of detailed info and help) so thanks to all of you that have shared such great knowledge.
I thought I would share it here as most of it could be useful for xite users (newcomers and early adopters alike)
Its not fun having to remember these quirks and best practices, so i wrote it all down!!! (leaving my mind free to just make music and sound)
(not sure if this post is best in tip&tricks or the xite forum)
..........................................................................................................................................
Double L Studio rules, quirks and how to avoid annoying stuff. (just included my cubase and xite tips)
Windows XP, 32bit sp3, 4 gig ram, Cubase 5, Scope 7.
Windows 10, 64bit, 8 gig ram, Cubase 11, Scope 7.
Cubase...
1.Best not to start from the beginning of the arrangement window, have the start of music a few bars in. (Not really an issue since cubase 5)
2.
A.Use Virus TI2 vst 2 (vst 3 has a X in front of the name) plug in for all dials to respond to the ai knob on the cc121.
B.If Virus TI2 vst fails to load and communicate with Virus TI2 hardware, close cubase project down so its empty and load the vst to activate driver communication.
C.User presets for the Virus don’t get saved with the project So it's important, if you create a patch or edit a preset to save it within the virus software.
D.User presets for waves synths don’t get saved with the project. Create presets and reload after loading the project.
E.Presets for Proteus X don’t get saved with the project, so any edits done you need to save the whole bank as a new file.
3.Keep MIDI Info (notes & cc) tidy.
4.Even though you can send midi clock to all midi ports it's best to send to its own isolated port for only this info so as not to clog up other ports that will be used for notes and cc. INFACT it's best not to use midi clock or sync stuff in cubase, the computer can not handle it properly.
5.ScopeSync can be used for cc to scope via sample accurate audio trickery, the use is a much smoother higher resolution than midi.
6.The usamo box is a vst and a physical output for midi notes, cc and midi clock. All in perfect sync with cubase audio.
7.Keep the environment clean, as all graphics eats into valuable processing that would be better directed to midi and audio processing.
8.Freeze vst instruments when things start to get a bit too much for the computer.
9.When in play and you manually move around the arrangement window, midi clock sync (if in use) will get lost. Stop and resume play when navigating the song and jumping from place to place.
Scope Xite-1
Win 64bit version has no sts, vdat or wave drivers, Focusrite 18i8 is installed and routed to adat 1+2 of scope! This has working 64bit wdm wave drivers. In modular avoid using sampleOsc & tapedelay.
Remember to "save as" when changing the title in the scope project and saving it for the first time otherwise you overwrite the last file you opened! Best to be in the habit of always using “save as” to make sure no mistakes are done.
When you save a scope project, when asked to save "left preset list" of a device say yes (unless you know the changes to the presets you made/saved or created are unwanted)
If you load a device and a dsp limit is reached, cancel the pop up and assign to another dsp or resign to the fact you can't load it and delete the device!
Changing sample rate back and forth, switching synths voice to 0 and back, re assigning a device to a dsp or re loading a device sorts out most bugs and oddities should they occur.
If you are going to use a lot of midi in your projects have ulli settings set to 13ms laytency (that's if it was at 44.1hz). lower than that, midi jitter will be introduced once a lot of midi notes and cc gets used. The USAMO box eliminates midi jitter (1 port)
HPM Digital's preamp device seems to provide the most accurate volume control from midi cc!
1.STM Mixers...
A.Note down mixer settings such as midi cc assignment (cc assignment can be saved in the midi bank preset list which would need to be recalled when the scope project is reloaded) and certain things used in inserts like comp side chain channel choice, as they do not get saved with the whole project reliably.
B.Each channel can be delayed by milliseconds to account for issues with timing (if you ever come across it, or if you happen to just want to nudge back the timing of a sound/channel).
2.STS Samplers...
For Scope v7 initial release pull over these files from Scope v5.1 and overwrite the v7 ones.
From and to folder SCOPE XITE/App/Dsp
s3kimix.dsp
s4kimix.dsp
From and to folder SCOPE XITE/App/Sys
KGPar2.sys
KGPar3.sys
TStretch.sys
(This has already been done but have kept the note in case of re install needed)
A.You can load at least 3 Sampler, but "only" with 32 voices (max) and you need to place each of them on DSP 7, 8, 9 or 10. Each on a single DSP.
B.If on Project reload the Sampler has no sound, than type in for the voices "0" and again the number of voices the sampler had before.
C.Save STS wav/audio samples in Project Data/Samples/STS Samples.
D.Best not to use the sts at the same time as proteus x or kontakt as they fight for ram and things can become unstable.
3.Modular...
A.Cancel if asked to save "patch", always save "left preset list" when asked.
B.MDS8 bug - Duplicate module, wire in cables then delete the initial module, edits or the changing to a different pattern won't apply unless sample rate or polyphony switching is done. So it can only be used for one pattern unless point c is done.
C.the problem with some sequencer modules is that the basic dsp module that is inside each of them, only works on xite dsp#1 & #2, it is the same module shared by solaris, etc. and modular sequencer modules. if you need to use sequencer modules inside the modular on the xite, you have 2 choices at the moment:
1.Is to use the flexor modules(they use audio rates)
2.load the buggy sequencer modules inside a modular shell(only the sequencer modules), assign the modular shell to dsp#1 or #2(it's ok if you only load the sequencer module on dsp#1 & #2 there is enough power) then use the modular in and out connections to patch with another modular shell where you have loaded the oscillators and all the rest.
3.At the moment the modular shells we have only cater for mds8 and the pattern controller as the other seq modules use different types of outputs that the shells don't have. The seq elements can still be used, its just you can't use more than one pattern due to the need of sample rate or polyphony changing to apply edits!
4.Synths
A.With older un optimised synths such as Solaris it's best to browse presets with synth set to 1 voice. Once a preset is chosen you can up it to 3/4 voices most of the time without it hitting a dsp limit! (The more complex the preset the less voices). If you do hit a dsp limit just press cancel and lower voices/change preset.
C.If presets are changed while MIDI is being sent expect a hung note sometimes.
D.Step sequencer element on Solaris does not work properly, editing the steps does not take effect until you do the following, under samplerate settings in scope, change the samplerate back and forth or re assign device to a dsp by right clicking on the device in the routing window or switching polyphony , and the step sequencer edits will come into effect. The step sequencing element on Solaris has pattern banks which you could automate but that's useless as of course pattern changes don't take effect unless the sample or polyphony switching is done.
E.Fully working step sequencers (no sample rate changing or dsp re assignment) on scope (full or part of a device) Ocean Storm, Gateway & SC-autogate (assign to dsp#1 & #2), Mattomat, SB 404, Loop, Xtreme cut pro, LBH (& SpaceF stuff), CWM devices & modular modules, and flexors seq modules for modular.
F.SB 404, don’t turn off delay or chorus on the device as turning them back on causes errors.
It seems if you click OK on the error message and use the Store option to save over the preset (and then resave the preset bank) that this fixes the error message.
5.Mattomat...
A.When play starts (synced to midi clock or via midi cc trigger) it will always start on the first beat of its bar so make sure to start on the first beat of the bar in the sequencer (cubase) usamo starts to send midi clock when the project gets to the first beat of a bar.
B.Start a project allowing one cycle of Mattomat before it receives midi from cubase.
C.Use and make presets for automation from cubase via program change cc in the midi editor window of cubase.
D.Use bank select on the midi channel in cubase to select which bank of presets in Mattomat to automate.
E.To demo presets for Mattomat load Minimax as well and use corresponding "Mattomat Release" presets, load the midi controller preset for Minimax.
F.Synths controlled by Mattomat, with adsr, just use ad and have sr set at 0.
G.Best to use Mattomatt in master mode and manually/midi trigger sequence and record its output to a midi track in cubase.
6.MIDI sync/Clock...
A.MIDI sync/Clock signal can be sent from cubase over all midi ports to Scope.
B.It's best not to use any midi sync functions from cubase, it's unreliable and causes crashes.
C.Usamo box sends a reliable midi clock.
D.Since initial release of scope 7 Midi Clock input reports an incorrect midi clock timing in the display when set to use external midi clock. Correct it by replacing the dsp file called TIMECLK3.dsp with the one from Scope 5.1.
7.MIDI from cubase...
Be aware of midi restrictions and limits.
Be careful of doubled notes, off notes being missed, and try and use 1 sequencer midi source port per instrument. Have aftertouch off on midi keyboard for general use.
8.VDAT...
A.When creating a new virtual tape save in E:/Audio Music Projects Samples Presets Soundbanks/project data/VDAT
B.To edit a vdat track in sound forge make sure tape is released (press the stop button so it's flashing) then you can press the edit button next to the track in VDAT settings.
C.Keep file names short. Long file names make it crash.
9.DSP Usage...
In general, DSPs 7-10 have the most inter-DSP connections, and provide the best place for mixer's to live (STM2448x go here) with the other DSPs intended for synths/FX on channels as such:
7 : 11, 15
8 : 12, 16
9 : 13, 17
10: 14, 18
Dsp assignments are not always loaded in the same order, unless you use the manual dsp assignment dialogue on each module/device before you save the project.
10.DSP2 folders are for patches/modules/devices that either need to be assigned to DSP2 or are using DSP2 to work!
Gary B (SC support, on 64bit scope 7)
“64 bit works GREAT for MOST uses.
i appreciate the softened tone, however, i should point out that the work that you wish IS being done. it may be too slow for you, but i can assure you that nobody is ignoring anything at S|C.
most of us can use Scope to our heart's content in 64bit(doesn't mean everything is perfect). again, to answer the op's question, XTC mode does not work in 64bit, the STS samplers and any sample OSCs that use the STS sample player do not work in 64bit. some sequencer modules do not work in 64bit. the Wave destination does not work in 64bit. of the other functions and possibilities(hundreds of plugins including most OLD free plugins), just about everything works. the few niggling bugs all have easy work-arounds(for example, delays used outside of inserts crash, but using a multifx module avoids the problem).”
So i did a bug/fact sheet type thing for my studio so as not to get caught out in the future and have a handy piece of a4 paper in there to reference to explain work arounds to bugs and explanations to things that seem slightly "illogical". Most of the information has come from planetz users and http://www.hitfoundry.com/archives/ (which is packed full of detailed info and help) so thanks to all of you that have shared such great knowledge.
I thought I would share it here as most of it could be useful for xite users (newcomers and early adopters alike)
Its not fun having to remember these quirks and best practices, so i wrote it all down!!! (leaving my mind free to just make music and sound)
(not sure if this post is best in tip&tricks or the xite forum)
..........................................................................................................................................
Double L Studio rules, quirks and how to avoid annoying stuff. (just included my cubase and xite tips)
Windows XP, 32bit sp3, 4 gig ram, Cubase 5, Scope 7.
Windows 10, 64bit, 8 gig ram, Cubase 11, Scope 7.
Cubase...
1.Best not to start from the beginning of the arrangement window, have the start of music a few bars in. (Not really an issue since cubase 5)
2.
A.Use Virus TI2 vst 2 (vst 3 has a X in front of the name) plug in for all dials to respond to the ai knob on the cc121.
B.If Virus TI2 vst fails to load and communicate with Virus TI2 hardware, close cubase project down so its empty and load the vst to activate driver communication.
C.User presets for the Virus don’t get saved with the project So it's important, if you create a patch or edit a preset to save it within the virus software.
D.User presets for waves synths don’t get saved with the project. Create presets and reload after loading the project.
E.Presets for Proteus X don’t get saved with the project, so any edits done you need to save the whole bank as a new file.
3.Keep MIDI Info (notes & cc) tidy.
4.Even though you can send midi clock to all midi ports it's best to send to its own isolated port for only this info so as not to clog up other ports that will be used for notes and cc. INFACT it's best not to use midi clock or sync stuff in cubase, the computer can not handle it properly.
5.ScopeSync can be used for cc to scope via sample accurate audio trickery, the use is a much smoother higher resolution than midi.
6.The usamo box is a vst and a physical output for midi notes, cc and midi clock. All in perfect sync with cubase audio.
7.Keep the environment clean, as all graphics eats into valuable processing that would be better directed to midi and audio processing.
8.Freeze vst instruments when things start to get a bit too much for the computer.
9.When in play and you manually move around the arrangement window, midi clock sync (if in use) will get lost. Stop and resume play when navigating the song and jumping from place to place.
Scope Xite-1
Win 64bit version has no sts, vdat or wave drivers, Focusrite 18i8 is installed and routed to adat 1+2 of scope! This has working 64bit wdm wave drivers. In modular avoid using sampleOsc & tapedelay.
Remember to "save as" when changing the title in the scope project and saving it for the first time otherwise you overwrite the last file you opened! Best to be in the habit of always using “save as” to make sure no mistakes are done.
When you save a scope project, when asked to save "left preset list" of a device say yes (unless you know the changes to the presets you made/saved or created are unwanted)
If you load a device and a dsp limit is reached, cancel the pop up and assign to another dsp or resign to the fact you can't load it and delete the device!
Changing sample rate back and forth, switching synths voice to 0 and back, re assigning a device to a dsp or re loading a device sorts out most bugs and oddities should they occur.
If you are going to use a lot of midi in your projects have ulli settings set to 13ms laytency (that's if it was at 44.1hz). lower than that, midi jitter will be introduced once a lot of midi notes and cc gets used. The USAMO box eliminates midi jitter (1 port)
HPM Digital's preamp device seems to provide the most accurate volume control from midi cc!
1.STM Mixers...
A.Note down mixer settings such as midi cc assignment (cc assignment can be saved in the midi bank preset list which would need to be recalled when the scope project is reloaded) and certain things used in inserts like comp side chain channel choice, as they do not get saved with the whole project reliably.
B.Each channel can be delayed by milliseconds to account for issues with timing (if you ever come across it, or if you happen to just want to nudge back the timing of a sound/channel).
2.STS Samplers...
For Scope v7 initial release pull over these files from Scope v5.1 and overwrite the v7 ones.
From and to folder SCOPE XITE/App/Dsp
s3kimix.dsp
s4kimix.dsp
From and to folder SCOPE XITE/App/Sys
KGPar2.sys
KGPar3.sys
TStretch.sys
(This has already been done but have kept the note in case of re install needed)
A.You can load at least 3 Sampler, but "only" with 32 voices (max) and you need to place each of them on DSP 7, 8, 9 or 10. Each on a single DSP.
B.If on Project reload the Sampler has no sound, than type in for the voices "0" and again the number of voices the sampler had before.
C.Save STS wav/audio samples in Project Data/Samples/STS Samples.
D.Best not to use the sts at the same time as proteus x or kontakt as they fight for ram and things can become unstable.
3.Modular...
A.Cancel if asked to save "patch", always save "left preset list" when asked.
B.MDS8 bug - Duplicate module, wire in cables then delete the initial module, edits or the changing to a different pattern won't apply unless sample rate or polyphony switching is done. So it can only be used for one pattern unless point c is done.
C.the problem with some sequencer modules is that the basic dsp module that is inside each of them, only works on xite dsp#1 & #2, it is the same module shared by solaris, etc. and modular sequencer modules. if you need to use sequencer modules inside the modular on the xite, you have 2 choices at the moment:
1.Is to use the flexor modules(they use audio rates)
2.load the buggy sequencer modules inside a modular shell(only the sequencer modules), assign the modular shell to dsp#1 or #2(it's ok if you only load the sequencer module on dsp#1 & #2 there is enough power) then use the modular in and out connections to patch with another modular shell where you have loaded the oscillators and all the rest.
3.At the moment the modular shells we have only cater for mds8 and the pattern controller as the other seq modules use different types of outputs that the shells don't have. The seq elements can still be used, its just you can't use more than one pattern due to the need of sample rate or polyphony changing to apply edits!
4.Synths
A.With older un optimised synths such as Solaris it's best to browse presets with synth set to 1 voice. Once a preset is chosen you can up it to 3/4 voices most of the time without it hitting a dsp limit! (The more complex the preset the less voices). If you do hit a dsp limit just press cancel and lower voices/change preset.
C.If presets are changed while MIDI is being sent expect a hung note sometimes.
D.Step sequencer element on Solaris does not work properly, editing the steps does not take effect until you do the following, under samplerate settings in scope, change the samplerate back and forth or re assign device to a dsp by right clicking on the device in the routing window or switching polyphony , and the step sequencer edits will come into effect. The step sequencing element on Solaris has pattern banks which you could automate but that's useless as of course pattern changes don't take effect unless the sample or polyphony switching is done.
E.Fully working step sequencers (no sample rate changing or dsp re assignment) on scope (full or part of a device) Ocean Storm, Gateway & SC-autogate (assign to dsp#1 & #2), Mattomat, SB 404, Loop, Xtreme cut pro, LBH (& SpaceF stuff), CWM devices & modular modules, and flexors seq modules for modular.
F.SB 404, don’t turn off delay or chorus on the device as turning them back on causes errors.
It seems if you click OK on the error message and use the Store option to save over the preset (and then resave the preset bank) that this fixes the error message.
5.Mattomat...
A.When play starts (synced to midi clock or via midi cc trigger) it will always start on the first beat of its bar so make sure to start on the first beat of the bar in the sequencer (cubase) usamo starts to send midi clock when the project gets to the first beat of a bar.
B.Start a project allowing one cycle of Mattomat before it receives midi from cubase.
C.Use and make presets for automation from cubase via program change cc in the midi editor window of cubase.
D.Use bank select on the midi channel in cubase to select which bank of presets in Mattomat to automate.
E.To demo presets for Mattomat load Minimax as well and use corresponding "Mattomat Release" presets, load the midi controller preset for Minimax.
F.Synths controlled by Mattomat, with adsr, just use ad and have sr set at 0.
G.Best to use Mattomatt in master mode and manually/midi trigger sequence and record its output to a midi track in cubase.
6.MIDI sync/Clock...
A.MIDI sync/Clock signal can be sent from cubase over all midi ports to Scope.
B.It's best not to use any midi sync functions from cubase, it's unreliable and causes crashes.
C.Usamo box sends a reliable midi clock.
D.Since initial release of scope 7 Midi Clock input reports an incorrect midi clock timing in the display when set to use external midi clock. Correct it by replacing the dsp file called TIMECLK3.dsp with the one from Scope 5.1.
7.MIDI from cubase...
Be aware of midi restrictions and limits.
Be careful of doubled notes, off notes being missed, and try and use 1 sequencer midi source port per instrument. Have aftertouch off on midi keyboard for general use.
8.VDAT...
A.When creating a new virtual tape save in E:/Audio Music Projects Samples Presets Soundbanks/project data/VDAT
B.To edit a vdat track in sound forge make sure tape is released (press the stop button so it's flashing) then you can press the edit button next to the track in VDAT settings.
C.Keep file names short. Long file names make it crash.
9.DSP Usage...
In general, DSPs 7-10 have the most inter-DSP connections, and provide the best place for mixer's to live (STM2448x go here) with the other DSPs intended for synths/FX on channels as such:
7 : 11, 15
8 : 12, 16
9 : 13, 17
10: 14, 18
Dsp assignments are not always loaded in the same order, unless you use the manual dsp assignment dialogue on each module/device before you save the project.
10.DSP2 folders are for patches/modules/devices that either need to be assigned to DSP2 or are using DSP2 to work!
Gary B (SC support, on 64bit scope 7)
“64 bit works GREAT for MOST uses.
i appreciate the softened tone, however, i should point out that the work that you wish IS being done. it may be too slow for you, but i can assure you that nobody is ignoring anything at S|C.
most of us can use Scope to our heart's content in 64bit(doesn't mean everything is perfect). again, to answer the op's question, XTC mode does not work in 64bit, the STS samplers and any sample OSCs that use the STS sample player do not work in 64bit. some sequencer modules do not work in 64bit. the Wave destination does not work in 64bit. of the other functions and possibilities(hundreds of plugins including most OLD free plugins), just about everything works. the few niggling bugs all have easy work-arounds(for example, delays used outside of inserts crash, but using a multifx module avoids the problem).”