In this instance, the mobius looper. You can send midi sync from mobius to any midi device on your computer. I'm on OS X so the specifics are a bit, different, but if fruity can sync to a midi input, you'd need to route the midi sync from mobius to it (really easy on OS X, but I think you need something called midi yoke on win).SylvainOn Fri, Jun 21, 2013 at 8:15 PM, kay'lon rushing <email@example.com> wrote:
What do you mean by external source?On Jun 21, 2013 4:39 PM, "Sylvain Poitras" <firstname.lastname@example.org> wrote:While there are loopers that can host vst or vsti plugins, I don't think there are any quite like mobius. I guess it depends what functions you're using in mobius. Another approach: get a host for both mobius and your fruity vsti (check out bidule).However, is the issue that fruity can't sync to an external source? I've never used it, but that seems odd?SylvainOn Fri, Jun 21, 2013 at 6:48 PM, kay'lon rushing <email@example.com> wrote:While we're on the subject of mobius, this is also a tangent. Are there any other similar vst or standalone loopers out there that can host vst plugins? I usually host a program in FL Studio but I want to somehow slave FL Studio to a looper that way I can sync FL Studio to the loop. FL Studio has a VSTi extension file so it CAN be used as a vsti.On Fri, Jun 21, 2013 at 10:04 AM, Sean Echevarria <firstname.lastname@example.org> wrote:
Bit of a tangent, but the advice here is incomplete. It's not simply a matter of where or not you trust the source, but whether you trust the source to write code that can't be exploited by 'bad guys' for nefarious purposes on your machine. Not that malware authors generally target vst hosts...
On 2013.06.20 6:13 pm, Jeff Larson wrote:
The only "bad" thing that might happen is if the program is malicious it
can alter sensitive system files. If you trust where it is coming from
then you don't need to worry about this. You certainly don't have to
worry about Mobius, SampleTank, or any of the commercial hosts.