In this video, DECAP demonstrates a workflow “cheat code” using Gig Performer as an external VST host alongside his main DAW (Ableton Live) to achieve ultra-low (near-zero) latency tracking.
-
The Problem: When running heavy audio production sessions in Ableton Live, increasing the audio buffer size is often necessary to avoid audio dropouts, pops, and CPU overload. However, higher buffer sizes introduce noticeable input/MIDI latency, making real-time tracking (playing VST synths, MIDI instruments, or recording vocals) feel unresponsive.
-
The Solution: DECAP routes his virtual instruments and vocal processing chains inside Gig Performer instead of directly within Ableton.
-
Ultra-Low Buffer Settings: Because Gig Performer is optimized purely for live VST performance, DECAP sets its buffer size extremely low (down to 16 samples via his RME TotalMix setup), giving it response speeds comparable to hardware synthesizers.
-
Direct DAW Tracking: He then routes the low-latency audio output from Gig Performer straight into his DAW (Ableton Live) for recording audio in real time.
-
Key Takeaway: DECAP calls this setup an “absolute game-changer,” as it allows producers to track software instruments and vocals with near-zero latency even while working on large, heavy DAW projects.
–
Read here full Summary
DECAP explains why Gig Performer has become an essential part of his music production and recording workflow. His primary reason is that it allows him to play software instruments and monitor live audio at very low latency, even when his DAW (primarily Ableton Live) is running massive projects with high buffer sizes.
His main argument is that Gig Performer functions like a hardware synth or an external low-latency mixer running on the computer, independently of the DAW’s latency.
Key Points
[1] Solves latency in large Ableton sessions
When an Ableton project grows to 100+ tracks, uses heavy mastering plugins (such as Ozone), or requires a large audio buffer (2048 samples), playing instruments directly inside Ableton becomes nearly impossible because of the noticeable delay.
Instead, he:
- Loads instruments like Keyscape and Omnisphere inside Gig Performer.
- Runs Gig Performer at a very small buffer (16–32 samples).
- Records the MIDI/audio into Ableton while Gig Performer handles the real-time playback.
The result is hardware-like responsiveness regardless of how heavy the Ableton session is.
[2] CPU efficiency
He demonstrates that:
- Multiple instruments and effects can remain loaded.
- Disabling plugins immediately lowers CPU usage.
- Even several synths and effects consume only around 10–12% of his M1 Max CPU.
[3] Replaces Universal Audio Console
One of his biggest takeaways is that Gig Performer essentially replaces the role of UA Console for his workflow.
Previously he relied on:
- Apollo interface
- Auto-Tune
- Softube CL1B
- LA-2A
- Other UAD plugins
Now he achieves the same low-latency monitoring using:
- an RME Babyface
- Gig Performer
- standard native plugins
without requiring Universal Audio hardware.
[4] Low-latency vocal processing
He routes his microphone through Gig Performer and inserts plugins such as:
- Auto-Tune
- Slate Virtual Mix Rack
- Reverb
- Other vocal processors
This allows him to:
- hear processed vocals in real time,
- record into Ableton,
- avoid headphone latency despite Ableton using a very large audio buffer.
[5] Guitar processing
He has another Gig Performer setup dedicated to guitar, using plugins like:
- TH-U
- Guitar Rig
- S-Gear
- FabFilter Pro-Q 3
He switches between amp models and effects from a custom Gig Performer interface.
[6] Custom performance environment
He likes that Gig Performer lets him:
- wire plugins visually,
- build custom control panels,
- organize synths, guitars, vocals, drums, and effects into one environment,
- quickly open plugin interfaces.
Final Conclusion
His overall message is:
Gig Performer is a “cheat code” for musicians who work with large DAW sessions.
Instead of relying on Universal Audio hardware for low-latency monitoring, Gig Performer lets him use any audio interface while maintaining hardware-like responsiveness for:
- software instruments,
- vocals,
- guitar,
- drums,
- live recording.
He repeatedly emphasizes that the biggest advantage is being able to run:
- a high buffer size in the DAW (for stability),
- a very low buffer size in Gig Performer (for performance),
at the same time, making it ideal for demanding production sessions and live recording workflows.