Blue Cat's PatchWork vs Magma ( Nomad Factory )
-
- KVRist
- 75 posts since 2 Jan, 2010
As there is a VST Chainer in Magma, I would like to know the different possibilities in Blue Cat's PatchWork.
-
- Beware the Quoth
- 35414 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Patchwork doesnt have built-in effects and currently doesnt handle automation of plugins. Apart from that, Patchworks grid is flexible from 1 to 8 parallel stacks of 1 to 8 serial plugins; Magma is fixed at a 4x4 rack of modules with 6 alternate routing between them, but a single module can host one of Magma's own effects or a chain of up to 8 VST plugins.
And Magma is an effect which only hosts VST effects. Patchworks is an effect and an instrument, and will hosts instruments.
And Magma is an effect which only hosts VST effects. Patchworks is an effect and an instrument, and will hosts instruments.
Set Theory claim:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate.
Red is Red and anything that is Red is an object, a class in itself or a real thing if you prefer"
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate.
Red is Red and anything that is Red is an object, a class in itself or a real thing if you prefer"
-
- KVRist
- Topic Starter
- 75 posts since 2 Jan, 2010
Thank you. Very fine explanation.
-
- KVRAF
- 10128 posts since 16 Dec, 2002
And it has no built in modulation system like Magma, shame as this would make it far more attracive.
There are already quite a few VST chainers in various guises both free and cheap
There are already quite a few VST chainers in various guises both free and cheap
-
- Banned
- 22457 posts since 5 Sep, 2001
[DELETED]
-
- KVRAF
- 14738 posts since 19 Oct, 2003 from Berlin, Germany
Kind of have to agree here. MB-7 looks just more flexible and more intuitive to use.
If Patchworx would get a routing matrix, where we can create our own routing and the likes, something that Magma hinted at, maybe I'll take another look. In the meantime, I'm still eyeing regular modular environments.
If Patchworx would get a routing matrix, where we can create our own routing and the likes, something that Magma hinted at, maybe I'll take another look. In the meantime, I'm still eyeing regular modular environments.
-
- KVRAF
- 7094 posts since 22 Jan, 2005 from Sweden
I did a little peek if to go for PT - and looking for solution to use VST in AAX64 environment Patchwork seemed a nobrainer to do that.
I just wonder when Avid will shut it down since it can be used to wrap VST.
Avid are ruthless in protecting their interests it seems - shutting down the two wrappers that did exist for AAX before.
No, I left the PT idea....mined territory, kind of, I dare not step further.
I just wonder when Avid will shut it down since it can be used to wrap VST.
Avid are ruthless in protecting their interests it seems - shutting down the two wrappers that did exist for AAX before.
No, I left the PT idea....mined territory, kind of, I dare not step further.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6334 posts since 8 Sep, 2004 from Paris (France)
You should not worry about AVID killing our products, as they are not wrappers. AVID have their reasons for not allowing actual wrappers that make VSTs visible as if they were AAX plug-ins. On the other hand, they are definitely open to plug-ins that can load other plug-ins.lfm wrote:I did a little peek if to go for PT - and looking for solution to use VST in AAX64 environment Patchwork seemed a nobrainer to do that.
I just wonder when Avid will shut it down since it can be used to wrap VST.
Avid are ruthless in protecting their interests it seems - shutting down the two wrappers that did exist for AAX before.
No, I left the PT idea....mined territory, kind of, I dare not step further.
If you still have a doubt, our plug-ins are currently advertised on the AVID AAX Blog and listed in the Pro Tools plug-ins database. Blue Cat's PatchWork has also been posted this week on the AVID Pro Tools facebook page.
-
- KVRAF
- 7094 posts since 22 Jan, 2005 from Sweden
Thank you - good to hear if I ever overcome my fear of such companies like Avid.Blue Cat Audio wrote:You should not worry about AVID killing our products, as they are not wrappers. AVID have their reasons for not allowing actual wrappers that make VSTs visible as if they were AAX plug-ins. On the other hand, they are definitely open to plug-ins that can load other plug-ins.lfm wrote:I did a little peek if to go for PT - and looking for solution to use VST in AAX64 environment Patchwork seemed a nobrainer to do that.
I just wonder when Avid will shut it down since it can be used to wrap VST.
Avid are ruthless in protecting their interests it seems - shutting down the two wrappers that did exist for AAX before.
No, I left the PT idea....mined territory, kind of, I dare not step further.
If you still have a doubt, our plug-ins are currently advertised on the AVID AAX Blog and listed in the Pro Tools plug-ins database. Blue Cat's PatchWork has also been posted this week on the AVID Pro Tools facebook page.
I might buy Patchwork for overcoming routing limitations in other daws I use right now either way - and support the work that it might get VST3 loading support in future.
Why not synth version do support 16-32 stereo outs as VST instruments does - I don't know.
Why this 4 stereo limitation for outs?
And why not make a proper scan of plugin directories like hosts do. That would open up to using WaveShell and make it much more versatile. My old Vsampler plugin do support VST scanning - and it just pops up a screen "New plugins in system - Scan or Skip".
I don't know if you looked at Tracktion rackbuilder - really cool.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6334 posts since 8 Sep, 2004 from Paris (France)
VST Shells are actually supported (just try to open the shell file and you'll be able to select the plug-in you want).
Multiple I/O is currently not fully implemented, at least not as well as we intend to do it (it can basically be run on multichannel tracks but busses are not supported yet for non-VST formats that have bussing capabilities).
About scanning: it may be implemented in the future as an additional way of selecting plug-ins, but we wanted the ability to quiclky choose a new plug-in without having to rescan everytime.
Multiple I/O is currently not fully implemented, at least not as well as we intend to do it (it can basically be run on multichannel tracks but busses are not supported yet for non-VST formats that have bussing capabilities).
About scanning: it may be implemented in the future as an additional way of selecting plug-ins, but we wanted the ability to quiclky choose a new plug-in without having to rescan everytime.
-
- KVRAF
- 7094 posts since 22 Jan, 2005 from Sweden
Thank you - good info about waveshell.Blue Cat Audio wrote:VST Shells are actually supported (just try to open the shell file and you'll be able to select the plug-in you want).
Multiple I/O is currently not fully implemented, at least not as well as we intend to do it (it can basically be run on multichannel tracks but busses are not supported yet for non-VST formats that have bussing capabilities).
About scanning: it may be implemented in the future as an additional way of selecting plug-ins, but we wanted the ability to quiclky choose a new plug-in without having to rescan everytime.
As Vsampler implemented it seems no sweat to do.
I don't think they do full scan.
To just check which files are in different folder structures, and store away (path+names + timestamp)and compare at next startup of plugins - is done in <1s. Waves authorization takes a couple of secs to do.
Doing this as a static member could mean only once per session.
-
- KVRAF
- 4329 posts since 26 Jun, 2004
Im guessing, atm, that PatchWork has a lower base overhead than Magma.
Can anyone confirm?
Can anyone confirm?
-
- KVRer
- 27 posts since 19 Jan, 2006 from Sweden
A wet dream and ultimate solution / would be a product like this with:
- Meldaproductions magnificent modulation capabilities of the hosted effects vst-parameters.
- A bundled 'effect' that hosts an ASIO driver (allowing a 2nd soundcards I/O for external effects)
That would indeed be the ultimate solution for me
/Kristofer
- Meldaproductions magnificent modulation capabilities of the hosted effects vst-parameters.
- A bundled 'effect' that hosts an ASIO driver (allowing a 2nd soundcards I/O for external effects)
That would indeed be the ultimate solution for me
/Kristofer
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6334 posts since 8 Sep, 2004 from Paris (France)
It's not an implementation issue. It's just freaking boring to have to wait before you can use newly installed plug-inslfm wrote: I don't think they do full scan.
To just check which files are in different folder structures, and store away (path+names + timestamp)and compare at next startup of plugins - is done in <1s. Waves authorization takes a couple of secs to do.
Doing this as a static member could mean only once per session.
-
- KVRAF
- 7094 posts since 22 Jan, 2005 from Sweden
OK, thank you.Blue Cat Audio wrote:It's not an implementation issue. It's just freaking boring to have to wait before you can use newly installed plug-inslfm wrote: I don't think they do full scan.
To just check which files are in different folder structures, and store away (path+names + timestamp)and compare at next startup of plugins - is done in <1s. Waves authorization takes a couple of secs to do.
Doing this as a static member could mean only once per session.