SirSickSik Contributions

#278

Sorry,I will use yours (native...) :slight_smile:

#279

how to add active/unactive option:
it's pretty easy, just embed the module and enter for both the K-rate and A-rate code:

if(inlet_active){
"code"
}

for the k-rate code, if you see a "int32_t" or "float32_t", these need to be added to the "local"-code
to finish it, add a bool pin and call it "active".
if you still don't understand, take a look at one of the modules while taking this text into account..

about sound clicking, I didn't really notice and even if it is the case, it should be easy to make a small ducker that mutes the sound for a couple of milliseconds if necessary

#280

ps. about the tableOsc,
you can also just make a recording with several of your favorite oscillators, morphing them to anywhere and then use this recording to play/morph through selections with the tableOsc.
I'm now experimenting with the polyTableOsc (4-voices in one oscillator) and it works like a charm without any glitching/bleeping.

#281

NEW MODULE

"qtsLFO"

four tempo synced sine LFO's with multiply, divide and octave tempo and phase offset control (internal and external)

#282

trying to make a new control system to enable multiple parameter control with just 4 knobs and a couple of buttons

table multi controller.jpg1498x859 342 KB

#283

Check this Modular thing controller subpatch. It has got two layers, put is is pretty easy to expand. And it works properly, with "soft take over". But making som dedicated objects with hook etc. would be awesome, and probably more DSP friendly.

#284

my modules automatically update the right way. if you switch over to another destination, it updates the knob to the newly chosen location.
now I'm building-in preset-ability and I'm thinking about adding a function generator, though that last piece could get it a bit too complex/big for the simplicity I want..
also, as you can select which instance is the receiver, you can add up to 32 receivers.. that's 32*8 controls :wink: (though you could change that in the code to even more receivers)

#285

Not sure I understand that. The patch I made, has got hellcores hookmod, which works with GPIOs. The regular hook object doesnt, only works with dials. The knob only takes over when you turn the button to the setting you set to it before you switched to the other layer.

Probably same way yours work.

#286

How is the DSP load with your objects?

#287

3%, but the reveivers aren't connected to anything

#288

but anyway, the way your patch could use this module is to be able to control anything with the joystick or whatever knob you choose, using buttons to switch between receiving modules and selecting outputs

#289

I think I'll just build a new one from your objects if you put them in here sometime.

But yeah, good idea to keep the joysticks destinations "open". You mean joystick can be assigned to any destination that the other knobs are assigned to?

#290

you can connect any control to any parameter, so you can make a controller for your synthesizer with lots of different styles of controls and you just use the one you like for that parameter..

#291

Sounds pretty interesting :slight_smile:

Would be awesome with an example patch for these, how to set it up etc.

#292

Btw, do you have some kind of smoothing for the GPIOS inputs implemented into the objects?

Or does that have to be added with an "external object"?

#293

I haven't used those inputs, it's more of a general routing module. so that's where your module comes in
or maybe it's an idea to combine the modules once it's finished?

#294

Yeah, first I think I just need to try the ones you have made and understand how they work , I guess :wink: And then find the best combination :slight_smile:

#295

NEW MODULES

PATCH

"sendMatrix"
"receiveMatrix"
"dispMatrix"

the first is a module to write the controller value to a table or to get it's value to the controller when another destination/preset/output is being selected
Can be controlled by GPIOS controls using the CV input and button-inputs to walk through the menu

the receiveMatrix reads from the table and outputs 8 signals per module. A selector is used to select which instance it is. (this could even be manually controllable if you want, such as to switch control-values between groups of parameters)

the dispMatrix is a quick way to show which destinations are being selected.

NOTE though, that when two controls select the same destination, the destination will get the valuefrom the last module in the direction of the code. (eg most-right module)

#296

My axocontrol objects have a low pass filter on the analogue inputs. So you could combine mine and sss to get what you want.

#297

I figured offloading the dial management to an arduino would allow me to do more with my axoloti.

I have endless rotary encoders up dating a number of variables on the arduino. Which send via midi if they change. It does mean I am going to have a lot of cc receive objects in my patch tho.