Hello!

I think this topic solves your issue:

https://forum.pdpatchrepo.info/topic/12076/question-about-the-sample-rate-obj

@ben.wes I ended up writing a few externals for the "gen~" codes I wanted to translate.
Looking for a pd-vanilla way was quite instructive.

I guess some pdlua script would have worked ?
If so, I think a puredata vanilla "scripting" object would be a really nice feature...

@ben.wes your graph is a pdlua script of yours ?

@ben.wes neat piece of code!

I'll try it, and also learn from the way you graph the signal ( it must be an else object? )

@whale-av Cheers !

I never knew this topic would go that deep...
I'll try and improve my onset detection / detrending, then see if I need the counter to be that accurate ( my guess is "no" )

@lacuna

Well, I think the counter being off isn't an issue, in the end it's off for the 4 mics and I end up with correct inter-onset values. ( I hope so )

The patch evolved and has fewer uncertainties ( the screenshot I posted in the previous thread was wrong in many ways... )

I gave up using Lowpass to filter onsets, I went on trying to reproduce some "Gen~" code with "fexpr~" ( as I understood a few things about expressions reading all the different answers I got on the forum.

I got better results ( I've been provided a 4 tracks recording, and a list off all inter onsets produced by the max patch so I can compare ) I spent a few hours trying to have the exact behaviour of :

in a fexpr object.

Question, does anyone think this Gen~ code can be transposed to fexpr~ ?

@ddw_music ,

Maybe ok for one second

I count only 256 samples, I assume it will be precise then ?

@ddw_music , even better, I guess this would be more cpu friendly ?

@jameslo

I try to be precise when asking for things, but when I post I've been struggling for a long time, smoke is coming out of my ears, I end up with confusing messages....

Thanks a lot, again!

I just had to invert things:

fexpr~ if($x != 0, ($y + 1) % 44100, 0)

beautiful.