No announcement yet.

VST Isotope Plugin

  • Filter
  • Time
  • Show
Clear All
new posts

  • VST Isotope Plugin

    Maybe I'm missing something, but is this plug-in suppose to work like the real program? I've download the Isotope RX demo, and I've viewed the Isotope videos. And they seem really effective for cleaning up noise.

    But using the plug-in there seems to be no control over the functions, like using the train function, there's no spectral anaylsis in order for you select a range for it to analyse.

    And the declipper seems to do nothing? Or are I just wishing for too much, because these tools are essential to make this application worth while, and I'd rather not then have to fork out another $380odd for the stand alone.

    Is there something I need to turn on in the settings to get this plugin to work like it should?

  • #2
    Maybe I need to rephrase things

    as 137 people have looked at this thread but no replies, and I'm a new kid on this forum block, but I believe there are some moderators who actually work for Canopus from what I gather from other posts I've read.
    My question would be is this plug-in, I mis-stated it above as a application, be updated possibly in future versions to work like the stand-alone programme works?
    As in the 'train' button, to be able to select a portion of the displayed spectrum to let it plugin know what silence should sound like for example, remove hums, and wind noise perhaps etc etc.
    It would certainly raise the bar on the audio side of things with this great programme to be able to have a bit more functionality in this area.
    I had a slightly hot audio voice recording on a interview I was hoping the declipper could fix, but it seemed that it had no effect at all. When I watch the video demo's on the isotope RX programme using this same feature, it performs miracles, and would certainly save one's bacon now and then.



    • #3
      Anton Strauss has put together a tutorial video that should help get you started:


      • #4
        thanks Thoff

        for that,

        I see now how it the principle works, look forward to using it correctly!

        Kind Regards



        • #5
          Those of us who are here are here when we have time, if we have time... which is unfortunately not a lot these days as we all have full-time responsibilities.

          It is difficult, sometimes impossible, to get a plug-in to work the same as a stand-alone application, for a variety of reasons:
          1. Look-and-feel varies, and plug-ins will sometimes have to alter their look-and-feel to be consistent or operational with the host application.
          2. Plug-ins (usually) don't have direct access to the source data. For audio, this means that the plug-in in only has the frames that EDIUS has given it. In real-time processing, the plug-in only gets frames in real-time, so it can't "look ahead" at things in the future.
          3. Architecture limitations can limit capabilities. The plug-in architecture may not provide all the data the standalone application can, or as much as the standalone application might.

          So most times, while having a plug-in provides workflow convenience, many times it comes at the sacrifices of at least a little bit of functionality.