Richard wrote:I'm not sure I understand what you mean here. Generally speaking, all editing in a synth should be realtime and instant, so that you can immediately hear what you're doing - and this is exactly how the Wavetable editor works.
Ok, I'll try describe it in diferent way.
Imagine you have some wave, and want make it retrace it with segment tools. Maybe not whole wave but some part. It is possible because when you hold shift, it snap segment in to wave path. And now imagine you want move segments or rearange segments in different way, but still want retrace wave path. But due to Segment Tool change wave in realtime you can't because wave is redrawn by Segment Tool and there is no more original wave. Therefore it need some button where user change Segment Tool behavior to not change Segment Tool wave in realtime. And now he can retrace wave with Segment Tool and make further editing until he is not satisfied.
As I thinking now, you have right it should change wave in realtime to hear changes, maybe better will be "bake" or hold a wave in to some slot (graphical layer) or memory (each table can take one wave and load existing wave) and with Segment Tools you can do what I was describe above, and it will be in realtime.
That means each table will have second layer where user can save / load wave in to this layer. But it will be as for reference for segment tools and others (that means wave in second layer can't be changed, it can only load waves from file or "bake" wave from current wave in table). If user turn on this second layer, Segment tools didn't change second layer in realtime and when shift is used, it will snap wave from this second wave layer. And can convert wave from second layer in to Segment Tool. Second layer wave can be in different color to be recognize.
Hope it is more clear now.