Hi there, I've recently created an envelope patch for a project I'm working on, it works fine and draws to an array but the only problem is that I have to wait for the entire sample to elapse for the array to update! Is there some way I can see what I'm doing as I'm doing it onto the array? I've already attempted to hook up all the envelope sliders to a [bang] object, but the issue prevails, unfortunately. Here's my patch:

envpatch.pd

You could use [metro] to repeatedly bang the parameters into [vline~] while you are changing them.
David.

I think the issue is that [tabwrite~] needs to wait for all the values that would fill the table before output its result -- in other words, it needs to wait for the whole sample in order to make a table or array out of it.

Yes, if you metro bang it repeatedly it outputs all of the parameters at each bang, so you have a better idea about whether you are really doing what you want (live)...... woof!.

whale, could you give me an example of what you mean using my patch? I've tried using the metro object to no avail.

@gsagostinho That's exactly right - any ideas?

@Jamestocher Hello James,
Sorry to be so long replying. Here is your patch. I have banged in some values to start, as some of the faders give values outside the range of the array. Also, I have ignored the sample, as I suppose, maybe mistakenly, that you are trying to fine tune your envelope patch. As you are not visualising the sample itself I have fixed the sample length (array size) at 15000, but of course you can change that. I hope it is helpful.....env_array.pd
Of course that was the solution. You don't need the metro bang as you were already banging the whole message every time you move a fader, but you do need the array size set in advance so as to instantly visualise your changes.
When you finally use your patch in anger you could always run this envelope, set to the maximum sample length, in parallel. That way you can always visualise how you will be shaping your samples before they are loaded..
David.