Captain Chords in Waveform 12 pro

[jn2002dk]

I can't get the new Captain plugins to display properly. This is on the latest Win 10

Here is how it looks when i just add it


Then, if i toggle between plugin and faceplate, it looks like this which is displaying the entire plugin but the size is still way too small to be used comfortably. Also, dragging the plugin resize handle does not resize the plugin, only the faceplate


Finally, if i toggle to faceplate and drag that window to a large size and then toggle back it looks like this

Expected size but now part of the plugin is cut off making it unusable

This is with dpi awareness on
I have also tested the same plugins in Studio One where they look exactly as they should with no issue

[Watchful]

It's my understanding from the last couple years that pretty much every plugin that truncates like this has a problem with the JUCE framework, which is outside of Tracktion's control. More particularly, there's something within JUCE that causes this--it's not a problem with the plugin itself or with Waveform. Tracktion has made numerous, numerous requests with the JUCE developers to address this perpetual issue.

[jn2002dk]

It's my understanding from the last couple years that pretty much every plugin that truncates like this has a problem with the JUCE framework, which is outside of Tracktion's control. More particularly, there's something within JUCE that causes this--it's not a problem with the plugin itself or with Waveform. Tracktion has made numerous, numerous requests with the JUCE developers to address this perpetual issue.

That's disappointing but thank you for explaining why it is happening

[Watchful]

Sure! I'm not saying I'm right, but that's my understanding from seeing years of these types of screenshots. I know Tracktion has attempted to escalate this, and I can't speak for the priorities of the JUCE developers but I'm hopeful they're not dismissing it as "inconvenience, yes, but you can still use the plugin." In your case, it isn't useable. Maybe this is an opportunity for Tracktion to push it one more time.

This also explains why other DAWs render these plugins fine--they're not JUCEd.

The only plugin that consistently does this to me is Melodyne, but mine at least is useable after a quick restretch.

What I don't get--and someone can explain it to me--is that Waveform has one of the most strict plugin testers there is, but somehow this gets past it. I don't know if there's no practical way to test for this; which is too bad, because I think 90% of the complaints about Waveform are these plugin display issues.

[Kott]

have you try toggle DPI Awareness for that plugin?

[jn2002dk]

have you try toggle DPI Awareness for that plugin?

Yup, still the exact same behaviour

[Kott]

have you try toggle DPI Awareness for that plugin?

Yup, still the exact same behaviour

sorry, see now

I haven't any good idea except test Captain Chords under other JUCE-based host, and either report it to JUCE/plugin devs, or it's a WF specific issue.

[jn2002dk]

have you try toggle DPI Awareness for that plugin?

Yup, still the exact same behaviour

sorry, see now

I haven't any good idea except test Captain Chords under other JUCE-based host, and either report it to JUCE/plugin devs, or it's a WF specific issue.

It's ok. I can just use them in Studio One. I just prefer working in WF but it's not like it's hard to export the midi or the stems to WF. I just wanted to know why it's happening and make Tracktion aware of the situation but i guess they already are. Thanks for trying to help

[UnionS8]

have you try toggle DPI Awareness for that plugin?

Yup, still the exact same behaviour

sorry, see now

I haven't any good idea except test Captain Chords under other JUCE-based host, and either report it to JUCE/plugin devs, or it's a WF specific issue.

It's ok. I can just use them in Studio One. I just prefer working in WF but it's not like it's hard to export the midi or the stems to WF. I just wanted to know why it's happening and make Tracktion aware of the situation but i guess they already are. Thanks for trying to help

Hehe. I'm in the same situation. I never worked faster than now with Waveform. Its workflow is an absolute gem. But these issues prevent me to use W12 as my main DAW. Quite pity. Does the same apply to VST3 plugins? Are those bugs JUCE related too?

[Watchful]

Some do, some do. Although VST3 are supposed to be more strict about standards, anything can happen. Sometimes a VST3 works better than its VST2 version...sometimes the opposite. Tracktion doesn't control the third parties.

I'll add something else: I can have a problem, but people with a nearly identical setup to mine have no issues at all. It's dependent on so many variables out of anyone's control.

[fde101]

I had display issues like these with a number of the newer versions of various Waves plugins under WF11 (on my Mac, with a non-retina display - my display is 1920x1200) but I am not seeing those issues (yet) under WF12. Go figure.