Using an AudioProcessor or AudioSource as a Tracktion Engine plugin

[erikronstrom]

Hi,

If I have an JUCE AudioProcessor or AudioSource, is there any way to wrap it into a Tracktion Engine plugin?

I saw this earlier forum post but I’m not sure that the answer was conclusive:

Wrapping an AudioProcessor into a Tracktion Engine Plugin

As I work on some plugins, I’m trying to use the Tracktion Engine in the standalone app versions, using custom standalone windows as described here and elsewhere: The rationale is that I want to have access to a functioning transport and the engine’s device manager etc. in the plugin’s standalone version. I can get the engine and its transport to work just fine, but I’m trying to wrap my head around how I’d wrap the project’s AudioProcessor into a tracktion engine Plugin so I can insert it in…

Thanks!
Erik

[dave96]

You probably want to just subclass tracktion_engine::Plugin and then register that subclass with the engine. Then you can use that subclass to wrap your existing functionality.

That’s how most of the built-in plugins work so have a look at those for examples?

[erikronstrom]

Thanks!

Yeah, that’s what I was doing, I was just having this feeling of “there has to be a simpler way of doing this”

(Not that subclassing Plugin was particularly hard, I just would have thought that re-using JUCE AudioProcessors to be such a common use case that there would be some kind of built-in wrapper)