There are exactly zero velocity layers mapped to the neck of a guitar here. Cinedream works as a chord trigger — hold down a key, and the engine builds an evolving guitar part from noise, harmonics, and sustain tails that shift while your hands stay on the faders. For a video editor who needs a bed under dialogue, that means you play a root note and get back a texture that fills the gap between the last line and the next cut without touching an amp sim.
On a session bus, I treat it like a reverb return that happens to come from a guitar. Drop it on a stereo aux, send the piano or a muted string stem to it, and mix the fader up until the scene breathes. The onboard effects — space, movement, a little grime — are quick enough that I don't reach for a second plugin. If a cue needs to darken in the final thirty seconds, I grab the filter knob rather than automating an EQ curve.
The four plugin formats (VST2, VST3, AU2, AAX) mean it loads in Logic, Pro Tools, and the free DaVinci Resolve track without a wrapper. I keep the UI on a secondary display, but the minimum resolution is 1280 by 768, so even a thirteen-inch MacBook Air on set fits the window.
Where it fits: right after a rough picture lock when the temp score feels too literal. Cinedream gives you atmosphere that doesn't fight the dialogue bus, which matters more than any spec sheet number when the render bar is moving.
Silence After Loading? It Waits for MIDI Notes
The first thing that trips people up is silence after loading the plugin. Cinedream doesn't make a sound until MIDI notes hit it — it's not a noise generator, it's a chord-triggered instrument. If your DAW transport is rolling and the meter is flat, check that the track is armed and your MIDI controller is sending on the right channel. The plugin listens on all channels by default, but some hosts route incoming data to channel 1 only, and a mismatched controller will leave you staring at a motionless interface.
Another headache: the plugin window opens but the graphics are a blank grey rectangle. That's almost always a Metal compatibility issue on older macOS installs. Toggle your DAW's graphics acceleration setting off and back on, or switch the plugin between windowed and full-screen modes. On Apple silicon machines running Monterey, a one-time permissions prompt for microphone access can block the audio engine — grant it through System Preferences > Security & Privacy, restart the host, and the signal path lights up.
If you dropped the component file in the wrong folder and your DAW refuses to scan it, the fix is simple but specific. Cinedream's AU sits in /Library/Audio/Plug-Ins/Components/VG-CINEDREAM.component, and the VST3 goes into /Library/Audio/Plug-Ins/VST3. A mismatch — putting the VST3 into the Components folder, for instance — causes blacklisting. Delete the offending file, rescan, and place it where it belongs.
Map the Mod Wheel to Filter Cutoff First
Before you compose a single note, map the mod wheel to the filter cutoff. Cinedream doesn't do this by default, but every DAW worth its buffer size lets you assign MIDI CC #1 to the cutoff parameter. Now you can ride the brightness of a pad the same way you'd ride a fader, opening it up for a reveal or closing it down under dialogue.
Next, audition the styles dry — kill the onboard effects completely, then bring them back one at a time. The movement knob is the one that gets overused fastest. A little goes a long way, and if you're layering Cinedream under a real guitar take, you want the texture to sit behind the transient, not compete with it. Save a dry preset as "Flat Start" so you're not always stripping effects before building your own chain.
Set up a template track with the gain staged at -12 dB. Cinedream's output can run hot when you stack chords, and gain-staging early saves you from chasing clip lights later. If you're on a laptop with 8 GB of RAM, bounce the track to audio once you're happy — the plugin streams samples from disk, and a dense session with multiple instances will push memory limits faster than you expect.
Runs Natively on Apple Silicon, No Rosetta
Does it work on an M1 Mac without Rosetta? Yes. Cinedream ships as a universal binary, so it runs natively on Apple silicon. No translation layer, no performance penalty. On an M1 Max machine with 32 GB of RAM, it loads in under two seconds and sits comfortably in a session with forty other tracks. On an M1 Air with 8 GB, you'll want to freeze tracks sooner, but the plugin itself runs without complaint.
Can I use it in Resolve for film scoring? Absolutely. Fairlight sees AU and VST3 plugins, and Cinedream loads cleanly on the track insert. The chord trigger works the same way it does in Logic — play a MIDI region on the timeline, and the engine generates the performance. For editors who score directly in their NLE, this skips the roundtrip to a separate DAW.
Is it a one-trick pad machine, or can I get a lead tone out of it? It's built for texture, not for leads. You can push the saturation and roll back the space effect to get something grittier, but if you need a melody line with vibrato and bends, reach for a different Virtual Guitarist. Cinedream shines when you want the guitar to be felt rather than heard.
AU Validation No Longer Fails in Logic
The jump from the initial release to 1.0.1 didn't add new styles or effects, but it fixed a handful of issues that made the plugin unstable in specific hosts. The most noticeable improvement: AU validation no longer fails on Logic Pro scans when multiple UJAM instruments are installed side by side. That alone saved me a morning of deleting caches and re-approving plugins after a library reshuffle.
On the VST3 side, parameter automation now recalls correctly when you reopen a project. In earlier builds, the movement and space knobs would reset to noon, forcing you to re-automate every time you loaded a session. That's gone — the values stick. AAX users on Pro Tools saw a similar fix for the filter knob, which previously snapped to zero on session reload regardless of the saved state.
Also fixed: the plugin no longer spikes CPU by 20% when the UI is open on a Retina display. That was a quiet annoyance for anyone mixing with the window visible on a secondary monitor. Now the graphics thread stays in its lane, and the render bar keeps moving.
- macOS 10.13 or later
- Apple Silicon and Intel supported
- 8 GB RAM
- 4 GB free disk space
- 1280 by 768 minimum display
- Internet connection required
Notes from the edit bay · 0
Sign in or get an edit-bay pass to leave a note.
No notes from the edit bay yet. They go up after I read them.
