[PD] Re: [PD-announce] wvvw - wave viewer, some ideas

[derek holzer]

Thanks again for a terrific toy, Tom.

Just a few ideas which might make it even cooler. Embrace or disregard 
them as time allows...

1) Ability to make multiple instances of the viewing window instead of 
one master window.

2) Ability to nest seperate windows in patches, or even graph-on-parent.

3) Ability to label each track in the window(s?), either statically by 
array-name, or dynamically with the pathname of the file loaded [from 
soundfiler]

4) Of course, eventual multiplatform support would be nice, so people 
like Frank could use it in their end-user-oriented patches such as the 
RRADical patches.


About the keybindings:

I was just playing with the keybindings for getting the array position 
and length of the mouse selection from the window, and I find it 
wonderful. It was almost effortless to figure out how to assign a 
different keybinding to each track in the window (via [route x], [route 
y], [route q], etc....] I am curious, however, why I cannot see the 
contents of the packed message coming directly out of the [route] 
object. Common sense would tell me that the output would be a compound 
messsage of position and length, but a [print] object still only gives 
me the key event, and not the numbers. Why is that?

best,
d.


-- 
derek holzer ::: http://www.umatic.nl
---Oblique Strategy # 89:
"Imagine the piece as a set of disconnected events"