How to export from fruity loops to cubase

Written by michael roennevig Google
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to export from fruity loops to cubase
Exporting a loop from FL Studio to Cubase is a straightforward task. (Medioimages/Photodisc/Photodisc/Getty Images)

Fruity Loops, or FL Studio as it is now known, is commonly used by electronic music producers to make loops to be rendered down for use with more powerful audio sequencers. Once you've perfected a loop in FL Studio, it's a straightforward task to mix it down and export it to Cubase. You can then expand the loop into a full track using Cubase's integral and VST instruments and effects.

Skill level:
Moderately Easy


  1. 1

    Launch FL Studio and open the project you want to export to Cubase.

  2. 2

    Click on "File" and select "Rendering."

  3. 3

    Check the option to render your loop to WAV format. This will ensure that your loop is mixed down to the highest quality possible.

  4. 4

    Decide whether you want to retain or wrap any decaying sound such as reverb and make a selection from the "Looping mode" drop-down box.

  5. 5

    Set the bit rate of your rendered loop from the WAV drop-down box, press "Start," select a folder to store your rendered track in and proceed to mix down your loop. Your loop will be stored as a WAV file in the folder location you specified when the rendering process has finished.

  6. 6

    Launch Cubase and create a new project.

  7. 7

    Press "Ctrl" and "P" simultaneously to open Cubase's pool window.

  8. 8

    Click on the "Import" button, navigate to the FL Studio file you created and click on it to load it to the pool window.

  9. 9

    Right-click on the FL Studio file in the pool window and select the option to insert it into your project.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.