Is the output of edge~ somehow different to a bang? The attack of my kick sounds weird...

rosafell's icon

Dear Max community,

I'm really confused: I patched a kick synth which is in a sub patcher. If I trigger it with a bang, it sounds really nice. But if it's triggered by the output of edge~ (which to my understanding is just a bang?) it's sounds really different. The attack of each kick is different, it has this phasey, clicky quality kind of like a free running osc. My first guess was that multiple bangs come in quick succession. I know that's not the case, but this is a bit what it sounds like.

Now the reason I'm using edge~ here is because I wanted to do some sequencing with signal objects, like a subdiv~ going into a what~ which is then converted by edge~ into a bang.

To make things even weirder: It only happens with my kick synth. But I'm stuck looking for a problem with this synth, as it works perfectly fine unless I trigger it with edge~. Therefore I won't go into details with this kick synth to avoid making this post unnecessarily long.

I searched the forum before posting this, but all threads regarding edge~ problems referred to edge~ catching the start of a phasor cycle. I appreciate any kind of help or suggestion.

Source Audio's icon

edge~ can sure produce multiple bangs.

insert print or counter to see how many.

try to filter input to edge~, or insert onebang with some reset delay

at output.

rosafell's icon

I did both things to check this before posting actually. It's really just one bang coming from the edge~.

rosafell's icon

Here's a patch containing the kick synth with the described trigger options only.

Max Patch
Copy patch and select New From Clipboard in Max.

rosafell's icon

oh dear, I think i solved it. I had a larger I/O vector size than signal vector size: 256 and 64. Now with both set to 64 it seems to be gone.

Source Audio's icon

no strange sound here.

recorded kicks are exactly same no matter if triggered by edge~ or not

rosafell's icon

Thank you for checking this! I think it was all caused by my vector size setting. Now that I set both to 64 it's gone.