I've come across a few people on here that talked about cloning their projects in FL so that they can eliminate CPU by bouncing down audio files.
a few questions if I may:
Is this the main purpose of doing this?
Why not just do it in the same project file?
Do you bounce all files then create a new project and import?
Do you find it beneficial in some other way to work with only audio?
? about cloning projects in FL.
- KVRAF
- 7338 posts since 19 Apr, 2002 from Utah
I'll see if I can help answer some of your questions:soulkraka wrote:I've come across a few people on here that talked about cloning their projects in FL so that they can eliminate CPU by bouncing down audio files.
a few questions if I may:
Is this the main purpose of doing this?
Why not just do it in the same project file?
Do you bounce all files then create a new project and import?
Do you find it beneficial in some other way to work with only audio?
Yes, the main purpose is usually to save CPU by bouncing down to audio. Bouncing down CAN be done in the same project file -- in fact, there are many ways to do it. Bouncing and starting a new project and importing the file is another way of doing it -- whatever suits you. I mainly only do it to save CPU (I have a slow machine.)
I hope this helps.
--Sean
http://www.fl-users.singingcrane.com/FL ... opic=188.0
-
- KVRian
- Topic Starter
- 1144 posts since 9 Jan, 2004 from tOKYO
thanks
I understand how to bounce in FL. Its quite flexible. Im mainly just curious about other users workflow.
I understand how to bounce in FL. Its quite flexible. Im mainly just curious about other users workflow.
Not bad meaning bad but bad meaning good