Details :

I set up my guitar/pedal smartphone app to read gyroscope values (x,y,z) and bend (turn the knobs) on preset pedal-effects, ex. gain, feedback, delay, pitch etc. Sort of a 3-d tremolo bar effect yet for any parameter I want.

That was all good and well and works great. However...

I am attempting to trigger a calibrate function/subpatch:

when the toggle is on it reads the x,y,z signals,
when you turn it off it triggers a [sel 0] and it sets the current values, ex [v curX]
which are then used to center the pedals on 0.5 (the center of my mobmuplat knobs)

So you turn it on, move your guitar around until its "centered", then click off and it stores those values and calibrates the incoming x, y, z accordingly.

I worked on this for about 8-10 hours and couldn't get it straight.

My smartphone rotates and sends out a signal (gravitationly based) for x y and z in the range of -1 to 1

My knobs are in the range of 0 to 1 with the middle at 0.5 (which is where I want them and apparently not as trivial as I thought).

I need to offset the curve (-1 to 1) so it "rests" around [v currX] etc values and thus is centered around the 0.5 of the knob.

How do I do that?

meaning how do I:

given an initial value, a, between the range of -1 to 1, set it so all future values between -1 and 1 rotate around that set/center point?

Thanks for your help.

I am very excited to get this done as I think it is way cool feature/effect for my rig.

peace. Look forward to your help.

-svanya

Hi
Scalar-knob is a graphic knob overlaying a Vslider
Thanks to @whale-av for the dirty tag in [donecanvasdialog <args>, dirty 0(
and @Greener for making up my mind not to bother with fonts as graphics
Cheers
Balwyn

scalar-knob.zip

I am trying to Vanilla-ize my PD-Extended patches, and for the most part, it's going great. But I miss "knob," and I can't find a suitable replacement.

I've tried moonlib/mknob but something is unhappy... perhaps related to the PD-X warning about moonlib on 64 bit systems? Anyway, I can't adjust its properties with everything barfing.

I can't find flatspace in Synaptic, in order to try flatspace/knob. I just installed deken (finally) but nothing comes up for Knob or Flatspace.

Does anyone have any suggestions? Basically, I want a nice visual correlation to the knob on my Korg Nanokontrol, for my less PD-savvy (so pretty damned unsavvy) musical collaborators. Guess I could use a really squat HSlider... but I like Knob.

By the way, I'm running KXStudio/Ubuntu 64bit. And I wasn't able to get PD-L2Ork working either (now I've forgotten why - some unmet dependency).

Hi there,

I'm trying to make a nice gui using knobs surimposed over an image loaded by [image]. First I noticed (long time ago) that a knob created before the [image] will be in a layer under it and becomes invisible if placed where the image stands.
My workaround is creating knobs after the image. But if I want a 'two-state' image, thus refreshing the latter the knobs disappear forever.

Is there a way to handle background/foreground plane numbers or something to set my knobs (and other elements) 'always on top' ?

Thank you.

Nau

hi guys! so i've had an oxygen8 for a few years now and i see them everywhere, so i'm sharing this handy little patch i made.

basically you're stuck with 8 knobs, and two sliders (modwheel and data entry). all this patch really does is takes the keyboard's input, numbers those 8 knobs and 2 sliders in sets of 10, and lets you switch between those sets with the hradio for up to 120 different controller values. the key input is passed straight through so even when you switch between various controls you can play the keyboard consistently.

even if you don't have an oxygen8, this patch will give you a little selfcontained set of sliders that you can use as a midi controller... so it's still useful for when you're not at home with your keyboard, or if you don't even have one.

basically all this patch does is take those 10 controls and lets you switch between 12 sets of them. it's useful for me in ableton so when i need to map more parameters than i have knobs for, i can assign more, and the numbering system is much easier to stay on top of than the default control values for those knobs (it's like 17, 80, 74, no consistency it seems).

on linux you should be able to jack the keyboard to pd's midi in, then jack the output to wherever you want. i'm currently on windows and i select usb keyboard in for input, and loopbe for output.

the numbers do nothing but change when you switch the hradio - the sliders are the corresponding controls (with the mod wheel as slider 9 and the data entry knob as slider 10).

come to think of it i don't think i tested the pitch bend wheel, i've been using this patch almost entirely for parameter controlling and not playing the oxygen8 notes at all. [notein] is patched directly into [noteout]

any questions/comments/ideas please, post them. this is a real quick patch i put together that worked almost better than i wanted it to but it can be very expanded upon. i was going to add symbols so you could tag/name all 120 controls but i was having trouble figuring out a way to store them and recall them, and send/receive to the symbols... so i just scrapped that.

basically all i do is make a tiny pd window and make [SCET], and just have that sitting at the bottom of the screen under my DAW (in this case ableton).

i haven't run into any conflicts yet for the most part but it's possible the controller numbering system might conflict with certain apps/synths/etc.

cheers guys!

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

Yes, I already use something like midi yoke now. It is the standard osx midi routing software called IAC.

I forgot to mention in my question that I use one IAC output port to send signals from the PD patch to Ableton. In ableton I route signals from this IAC port to my MIDI outs (connected to the machines).

The other output I use to send signals to my controller, so that when I change the parameter of a knob I can send the current value of that parameter to the knob of the behringer (when I turn this knob the value doesn;t jump but starts from the value it is actually on).

This liimits my possibilities, I want to be able to filter out signals for certain machines. But now I can only use one actual midi output, The IAC bus.

The nice thing about PD;s midi controller interface is that another midi output is a different midi channel. So when I could have 4 midi output possibilities it would enable me to press a button that says to a knob: send to channel 17 (channel one of the second midi output device) instead of sending to channel 33 (channel one of the third midi output device).

I hope this is possiible. I think it actually is, because there are four midi inputs available.

I have tried this with the electribes before. The problem is the electribes use the midi control change messages a little funky. From what I remember (I got busy and never actually finished the patch) they send 2 messages for each knob move, one to identify the knob and one to identify the value of the knob. This makes the whole thing a little more complicated then it would be otherwise, but on a good note it looks like it differentiates what it sends based on which sound is actively selected (Example. Synth 1 Low Boost sends a different control then Hi-Hat low boost). This means that if you get it working properly you could potentially have 78 different knobs or so to play with.

Here is a link to the midi implementation.
http://www.korg-datastorage.jp/Software/MIDIImp/ER1.pdf

I will be working on this again but I don't think it will be anytime soon as I have too many projects at the moment.

I'll take another stab at a knob.

check this one out. You can send it [label $1( and [background $1( to change the color, and the knobs work much better. Still eats way too much cpu.

http://www.dafe.lukifer.net/pdpatches/crazymachineredux/knob.pd

Still needs to:

autoresize eg. [knob 100] for big knob
eat less cpu.
etc... what else?

I like that track, kept me interested and made me smile, and when it finished I wanted to listen to it again - I've listened to it about 5 times this evening. Good work!

I've been trying to make similar sounds. I'm working on doing more live stuff with Pd, it's mighty fun, I can spend hours twiddling with midi knobs making freaky noises. I think I spend too much time fiddling with the knobs and not enough time enhancing my patches - I've not got much to show for the last six months of Pd-ing.

At first I was mapping each midi knob to a single control of the patch, but poorly thought out - in one patch I have 4 breakbeats, and I had 4 knobs mapped to the bpm control of each beat - "bpm 1", "bpm 2", "bpm 3", "bpm 4" - and it was a nightmare trying to get anything to sound good with it. Now I am trying to have more useful controls - "master bpm", "second pair/first pair bpm ratio", "pair 1 bpm spread", "pair 2 bpm spread". Still having 4 knobs to control the 4 bpms, but in a more musically useful way. Like a mathematical change of basis or change of coordinate system.

Another way I am trying to make live performance easier is using algorithmic processes - instead of controlling every beat I control aspects of a process that generates the beats - instead of being the drummer and the bassist and whatever else I am more of a conductor or director, controlling "jitteryness" or "density" or whatever. These processes can have a random part, so the live performance takes on a new element of reacting to the unpredictable output.