Gravity Feed for FabFilter Pro-Q 4 and Pro-R 2
Map effect suggestions to Pro-Q 4 and Pro-R 2 with host automation.
This guide explains how Spatial9 Gravity Feed's effect suggestions relate to FabFilter plugins such as Pro-Q 4 and Pro-R 2. Status: documented route, no profile yet. FabFilter plugins expose their controls as host-automatable parameters but have no network or OSC input, so ideas are applied through your DAW's automation.
At a glance
| Item | Detail |
|---|---|
| Status | Documented route; no Gravity Profile |
| Control route | Host automation only |
| Formats | VST2, VST3, AU, AAX and CLAP (check each product page) |
| Gravity Feed output used | effect_suggestions |
What Gravity Feed returns
Each item in effect_suggestions has a track, a kind (reverb, delay, filter, width, dynamics or synth), an intent and a reason. Every item has executable: false: Gravity Feed never sends a FabFilter parameter value and never claims a value improves the sound.
| Idea | FabFilter controls to look at |
|---|---|
| Make room for a vocal | A Pro-Q 4 band on the competing track, possibly dynamic |
| Push an element back | Pro-R 2 mix, decay and pre-delay |
| Brighten for a chorus | A Pro-Q 4 high shelf, automated at the section boundary |
| Tighten a busy section | Pro-R 2 decay shortened for that section |
Applying an idea
- Read the suggestion's section and reason in the plan.
- Arm automation on the FabFilter parameter in your DAW.
- Write the change at the beat the plan gives, and listen.
FAQ
Will Gravity Feed ever move FabFilter controls automatically?
Only after an effect profile exists and passes testing. No effect profiles exist today.
Does Gravity Feed analyse my audio?
No. It plans from the session details your adapter sends, not from audio.