PatchWork lightweight host gets multicore and Apple M1 support

[Blue Cat Audio]

Full news has already been posted in the effects forum here, but I thought it would be interesting to discuss here these new hosting features of Blue Cat's PatchWork 2.5, our lightweight plug-ins host and multi effects application (and plug-in).

It now comes with a new multicore processing engine and Apple M1 support as a preview (as shown in our benchmark comparing Apple M1 and Intel Macs for audio, the new M1 processor seems really promising for real time audio). So you can now load many more plug-ins in parallel chains, even at lower latencies.



[All details in the effects section]

[antic604]

Wrong forum

[pdxindy]

Wrong forum

Patchwork is a host and this is the hosts forum. Seems like the right place to me?

[Blue Cat Audio]

Patchwork is a host and this is the hosts forum. Seems like the right place to me?

That was indeed the idea

[antic604]

Patchwork is a host and this is the hosts forum. Seems like the right place to me?

That was indeed the idea

Sorry, I wasn't aware it's a standalone app as well

[Blue Cat Audio]

Sorry, I wasn't aware it's a standalone app as well

I guess it was definitely worth posting here then

[ShawnG]

Interesting. I own this plugin from buying the guitar bundle, but I wasn’t thinking of it as an instrument host. Does it route MIDI data within the plugin? If it does it could be a solution that would let me use Jamstix with a Separate drum sampler within Reason.

[Blue Cat Audio]

Yes you can indeed route MIDI between plug-ins (using internal MIDI ports), so many people use it to load both MIDI effects and virtual instruments in a single instance in hosts for which MIDI routing is too complex or not available.

[fairlyclose]

Can each chain have its own stereo audio outputs?
EDIT i see there are a possible 8 stereo outs in an old tute. Is that still the case?

[Blue Cat Audio]

Can each chain have its own stereo audio outputs?
EDIT i see there are a possible 8 stereo outs in an old tute. Is that still the case?

The application (or the instrument plug-in) can indeed have multiple outputs. While parallel chains were not originally designed to be used like this, you can indeed route the output of any chain to a different output, using the audio I/O options of the plug-ins.

[fairlyclose]

Can each chain have its own stereo audio outputs?
EDIT i see there are a possible 8 stereo outs in an old tute. Is that still the case?

The application (or the instrument plug-in) can indeed have multiple outputs. While parallel chains were not originally designed to be used like this, you can indeed route the output of any chain to a different output, using the audio I/O options of the plug-ins.

following on... something I would love to do is use Riffer ( or other sequencers ) that sync to host within the standalone Patchwork. In other words have some sort of clock generated by Patchwork that will start and sync sequencers. In this way I could use Patchwork as a standalone generative system within a live performance context (or just as a generative system). Is this at all possible?

[Blue Cat Audio]

The PatchWork standalone application already has its own clock, and you can adjust the bpm in the audio/MIDI preferences. There is however no transport control (yet), so it would require that your sequencer has its own start/stop control.

[barbaroja]

I have had trouble with mastering, because of the single audio thread thing. That is good for composition and live situations but for mixing and mastering, where latency is of no importance, the real time CPU (speed) performance is a quick bottleneck.
I have resorted to splitting mastering in many tracks. However, not every host handles threading the same way. In my case, Reaper works much better than Live, as Live gets me HUGE amounts of latency when processing even cascaded tracks.

Is PatchWork able to overcome that limitation when inserted as a VST plugin? Can it decide what thread to allocate the plugins its loading (so to balance processor use) or is this dictated exclusively by the host?

[Blue Cat Audio]

As explained with more details in this blog post about multicore and parallel processing, there is no magic: you can process on multiple core effects that do not depend on each other.

It is not a matter of choosing the thread or CPU core to which a plug-in is affected: if it has to wait for the previous plug-in's output, it cannot be processed while the previous one is still processing, unless adding extra buffering and latency so that multiple buffers are processed in parallel (which PatchWork does not do).

PatchWork has its own reentrant thread pool, so it does not depend on the host to distribute processing on parallel chains. It relies on the operating system to do the load balancing on multiple cores, depending on overall system load (that's the most efficient way).

[xbitz]

I would like a send a big AFAIK PatchWork is the only plugin wrapper (tried many) which able to send keyboard signals (for ex. 'space' keys to the transport control of Cubase) to the host from opened plugins (not steal the focus), you would deserve a Nobel price or something

control would need more love(some modulation system) but I use Zenith anyway (if you need inspiration)


ps. would be nice if BC Plugins would have rent-to-own construction on splice as Zenith has for ex https://splice.com/plugins/38786250-zen ... y-audiaire I can see couple of free one only https://splice.com/plugins/search?q=blue%20cat