hello!
in pD extended i've been building a couple live performance environs. one is for a guitarist and drummer, triggering kick drum type samples from the kick drum and various signal processings of the guitar. the other for solo work, using cassete tape and guitar, the environ triggers things and has 'effects' banks.

i found the abstraction [scramble~] in the index and got really excited! because i wanted something to chop up and ..... scramble my guitar or whatever. when i applied the scramble~ (including all the message/number box arguments it has in the help page) to the guitar all i got was screaming noise. not in the good way! there seemed to be no scrambling as such, the only thing that seemed t wrk as a command was the pitch change.... changing the pitch of the noise.

anyway, do people know about this abstract?? does it not work well with distorted sustainful noise? why? its interesting, it worked so well with my voice when trialing it in the help menu! maybe theres a trick....

so, is there anyother scrambling/chaos type methods? in terms of building your own what would be the general METHOD. i tried making one using tablewrites and delays and shit.... but not very good!

nope i didn't know about it... looks nice.... but have to test it
thanks

i have an experimental unfinished effect which can reshuffle a live stream
you can feed it as an example with 4 3 2 1 and it will play the input chopped up into 4 parts in this order
1 2 3 4 would mean normal playback just with a delay of some beats

maybe that's what you are searching?

yeah that would be great! does it randomize also? like if the live stream is 1 2 3 4, then the output could be like 2 4 3 1 ... etc!
i want to make something like this, shuffle~ just popped up and seemed like it would do the trick... but maybe not! whats the key pieces in yr patch? tables and delays? or samplerate/ sample hold type things... im an early-intermediate user you could say... haha\

you know i just came across something that is similar to what we/i are maybe talking about:

thanks!

There a vst called supatrigga that does what you describe in a very musical way. Might be nice to check out just for inspiration.

okay
i share it... and you will share good changes or ill make you eat spiders!

as i said its incomplete, it reacts too slow for more than 100jumps/s and i wanted to make it list based... so that you can put into a list like |1 2 4 3( and it does this.. maybe you'll make this next step?

currently it works in 2 modes:
-randoom: every new step a randoom position is taken
-not randoom: it outputs the current position (in the sequencer) and wants you to input the position it should play now/next so it should play back normally (but delayed) if you put the output through a + 0 but its been a while i played with this thing

also it has a sync input with which you can try to sync it to a seq or whatever

but if you stare long enough at this mess you could have found out that by yourself ;p

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

Hey slur, nice patch. Here's a version with the list input you were looking for. I also got rid of the delay when you turn it on. I found it kind of annoying.

http://www.pdpatchrepo.info/hurleur/beatshuffler.mmb-mods.pd

yo! thanks for posting that! its really good to see ways people chop shit up. i love the delay.... quite strange. only had a quik play just now, want to check it out further later...
heres what i ended up making attached, i wanted something really responsive to what happens with a guitar so i used fiddle~ and went from there.... i guess its a pretty glitchy fucked up thing, but it shows you what i wanted to do i think! haha

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

oh shit, i just opened my patch i just attched and theres some things i forgot to change/save last time with the tables.... its not functioning as is.... but its shows the idea!

nice... thought the +1 was necessary
maybe it is... now there is a delay of 1 or blocksize samples

i thought about 2 list based modes:
1. synced to beats
plays always splice(beat-number%list-len)
2. repeat list
goes through the list independent of the current beat-number

you did the 3.
synced + repeat last

i guess the position output in your version is only a left over?
well it could be used as a sequencer

thanks

@slur said:

nice... thought the +1 was necessary
maybe it is... now there is a delay of 1 or blocksize samples

Can't remember what you mean by the +1, but there is probably a delay of blocksize. You can easily fix this by putting the [delwrite~] in a subpatch with an [outlet~] and the [vd~] in a subpatch with an [inlet~] and connect them.

[pd delaywriter]
|
[pd delayreader]

Nothing has to be connected to the [outlet~] and [inlet~] internally, though. This will ensure that Pd draws the dsp graph in the right order so that [vd~] can read from the [delwrite~] in the same block. You have to have at least a one sample delay with [vd~]. It needs it for the interpolation.

i thought about 2 list based modes:
1. synced to beats
plays always splice(beat-number%list-len)
2. repeat list
goes through the list independent of the current beat-number

you did the 3.
synced + repeat last

Probably wouldn't be too difficult to implement. I did it this way to keep the behavior of repeating the same beat when you send it a float and applying it to the last beat of a list that was shorter than the total divisions. Didn't want to fuck up what was there too much.

i guess the position output in your version is only a left over?
well it could be used as a sequencer

Yeah, this is the way it was originally. But I like the idea of having output the beat it is playing back, particularly in random mode. Then use *that* as the sequencer.