greets all.

I am having a fundamental brain fart moment. I am creating a looper that i want to record the first loop into a delayline ( and if directly into a table is better, please let me know, and why, and i will gladly go that route) where i will use the [realtime]object to get the length of the relevant recording, then use that to resize a table and loop it with tabplay~, but the whole thing has turned to gibberish.

at the root, i just dont understand these objects or their functions properly yet. any insight into what i am doing wrong, would be greatly appreciated. my hope is to create a counting function to go along with this patch (which i plan to have 4 syncronized copies of) that will only access the [realtime] function on the 1st go around going into the delwrite~. there will eventually be 10 tables and 10 tabplay~'s all set automatically to that length. as the counter abstraction counts up, the count will access the table/tabwrite~/tabplay~ combo for that number, up to 10. an "undo" function will mute down this list of tabplays and redo will unmute, but once it returns to 1, it goes back to the delwrite~ and creates a new loop that determines the length of all the others.

before any of that can happen, i really need to get a grasp on creating dynamically resizable tables and accessing them instantly.

sorry for such a noob question but this is my first foray into the audio objects. I've been swimming down at the midi end of the pool.

thanks in advance,

Onyx

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

ok, i changed the guts of the patch to create a master control section that will use vline~ to play individual tabread4's in what will be individual looping abstractions, but i am getting wierdness. (file attached)

it worked exactly once. the tabread4~ was playing it but on each repetition it was reducing in pitch by a half step then eventually it just didnt make any more sound. now it doesnt work at all for some reason. i dont know if my vline~ syntax is correct. sorry for the super noob questions.

thanks in advance.

Onyx

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

at the moment, you have your vline set up like this:

[0, 1 tablesize(
|
[vline~]

however, what [tabread4~] needs is:

[0, tablesize time(
|
[vline~]

for normal playback speed at 44100hz samplerate, time will just be tablesize divided by 44.1

Also, here's why i think it works ONCE but then messes up:

see how on the right hand side of your patch, there is a [timer] object next to the yellow start bang, and then a number box under that [timer]?

well, it has 2 cables coming out of it. I won't go into too much detail about how the execution order works, but the safest thing to assume is that if you take two cables from one object, then things are bound to go wrong. In general, you should NEVER take 2 cables from 1 object, as you really have to assume you don't know which cable will get sent the message first. so, you should decide which order you want, and then use [t f f] to make sure the order is forced correctly.

yaaaaaay!!! it all works! I knew it had to be syntax. and now i have added many trigger objects and cleaned up my cabling. thank you to both of you! i feel like i may not embarrass myself saturday night. cheers!

is that problem related to "Dynamic table resizing misunderstanding"

please start a new thread if you have a different problem

i wanted to share the "in progress" solution i've come up with for my multi layer looper.

I used the poke~ based sound on sound looper that Katja uploaded last year, but made it get its index dynamically from the vline~ that gets generated from the first loop length created. this allows each loop to be synced. and there is one record button so that clicking it once allows recording to start then again to start looping then on the second loop forward, it will do the sound on sound looping for each layer. to set the loop length for all loops, recording must start from the first loop.

the "undo" will mute all layer higher than itself and redo will unmute them. clicking record at this point will clear the table of that layer first before recording into it. my loop layer selection mechanism is really janky right now (it will sometimes mute everything, THEN, mute the proper layer) and although using [mod] allows me to keep up with looper position, that it doesnt stop at loop number range boundaries is a problem i will work on this week.

any insight is appreciated but i just thought i would share the results here for anyone who may find it of use. thanks Katja, for the sound on sound looper patch. it came in really handy. (the looplayer.pd will be in the following post as i dont know how to post two attachements with the same post.

onyx

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

here is the looplayer.pd patch neccessary for the patch to run

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

testing multiple attachments

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

testing multiple attachments

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

ok, to attach more than one patch to a post, it's not completely straightforward, but you can do it. The attachment options says:

"To add more attachments to a post the user needs to edit the message"

so, just make your original post with one attachment, and then edit it to include more. For the moment it looks like 8 is the maximum - if you need any more than that you'd be better of making a .zip file