Dear Waveform Devs...

[tmaworks]

Obviously not.

You have to implement a cross-platform part (to load 32-bit binaries) which the DAW communicates with. It's possible but brings complexity. So having out-of-process plugin scan and sanboxing in relatively recent JUCE/Waveform I don't think that devs would step in that in visible plans.

Thanks for enlightening me!

Yeah -I would consider a bridge the least of waveforms problems...

[tmaworks]

I had a conversation with the devs a couple years ago about including a bridge into Waveform. They were quite candid in their response: the number of support headaches a bridge would cause far exceeded the number of users that would benefit from it; they correctly pointed out that the number of people depending on 32-bit plugins decreases every year.

In short, it would make more people annoyed with performance issues than a bridge could ever make happy.

Yeah, I mean, I get it. Especially when you can just pay $15 or whatever it is and buy J-bridge...

As I was just saying to another poster -A bridge would be last on my list and the least of Waveforms deficiencies as I see it...

[Peter Widdicombe]

You can test JBridge and get a 20-minute per session demo. It essentially creates a little .DLL and a .TXT file that point back to the original 32-bit version, and runs with that overhead; effectively converting between the two.

To use, you use Jbridge to CREATE the "conversion .DLL" in a folder which the host uses - one for each (or only) .dll specified. This is a one-time thing. I have an SQ8L emulator of an ESQ-1 I found that will never have a 64-bit version.

In use, it then presumably loads some other Jbridge support stuff (??) plus the original VST. Waveform sees that "fake" as a valid 64-bit plugin and you can't tell the difference - although presumably it uses extra resources doing converting between what a 32-bit normally presents and what a 64-bit expects. I just tested converting MinimogueVA, and worked easily like a charm.

Use this if you have a WONDERFUL, IRREPLACEABLE 32-bit plugin; but replace with a 64-bit one as soon as you come across one that fills the need.

[tmaworks]

You can test JBridge and get a 20-minute per session demo. It essentially creates a little .DLL and a .TXT file that point back to the original 32-bit version, and runs with that overhead; effectively converting between the two.

To use, you use Jbridge to CREATE the "conversion .DLL" in a folder which the host uses - one for each (or only) .dll specified. This is a one-time thing. I have an SQ8L emulator of an ESQ-1 I found that will never have a 64-bit version.

In use, it then presumably loads some other Jbridge support stuff (??) plus the original VST. Waveform sees that "fake" as a valid 64-bit plugin and you can't tell the difference - although presumably it uses extra resources doing converting between what a 32-bit normally presents and what a 64-bit expects. I just tested converting MinimogueVA, and worked easily like a charm.

Use this if you have a WONDERFUL, IRREPLACEABLE 32-bit plugin; but replace with a 64-bit one as soon as you come across one that fills the need.

You are a VERY SMART person, Mr. Widdicombe!

Thank you for the great explanation and insight!