@grrrwaaa
First of all, thank you for all your Max involvement over the years. Brilliant.
I have a feature request, and Iām not certain of itās feasibility but here it is:
Iām making a syncable delay, which turned out to be relatively simple BUT I would like to be able to change the pulse-checking timer to listen to 48, 24, 8, 5, 2, and etc PPQ, all the way to a single PPQ. Iāve implemented a āhow many samples per pulseā bit of math which I forward to the Delay object and it works great but is currently hardwired to 24PPQ.
The thing is, Iād like to have an on-screen parameter option that is NOT Float. If I only have two options, in one example āis the delay free running or is it clock syncedā then I have to scroll through the at least half the length of the parameter value, 1000 decimal places (on the Patch) to get a simple 0/1 or 1/2.
FWIW, I did set āparam FreeSync @min .001 @max .002ā and then multiplied by 1000 before a Selector which works for now but is ham-handed.
Is there a way to set Oopsy screen-only parameters to be Zero or 1 integers or 1 through 8 for my delay clock division/multiplier selector?
If not, Iām happy with my .001*1000 workaround, but it doesnāt play well with the knobs/CV
So, essentially the request is for some parameters to be forced to integer values? [param cv1_int_mode 1 @min 0 @max 8] etc? [param cv2_int_enable 1 @min 0 @max 1] etc?
Amazing.
Yes.
Maybe youāre still reading my mind and are coming up with a way to not only implement external buffers but also to save them to SD card. The ability to turn Daisy into a recording machine is enticing, maybe even four channel wav files mayyyyybe?
Iām freekin inspired.
It should be alphabetical based on the gen~ object names. To give a name to each gen~ in a multi-patch, add an @title argument to the gen~ object, e.g. [gen~ @title program1], [gen~ @title program2] etc. would work.
āController pickupā
Little help here, having an unsuccessful time of getting a classic āMIDI fader/knob pickupā thing working. Brain melting on a Sunday morning.
Simply put: Trying to make an Oopsy for the Field wherein the buttons bring you to different āparameter pagesā for the knobs to manipulate BUT donāt want the knobs to auto-dictate the values until they are turned past the current value of the parameter, in a classic MIDI controller mode. This way I can have an oscillator on one button, ADADSR on the next, filter controls the next, etc. BUT only want to pass the value of the knobs on to the objects if the knobs are passing (or near?) the last current valueā¦ I think you get what I mean, itās a āstandardā on some midi control schemes and one that is built into Ableton āMIDI Pickup Modeā as an example.
To tell if a knob has āturned pastā a certain value, you can just compare them and see when it changes:
[param knob], [history value] => [> ] -> [change] -> outputs a trigger whenever the knob crosses the value.
For everything else youāll need triggerable logic states. Every time you need a state you probably need a [history] object to store it. You can whip up a latching logic state (one trigger input sends it high, another trigger input sends it low) by looping a [history], [and] and [or]. The and and or 2nd inputs are the triggers to open and close the state.
You can use one of these to know if you are in a particular mode, and another to remember if the knob has passed the stored value for that mode.
That can be fed into a [latch] (a track & hold operator) to feed the knob value through to the stored value for that mode.
(Actually you could reduce the number of history objects by having one history store the current button-selected mode as an integer value, which might be simplerā¦)
@grrrwaaa
I know Versio support is forthcoming but is Terrarium being added also?
I feel like I could problmaybe write that in myself, if need be, but Iād rather not
@as-her
As far as I can see Itās the same realm as Cycling74 licensing. Soā¦ until you make $200,000 with your Gen~ exported code then you are good, as far as money goes.
Honestly I need to re-check the licensing for this specifically but as standard practice itās good karma to attribute code snippets where applicable.
Iām sure Graham can clear this up in a jiffy and Iām just wasting forum space.
As far as your other point goes, YES we need an Oopsy forum header aside from āIntegrationsā because I imagine there will be an increasing amount of activity moving forward this year.
sorry if this has been brought up already, but is there a way to incorporate buffer objects? Apparently, Oopsy doesnāt allow buffer object. Also not sure on how to access sd card files?
Any ideas?
