I seem to find little info about XTC mode. I think it offers huge improvements to GUI speed, automation, system performance, and so on.
But I do realise it's not fully functional, not very stabile and undocumented. Here's some thoughts I'd want to share.
- Ingo from CW wrote me the XTC project doesn't need to be edited manually, but I found it easier to set up from in SFP mode -my projects just didn't seem to match. To edit the project from within SFP, open SFP/App/XTCApp/XTCProject.pro Backup the XTCproject.pro before editing!
You can save them w desired IO's, midi etc. here. Thanks Gonzoft for pointing me to this link. It explains how to save ULLI for XTC.
Here's an example XTC project:
- Solution for the device Tempo problem: set it via VST Automation. Click 'W' on the device, so a VST Automation track is created for the device. Now look at the controller's properties on the new track, customise it to include BPM or Tempo, and draw/drag it to the desired value. Zoom fully
- Also key commands are possible in SFP, but not by the numpad. I can dial in BPM times from the main keyboard numbers instead of from the numpad.
Of course, presets including the value will reset the device to the new value too. - This tweak is merely a matter of personal taste, I found it easy to work.
The VST host pre-loads or checks all VST/VSTi on startup. If during this check a plugin fails, you'll get a popup. The faulty XTC dev. is named on lower right corner of Cubase's boot popup. Since the list of plugins that caused errors was rather long,
I backed-up and removed all effects (.dll's in /VST-plugins/XTC/) except Multi-FX and midi remote (haven't used those, but I leave them in). I use MultiFX anyways to host (SFP-type, non XTC) plugins. It makes for much faster Cubase loading, it doesn't have to check every XTCplugin dll. So removed most effects, but the synths' .dll's were left untouched. - VST Automation integrates so well, I'm very excited about it. I still load the Pc1600x/MC-505 remote control presets in the XTC devices, monitor the midi track, enable write on the device, and all comes nicely on screen, every parameter can be automated.
I wonder if it enlightens MIDI. I think so, but have no scientific proof
It's very smooth, and has a huge value range: about 32k values instead of midi's 128 steps - Cubase SX is compatible with continuous rotating controllers, so are XTC devices!
- Some SFP devices, like a mixer, can be loaded into your XTC project. Use it to mix WaveSource and ASIO Mix to your speakers. Thanks, Marcuspocus. Here's a screenshot, with a comment from Dolphin below.
- XTC devices have different 'modes'. Green mode is a combination of Grey (VSTmonitor)) and Blue (Direct monitor).
- 24 bit works best here. Which ASIO version? ASIO2 = ASIO + clock + direct monitoring. I always use ASIO2.
Can you imagine how many XTC Delays you need to load if the Cubase project has 24 audio channels, 8 XTC synths, 16 VSTi channels, 16 Fruity Multi channels, 16 Reason Channels and 16 busses w XTC effects all over the place?
Only one XTC delay is required if you output all channels without XTC insert to a group which has the insert. Port that group to your Master output in Cubase.
Eric Dahlberg replied on the Pulsar-Scope group, and he had a great idea. He uses the groups to assign different steps of delay/latency compensation.
Here goes:
1) Load one 'delay compensator' in each group. You don't have to use CW's, here's another one: UAD-1 Delay Compensation Calculator
2) Route the groups: 1 ->2 ->...->n->Master.
Each group is be a step in latency compensation. Group 1 compensates for n plugins, group 2 for n-1, ... group n does not compensate for XTC plugins in it's chain.
Enjoy,
at0mic.
<font size=-1>[Edited on 2002-10-11 06:07]
[Edited on 2002-12-04 02:56]</font>
<font size=-1>[ This Message was edited by: at0mic on 2003-09-11 12:07 ]</font>