Hi, i would like to really understand CPU consumption.
Can you load a medium to big patch, clearly indicating the CPU consumption on Metamodule, so that i can (we can) exactly recreate it on PC, to compare the Metamodule vs own PC consumption.
(You should use foundamental or most common modules).
Thanks
ModuleFinder has info about the estimate CPU of a module
any patch that runs on the MM, should easily run on laptop/desktop, they are considerably more powerful than the MM. (assuming its not a potato.. but Im not even sure that would run vcv at all)
the other way around, you can only ever do an ‘estimate’, which is what modulefinder gives you.
why? because they completely different environments, possibly architecture.
e.g if you are running on an x86 windows PC, thats use SSE for floating point instructions, ARM uses NEON… is the module code optimise for one or the other?
so its always going to be an estimate, and as you can see in modulefinder, depending what you patch does, e.g. what it modulates, on some modules that be large, others marginal.
as for exact replication, pretty damn close in practice,
but it depends on module, some may have optimisations to help (e.g) reduce CPU load on MM, that could introduce small diferences.
also, you can oversample on a desktop/laptop, to help reduce aliasing where necessary.
BUT this is all about ‘exact’, frankly, most of the time its going to be close enough.
as for load, you get a feeling for whats possible on the MM, and the modulefinder can help, you its not exact, but again ‘close enough’. - you will need to test on the MM, and potentially make adjustments.
steps:
1.you load a Metamodule patch, showing the Metamodule consumption.
2.i recreate the exact same patch on my PC.
3.i compare the cpu power consumptions, to understand the potential of Metamodule, in relation to my Pc, before to buy it.
I think it’s simple and effective.
ok, so this is a pre-sales question, you dont have MM, you are trying to determine if its powerful enough for what you want?
answer is the same, you are better to use module finder!
think about the patches you want to create, the modules you want to use… then simply total them up. see what it comes up with - if too high, are you willing to compromise on module selection?, or sample rate/latency?
this will be much more accurate than trying to extrapolate some kind of ratio from MM to PC, its just not that simple… e.g. on my (old) mac mini m1, most MM patches hardly register any cpu load on it… but even then, I’ll say thats possibly down to module selection/ core usage etc.
I get that this is more effort on your part, but as purchase research, It’ll not only give a better idea of whats possible, but an opportunity to see whats available.
I guess, if you really want, you can even combine this with your idea, calculate load for a small patch with heavier modules, and see how that works compared to your PC.
Worth mentioning that MM’s processor is dual core, so you essentially get “2 for the (CPU) price of one “.