title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 6 of 6

Thread: VST plugin issues with R2022-11-25

  1. #1

    Join Date
    Feb 2020
    Posts
    6

    VST plugin issues with R2022-11-25

    Very happy to see that VST support has arrived (back) in the latest dBpoweramp release!

    Unfortunately a couple of VST3 effects I've tried seem to produce silence.

    Spoon: If I may suggest, try putting your VST host through its paces with Stereo Tool - it packs in a huge amount of processing for a single VST effect, and its complexity seems to expose problems in VST hosts readily. It also produces a comparatively huge amount of state data to serialise.

    Currently, when used with dBpoweramp, the VST3 version of Stereo Tool seems to produce silence, and the VST2 version seems to introduce regular-spaced artefacts in the left channel (buffer issue?); so it would seem well-placed to help narrow down any remaining host bugs.

  2. #2
    Super Moderator
    Join Date
    Jul 2011
    Posts
    1,217

    Re: VST plugin issues with R2022-11-25

    Thanks for the bug report.

    Any other VSTs than Stereo Tool that cause trouble?

    Stereo Tool VST3 seems to crash in IAudioProcessor::process(), so far we couldn't get it working at all.
    Stereo Tool VST2 works for me, output appeared OK. Any specific content that you tried it on? File format / sample rate / bit depth?

  3. #3
    dBpoweramp Enthusiast
    Join Date
    Aug 2009
    Location
    Florida
    Posts
    74

    Re: VST plugin issues with R2022-11-25

    +1 on using StereoTool as the test VST3. It's a monster.

    https://www.stereotool.com/

  4. #4

    Join Date
    Feb 2020
    Posts
    6

    Re: VST plugin issues with R2022-11-25

    Thanks for looking into this!

    Quote Originally Posted by PeterP View Post
    Any other VSTs than Stereo Tool that cause trouble?
    I've had a look for some free VST3 effects that don't work and you can use for testing without too much trouble, and so far I've found that the majority produce silence, unfortunately. I've not looked into what the ones that fail have in common. Maybe just whether they support 32-bit or 64-bit precision samples?

    Here's some: ToneLib TubeWarmth, Red Rock Sound EQ302, Analog Obsession ReLife, SNFK Music Unifilter, ChromaDSP HarmonicReverb.

    Quote Originally Posted by PeterP View Post
    Stereo Tool VST2 works for me, output appeared OK. Any specific content that you tried it on? File format / sample rate / bit depth?
    Everything I've tried is WAV / 16-bit / 44100Hz.

    With Stereo Tool VST2, I just applied it on a WAV file containing a sine wave at -40dB (downloadable here).

    This is what the output looks like when processed with Sound Forge:
    ok1.png

    This is the output with dBpoweramp (same settings) - notice artefacts in audio and extra silence added to beginning:
    problem1.png

    Zoomed-in view of the regular artefacts:
    problem2.png

    If there's anything you'd like me to test, do let me know.

  5. #5
    Super Moderator
    Join Date
    Jul 2011
    Posts
    1,217

    Re: VST plugin issues with R2022-11-25

    Thanks for all the details, compatibility issues are being investigated for the next update.

    Looks like many VSTs don't work at all if the host application doesn't access their user interface first, on the exact VST instance doing processing. Which is very problematic for converter type apps that save presets and use it for automated jobs. It doesn't matter if you touch VST settings panels from dBpoweramp first; a new separate instance is created for processing always.

    I'm trying to come up with some mitigation technique for this.

    It's even worse than it sounds, cannot stick and reuse VST instance that was configured before, since dBpoweramp runs multiple conversion threads and needs multiple effect instances working.

    I hope some VST developers read this and can fix the problem on their end, which has to be easier than fixing it on our side.

  6. #6

    Join Date
    Feb 2020
    Posts
    6

    Re: VST plugin issues with R2022-11-25

    Thanks for continuing to look into this... It sounds like a nightmare.

    Nobody like a backseat coder, and I understand you're creating your own independent implementation, but it might be worth having a quick look at the open source and now abandoned MrsWatson. It has no GUI and supports VST2 only, but doesn't have any issues with any plugins I've found so long as you supply a .fxp file created in another host.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •