Looking into this and seen loop start end on a sample abstracts. Is there an obvious example I’ve missed for this?

So for a sample, “one two three”:
Holding a note could go one two two two two…
And note off could go three.

Thinking I need 2 delay reads to allow fade outs and ins to avoid gaps or clicks when looping which is just about timing things right. Just looking to avoid reinventing the wheel if I can.

Cheers.

Thanks so much. One t f f and all is well! Now on to the next problem

This works perfectly on the Mac (press a note and increases it's value in the array), But when running on linux device it is holding on to last note value so increasing the wrong value on 1st press. Seems to happen on value 1. I'm a bit confused.

Do I need to force the process order more or is there a schoolboy error in this small bit of code?

Thanks for any help or pointers!

What about this? cz-osc_.pd

Great patch. Worth uploading again!

Yeah, this works for me http://www.pdpatchrepo.info/hurleur/cz-osc~.pd

This is the saw for example:

Will try and crank that...

Thank you - that is definitely beyond my current PD knowledge!

My error with pow as that is possible outside expr. I'm sure it wouldn't work yesterday when I tried.

It's this patch that I'm fiddling with (works lovely in normal PD): https://forum.pdpatchrepo.info/topic/5992/casio-cz-oscillators

I have an expression 'heavy' patch I was hoping to convert via Heavy to Owl but it has fallen at the first due to the use of expr and expr~. I was wondering if anyone could help with the first few and then I could try and get my head round the others.

expr~ ($v1<.5)$v1; ($v1>=.5)$v1 splits waveform in two.

expr pow($f1, 1.0/3) power without pow?

expr~ $v1*((.5-$v2)/$v2);(-1*$v1+1)*((.5-$v2)/(1-$v2)) is totally beyond my little brain at the moment too!

None of this urgent or anything, just having fun.

Did some better searching today and fixed with a little ramp up an then ramp down at end.

@rjp9 This is really nice patch.

Does the tabread4 in this patch need adjusting to avoid clicking when looping? I've read and tried a few suggestions to get round the clicks but haven't shaken them off yet.

@whale-av Thank you. That works great!

On doing a search this is a great patch but doesn't work doing reverse audio as suggested. Should it work using -1 ( as does for doubling or halving sample rate)?

Nice work! Really like it. Fun to play with.

@dzees

Demux is a gate on specific values if that's what you're after. It's part of Extended, so an external on vanilla.

This is exactly what I wanted and totally failed to search for.

Thanks Gilberto!

Anything "out of the box" that could provide say 3 options for values rather than spigots 1 that's on or off.

For example audio is put through to output 1,2 or 3 depending on value of a gate on the right being 0, 1 or 2.

Or alternatively a Select that acts as a gate for where audio or data is put through.

Think this makes sense?

@seed

Thanks too! I just used the route 1 0 to give an output from one of the toggles. This would not have come to me without seeing this.

Having a productive evening now...

@whale-av

That's awesome!!! Thanks. This patch looks so much better now so I can see what else I'm doing.

And it seems the pipe handles a longer key press event a bit better. At least I think that's what it is doing?

@whale-av said:

multi_fx.pd

Like the cleaner Select method that looks much better.!! I'll use that.

Unfortunately, when you take finger off the key it sends a note event (velocity 0 I guess) so turns it immediately off again. If that makes sense? So it's the 1st and 3rd out of 4 note events you need to capture.

multieffectexcerpt.pd

This will have at least 7 effects that I want to turn on and off with 7 different keys on musical keyboard. Just seems inefficient to have 7 integers incrementing to handle simple on off operation. (I"ve only shown one on patch).

Can anyone recommend a nicer way of doing this?

I'm trying to improve my messy approach to Pure Data so am after advice. I am controlling 8 toggle boxes (which turn on and off an effect) via a keyboard note.

To do this I am currently using, for all 8 effects, an integer increment when the relevant key is pressed, which is then divided by 4, and sent to Sel 0 1 2 3, to get the on event of the key (event 0 and 2). Then sending a Sel 1, or Sel 0 to the Toggle. As I'm doing this 8 times it looks and seems very messy. But at least it works I guess.

Any easier way to do this?