Sorry for the confusion, I meant "simple counter with max" indeed.
Actually if you need min and max, just add a constant to the counter output.
It may be a simple solution for what you're trying to do.
Something like:
Rec switch -> from 1 to 0 -> counter -> dispatcher num
-> dispatcher in
maybe you'll need to insert some "wait one cycle" somewhere in the signal path to control the order of the events.
If you want the samplers to play in sync, just put the first one in "loop" mode, all the other ones in "button" mode, and patch the "start play" outlet of the first sampler to the "play" inlet of all the others.
Rgds,
B.
Statistics: Posted by bmoussay — 07 May 2007, 20:20
]]>
I think bmoussay was referring to "Data/Counters/Counter Simple with max.pat". It counts from 0 up to max and then "wraps around" to 0 again. If you want to start at 1, just add 1 to the output.
BTW, I haven't added any counters like you're after in the PunchInLoops, but you could just as easily replace the list of "instances" module with something like you describe, and not worry about the script. In fact, I think I'll add such a function in the next version.
Regarding the script; unless you want to add to or change some of the behaviour of it, the only thing that you need to change within is the NUM_INST constant to increase the number of instances playing, and then recompile the script (Ctrl-F9). You might have noticed that there's also a similiar Constant module that needs to changed accordingly. I'm using the same constant value twice just to reduce the CPU load of the script.
Statistics: Posted by bsork — 07 May 2007, 14:46
]]>
I notice I really didn't explain myself too well. I managed to find at least one way of solving my problem though.
The issue was, and now I'll try and be more specific:
I have a Rec Switch, to start and stop the active sampler. This is all the time sending either a 1 or a 0.
I use some modules (right now I'm using a Selector going into a Dispatch) for routing to which sampler that rec on/off value goes. And after the active sampler's rec is stopped the selector changes to point to the next sampler. For this information i need to use the Out of the Selector, then add 1 to that. My problem was solved when I found the From 1 to 0 Sub-patch. This seems to "convert" a change in value (Rec switch goes from 1 to 0) to a quick trigger (a "bang" like it's called in Max/MSP i think. good name.), i.e. it outputs a 1 and then a 0 immediately after. Before I found this, I was having the problem that my Selector Out +1 module was causing the Selector to "race".
Hope I was any clearer this time around
Anyway, I'm getting along now.
I can see that the Counter sub-patches might be better than the Selector for this purpose. Didn't try it yet. I can't find one called "Counter simple with min-max" though. I can find:
Counter simple with max (down)
Counter simple with max
Counter simple
Where, I wonder, might I find the one with both min and max?
The scripting in PunchInLoops was confusing me at this point, so I'm happy I found some solution without scripts.
Nontheless, I appreciate all of your help immensily. Usine is growing on me!
antwan
Statistics: Posted by antwan — 07 May 2007, 14:04
]]>
To begin with Usine also means browse first with the browser! Many interesting things in it.
Statistics: Posted by Guest — 05 May 2007, 20:04
]]>
Have you checked the simple "counter" subpatches included in Usine, especially the "counter simple with min-max", (I think it's in the "data" folder), these might fulfill your needs.
Rgds,
B.
Statistics: Posted by bmoussay — 05 May 2007, 14:59
]]>
Might you be able to quickly elaborate on this event loop situation I had with the Selector. The problem being that I use the Selector's output to determine where to point next (using a +1 module) within the Selector itself, then the input races all the way to 16 in a nanosecond. I seem to be bumping into that kind of a thing quite a lot so I guess there's some simple/fundamental way to get it right. I hope you understand what I'm referring to
I'm not too good at explaining things yet./a
Statistics: Posted by antwan — 04 May 2007, 10:11
]]>
Anyway, you are right, you need as many samplers as wanted layers.
AND NOW A COMMERCIAL BREAK:
the punchingLoops is similar to Echoplex but more precise in time.
It could also be good starting point.
END OF COMMERCIAL BREAK.
Statistics: Posted by senso — 04 May 2007, 09:45
]]>
AND NOW A COMMERCIAL BREAK:
From what I understand of your description, it doesn't quite fit the bill for what you're after, but I think you maybe will have a better starting point for building your own live looper if you take a look at my PunchInLoops workspace in the Add-ons. I'm working on a V2 that's nearly finished, but some of the V2 patches will have so many wires going everywhere that V1 is easier to begin to "decipher".
END OF COMMERCIAL BREAK.
Ooops, have to get back to work!
Statistics: Posted by bsork — 04 May 2007, 09:11
]]>
I'm trying to build a live looper according to my needs. On a more general level, so far I know this much:
- I need my live looper to trigger it's rec and stop according to sync. This I can appear to be able to achieve by quantizing the rec button (although only to cycle,bar,beat or 8th)
- I need it to be able to record many (let's say preferably up to 20) mono layers or tracks (perhaps with control to each of them, as in mute or level or feedback...), each in sync with the clock but allowing to be of different lengths. . I found the Sampler module has overdub mode but doesn't work for me because sync gets screwed up if the overdub is of different length.
- The currently recorded loop should start to play and loop immediately after stopping of recording
- Could be I'm forgetting some of my requirements
So far I've come to the conclusion that I guess I have no option but to use as many sampler modules as I want to have recordable layers.
I've been looking into the Echoplexx (mono) and the EchoPlex Simple... but neither quite fullfill all of my requirements.
Feel free to through in any ideas/tips to a complete Usine-rookie as I am.
But I also have a more specific question ready:
I was trying to understand the Count Layer sub-patch in Echoplexx (mono) but with no luck so far. Basically, if I indeed need many Sampler modules then I guess I should build this kind of counter, based on a selector, which points to the sampler to be used next. I was trying to have the Rec-button trigger this Selector's select input always increasing it by 1 but I end up with some sort of event loop where the Selector shoots through the Values and that's the end of story.
Helping hand?
Appreciate it.
Thanks.
antwan
Statistics: Posted by antwan — 03 May 2007, 23:08
]]>