that is about module processing order. as in, for audio processing module A has its audio generated first, then module B, then module C, etc.
VCV Rack, at least on the free/open standalone version, has the concept of “first come, first take”.
which usually ends up meaning that, depending on the order of when you added modules, that dictates their audio processing order. the first module you ever added is going to be the first in the chain to be processed, then the 2nd you added etc etc. it is all based on a ever-growing list of loaded modules.
it is not possible to know for sure if this same approach is used in Rack Pro, since it is not open.
this is not about the order in terms of position on the rack, but the order of audio processing.
Most of what @falkTX says is true, and to the point. I do disagree with the conclusion that you can’t know the answer because it isn’t open source. Open or closed, the germane thing would be to measure the performance and compare them.
And for sure it’s totally true that if something isn’t open source, then it isn’t open source.
you are right, it is possible to measure it and get quite valid deductions from it.
tbh I really think it will just be the same as the free standalone version, since pretty much everything else works the same way.
if it is the same modules, the differences in performance will be not that much.
I used to have LTO enabled to get the linker optimizing the whole build (because it knows ALL the plugins code during build+link stage), but this causes breakage on some modules as LTO was never officially tested by them anyway
at the end of the day, I dont think differences in performance are going to be what makes people choose one over the other.
cardinal exists as a way to have a proper, self-contained and opensource plugin edition of VCV Rack. the static module list is intentional, pretty much any patch made from Cardinal first release is compatible with the latest one without having to mess with downloading 3rd party modules. Plus we can assume compatibility between not just Linux, macOS and Windows, but also BSD and Web systems (and hopefully soon HaikuOS too)
not being able to fix a software issue I have the knowledge for, being blocked only by “well it is proprietary” is just not something a few of us are no longer happy to live by.
that said, please support VCV if you can, so the ecosystem can keep existing. Cardinal cannot exist without VCV Rack.
Hmmm, hypothetically if VCV Rack would vanish, Cardinal would still be there, and of course, Cardinal could be developed further independently from VCV Rack (in case of latency compensation, this already happened).