[PD] Pd as sound editor (issue with "scrolling" a table) ??
jancsika at yahoo.com
Tue Mar 4 19:20:21 CET 2014
On 03/04/2014 10:11 AM, i go bananas wrote:
> 2014-03-04 12:12 GMT+01:00 i go bananas <hard.off at gmail.com
> <mailto:hard.off at gmail.com>>:
> just for interest perhaps, here's the sound editor i made
> years ago:
> and probably even more interesting, here is maelstorm's wave
> display abstraction:
> basically, what maelstorm discovered was that using [until]
> with a counter was not nearly fast enough to do the
> calculations needed for a decent zoom/scroll function, and we
> looked into it, and there just didn't seem to be a vanilla
> workaround. So he uses iem_tab objects to do the table
Remember that when you redraw an element of an array you actually redraw
the _entire_ array in Pd Vanilla. And depending on the array style you
may have a separate tk canvas item for each element.
So when you use the [until] loop you are sending drawing instructions to
the GUI ($arraysize * $no_mouse_events) times. A single array redraw
instruction in tcl is about 4k, so to scroll a single pixel for a
100 elements * 1 = 100 redraws * 4k = 400k
That's flowing from the core to the GUI for a _single_ mouse event. If
you trigger ten scrolls you're already at 4 megs of data sent.
I'm pretty sure commercial editors avoid that type of design. In
editors like the upcoming Openshot Video that have several discrete
parts that sending messages, the GUI part almost certainly sends nothing
at all to the video core for zooming/scrolling. For moving a chunk of
audio/video, it almost certainly sends a single message about a single
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list