PlanetZ forums - scopeusers.com

Hi!

Just to clear the air on this:

If I buy any of the aforementioned cards, will I encounter any Fruity related problems? I've read some posts where there seem to have been probs concerning Fruity and dsp. Am I wrong bout this? Are there any issues I should know bout before purchasing? Please enlighten me!

Cheers,

Aallvor

3 things to know before hand :

1st - fruity can only be slave (nothing to do with dsp cards, but hey, better to know before)

2nd- fruity doesn't have latency compensation (PDC), and badly support audio input, thus XTC mode is unusable from creamware cards, and for Powercore and UAD, well they don't work at all.

3rd- fruity work exceptionnally well when using native sfp mode, really fast, and permit alot of midi control that many other sequencer can't do. Like arpegiators, or LFO on any parameter, and even function affecting many parameters at once, to name a few.

So, fruity can be really really coOl, or a pain in the ass according to the way you would use SFP.

Fruity kicks ass in conjonction with scope in native mode.

BTW, you'll need a recorder app like wavelab, SoundForge or the free 'SilverSpike Tape-It' vst plugin to make the mix down that will include scope effects and synths with fruity.

Hope that help and that i didn't say anything stupid here



<font size=-1>[ This Message was edited by: marcuspocus on 2004-10-19 08:15 ]</font>

Excuse me for reaching undiscovered heights of newbie'ness, but what's the difference between native mode and xtc mode..?

Regards,

Aallvor

xtc mode allows you to insert the SFP synths and effects within the sequencer application. They basically function as vsti's. But as was already mentioned, forget about xtc mode in Fruity.

One problem I came across was that all the SFP synths were suffering from latency in FLS. They played behind the beat, it was very noticeable. I tried everything, but the problem didn't go away until I installed the Fruity Wrapper beta. You can download it from the FL forums.