[Cramp]

"itege":34oe3nud wrote:

I’ve made a very basic panel if you would like to help out with it… I can send midi CC’s from the VST to the SP, but not note data for some reason.[/quote:34oe3nud]
ensure that device recieves and sends MIDI CC. I’m not sure about how to…haven’t look for manual yet.

[Cramp]

I was thinking to do this panel after the Nord Lead 3. Own Slim Phatty a month now. Probably will do as well

[Cramp]

"atom":9iiwtkj6 wrote:

You are trying to fetch a byte range from a SysEx message, in case of $21 in the manual the table at page 149 states, that the program data starts at byte 41 (16 bytes for name, 16 spare bytes, 2 bytes that make the version and the message header). So the program data is at byte 41 to the end -1 (-1 cause sysex ends with F7 always and it’s not part of the data).

[code:9iiwtkj6]
programName = midiMessage:getLuaData():getRange(7,16)
programData = midiMessage:getLuaData():getRange(41, 261-41-1)
[/code:9iiwtkj6]

AND have a look at page 155
[quote:9iiwtkj6]
The patch data is viewed as a bit stream where the different parameters only use as many bits as necessary for their actual format. All parameters are oriented with the most significant bit first. An 8-bit
checksum is calculated over the entire data block and stored as the last 8 bits of the file. The checksum
is calculated by adding all data Bytes together.

[b:9iiwtkj6]Since a MIDI SysEx data Byte can only contain 7 bits,
the bit stream is 8 to 7 bit converted to fit the MIDI format[/b:9iiwtkj6]
[/quote:9iiwtkj6]

that means that these bytes are converted to fit the 7bit format that MIDI takes, now i’m not sure what does that mean in this case, but all bytes that are longer then 7 bits will be encoded in some way.[/quote:9iiwtkj6]

Really appreciate your help mate
will try now to change the code

[Cramp]

"dasfaker":2lk0n8z3 wrote:

[quote:2lk0n8z3]mate, could you please clarify what values should I use for that ranges?[/quote:2lk0n8z3]

Program data are the bytes that correspond to controllers values. So from the dump you receive from the synth, you have to count past the end of the header (value01) to the end of the controller data (value02). You have to look for it in the manual of the synth.

programNumber is a byte from the Virus dump that corresponds to the program number of the bank in which the patch is stored. It’s possible that in the Clavia dump this data is not stored.

As Atom said, you have to look in the manual which byte corresponds to each controller and later assign each byte to each modulator.[/quote:2lk0n8z3]

Sorry, manual doesn’t say that info. Or I can’t read it properly.
The only thing I get is that
– a complete Patch (Program) Dump, including SysEx header and data, is transmitted in 261 Bytes
– I guess that Patch Data could be from 1 to 210 according to "PROGRAM DUMP TO/FROM MEMORY LOCATION (MESSAGE TYPE $21)" where are the fields numbered as Patch Data 1…Patch Data 210
– the maximum size of each parameter in Bits is 8 from the table
– An 8-bit checksum is calculated over the entire data block and stored as the last 8 bits of the file.

In that case as I understood
value01 is equal 1
value02 is equal 210

as for
values03 it probably goes then as 211
value04 = 261

I opened patch as SysEx and it has content like 10 rows with 2 columns. Each row column has 8 bits in HEX format. Totaly 261 cells

I might be wrong..

This is NL3 manual which has Sysex info section as well

https://dl.dropbox.com/u/4202790/docs/C … l_v1.2.pdf

[Cramp]

"atom":2md8iofx wrote:

You are mixing two things, program data and controller data. Program data is what you get from the device if you request a program dump, a big blob of memory that describes the device state, it’s usualy a big SysEx message, this is what’s happening on the Virus TI panel.

You need to read the manual for the device, and find the section for Program Dumps or Bulk Dumps or something similar, and see how the data is structured there.[/quote:2md8iofx]

mate, could you please clarify what values should I use for that ranges?
[code:2md8iofx]
programData = midiMessage:getLuaData():getRange(Value01,Value02)
programNumber = midiMessage:getLuaData():getRange(Value03,Value04)[/code:2md8iofx]

As I’ve already posted text from manual says
[quote:2md8iofx]PROGRAM FORMAT
In the Program Dump Messages, the Data Bytes contain the actual Program settings.
• The patch data is viewed as a bit stream where the different parameters only use as many bits as necessary for their actual format. All parameters are oriented with the most significant bit first. An 8-bit checksum is calculated over the entire data block and stored as the last 8 bits of the file. The checksum is calculated by adding all data Bytes together. Since a MIDI SysEx data Byte can only contain 7 bits, the bit stream is 8 to 7 bit converted to fit the MIDI format.
• A complete Patch (Program) Dump, including SysEx header and data, is transmitted in 261 Bytes. See page 156. (There is a big table which shows controls like OSC, Lfo and etc – Link to PDF https://dl.dropbox.com/u/4202790/docs/C … l_v1.2.pdf) [/quote:2md8iofx]

So as far as I understand I should add SysEx size 261 into code like this. am i right?
[code:2md8iofx] s = midiMessage:getSize()
if s == 261 then
if dump_send ~= nil then
if dump_send == 1 then
— console("received program data")
PatchDataLoaded = midiMessage:getLuaData()
assignValues(midiMessage)
dump_send = 0
end
end
end[/code:2md8iofx]

Now for values Program Data and Patch Data – I dunnot what values show be used there.
pleas help!
Ilnaz

[Cramp]

strange thing it works only specific time…dunno why..if only I re-open panel. all start works again. seems there is some caution which has limit on specific value

[Cramp]

after I finished the post and then tried to figure out again script according to Message Type $40 it works now without configuring each controller and knob.

I created Update button and set the ‘Update’ script on it

[code:1xfzwott]UpdatePatch = function(modulator, newValue)
slot= panel:getModulatorByName("Slot Number")

if program ~= nil and bank ~= nil and slot~= nil then
m = CtrlrMidiMessage({0xF0, 0x33, 0, 0x09, 0x40, slot:getModulatorValue(), 0xF7})
panel:sendMidiMessageNow(m)
end

end[/code:1xfzwott]

midiMessageRecieved looks like
[code:1xfzwott]–
— Called when a panel receives a midi message (does not need to match any modulator mask)
— @midiMessage http://ctrlr.org/api/class_ctrlr_midi_message.html
—

midiMessageReceived = function(midiMessage)
—
s = midiMessage:getMidiMessageType()
if s == 7 then
program_number = panel:getModulatorByName("Patch")
if program_number ~= nil then
xx = midiMessage:getValue()
if xx ~= nil then
program_number:setModulatorValue(xx+1,false,false,true)
end
end
end
—
s = midiMessage:getSize()
if s == 524 then
if dump_send ~= nil then
if dump_send == 1 then
— console("received program data")
PatchDataLoaded = midiMessage:getLuaData()
assignValues(midiMessage)
dump_send = 0
end
end
end
end
function assignValues(midiMessage)
— console ("assignValues")
lastSavedProgram = midiMessage:getLuaData()
programData = midiMessage:getLuaData():getRange(09,514)
programNumber = midiMessage:getLuaData():getRange(08,1)
PatchDataLoaded = midiMessage:getLuaData()
— console ("RAW DATA: ")
— console (PatchDataLoaded:toHexString(1))

— panel:getModulatorByName("FilterFreq1"):setModulatorValue(programData:getByte(74), false, false, true)

symbols = {"|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|","|"," ","!","","#","$","%","&","’","(",")","*","+","4","-",".","/","0","1","2","3","4","5","6","7","8","9",":",";","<","=",">","?","@","A","B","C","D","E","F","G","H","I","J","K","L","M","N","O","P","Q","R","S","T","U","V","W","X","Y","Z","[","b","]","^","_","`","a","b","c","d","e","f","g","h","i","j","k","l","m","n","o","p","q","r","s","t","u","v","w","x","y","z","{","|","}","~"}
a = symbols[programData:getByte(240)]
b = symbols[programData:getByte(241)]
c = symbols[programData:getByte(242)]
d = symbols[programData:getByte(243)]
e = symbols[programData:getByte(244)]
f = symbols[programData:getByte(245)]
g = symbols[programData:getByte(246)]
h = symbols[programData:getByte(247)]
i = symbols[programData:getByte(248)]
j = symbols[programData:getByte(249)]

patch = programNumber:getByte(0)

if patch ~= nil and bank_Select ~= nil and program_Select ~= nil then
text1 = string.format("%s%s%s%s%s%s%s%s%s%s", a, b, c, d, e, f, g, h, i, j)
patchName = panel:getModulatorByName("Patch")
if patchName ~= nil then
c = patchName:getComponent()
c:setPropertyString ("Patch Name", text1)
end
pos = 1
text = string.format("%s", "Patch Loaded")
text2 = string.format("%s", text1)
end
redraw = panel:getPanelEditor():getCanvas()
redraw:repaint()
end
[/code:1xfzwott]

and also set prgram change know to use that script. and it works
when I change program (patch) on panel every knob and slider lights changing to patch values. thats awesome

The only thing I cannot realize is how to change Slot value. Is there any code how to change the MIDI channel?

[Cramp]

"atom":1bb7xnkh wrote:

You are mixing two things, program data and controller data. Program data is what you get from the device if you request a program dump, a big blob of memory that describes the device state, it’s usualy a big SysEx message, this is what’s happening on the Virus TI panel.

You need to read the manual for the device, and find the section for Program Dumps or Bulk Dumps or something similar, and see how the data is structured there.[/quote:1bb7xnkh]

thanks Atom
I read the manual and founf the following – Patch (Program) Dump Request. And it is devided into 2 sections:

[quote:1bb7xnkh][b:1bb7xnkh]1. Patch Dump Request from Slot (Message Type $30)[/b:1bb7xnkh]
And it says that when the patch request message below is recieved by Nord Lead 3, it will reply by sending a Patch Dump of Message Type $20 (from Slot). Nord Lead 3 Slots are assigned to MIDI Channel. So Nord Lead 3 has four MIDI channels on output. Total number of slot is 4

Byte (Hex) – Description
$F0 – System Exclusive
$33 – Manufacture ID (Clavia)
<Device ID> $00-$7F – selected Device ID for the specific instrument, 1 -127, All (what is that mean??)
$09 – Model ID for Nord Lead 3
$30 – Message Type specifies dump request source. $30 – from Slot
$00-$04 – Message Specification specifies the requested Slot: $00-$03 = Slot A-D. $04 – Active Slot.
$00 – Spare. Always set to $00
$F7 – End of System Exclusive
[b:1bb7xnkh]
PROGRAM DUMP TO/FROM SLOT (MESSAGE TYPE $20)[/b:1bb7xnkh]
Byte (Hex) – Description
$F0 – System Exclusive
$33 -Manufacturer ID (Clavia)
<Device ID> $00-$7F – selected Device ID for the specific instrument, 1-127, All
$09 -Model ID for Nord Lead 3
$20 -Message Type specifies dump source. $20 = from Slot
$00 to $04 -Specifies the source Slot: $00-$03 = Slot A-D. $04 = Active Slot.
$00 -Spare. Always set to $00
<Program Name> – Program Name. Max 16 characters long. Zero terminated if less than 16 char- acters.
$00 (x 16) – 16 spare Bytes for future expansion. Always set to $00.
<Version MSB> – Most significant 7 bits of version number.
<Version LSB> – Least significant 7 bits of version number.
<Patch Data 1> – See page 156. (There is a big table which shows controls like OSC, Lfo and etc – Link to PDF [url:1bb7xnkh]https://dl.dropbox.com/u/4202790/docs/Clavia_NordLead3_Manual_v1.2.pdf[/url:1bb7xnkh])
<Patch Data 2>
<Patch Data 3>
:
<Patch Data 210>
$F7 – End Of System Exclusive

[b:1bb7xnkh]2. Patch Dump Request from Memory Location (Message Type $31)[/b:1bb7xnkh]
And it says that when the patch request message below is recieved by Nord Lead 3, it will reply by sending a Patch Dump of Message Type $21 (from Memory Location)

Byte (Hex) – Description
$F0 – System Exclusive
$33 – Manufacturer ID (Clavia)
<Device ID> – $00-$7F selected Device ID for the specific instrument, 1-127, All
$09 – Model ID for Nord Lead 3
$31 – Message Type specifies dump request source. $31= from memory location
$00-$07 – Message Specification specifies the requested Bank (1-
$00-$7F – Message Specification specifies the requested memory location (1-128)
$F7 – End Of System Exclusive

[b:1bb7xnkh]PROGRAM DUMP TO/FROM MEMORY LOCATION (MESSAGE TYPE $21)[/b:1bb7xnkh]
Byte (Hex) – Description
$F0 – System Exclusive
$33 – Manufacturer ID (Clavia)
<Device ID> – $00-$7F -selected Device ID for the specific instrument, 1-127, All
$09 – Model ID for Nord Lead 3
$21 – Message Type specifies dump source. $21= from memory location
$00-$07 – Specifies the source Bank 0-8
$00 to $7F – Message Specification specifies the source memory location 1-128
<Program Name> – Program Name. Max 16 characters long. Zero terminated if less than 16 char- acters.
$00 (x 16) – 16 spare Bytes for future expansion. Always set to $00.
<Version MSB> – Most significant 7 bits of version number.
<Version LSB> – Least significant 7 bits of version number.
<Patch Data 1> – See page 156. (There is a big table which shows controls like OSC, Lfo and etc – Link to PDF [url:1bb7xnkh]https://dl.dropbox.com/u/4202790/docs/Clavia_NordLead3_Manual_v1.2.pdf[/url:1bb7xnkh])
<Patch Data 2>
<Patch Data 3>
:
<Patch Data 210>
$F7 – End Of System Exclusive

and in the end

[b:1bb7xnkh]ALL CONTROLLERS REQUEST (MESSAGE TYPE $40)[/b:1bb7xnkh]

This message instructs Nord Lead 3 to send all current MIDI Controller values for a specified Slot.
This message can also be transmitted from the Nord Lead 3 by using the ‘Send MIDI Controllers’ function described on page 121.
Byte (Hex) – Description
$F0 – System Exclusive
$33 – Manufacturer ID (Clavia)
<Device ID> – $00-$7F selected Device ID for the specific instrument, 1-127, All
$09 – Model ID for Nord Lead 3
$40 – Message Type specifies All Controllers Request.
$00-$04 – Specifies the requested Slot: $00-$03 = Slot A-D. $04 = Active Slot.
$F7 – End Of System Exclusive
[b:1bb7xnkh]
PROGRAM FORMAT[/b:1bb7xnkh]
In the Program Dump Messages, the Data Bytes contain the actual Program settings.
• The patch data is viewed as a bit stream where the different parameters only use as many bits as necessary for their actual format. All parameters are oriented with the most significant bit first. An 8-bit checksum is calculated over the entire data block and stored as the last 8 bits of the file. The checksum is calculated by adding all data Bytes together. Since a MIDI SysEx data Byte can only contain 7 bits, the bit stream is 8 to 7 bit converted to fit the MIDI format.
• A complete Patch (Program) Dump, including SysEx header and data, is transmitted in 261 Bytes. See page 156. (There is a big table which shows controls like OSC, Lfo and etc – Link to PDF [url:1bb7xnkh]https://dl.dropbox.com/u/4202790/docs/Clavia_NordLead3_Manual_v1.2.pdf[/url:1bb7xnkh])
[/quote:1bb7xnkh]
Please could you help define what actual values need to be used in midiMessageRecieved LUA script?

Many thanks in advance
Ilnaz

[Cramp]

hi,
I wanted to say that I faced to one issue.
I wanted to re-create the AU component within DAW using CtrlR AU plugin. But NL3 plugin as AU was loaded everytime when I started Logic or Ableton even if I deleted Ctrlr-AU.component from /Library/Audio/Plug-Ins/Components and Nord Lead 3.component.
I founf the way where systems stores original one
/Library/Components – delete compiled AU of your panel from there and copy new CtrlR-AU.component to /Library/Audio/Plug-Ins/Components
And then it will work again.

Ok,
/Library/Audio/Plug-Ins/Components – stores components of all AU plugins
/Library/Components – stores AU pluging you created using CtrlR as exported as Standalone instance from your DAW

Hope that helps

[Cramp]

nice one. was useful the Sysex understanding as well

[Cramp]

"atom":1pdf5qg2 wrote:

Sure i’ll do that.[/quote:1pdf5qg2]
thanks mate

[Cramp]

"atom":1fyah3yo wrote:

Logic is a different animal, it has some sort of AU cache file in Library/Cache/com.apple.audiounit.cache that needs to be delete and Logic restarted for changes to take effect at all (i discovered it now). I don’t know what else i can do with AU, the names reported by the hosts are in the Resource files (.rsrc) file that is changed when exported i asked in the JUCE forum i’ll see what others have to say about this.[/quote:1fyah3yo]

thanks mate.
I will now continue working on panel. #excited

p.s. Edit mode – could you disable that option in Generel menu when you export AU as standalone instance?

[Cramp]

"atom":3ttc9k7f wrote:

I’m trying to find a way to rename the exported instances to the panel names but the AU subsystem is more complicated then VST, it might take me a moment to figure this out[/quote:3ttc9k7f]
you are doing really great job man

[Cramp]

"atom":sxreimb1 wrote:

I’m trying to find a way to rename the exported instances to the panel names but the AU subsystem is more complicated then VST, it might take me a moment to figure this out[/quote:sxreimb1]
mmm

i tried to check how it looks in Ableton

the thing is – it is looks like I want
[img:sxreimb1]https://dl.dropbox.com/u/4202790/logic-tut/ableton-au.png[/img:sxreimb1]

and automation appears if I turn knob on panel or on synth itself – and Ableton shows only one parameter which I touched
[img:sxreimb1]https://dl.dropbox.com/u/4202790/logic-tut/ableton-au-2.png[/img:sxreimb1]

[Cramp]

"atom":1ufbv0nv wrote:

Allright i ,now how to open Ctrlr, and undefined parameters are OK in that case since Logic can’t update parameter names. But once you start Ctrlr as AU, open your Nord panel, export is as a standalone instance and open that instance, do you still get undefined names in that instance ?

Also i was able to load your Nord panel on windows export it as a instance and start it, no resources were missing and it works ok. I’ll check the AU stuff asap i just need to download a "demo" version of Logic.[/quote:1ufbv0nv]

Man, that works!

But, was searching for component a while.
ok. I did export within Logic started CtrlR as AU (opened my panel) and did export as standalone instance on my mac desktop.
It took about 10 minutes to export.

I found that file with extension as "component" as AU
[img:1ufbv0nv]https://dl.dropbox.com/u/4202790/logic-tut/nl3comp.png[/img:1ufbv0nv]
Opened [b:1ufbv0nv]System HD – Library – Audio – Plug-Ins – Components [/b:1ufbv0nv] – deleted previous CtrlR component file from your package. Put created for Nord Lead 3.

Started Logic
Cannot find it. I was confused…then realized that this AU is still there
[img:1ufbv0nv]https://dl.dropbox.com/u/4202790/logic-tut/au/CtrRAU.png[/img:1ufbv0nv] hmmmm…but I deleted it..
And started..then….tada

it works man
[img:1ufbv0nv]https://dl.dropbox.com/u/4202790/logic-tut/au/logic-nl3.png[/img:1ufbv0nv]

As you can see automation values are equal to names I put for modulators (components)
Also I tried to record MIDI and did manual Automation – it works
[img:1ufbv0nv]https://dl.dropbox.com/u/4202790/logic-tut/au/logic-nl3-2.png[/img:1ufbv0nv]

this is great man

The only thing I would remove is "Edit Mode" and the posibility to rename Ctrl-R or do it as for exmple CtrlR + Panel name

your thoughts?

Started Logc – didn;t find it. The th

[Cramp]

"atom":2jp83obj wrote:

But once you start Ctrlr as AU, open your Nord panel, export is as a standalone instance and open that instance, do you still get undefined names in that instance ?
[/quote:2jp83obj]
you mean to do an export within Logic?
Let my try!

[Cramp]

"atom":28b5jrxr wrote:

Don’t worry about the version difference it’s a SVN thing, it’s ok it always will be one smaller.

The Unknown paramters are weird they should be named, and not the Visible Name but the Modulator Name is used, could someone enlighten mi on how to add a AU instrument in Logic, i’ll be able to debug it then, i don’t know Logic at all so i can’t help really. Please write in points on how to add a AU as an instrument in Logic.[/quote:28b5jrxr]

there is no problem.

1. well first start Logic. I’m using version 9.1.7 and my Mac OS is Lion 10.7.4

2. Then go to File – New..
On first pic click Empty Project
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen01.png[/img:28b5jrxr]

3. Then as you started new project it will ask you to create at least one instrument, audio or whatever. Select Software Instrument
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen02.png[/img:28b5jrxr]

4. The go to channel mixer of the Software Instrument (left hand on the screen [b:28b5jrxr]Inst1[/b:28b5jrxr]) and click once on field above the StereoOut
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen03.png[/img:28b5jrxr]

5. Once you click on the field in point 4 then you have to select the CtrlR. See the path from the screen below
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen04.png[/img:28b5jrxr]

6. Ok, CtrlR will open. Now you may open your or any panel you want
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen05.png[/img:28b5jrxr]

7. To display the Automation lines press A on your keyboard and then you will be able to see Automation parameters of your instrument including the default (Main) and CtrlR as well. See picture below
[img:28b5jrxr]https://dl.dropbox.com/u/4202790/logic-tut/logic09-screen06.png[/img:28b5jrxr]

Hope that helps mate.
Cheers, Ilnaz

[Cramp]

"atom":2v1k0a13 wrote:

Can you upload the panel here so i can debug it ?[/quote:2v1k0a13]
check PM for link mate
the strange thing.. I tried now to export standalone version on Mac. the same thing.. I changed the background today. I dunno why resources are not exported.

[Cramp]

"atom":z6tpvtoi wrote:

Can you upload the panel here so i can debug it ?[/quote:z6tpvtoi]
I will PM you a link. Panel is still in progress. Will share only final version to public.

[Cramp]

first,
you have to copy your CtrlR AU.component to Library/Audio/Plugins/Components
Start Logic
Then start new project and create Software Instrument
As you can see from screenshot above click on field above StereoOut and Find instrument as CtrlR. It shown under the venoder name like Integrator ..dunno remember now..will check at home.
To see the automation lines press A on your keyboard.

[Author]

Posts