@patrickpagano forgot to mention, that PDs fft objects are also not supported… and there isn’t a way to use fft in gen as well, as the relevant msp objects are outside the gen object. Gen works per sample, so sampling a window for further processing is the first task to solve, besides there isn’t any way further inside a gen object yet.
nice you are experimenting with newer hardware. Did you add a display, too?
Also, i have a bunch of pedals with silent switches. Those are both momentary and toggle kinds. If you want i can open those pedls at some point and find out, which switches exactly are used. Let me know.
Those pedals are for instance the Hexe Revolver, Montreal Assembly Count To Five, Chase Bliss Brothers, TC Electronic Ditto X2…
The Ditto switches have gone through hell – dusty stages, too many dance theatre shows on fog-covered ground etc. – and they still work, though sometimes need Tuner 700 contact spray 🙂
Switches for people who do low volume music and who like to play their stompboxes. That’ll be awesome.
i use a Stereo Memoryman with Hazarai, which has push-to-save rotary encoder for the presets. In fact it isn’t very reliable. When this thing got hit on the top (my bad, i know) it lost its saving function…
Ah, MIDI. Would just be nice to tune a delay, feedback or filter with keys, or whatever other musical function this could have.
Personally i like 5-PIN MIDI, but the smaller modern keyboards usually only have USB.
SIMPLE PSEUDO TRIGGER SPEED LIMITING
The patch below enables speed limiting on trigger generation. Oftenly, when you create triggers from audio signals you end up having too many triggers per time. Even if your threshold level sits right you might get several quick triggers upon attacks in the audio signal. You mostly only need the first of those.
The following code let’s you do exactly that: Have only the first of some fast triggers pass through and only open the gate again after a time you can specify. This code was to it’s biggest part created by Graham Wakefield from the gen forum.
I only added some control elements and a random trigger generator, so that it gets more obvious, what it does.
This should sit right after the trigger generator and has one control: limit.
Erm, addendum. Looked at your gendsp quickly, yes, an envelope would be good. Check out the gen~.7_segment_envelope from the Max gen examples. That’s a very bloated version, but you may minimize it down to your needs.
Might help to wrap an envelope around this then.
Make a 2ms fade out upon trigger, then fade back in quickly. I’d take a closer look at this sometime later, but can’t right now. However, to me it seems again (i had proposed that before), that we should open up a library for gen code snippets somewhere here, so we all won’t run into the ever same problems. The maxmsp gen forums must have thousands of threads about click in glitchy loopers!
Hey Martin, I’d test a beta version right away!
I personally i favor
– more user slots.
– replacing exp in gen with the codebox workaround i proposed here is not an option? Worked fine for me, though it actually might need readjustment for certain value ranges (untested besides i used it in a transpose to pitch situation).
– i have no use for samples myself, other than sampling from live input, which is possible already. Hardcoding sample into code could be sexy for some i suppose. A user Sliderule over at the Patchblocks site developed a cool idea for this including a sample to code converter on a website. Just FYI.
– some guitar pedal manufacturers provide MIDI over jack input things (Chase Bliss), this could be an interesting thing, if only to select patches without having to use the push button, but not just that.
Thanx for the good news!
Okay, dual poti and opamps, that’s what i thought. Maybe my question was a bit useless.
Hi Patrick, everything has to be Vanilla, and a list of supported PD Vanilla objects is here.
expr~, fexpr~ and non signal rate counterparts are NOT supported. (Grmph.)
Long time complaint of mine. I suggest starting with gen very soon, as that gets you rid of a lot of troubles in one go. Gen has a codebox, if you really need to handcode stuff in a similar way to C++.
Martin? Any news about this?
Patrick, actually i didn’t, as pd~ is not on the list of supported objects of the Heavy compiler.
Worth a try, nonetheless. The Organelle uses libpd, no?
Asking, because i also use a Bela, and for that platform official statements indicate, that libpd there runs slower, than Heavy-compiled code. I haven’t tried it, though, again for limited PD object set in Heavy.
My patches get CPU-intense all too soon,
so where’s actual truth about absolute speeds/code efficiency there?
Yeah! (Besides putting more buttons, faders and switches into that stomp box, which i am planning since long, but didn’t dare to do it yet…)
I checked out your patch and to me it seems, that if you had a [slide 16 16] (or bigger values) behind the constant value change of your glitch, you could probably avoid the clicks completely.
pepper, you could connect a switch to the expression pedal input and use that instead of the push button for further functionality. I also belong to the “want more buttons and switches and faders” group, unfortunately the OWL lacks at least one (momentary) footswitch and yet the ability to use the push button led to signal tap tempos, menu levels and such. hopefully we’ll get there.
Aside that, some hacking seems possible.
Thank you Martin, will rewrite this again to also have reverse delay modes. Using the data object in gen one can poke, peek and phasor the heck out of an audio signal without using external buffers in Max. … In some days… going to Istanbul now and play!
I’ll checkout your code snippets above. Is there a way to go to green color as well?