Forager Support

    Need help? Contact us at contact@harvestplugin.com

Setup

Forager

Ableton Live

Step 1: Make two new MIDI tracks. Apply the Forager plugin onto one track and apply a MIDI instrument to the other.

Step 2: On the “Midi From” drop down on your instrument track, change from “All Ins” and select the MIDI track that Forager is on.

Step 3: Still on the instrument track, change the dropdown that says "Post FX" to "Forager".

Then, change the “Monitor” setting from “Auto” to “In”.

Step 4: Arm the Forager track for recording.

Forager is now ready for use in Ableton Live.

Logic Pro X

Step 1: Create a track and select an instrument.

Step 2: In the inspector of your instrument track, click MIDI FX, and select Audio Units > HarvestPluginsLLC > Forager

Step 3: Be sure the instrument track is armed

Forager is now ready for use in Logic Pro X.
How do I record MIDI in Logic?

FL Studio

Step 1: Insert FL Studio's Patcher plugin into a track.

Step 2: In Patcher, right click to insert Forager.

Then, right click to insert your instrument of choice.

Step 3: Connect From FL Studio > Forager > Instrument > To FL Studio.

Step 4: Click the Gear icon to open the Settings in Forager’s plug-in window. Change the Output Port number to any number.


Forager is now ready for use in FL Studio.

Studio One

Step 1: Make two new instrument tracks. Apply the Forager plugin onto one track and apply a MIDI instrument to the other.

Step 2: On your instrument's track, expand the height of the track to make the Input selector visible.

Step 3: Change Input from "All Inputs" to "Forager"

Step 4: Select the Forager track so it's highlighted and armed

Step 5: Arm the instrument track, ensuring both tracks are armed.

Forager is now ready for use in Studio One.

Cubase

Step 1: Make two new MIDI tracks. Apply the Forager plugin onto one track, and apply your MIDI instrument of choice to the other.

Step 2: On the “Midi From” drop down on your instrument track, change from “All Ins” and select the MIDI track that Forager is on.

Step 3: Arm the Forager track for recording.

Forager is now ready for use in Cubase.

Reaper

Step 1: On an empty track, click "FX" to open your effects browser.

Step 2: Select Forager from your list of effects.

Step 3: Click "Add..." from your effects window to add your instrument of choice.


Step 4: Arm your track and enable Record Monitoring.

Forager is now ready for use in Reaper.

Bitwig

Step 1: Create two new instrument tracks; one with Forager and one with your instrument of choice.

Step 2: Show I/O Routing by clicking the button at the bottom left of the Tracks window.

Step 3: On Forager's track, change the Output from "Master" to "Tracks > [YOUR INSTRUMENT TRACK NAME]".

Step 4: Click Forager's track so that it is highlighted.

Forager is ready for use in Bitwig.

Cakewalk

Step 1: Create two tracks: one with Forager, and one with your instrument.

Step 2: Expand the instrument track so that Input options are visible.


Step 3: Change the instrument's input from "Omni" to "Forager1Omni" by selecting "Forager 1 > MIDI Omni".

Step 4: Click "Input Echo" and change the setting from "Auto" to "On".

Step 5: Click Forager's track to select it.

Forager is now ready for use in Cakewalk.

Mixcraft

Step 1: On an instrument track, click the Keyboard icon next to the Mute button.

Step 2: Select Forager from your list of instruments.

Step 3: In the same window, under instruments, click the down arrow next to the words "Select Synth", and select your instrument of choice.

Forager is now ready for use in Mixcraft.

Waveform

Step 1: Create two new instrument tracks and drag Forager to Track 1 to the left of the Volume and Pan controls. Then, drag your instrument to Track 2.

Step 2: Right click on the Input Device Selector on the left of Track 2 and select MIDI Tracks -> Track 1

Step 3: Arm Track 2

Forager is now ready for use in Waveform.

MuLab

Step 1: Create a new project where a Basic Synth track and rack are inserted automatically. (The Basic Synth can be replaced with any other instrument)

Step 2: Drag your instrument to a lower slot in the rack

Step 3: Insert Forager in the rack’s first slot.

Forager is now ready for use in MuLab.

Frequently Asked Questions


Q: Can you drag MIDI from the plugin into the DAW timeline?
A: This is currently not possible, though it is being worked on.

Q: Is Forager available for Logic Pro X, or in an AU format?
A: Yes! Forager is available for Logic Pro X.

Q: Is Forager compatible with Pro Tools?
A: Pro Tools compatibility a goal but there is no estimated time frame as of now.

Q: Is Forager compatible with Reason?
A: Unfortunately, Reason is not supported because it does not support third-party MIDI routing.

Q: Is Harvest compatible with Cantabile/Digital Performer/etc?
A: If your DAW supports the VST or AU format, there's a very good chance that Harvest will work in your DAW. If you're unsure, we recommend testing it with Harvest Mini (which is free).

Q: Is Forager 32-bit or 64-bit?
A: Forager is 64-bit and can only be used in 64-bit environments.

How to Add a Plugin to Your DAW



To get advice specific to your DAW, I would recommend searching online "how to install plugins in [your DAW]". However, the process is usually pretty consistent across DAWs. The main idea is this: your DAW looks into a folder for it's third party plugins (like Harvest). You can usually set what this folder is, and you must have the plugin in the folder for it to work.
  • First, find out what folder your DAW is looking for plugins. This can usually be done by going into the Settings or Preferences of your DAW, and often there is a section for Plugins.
  • Once you know what folder to use, run the Forager Installer. After inputting the activation code, the installer will ask where it should place Forager.dll (PC) or Forager.vst (Mac). Select the file path that your DAW is looking at. You may need to use a "Scan for Plugins" function, or restart the DAW for the Plugin list to be updated. If done correctly, Harvest will show up in the Plugins section in your DAW.
  • The Forager.dll or Forager.vst files do not need to be placed by the installer for it to work: as long as they end up in the folder somehow.