Forums > MaxMSP

Totally n00b question.

March 29, 2014 | 6:56 am

Hy Guys,

 

Working on a synth, just added patching matrix system, would like to control the main parameters with LFOs.

Example attached.

The problem is that its not working…

 

The knob controls the pitch of an OSC, from -24 to +24. I would like to control the LFO this pitch aswell, with +/- 24, but like this :

If knob is 0, then with lfo control, the out should be +/24…if the knob is 12 then the LFO controlled out should be -12. +36.

What is the problem?

<pre><code>

– Pasted Max Patch, click to expand. –

</code></pre>

 


March 29, 2014 | 7:46 am

the problem here is that the [+ 24]‘s right inlet is a cold inlet : won’t trigger the output
(see max tutorial 6 for more info)
yopu need [t b f]
<code>

– Pasted Max Patch, click to expand. –

</code>
not sure if you wanted to have floating ponts there. i added them everywhere just in case.


March 29, 2014 | 2:47 pm

Thanks Vichug…
I should sleep :D

Anyway, a new problem pops up.
If I "unroute" the LFO, the osc’s freq is not set back to -24. +24.
It seems its multiplied the LFOs last amount…


March 29, 2014 | 4:07 pm

hmmmm, if you ‘unroute’ the lfo, what do you mean ? ..


March 29, 2014 | 4:12 pm

well i think i see what you mean. You must find a way to have a 0. as last value of the lfo (=right after you unroute it). Or maybe a 1 (before scale, 24 after scale) since there is that initializing value in your [+ 24] box
tl;dr : find a way to reset the inital value of [+] box’s right inlet when unrouting lfo

<code>

– Pasted Max Patch, click to expand. –

</code>


March 29, 2014 | 11:01 pm

Sorry about I wasn’t clear.
Im using a matrix control object with a ruter object to connect the lfos, the problem starts when I "unroute" the lfo from the oscillator :)
Will check your patch, thank you!


April 4, 2014 | 1:14 pm

I still can’t solve the problem.
I’ve checked the BEAP oscillator, and it works great, it "re-set" the osc freq value after disconnect the LFO…
Any tips?
Adding a VCO reset button is … very cheap :(


April 4, 2014 | 1:29 pm

I’ve attached the VCO patch…absolutely no idea how to solve this :(

– Pasted Max Patch, click to expand. –

April 4, 2014 | 6:03 pm

this is totally normal that it does not switch back to whatever default value when you disconnect one of the modulators. you will always have to implement such things yourself. :)


April 4, 2014 | 9:48 pm

Yeah :)
A "silly" idea,
What if I replace the router object with a matrix and use signals as control messages?


April 5, 2014 | 1:43 am

hmmm, maybe again jsut a priority order problem ?

– Pasted Max Patch, click to expand. –

April 5, 2014 | 1:56 am

Thanks Vichug, will check it later.
I think I should put your name into the thank you list if I finish this project.

The main problem is that the + object holds the number from the inlet, actually if I put a flonum object right after the inlet, it holds the last amount even if the modulator is unrouted.
That is why I toughed that if I use signal as control it will fall back to 0 after unroute it from matrix…or not:) have no time to check it right now:(


April 5, 2014 | 5:05 am

matrix solved the problem, so I have to re-write the controller patcher from 0. :D


April 5, 2014 | 5:16 am

what you say sounds like a totally solvable problems, with the right logic.. but with matrix it’ll probably be better anyway ! still you might want to comprehend well that matter, for future reference ;)


April 5, 2014 | 6:03 am

Well, it works.
The problem was :

LFO -› router object -› OSC tune

The problem was that if I "un-route" the LFO in the matrixctrl, the last amount of the LFO was still on the the inlet of the OSC (and in the + object.)

When I use the same method, but with matrix object, right after the un-rote, the outlet of the matrix (so the inlet of the OSC) is 0.

It needs a bit more CPU power, but will clean up the patchers, I can live with it :D


April 5, 2014 | 7:17 am

:)


Viewing 16 posts - 1 through 16 (of 16 total)