PRISM PRO problems
The scene says LISTENING, the note is wrong, the harmony went quiet, MIDI took over and will not give the voice back. What each one means.
Read the plugin before you change anything
PRISM PRO writes what it is doing on its own face. The scene names the state, the chip names the note, and the row under the harmony switches names the source that is driving the line. Almost every report below is the plugin correctly describing a routing decision that was made somewhere else in the session, so the read-out is the first place to look. PRISM PRO is this plugin's name from version 1.2.2 on; it was called PRISM up to that release, so an older install still reads Nolvra PRISM in your plugin browser. The bundle identifier did not change with the name, so a saved project finds it either way.
The scene says LISTENING and nothing moves
LISTENING means no signal is arriving. The three usual causes, in the order they turn out to be true: PRISM PRO is on an instrument track or an empty audio track rather than the track carrying the voice, the track is not playing or not monitored, or the vocal is routed past the insert PRISM PRO is sitting in.
The state is deliberate. Rather than animating a grid with nothing behind it, the plugin stops and says so.
The line breaks up and the gap says UNVOICED
That is the engine telling you the frames it dropped were unvoiced: consonants, breath, silence between phrases. A talkbox has no pitch to follow there, so it does not invent one. Long UNVOICED stretches inside sung notes point at the source rather than the plugin: a gated or heavily de-noised take arrives with holes in it.
I only hear my own voice
MIX is the balance between the talkbox path and your dry voice, and at 0% you hear the voice you sang. Turn MIX up. The blended sound most people want sits around 45%.
The reverse case has the same control behind it: at 100% you still hear consonants and air, because two paths carry your own signal to the output on purpose, and DRY is their shared level.
The compressor and the chorus do nothing
Both sit on the wet path only. With MIX at zero there is no wet path to process, so switching them on changes nothing, and the row above them says so when it happens.
It is singing the wrong note
Work down the pitch source order, because whichever source is highest is the one deciding. MIDI outranks the chord on the sidechain, which outranks key and scale, which outranks the follower running free. The line beside the lists always names the one in charge.
If nothing is quantised, SCALE is on CHROMATIC, which is the off position and what a fresh instance opens on. If the note is right but in the wrong register, that is OCTAVE, the anchor. If a scale is set and the note is still outside it, check TRANSPOSE: with a scale locked it moves in scale degrees, and in CHROMATIC it falls back to semitones and the label says so.
AUTO says LISTENING and never locks
SCALE on AUTO works the key out from the engine's own note decisions and will not quantise before it has decided. Until then the line reads AUTO KEY: LISTENING - NO QUANTIZE YET. Give it more material, or set the key by hand. A wrong lock is worse than no lock, so the detector waits rather than guessing.
The chord version of this is the same idea: while confidence is low the last chord is held rather than dropped, so a quiet bar does not unlock the line.
MIDI took over and will not give the voice back
Once a note arrives, MIDI is the highest source and everything below it steps aside: quantising stops, the key and scale chips dim and say why, and harmony is passive in this version because the keyboard is choosing the pitch.
PRISM PRO releases on its own. Seven seconds after the last note is let go, the follower takes the line back. If it never releases, something is still holding a note: a stuck sustain pedal, a held note in a clip, or a controller sending notes you did not play.
One thing that deliberately does not count as MIDI: a panic. All Notes Off and All Sound Off are what a host sends when the transport changes, and arming a channel cannot silently take the follower away from you.
The plugin is not in my DAW
This is a host problem rather than a PRISM PRO problem, and the family article on plugins not appearing covers it. Two host-specific notes: FL Studio does not scan for new plugins on its own, so a fresh install needs Plugin Manager and Find installed plugins, and Logic validates Audio Units at launch, so a plugin installed while Logic was open shows up after the next start.
It will not open at all
An unlicensed PRISM PRO shows an activation screen rather than its interface, and the badge names what it found. The activation article covers the two doors and the offline window; the family troubleshooting article on activation covers the rest.
Still stuck?
Nothing here matching? Write to a person.