Originally Posted by Stejo ➡️

Can standalone run in the background as an always on vst host? Would have to be autostarting with the system, retaining settings and starting and running minimized in tray.

Currently using open source LightHost for this functionality, but I'd happily switch to something actively maintained and more feature rich like patchwork if it had the aforementioned features.

Originally Posted by barada ➡️

Unfortunately not, not at least not in the way this is working in other DAWs. Example, I can choose to map plugin parameters automatically, but in Patchwork interface they appear as numbers. Not as plugin actual parameter names. Or something labeled as user wish.

Also there's no way to (for example) map a value from one plugin and assign it to a Patchwork knob, then map some other value from different plugin in a chain - to a same knob. Like macro knob. Patchwork can't do that yet.

Also it can't scale knob range.

But don't let that put you off, Patchwork can do some seriously impressive stuff and chains. I highly recommend it. Somehow (it is a guess) I am sure they will add such "macro" features in the future.

I couldn't care less for oversampling part. I hope they focus on Macro and parameters instead of oversampling feature. I understand some want oversampling, just saying, workflow features are more important - for me.

Originally Posted by bluecataudio ➡️

But extending this to a powerful macro system is indeed something that has been on the todo list for quite some time!

Originally Posted by Telephone Line ➡️

any chance to get external audio routing?

Originally Posted by bluecataudio ➡️

What do you mean?

Originally Posted by bluecataudio ➡️

Parameters mapping was indeed initially developed so that hosted plug-ins could be easily controlled via MIDI or automated in a DAW, so it's currently limited to 1-1 full range mapping.

Originally Posted by bluecataudio ➡️

I can indeed keep running for days. You can start it with a command line with a preset file path so it's pretty easy to automate its startup.

Originally Posted by Telephone Line ➡️

If you imagine Patchwork as a Mastering Console, it would be extremely innovative to have the chance to put external inserts (the real outboard actually) inside. Just like Cubase and other DAWs do. It would come handy even in a DAW environment. Endless possibilities

Originally Posted by ChocolateHawkins ➡️

I started to try the built in FX and they are no joke either. Some seriously good stuff there. The waveshaper is really great.

Originally Posted by no genre ➡️

It's amazing how much difference it makes in parallel processing if you turn that feature on. Yes, I am the type person who would wonder why the speakers aren't working before noticing I haven't turned them on yet.

The more I learn about this, the more I am convinced it's the Blue Cat's meow.

Originally Posted by FerrousMeuhler ➡️

BlueCatAudio, Ive noticed that when loading a large patch in Ableton or Pro Tools say with up to 16 plugins all saved in bypass mode, it automatically seems to engage the full workload of all those plugins, regardless if they are in bypass mode or not. Is this behaviour intended ? If so any plans for optimizing the unused resources further ?

Originally Posted by bluecataudio ➡️

Quote:
Originally Posted by Uncovered Pitch ➡️
The only problem is that the audio connection gets lost every time you put the computer to sleep, so you have to close and re-open Patchwork to get the sound back. My DAW doesn't suffer from the same problem so I doubt it's my interface.

That's odd, indeed. Maybe it is related to the soundflower virtual driver?

Originally Posted by Mercado_Negro ➡️

I just downloaded the MAC VST3 Demo and it doesn't seem to be universal binaries because the ARM build of REAPER doesn't detect it as such.

Originally Posted by ChocolateHawkins ➡️

Can anyone tell me if what I’m trying to do is possible? It seems like it but I can’t tell from the manual

I’d like to be able to setup 4 parallel stereo channels to accept input on 4 separate channels and the output on 4 separate stereo channels.

I’d like to do this so that I can keep my global parallel channels in one tidy package on one channel in my DAW as opposed to running 4 separate ones.

Originally Posted by barada ➡️

If I understand you correctly, this is precisely where Patchwork excels at. And you can have up to 8 separate parallel stereo channels, turning them on or off easily.

Try installing the demo and have a fun with it. There are good youtube videos on it.

Originally Posted by ChocolateHawkins ➡️

I own it! Maybe it’s a case of me not explaining properly.

I want to be able to send to each of the parallel channels in differing amounts. So parallel channel one would be on the 1/2, channel two on 3/4, 3 on 5/6, etc. So when I send from a channel in my DAW I could send it to each in varying amounts.

Originally Posted by bluecataudio ➡️

That's indeed possible, even though PatchWork was not really designed for that purpose. You just need to insert a plug-in and assign its I/O to do that. For example use the built-in gain plug-in as the first plug-in in each parallel chain. Then for each one, select "audio I/O" and set it to manual (2 ins / 2 outs), select the appropriate channels, and "mute unused channels".

Each parallel chain will process only the selected input channels. If you do not want to bother managing channels for each plug-in in the chain, you can assign the outputs of all gain plug-ins to channels 1/2. You will then be able to re-route these channels to any output channel using the same trick at the end of each parallel chain.

I hope this makes sense!