Fruityloops & ASIO question
-Fruity uses one way audio drivers, that means that it has no sound input, just like ie. Rebirth.
-Fruity exports wav and midi.
So you must
-record in a 2nd program (SoundForge?) or
-export midi, play in Cubase/Logic/... and record Pulsar there.
I suspect that this one-way drivers also are the problem for Fruity and XTC. Is anybody working w Fruity & XTC without clicks and pops?
-Fruity exports wav and midi.
So you must
-record in a 2nd program (SoundForge?) or
-export midi, play in Cubase/Logic/... and record Pulsar there.
I suspect that this one-way drivers also are the problem for Fruity and XTC. Is anybody working w Fruity & XTC without clicks and pops?
Hi,
I'm sorry if there's a misunderstanding here, but here's a new attempt to answer Spirit's question. Actually, Spirit posted a dual question. Subhuman, you answer to the first question. I've replied to the 2nd question...
Other suggestions could make my Fruity easier to work with too. But I'm afraid there's not too much of options for now:
Fruityloops exports internally generated audio to wav and mp3. It cannot render Pulsar devices or ASIO input. It has no audio input.
I guess XTC would make it possible though, but I experience clicks with Fruity & XTC, so I use OS mode.
2 ways to get your Fruity sequenced Pulsar synths to wav:
->You can export midi from Fruity (mute wav tracks or the notes for internal sample/synth will be included too). Open the midi in Cubase/Logic/..., play and record as if you made the song in Cubase/Logic.
->Record Live into wav recorder (SoundForge/STS?)
Fruity's fine for midi outs, you can even assign CC# and automate them. Just create a new track, 'Midi Out'. These Midi tracks have to be exported a midi file for recording.
Am I missing something?
at0mic.
ps. undocumented but true -enable midi remote control and FLP will even slave to midi clock
<font size=-1>[ This Message was edited by: at0mic on 2002-04-01 05:41 ]</font>
I'm sorry if there's a misunderstanding here, but here's a new attempt to answer Spirit's question. Actually, Spirit posted a dual question. Subhuman, you answer to the first question. I've replied to the 2nd question...

Fruityloops exports internally generated audio to wav and mp3. It cannot render Pulsar devices or ASIO input. It has no audio input.
I guess XTC would make it possible though, but I experience clicks with Fruity & XTC, so I use OS mode.
2 ways to get your Fruity sequenced Pulsar synths to wav:
->You can export midi from Fruity (mute wav tracks or the notes for internal sample/synth will be included too). Open the midi in Cubase/Logic/..., play and record as if you made the song in Cubase/Logic.
->Record Live into wav recorder (SoundForge/STS?)
Fruity's fine for midi outs, you can even assign CC# and automate them. Just create a new track, 'Midi Out'. These Midi tracks have to be exported a midi file for recording.
Am I missing something?
at0mic.
ps. undocumented but true -enable midi remote control and FLP will even slave to midi clock

<font size=-1>[ This Message was edited by: at0mic on 2002-04-01 05:41 ]</font>