ABYZOR Variations removed external Host Sync MIDI output in version 2.1.0 and now uses LINK for synchronized internal preview audio. Old two-track routing instructions therefore solve a workflow that the current plugin no longer exposes.
Two paths are supported, with a sound source hosted inside Variations for transport-synchronized auditioning and audio from the same track. Drag or export MIDI when a separate DAW instrument should play the notes.
Keeping those jobs separate prevents most silent-output problems. LINK handles audio produced within Variations, while exported MIDI becomes an ordinary clip for another instrument. A DAW cannot receive live MIDI from a plugin output that is no longer available.
Enable LINK, select the original, variation, or arrangement row with its play control, then start the DAW transport. With LINK active, that control chooses the target while the host transport governs playback, seeking, looping, and tempo.
Preview audio becomes silent when the playhead leaves the DAW loop region, which can look like a failed instrument or broken route. Extend the loop across the full pattern before changing ports or reinstalling anything.
LINK always follows the DAW tempo, even when the genre-groove control is active. Although the groove may add synthesized backing drums during preview, they never enter exported MIDI, so missing percussion afterward is expected.
Record or bounce the audio from the Variations instrument track once the hosted sounds are right. This same-track synchronized preview includes internal timbres, samples, hosted instruments, and the optional backing groove. LINK is session-only rather than a saved preset setting, so verify its state after reopening the work.
The change matters because many routing tutorials assume a VST publishes MIDI that another track can select as an input. Ableton Live, for example, can receive such output on a second MIDI track with monitoring enabled. That method only works when the source plugin actually provides a MIDI output.
Assigning wrapper ports or creating extra receives cannot restore removed Host Sync behavior. Those controls route data already exposed by a plugin, not notes held only inside its interface. For current Variations sessions, use hosted instruments for live playback or commit the row to MIDI.
That handoff fits the individual MIDI snapshot export because one accepted state can become a conventional clip before sound design begins. Keep the original snapshot until the transferred clip has passed a playback check. Visual presence in the arrangement does not guarantee a clean ending or correct placement.
Audition the exported clip at the same tempo with a comparable patch, separating instrument differences from an actual transfer failure. Different attack, release, voice limits, or pitch range can make identical notes sound shortened, crowded, or absent.
Replace that internal sound with the intended hosted VST3 only after the first test passes. If silence begins, then inspect the loaded patch, register, channel controls, and post-instrument EQ. Rebuilding DAW routing would target the wrong layer.
Test the export path on a clean instrument track with a simple patch. Confirm that the MIDI clip contains notes, begins at the intended bar, and reaches the synth while monitoring or playback is active. Audio silence with visible incoming notes points downstream toward the instrument, not Variations.
Avoid running LINK preview and the exported clip together during comparison. Two synchronized sources can double attacks, add unexpected backing drums, or create a louder result that resembles a better route. Mute one path and compare under equal playback conditions.
Finally, play from before the clip start through its last note and beyond the loop boundary. Listen for duplicate triggers, clipped releases, hanging notes, and timing changes after a transport restart. A route is dependable only when it starts, stops, seeks, and repeats without manual recovery.
Two paths are supported, with a sound source hosted inside Variations for transport-synchronized auditioning and audio from the same track. Drag or export MIDI when a separate DAW instrument should play the notes.
Keeping those jobs separate prevents most silent-output problems. LINK handles audio produced within Variations, while exported MIDI becomes an ordinary clip for another instrument. A DAW cannot receive live MIDI from a plugin output that is no longer available.
LINK keeps preview audio on the Variations track
Load Variations as an instrument rather than a MIDI effect, then choose an internal synth, imported sample, or hosted VST3 for each preview channel. No second DAW track is required for this auditioning path.Enable LINK, select the original, variation, or arrangement row with its play control, then start the DAW transport. With LINK active, that control chooses the target while the host transport governs playback, seeking, looping, and tempo.
Preview audio becomes silent when the playhead leaves the DAW loop region, which can look like a failed instrument or broken route. Extend the loop across the full pattern before changing ports or reinstalling anything.
LINK always follows the DAW tempo, even when the genre-groove control is active. Although the groove may add synthesized backing drums during preview, they never enter exported MIDI, so missing percussion afterward is expected.
Record or bounce the audio from the Variations instrument track once the hosted sounds are right. This same-track synchronized preview includes internal timbres, samples, hosted instruments, and the optional backing groove. LINK is session-only rather than a saved preset setting, so verify its state after reopening the work.
External synths need a committed MIDI file
Drag or export the chosen row onto the destination instrument track, then let the DAW play the resulting MIDI normally. This path trades live regeneration for editable, repeatable note data.The change matters because many routing tutorials assume a VST publishes MIDI that another track can select as an input. Ableton Live, for example, can receive such output on a second MIDI track with monitoring enabled. That method only works when the source plugin actually provides a MIDI output.
Assigning wrapper ports or creating extra receives cannot restore removed Host Sync behavior. Those controls route data already exposed by a plugin, not notes held only inside its interface. For current Variations sessions, use hosted instruments for live playback or commit the row to MIDI.
That handoff fits the individual MIDI snapshot export because one accepted state can become a conventional clip before sound design begins. Keep the original snapshot until the transferred clip has passed a playback check. Visual presence in the arrangement does not guarantee a clean ending or correct placement.
Audition the exported clip at the same tempo with a comparable patch, separating instrument differences from an actual transfer failure. Different attack, release, voice limits, or pitch range can make identical notes sound shortened, crowded, or absent.
A short signal test isolates silent playback
Start LINK diagnosis with an internal Variations synth rather than a third-party instrument. Select one populated row, cover its length with the DAW loop, start transport, and watch the track meter. Successful internal audio proves that selection, clocking, and the host track are working.Replace that internal sound with the intended hosted VST3 only after the first test passes. If silence begins, then inspect the loaded patch, register, channel controls, and post-instrument EQ. Rebuilding DAW routing would target the wrong layer.
Test the export path on a clean instrument track with a simple patch. Confirm that the MIDI clip contains notes, begins at the intended bar, and reaches the synth while monitoring or playback is active. Audio silence with visible incoming notes points downstream toward the instrument, not Variations.
Avoid running LINK preview and the exported clip together during comparison. Two synchronized sources can double attacks, add unexpected backing drums, or create a louder result that resembles a better route. Mute one path and compare under equal playback conditions.
Finally, play from before the clip start through its last note and beyond the loop boundary. Listen for duplicate triggers, clipped releases, hanging notes, and timing changes after a transport restart. A route is dependable only when it starts, stops, seeks, and repeats without manual recovery.
