I realise that Dan has previously alluded to the limited screen refresh capabilities of the Meta, but I would really appreciate a special mode for the Meta where it could be switched entirely into a 2 or 4 channel scope. Surely if everything else is depreciated for the time it’s in 'scope mode there would be sufficient onboard horsepower for it to act as an occasional oscilloscope. The feature could be toggled via a multi button press.
1 Like
this would be nice to have! guessing it would take some cpu so patches running hot (70%+??) would maybe not be able to use it
At some point, it might just be mimicking a Mordax DATA? I’m ok with that.
2 Likes
yah seeing as how the modules are currently displayed on screen I doubt it could be done without some kind of major reworking. I hope at some point it could be updated to work though as that’s exactly the kind of usage I envisioned when first purchasing the metamodule, less of a patch running device and more of a way to quickly throw in 1 to 1 vcv modules when needed in a patch. Also I love scopes but don’t think their fund to spend money on / take up rack space.
I think there could be two different use-cases here:
a) scope on jack
so the Percussa SSP has a nice feature, which is you can go to any jack, and it will give you a small scope for the values present on that jack. so you dont need to wire anything up to see it.
(vcv allows you to see numeric data values which is useful, but not great for signals)
b) scope module
I implemented something quite similar to DATA (the scope part) on the SSP - once the drawing api becomes available, I might see if I can do something similar on the MM.
(a) would have to be done by 4ms, but I see (b) could be done by 3rd parties once we have the api for native drawing.
ALL that said, @danngreen has already mentioned the update rate of the screen is somewhat limited, so Im managing my expectations about whats possible here.
the other thing, is by definition this drawing will eat cpu too… so thats something to take into consideration.
I did mention to dan, it be useful to have the concept of a ‘full screen’ app, which a scope module could definitely make use of.
this would be useful since
i) a scope module wants to be pretty big to be useful
ii) id want to save ‘cpu’ whilst not actually looking at the scope.
(I recognise this has other issues… but its a compromise)
definitely, something Id like to see… but I think it probably relies on the new 2.0 api being done first - all these things take time, and I think dan is v. busy already !