[lfo2vco]

Hi Atom, I downloaded the latest nightly build (Ctrlr_1539.dmg) for Mac OSX and still the inverted modulator persists. Did you have time to try a fix this time around?

I understand you have a life outside Ctrlr, so I’m not hassling you regarding this. Cheers.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Atom, yes the variable VS does refer to the “w” from the manual.

The (00)(01)(02) in the method refers to the list of comboValues in the combobox.

Update it seems that it is working! Your suggestion of checking the byte values in the console revelled that I was not getting the required byte back from the synth. Oddly this only affected one patch, the one I was using to test my script.

Indenting code… when to tab that is the question?

Thanks for your patience and assistance as always : )

• This reply was modified 10 years, 7 months ago by lfo2vco.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

atom wrote:

As far as i can tell you don’t need to do anything, i need to fix my bug and the default expression will work, there is no additional logic needed here. Just give me some time to fix my side.

Cool, I look forward to giving the new version a go. I’m being dragged away from my synths and computer (kicking & screaming) for a long weekend. I’ll touch base a soon as I get back. Many thanks.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hecticcc wrote:

The values your device sends are not linear. It sends 1,3,4,6,8… instead of incrementing by 1.

You will need to figure out a formula for it or make a script that translates these values.

The values are me twisting the knob as Atom requested. Just like the avatar to the left : )

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Files attached as requested, I appreciate your time and effort Atom.

Attachments:

You must be logged in to view attached files.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Syntax and stuff has got the better of me again. I didn’t realise you could put the – in front of the value (because all the examples I’d seen had it behind). But I now understand a little more of the maths the expression is performing.

I have tried 127 – modulatorValue, 127 – midiValue, swapped them around, doubled them, halved them… nothing seems to work.

I also gave Hecticcc’s method a go… no luck

It makes absolutely no sense.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

I put “midiValue – 127” in the reverse expression, but still the problem persists.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Atom, as requested the data from the MIDI monitor is

7f,5f,3f,00

So the 3P is definitely sending inverted data for this byte.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Many thanks Atom, that has resolved the problem.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Well, I have got so far. The code doesn’t crash the panel. Syntax was bugging me, as I don’t fully understand what I am doing so I missed a few things initially.

byte = programData:getByte(20) 
bi = BigInteger(byte)

panel:getModulatorByName("DCO 1 Range"):setValueMapped(bi:getBitRangeAsInt(0,2), false)
panel:getModulatorByName("DCO 1 Waveform"):setValueMapped(bi:getBitRangeAsInt(2,2), false)

It works a treat, however I had to change the Combo Contents to this:

00=16
01=8
10=4

from this:

16=0
8=32
4=64

Now I am going to look at some putting Lua in the Combobox to make this conversion.
Cheers Dude : )

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

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Again many thanks. I am totally new to programming so I copied msepsis’ code not fully understanding what the instructions are doing! For example I now realise…

programData = midiMessage:getData():getRange(1,112)

should be..

programData = midiMessage:getData():getRange(10,128)

Most of the modulators correctly reflect the patch now, it seems the comboboxes are still not changing.

Also some of the combobox bytes are expressed like this:
Byte (20) DCO1 Wave/Range, Data Type 0000yyxx, xx =DCO 1 Range 00=16′ 01=8’10=4′ yy =DCO 1 Wave 00=Saw 01=Pulse 10=Square
Wave and range being two separate comboboxes, I guess that the bits have to be assigned individually?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

atom wrote:

You must remember that getData() returns the entire message as a memory block, so you’ll get any “headers” and sysex prefixes that you should bypass to get to the actual data.

Many thanks for the prompt response Atom. I took me a while to understand your reply, but in essence I take to mean that I should include the headers in the byte count so:
panel:getModulatorByName(“DCO 1 Frequency”):setModulatorValue(programData:getByte(20), false, false, false)
becomes:
panel:getModulatorByName(“DCO 1 Frequency”):setModulatorValue(programData:getByte(32), false, false, false)

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Better post the assign method too:

assignValues = function(midiMessage)

programData = midiMessage:getData():getRange(1,112)

	-- DCO 1 Wave/Range here (19)
	panel:getModulatorByName("DCO 1 Frequency"):setModulatorValue(programData:getByte(20), false, false, false)
	panel:getModulatorByName("DCO 1 Env Mod Amt"):setModulatorValue(programData:getByte(21), false, false, false)
	panel:getModulatorByName("DCO 1 LFO Mod Amt"):setModulatorValue(programData:getByte(22), false, false, false)
	-- Byte (23) Not used
	-- DCO 2 Wave/Range here (24)
	panel:getModulatorByName("DCO 2 Frequency"):setModulatorValue(programData:getByte(25), false, false, false)
	panel:getModulatorByName("DCO 2 Fine Tune"):setModulatorValue(programData:getByte(26), false, false, false)
	panel:getModulatorByName("DCO 2 Env Mod Amt"):setModulatorValue(programData:getByte(27), false, false, false)
	panel:getModulatorByName("DCO 2 LFO Mod Amt"):setModulatorValue(programData:getByte(28), false, false, false)
	-- Byte (29) Not used
	panel:getModulatorByName("Cross Mod"):setValueMapped(programData:getByte(30), false)
	panel:getModulatorByName("DCO Source Mix"):setModulatorValue(programData:getByte(31), false, false, false)

end

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

OK, not had as much time to work on this lately. However the panel is sending the Tone Buffer Edit Dump request then the Lua method is hooking up with the resulting Sysex response as msepsis instructed above. But then the values from the Lua assign method are not responding as I would expect.

For example a DCO1 Tune that should be set at 64 by the Lua assign ends up placed at 32 on one patch and then 115 on the next.

Any ideas on where I am getting it wrong would be very welcome.

Here’s the dump request:
[System exclusive] Ch:[–] No:[—-] RAW:[f0 7f 7f 7f 60 01 00 03 f7]

This is what the 3P returns:
[System exclusive] Ch:[–] No:[—-] RAW:[f0 7f 7f 7f 60 01 00 04 00 01 48 69 67 68 20 53 74 72 69 6e 67 73 20 20 20 20 20 20 20 20 01 3f 3f 00 3f 01 40 29 3f 00 3f 00 3f 0a 00 57 00 00 43 3b 3f 00 00 13 1f 61 13 1f 1f 61 1c 01 68 18 01 79 18 00 2f 03 41 00 00 3f 00 00 00 00 03 0c 00 00 00 00 6f 00 00 00 00 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f7]

This is how the KiwiTechnics manual describes the first few lines of data:
$04 (4) Transmit/Receive Tone Edit Buffer Dump
2 x null bytes sent followed by 128 bytes of data in the following format

Data $00-$13 / Byte (0-19) = Tone Name / Data Type Ascii Bytes / Data Details Tone Name
Data $14 / Byte (20) = DCO1 Wave/Range / Data Type 0000yyxx / Data Details xx =DCO 1 Range 00=16′ 01=8’10=4′ yy =DCO 1 Wave 00=Saw 01=Pulse 10=Sqr
Data $15 / Byte (21) = DCO1 Tune / Data Type 0xxxxxxx / Data Details (0-127) Split Control +-63 (+- 1 octave or +-1200 cents)
Data $16 / Byte (22) = DCO1 Env Mod Amount / Data Type 0xxxxxxx / Data Details (0-127) Split Control +-63

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Many thanks msepsis, a very clear explanation.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

atom wrote:

The Roland JUNO106 uses Sysex to do bi-directional editing. You can use that as an example.

Hi Atom, I have indeed been looking at your Juno 106 panel as an example of what I wish to achieve. What confused me initially was the considerable differences in Manufacturer IDs between Roland and KiwiTechnics. Once msepsis had confirmed that part was correct I felt confident to explore the formula further.

I should say many thanks for putting Ctrlr out there, brilliant software. I am using the panel in CC at present and it has enabled me to start getting sounds together very quickly.

One question regarding sysex, I’m hoping that the panel will be able to reflect patch changes made on the 3P. Will this require extra scripting or settings to be made in the Ctrlr panel?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Many thanks msepsis, your response let me know I was working somewhere in the right ball park.

I entered the formula as you specified but it locked up the patch on my 3P. So I fiddled about a bit. Your comment about binary made me reconsider the formula, so I checked what MIDI the 3P was sending out when in edit mode (via MIDI Monitor). It seemed that the 04 and the 15 where replaced by b0 and 0a in the formula from the 3P. So I tried this:

f0 7f 7f 7f 60 01 00 b0 0a xx f7

It worked! the results looked like this:
[22:49:02:000181]: [System exclusive] RAW:[f0 7f 7f 7f 60 01 00 b0 0a 44 f7]
[22:49:02:000281]: [System exclusive] RAW:[f0 7f 7f 7f 60 01 00 b0 0a 43 f7]
[22:49:02:000315]: [System exclusive] RAW:[f0 7f 7f 7f 60 01 00 b0 0a 42 f7]
[22:49:03:000678]: [System exclusive] RAW:[f0 7f 7f 7f 60 01 00 b0 0a 40 f7]

Next stage is to see if this method will also apply to a DCO Range uiCombo popup menu.

Many thanks msepsis for your assistance and pointing me in the right direction.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Back yet again,

I have modified Jinsai’s panel slightly and have attached it in case anyone is interested. I cannot take credit for anything other than some cosmetic and layout changes.

I have also increased the overall dimensions. Works very nicely with the Kiwi-3P. Many thanks to Jinsai for doing all the hard work.

CHECK TOTALLY REVISED PANEL NOW AVAILABLE IN DOWNLOADS

Attachments:

You must be logged in to view attached files.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi msepsis,

No justification required for the Leipzig… it’s a wonderful, dirty, old school analogue synthesizer and proud of it. I find the sound and sequencer very inspirational, also in the mix it shows the Voyager a thing or two.

MIDI is very basic, nothing coming or going from the knobs… but in the Leipzig’s case I find that to be just fine.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Back again,

Have the JX-3P now and it’s extremely easy to program from the from panel. So please ignore the above question.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[Author]

Posts