V5 Scope is still in Release Candidate mode, so there are still some last tweaks being done to the main program.įYI.I've pushed 12 synths at 5 voices each into Xite, with plenty of headroom left for two mixers, some delays and reverbs, and my 2 year old PC still has headroom to run large projects in Samplitude with several hefty VST's such as Superior2. I personally don't bother using XTC, so I haven't kept totally in the loop on this. I HAVE had success with MTC driving some of the delays and arps.įor #3, Scope/Xite has XTC mode for running Scopes' plugs in your host - except that for V5 Scope there is a tweak to get XTC to work like it did in 4.5. Jim and a couple others have spent a lot more time with many of the devices. master or slave.Siriusbliss wrote:For 1 and 2, yes - although I haven't honestly had time to test ALL the clock-based parameters in ALL the synths/arpeggiators, filters, LFO's, effects, etc. Other DAW's allow slave mode ie they can be the receiving machine. Really the best option.Īs Studio can only send (no slave mode) either of these things for the moment, getting one Studio One computer to drive a second Studio One computer in sync is not possible right now. (not tempo dependant, but constant all the time) The receiving machine just reads the clock and makes sure its own sequencer is in time relation to it. MTC (Midi Time Code) is another form of continuous pulses being sent but this time its hours, minutes, seconds and frames. Otherwise the two DAW's, even after both getting a start signal, would free wheel and eventually start drifting out of time with each other. Time between sync pulses is tempo dependant. Sync happens every 1/24th of a beat in the bar. It usually includes a master machine sending out a continuous midi clock at a rate of 24 ppq (24 pulses for every beat in the bar) from the moment it starts, locking the receiving machine (slave) so it remains in perfect sync with the master. Sync means more than just a command to start, stop.
0 kommentar(er)
