Quote:

To add to this discussion, one could add a simple DAW as a slave like Cakewalks MC5, or Reaper to tempo lock the VSTi, and then send the midi data from RB to say MC5 thru rewire, and then out of jamstix.

Until MC3, and or Sonar 4 Cakewalk was also a DX based and therefore used a VST wrapper to make VST and VSTi plugs work as DX and DXi plugs, that was nice but kind of shakey.



I think the point is that requiring a separate host to simply host VSTi and then needing ReWire support between RB and that host, seems to be a kludged way of getting VSTi tempo locking- and rather expensive, when nearly all other sequencing/DAW programs that claim VST/VSTi support do tempo locking to VST/VSTi as a matter of standard practice.

Which would you rather have?

1. RB-->Tempo Locking for VST/VSTi native

2. RB-->ReWire-->DAW that has tempo locking for VST/VSTi native

I'd rather have #1. Much less complicated from a user standpoint.

My Songs, photos, writing,etc.
My Sound Cloud