Robin Gareus

Or try this quick/dirty patch (right-click on the scope's display when the scope is not paused. That's not very discoverable though. ```diff diff --git a/gui/sisco.c b/gui/sisco.c index 5d5c390..679fb9a 100644 ---...

> Maybe some hidden/not immediately visible functionality is OK a well? If a user accidentally hides the sidebar, that's a problem, still. There could be a text in the bottom...

> What about a context menu? None of my plugins have context menus or popup windows of any kind. That is very bad practice for any plugins.

Depends on your hardware and system. pro-audio systems can be tweaked to run reliably (zero x-runs) at sub millisecond latency. -- While some casual consumer systems have issues to with...

That is outside of the scope of the plugins. The meter plugin's sole purpose is to reliably measure and correctly visualize the measured signal (with proper ballistics, rise-time, overshot, burst...

The data is [supposed to be] continuous. There's no gap right-edge -> left edge. I'll verify this again. The number of grid-cells depends on the width of the window and...

Works just fine here (after resizing the window). 48KSPS, 720px wide effective display 

PS. there's a define `WITH_TIME_ADJ` in gui/sisco.c:29 which, if enabled, adds a dial to to variably adjust and fine-tune the time-scale. It's still limited to granularity of 'integer number of...

Looks like you've got an older version. Resizing was added just after the v0.5 release and v0.6 is not yet tagged.

Regarding numeric entry of the time-scale: Maybe. I'm still pondering how to best facilitate variable time-scale in general. As documented under (1) and (2) at http://x42.github.io/sisco.lv2/ the time-scale configuration is...