yeah i seen that. the only thing i dont lilke is that it cuts them into random order.
but maybe i can edit the patch to keep it from doing that?

i have seen hardware dj mixers that output a fairly accurate LED bleep in time with tempo - and i very much doubt they are doing any sort of spectral processing. would be cool to find out how they do it.

@hardoff said:

i have seen hardware dj mixers that output a fairly accurate LED bleep in time with tempo - and i very much doubt they are doing any sort of spectral processing. would be cool to find out how they do it.

huh? wrong topic?
not trying to be rude but i'm not sure why you said that

The difficult part of a good beat slicer is a circuit that can accurately find where the beats are in the audio. It's spot on topic. But alas the DJ mixers are finding the peak signals, which isn't the same as accurately finding the starts. The more I think about it a two pass solution using [bonk~] looks the best.

Actually they are doing spectral processing of a kind... simple narrow band analog filters

@Laserbeak said:

@hardoff said:

i have seen hardware dj mixers that output a fairly accurate LED bleep in time with tempo - and i very much doubt they are doing any sort of spectral processing. would be cool to find out how they do it.

huh? wrong topic?
not trying to be rude but i'm not sure why you said that

months later now i get why you said it. :P
ok anyone make progress with this? hehe? i'm back i had some family issues and had to take a break from a lot of things..

@obiwannabe said:

the DJ mixers are finding the peak signals, which isn't the same as accurately finding the starts. The more I think about it a two pass solution using [bonk~] looks the best.

what do you mean by two pass?

Two pass is where you scan through some data or code twice, first to build a list
of markers/tags, and then going through the data again applying some function which
uses the tags, like building an index. Because [bonk~] acts on a signal, not an array, one would need to store the sample in an array first then read it out with [tabplay~]
through [bonk~] to create a second table of markers. That's a roundabout kind of way to do it, far less elegant than just operating on the data in the array, but as we have decided we don't really have any good feature analysis tools that operate on stored data in Pd. Does that make sense?

definately more than it did before obi. but what about aubio? what do you feel about that? and trying to figure out how it was used in freecycle? that sounds like a way to go as well. to be honest i dont really care what way we take as long as we take into consideration all available paths first. cause then we might know what's the best path.(?)

Hello. This beat slicer breaks up your beat into however many pieces you specify, and then you select piece piece you want to play.

http://mccormick.cx/viewcvs/*checkout*/s-abstractions/s-samplepiece~.pd

We were discussing this patch before here or on the list, it's the fixed interval slicer, a nice neat implementation Chris, but it won't help you in those cases where the beat loop
is either incorrectly trimmed at start/end or is not perfectly regular (like swingy dance beats), I think the goal is still something like recycle/freecycle with the ability to output
a groove list (timings between beats) and write the chunks of audio as separate nicely enveloped files. What looks interesting is an "aubio" wrapper for Pd which can "search" an existing audio file on disk for features.

@obiwannabe said:

What looks interesting is an "aubio" wrapper for Pd which can "search" an existing audio file on disk for features.

that intrests you?
cool so should we look more into that?
think im gonna join his mailing list and stuff.

Yeah, good idea, do some research. I really think a program that operates on files
would be so much better. Anyway, here's a quick tutorial I did on [bonk~] for beat following. http://www.obiwannabe.co.uk/html/music/bonker/bonker.html

cool lookin at it now

i've got a patch that analyse a sound with fiddle and records the events into an array

it is still a draft i want to make it an abstraction after

Human Koala

http://www.pdpatchrepo.info/hurleur/analysisRythm.pd

ok,
i havent really gotten into the gui side of PD yet and i hate it cause it confuses me when it comes to seeing what is going on in the patch

i guess i could just download the patches but it feel like cheating and i wonder how much i would really learn.

just gave a close look at it and it doesnt look that complex but i wish the tutorial was a bit more detailed as to how and why certain things are connected to bonk....

ok ok so i'll download the patched and rev. engineer or something

ahh very interesting tutorial.
how to get bonk to read sounds from an input and then it maps the input to a certain value and returns it whenever the value is replayed.

well the sequence i had in hydrogen had other samples in it that i did not set bonk to learn. but everytime they played bonk output a certain value(i did notice a different value once or twice in the 5 minutes i let it play) how did it decide what value to output?

@Laserbeak said:

ok,

i wish the tutorial was a bit more detailed as to how and why certain things are connected to bonk....

Okay, thanks. I'll try and add that sometime, I didn't say much about the bonk~ params at all did I, hmm, well because theres quite a bit to say.
I would try just getting it to work with some break loops or something to start with.
I think Koala is suggesting that the array writing part of his patch could be modified replacing fiddle~ with bonk~ and we would have most of a working beat slicer.
Have a look, I'm a bit busy this eve.

ok i'll give it a try. thanks for the tutorial btw. and thanks hu_koala for helping out. will check it out soon

@hu_koala said:

i've got a patch that analyse a sound with fiddle and records the events into an array

it is still a draft i want to make it an abstraction after

Human Koala

uh oh time to learn some french