JoeV: It sounds like you might still be using the 0.9.3 version. In the 0.9.4 beta we streamlined Prism, removing MIDI preset/scene triggering in favor of a parameters-only approach. This is exactly how the original Cymatic Labs plug-ins also function. We feel that creating "scenes" of parameter states that can be recalled via simple sequencing triggers is still a valuable concept vs. parameter automation, but ultimately decided that it would be best to implement it in a standalone version. For instance, since MIDI is event-based, proper timeline scrubbing is impossible (as opposed to automation envelopes where the exact state is known at all times). Since 0.9.4 is more similar to the original plug-ins, most of your workflow and approach should translate. We will reach out to you directly to see if we can assist with any remaining issues.
Rodulf: Audio input modulation functions much the same between the two plug-ins. It's possible that somehow gain stages or levels are slightly different between them, but this is something that should be easy to compensate for by boosting either audio input gain before Prism, and/or Audio Input Gain within Prism. One difference however, is that Prism by default applies gamma correction to make LED output brightness more linear on the LED glasses. It is possible that since the old plug-ins did not provide this correction, you experienced disproportionately bright modulation from the input source. In Prism's settings you can try adjusting or disabling Gamma Correction to see if the brightness curve more closely matches your prior experience.
Updates to Prism's input modulation are already in the works, and you can read about them
here (as well as discuss feature requests).
Additionally, we're trying to cover some of Prism's frequently asked questions
here.
Bookmarks