@dwan Thanks for the help. Unfortunately I still have to bumb up the audio delay to 40ms, but no one will notice that small a delay.

@dwan thanks for the suggestion, based on what you said I tested the patch with increased audio delay which fixed it, so [nbuntil] should work. But I am using computers at university, and they dont seem to have the [nbuntil] object built in. How do i get it?

Each time a big sectoin of my patch is run it causes an audio pop. The section of the patch uses [until] to iterate over arrays and do calculations. How do I stop this from happening? There is nothing in that seciton of the patch which is audio related.

@gsagostinho thanks for the help, that seems like it will work perfectly for my patch thanks.

I want to be able to write the values of a temporary array, into the array that is currently being outputted to the DAC. The way ive tried to do it is:
[phasor~]
|
[tabread~ arrayTemp]
|
[tabwrite~ arrayCurrent]

But it doesn't seem to be working, is there something else i should be doing?

That seems to have helped thanks.

Rhythm prototype.pd

I want to convert a simple array of note durations(in multiples of beats) to an array of volume values based on ADSR. But it crashes PD, obviously there is an infinite loop somewhere but i dont know where. Would someone mind having a look at it?

Okay so I dont know whats wrong, but basically I cant manually make extended objects, I have to actually find their reference, and then copy and paste the objects from that.

I am using Pd extended but it doesnt seem to recognise tabset. Thats okay though, because if Pd interprets those messages as arrays then I can use them easy enough, I was just confused because I wasnt sure how Pd handled those messages in the first place.

Thank you a lot for the help. You are a life saver.

Ive had a look around online and cant seem to find info on how to use bundles in PD and have come to a blank. I want to be able to write the following message to two different tables. They are two different messages.

print: /rhythm 2 -1 -1 1 1 1 -1
print: /melody 0 1 1 0 0 0 -2

Can anyone help me do this?

Thanks for the reply,

The bangs from the trigger are going to two different number messages. Such that number X is sent to the rightmost inlet, THEN number Y is sent to the leftmost inlet. At least thats what i thought i was doing. I worked out a way to control the patch by changing a different variable so im not sure how it was set up before, but i must have had something connected wrong. I just tried to control Mod as i described in an empty patch and it worked as expected.

Thanks for the tip on counter though, it helped me clean up my patch a bit.

So right now ive set up a counter, connected to a trigger. The trigger first bangs a number message (which is connected to the cold intlet of MOD) then sends the float to MOD. But this setup doesnt change the MOD at all.