[goodweather]

Hi Puppeteer, hope your are fine!
well, I’m replying in this post as I also don’t have any feedback from my hardware… and the issue is that I don’t remember if I had feedback before.

I’m using 5.3.94 on Windows; Midi Input, Output and Controller are towards my Sub37.
I have a panel with CC and another one where I used NRPN.
Just tested both to check the feedback from the Sub37 to Ctrlr and indeed I don’t see anything.

Any setting that needs to be done?
Any tip to put us on tracking the issue?
Checking some stuff with Midi monitor or MidiOX?

Thx in advance!

[goodweather]

Thanks Atom!

[goodweather]

Hi, I’m still working on it as I’m discovering Ctrlr at the same time. I’m only working on it during w-e (sometimes a bit during the week though).
I had to switch from CC messages exchange to NRPN.
I also discovered errors and missing messages in the NRPN pages of the Sub37 manual.
The panel is almost fully functioning but I’m missing the 6 and 4 positions buttons.
I will adapt the layout now as I will add enveloppe display (this is working in my test panel) and so I know how to do this.
Next step to test is to make buttons moving or switches changing when you do it on the actual synth. I have the impression this has been working once but not anymore. Maybe due to the switch to NRPN? (I have changed the output filter to NRPN on the Sub37 Midi menu 3.3).

@Atom: any feedback on this? IS there something to do to have buttons following the actual physical state? I have seen methods like midiMessageReceived
Then next step will be to output a patch from the Sub37 (Midi menu 3.5 buffer send), to analyse it to be able to rebuild it in Ctrlr and to have a method able to resend it to the Sub37.
Then add a way to read all presets names in each bank and display them in the panel.
So, still some work…

[goodweather]

Hi,
thx for all updates Puppeteer!

TO ALL: please bear in mind that this is the IN DEV version! The idea with this thread was to gather info then publish it as a new version of the “official” thread (official is very bad naming…).

“Official” thread is: http://ctrlr.org/forums/topic/ctrlr-step-by-step-guide/

[goodweather]

Hi again,
to come back on this topic it is worth adding some precision to what Puppeteer explained above…
There are 3 things to consider: the text that will be displayed, the value to test in the Lua code and the value that is send by Midi.

• The text to display (you need to have Text position different than “none”) is what’s come on the left side of “=” sign
• The value sent by Midi is on the right side of the equal sign
• The value to test in your Lua code is the rank of each line starting by 0

On the Moog Sub37, there is a button that indicates the destination of the pitch modulation (Osc1+Osc2, Osc1, Osc2). CC is 88 and Midi values to send are 0, 43 and 85. The destination is indicated on the synth by 2 leds (1 and 2).
The Lua code is used to set the corresponding LEDs ON depending on each button press.

So, for button values I have:
Osc1+Osc2=0
Osc1=43
Osc2=85
(I set Text position to top just for testing purposes, otherwise it is none.)

In the Lua code I have:

function mod2OscSelect(modulator, modValue)

	-- console ("Value: " .. modValue)
	if modValue==0 then
		-- console ("Osc1+Osc2")
		panel:getComponent("ledMod2Osc1Pitch"):setValue(1,true)
		panel:getComponent("ledMod2Osc2Pitch"):setValue(1,true)
	end
	if modValue==1 then
 		-- Send 43 to Midi
		-- console ("Osc1")
		panel:getComponent("ledMod2Osc1Pitch"):setValue(1,true)
		panel:getComponent("ledMod2Osc2Pitch"):setValue(0,true)
	end
	if modValue==2 then
 		-- Send 85 to Midi
		-- console ("Osc2")
		panel:getComponent("ledMod2Osc1Pitch"):setValue(0,true)
		panel:getComponent("ledMod2Osc2Pitch"):setValue(1,true)
	end
end

Checked on the panel and with the synth.

• This reply was modified 8 years, 8 months ago by goodweather.

[goodweather]

Thx for your explanation Puppeteer (and dasfaker) ! I was also looking for this and was sure to find it in the forum 🙂
I’ll add your explanation in the user guide.
About that one, I’ll keep a post with a “released” version then I will create another post with “in dev” version so other people can write.
I started with some LUA programs…

[goodweather]

Thx to both of you!
Yes sure, I think we can join forces to build something nice and by this contribution complete the work done by Atom.
I will correct the yellow questions with your feedback Puppeteer.
I will also think about a new Chapter structure so we make the doc more generic.
For example:
– Part1= Panel basics (using 2 or 3 examples each time?)
– Part2= Panel Advanced
– Part3= LUA programming (a summary of typical propgramming stuff: variables, loops, input/outputs…) Summary only! The goal is not to write a guide on how to program but to present LUA to people knowing how to program in other languages
– Part4= Using LUA for a Librarian – Basics
– Part5= Using LUA for a librarian – Advanced (?)
– Part6= Graphics – EG curves display
– Appendix
– Reference guide of Ctrlr (? quite difficult to maintain, maybe too long…?)

What do you think?

After we agree on something, then we can organize our work and maybe exchange outside the forum then publish our result… Anyway, no hurry… I’m writing a paragraph each time I’m discovering and using something…
And now it is vacation time 🙂

[goodweather]

Well, as I explained in my previous post, you can only adjust the OUTPUT resolution from the Sub37, not the input. So I was quite confident this wasn’t the issue.
And I also found how to setup a double CC message for values 0-16383.

I found the issue: besides setting the Sub37 as Output device I had also to set it in MIDI Controller. I’ll search the forum for an explanation or maybe you can explain the difference between Ctrlr Midi Output and Ctrlr Midi Controller.
I’ll copy your explanation in my step by step guide.

So, now I can complete all buttons, test them then start thinking about the librarian (no info about Sub37 sysex messages in the manual though… will try the Minitaur way…).

[goodweather]

Hi Atom, I have now built a v1.0 Step by Step guide for building a panel (I’ll publish it as PDF in the coming days under Releases) and have a few buttons with CC messages ready. Output to Midi monitor console is fine (changing Amp Attack time is CC28 giving as message for example B0 1C 37 (for 55 as value).
Output device is Moog Sub 37 and recognized (got confirmation in green) BUT the sound is not altered on the synth…
Any tip of things to check?
I will try sending a 0-16383 double message instead of one 0-127.
On Sub37 output one can choose 7 or 14bits operation. Don’t know what it is expected as input.
Thx in advance!

[goodweather]

Thx for the tips guys!
Actually, it doesn’t appear on the panel itself.
I suppose it is OK to mention the name of the Ctrlr panel as “Moog Sub37 panel”. Otherwise I’ll call it “Sub37 panel” only.
And I can remove the Moog wording from the Ctrlr documentation I’m busy to write.
Let me know what do you think, Atom. We need to respect the synthmakers brands 🙂

[Author]

Posts