Possible bug with DPMP4 - VST3 x64 version

[Tappistry]

Hello!

In the process of demoing DPMP4, I may have come across a possible bug with Reaper 5.70. I'm running Windows 10, 64-bit. Reaper is also 64-bit.

The VST2 64-bit plugin seems to function normally. However, the VST3 x64 version of the plugin does not let the audio pass through when it's enabled on a track.

The evidence seems to be pretty clear in the Reaper plugin window. On the VST2 version of the plugin, Reaper shows the typical "VST Out 1 and 2" for the audio routing. On the VST3 version of the plugin, the Output section is labeled "Unused."

If this is user error, please let me know. Though no matter what settings I change in the plugin seem to help. And Reaper doesn't give me the option to enable the VST audio output with the VST3 version. Let me know if you need any further information to help identify the potential problem.

[cturner]

Turn Reaper's wet/dry control for DPMP to 100% dry.

[Tappistry]

Turn Reaper's wet/dry control for DPMP to 100% dry.

Interesting! That fixed the issue.

[Blue Cat Audio]

This is indeed a known issue with the VST3 version: in some hosts audio will not pass thru. We have a pending fix for this problem. Anywaywe strongly recommend to stick with VST2 unless you need to switch to VST3 for specific features.

[Tappistry]

This is indeed a known issue with the VST3 version: in some hosts audio will not pass thru. We have a pending fix for this problem. Anywaywe strongly recommend to stick with VST2 unless you need to switch to VST3 for specific features.

Yes, I will stick to the VST2 version.

Sorry if my post was redundant. I searched the forum here but didn't see any threads about it, perhaps I didn't search carefully enough.

[Blue Cat Audio]

Sorry, I just meant that it is an issue we are aware of.