[zmix]

Thanks for confirming, I posted a request..

Also, when I right click on a panel, the menu that appears has the “Add Component” menu as a sub-menu within the “Replace With” menu.
If you try to Add a component from the Add Component menu any component you select will replace the entire panel with that one component.

There is no other menu to add components, and this menu is only able to replace an existing component.

Shouldn’t the “Add Component” menu be at the top level of that sub menu?

Is this a BUG?

Attachments:

You must be logged in to view attached files.

[zmix]

zmix wrote:

So weird.. when I change the uiSlider to a uiFixedSlider I can no longer adjust the thumb width or height?

Is this a BUG?

[zmix]

Here is an example of the “SIZE” parameter for the PCM-70

It is sending a Sysex string as follows:

Sysex:Lexicon:PCM-70:MIDI CHANNEL 1: PARAMETER 03: MSB:LSB:EOX

F0 06 00 20 03 MS LS F7

The data range for the size parameter is given in the Lexcon manual as from 488 to 537

I simply set the component minimum value to 488 and maximum to 537

I manually entered the “Slider Contents” to match the PCM-70s displayed values

3.5m=488
4.2m=489
4.9m=490
5.6m=491
6.3m=492
7.1m=493
7.8m=494
8.5m=495
9.2m=496
9.9m=497
10.6m=498
11.3m=499
12.0m=500
12.7m=501
13.4m=502
14.2m=503
14.9m=504
15.6m=505
16.3m=506
17.0m=507
17.7m=508
18.4m=509
19.1m=510
19.8m=511
20.5m=512
21.3m=513
22.0m=514
22.7m=515
23.4m=516
24.1m=517
24.8m=518
25.5m=519
26.2m=520
26.9m=521
27.6m=522
28.4m=523
29.1m=524
29.8m=525
30.5m=526
31.2m=527
31.9m=528
32.6m=529
33.3m=530
34.0m=531
34.7m=532
35.5m=533
36.2m=534
36.9m=535
37.6m=536
38.3m=537

Attachments:

You must be logged in to view attached files.

[zmix]

Yes, it’s so exciting to have complete control of every parameter int eh PCM-70, especially when using the Mackie C4 32-encoder control surface to adjust it in real time..I only wish the parameter names would say more than “Undefined_01…Undefined_64”

Since the PCM 70 doesn’t have direct access to the algos, and using a program change is worthless since it pops out of preset mode as soon as you adjust anything, some sort of bulk, send to the working buffer in the unit might ensure that I am starting from a known algorithm.

I have a collection of 312 byte sysex presets, how could I activate them via a tab, and then send the panel parameter settings?

[zmix]

human fly wrote:

have you got the lexicon responding to sysex yet?

It has been working perfectly the whole time, I’m a little confused by all the diversion into byte order, etc.. I’ve got all that worked out already.. Maybe I wasn’t clear enough about that.

I was looking for a way to get the settings on the panel to correspond to the parameter values, and thanks to you guys I have that mostly worked out.

I’m still unsure about making a multi algo panel, it might be a waste of time given the structure of the PCM-70.. maybe it will require sending and receiving full 312 byte data dumps..

Also still not getting modulator names to appear in the DAW using the AU component.. is there a secret I’m missing?

[zmix]

BEST thing about using the uiFixed slider is that I can put in the display values, and their direct Sysex values…!!!

170Hz=497
350Hz=498
530Hz=499
720Hz=500
920Hz=501
1.12kHz=502
1.33kHz=503
1.55kHz=504
1.78kHz=505
2.02kHz=506
2.27kHz=507
2.53kHz=508
2.81kHz=509
3.1kHz=510
3.41kHz=511
3.73kHz=512
4.08kHz=513
4.45kHz=514
4.85kHz=515
5.28kHz=516
5.75kHz=517
6.27kHz=518
6.83kHz=519
7.47kHz=520
8.19kHz=521
9.02kHz=522
10kHz=523
11.1kHz=524
12.3kHz=525
13.6kHz=526
15kHz=527

[zmix]

So weird.. when I change the uiSlider to a uiFixedSlider I can no longer adjust the thumb width or height?

[zmix]

Ok, so for example, there are 32 listed frequencies for the High Cut filter:

0Hz
170
350
530
720
920
1120
—
snip
—
12300
13600
15000Hz

The modulator covers these 32 values by sending 496-527 in the Sysex parameter range MSB / LSB

When you get into the reverberation times, it has a table of 32 more magic numbers 5,6,8,9,11,12,13,14,15,17,18,20,22,244,26,28,30,34,38,42,46,52,57,65,75,85,100,120160,220,350 and 700

These numbers are entered into a formula which varies based on the program, the selected size, etc..it’s in the manual on page 6-13

Attachments:

You must be logged in to view attached files.

[zmix]

‘expression to evaluate’ + number worked perfectly! Thanks.

Now to map other non sequential numbers, like the 15 possible filter cutoff settings, room sizes etc..

Will that require some sort of lookup table?

[zmix]

I downloaded your evaluate panel, that looks promising.. I’ll play with ‘expression to evaluate’ on my panel and report back..!

[zmix]

You guys are great.. let me try to wrap my head around all this and see what works..!

[zmix]

Thanks Guys…

I’m not having any trouble sending the MSB / LSB Sysex to the unit.

That is already working perfectly.

It’s just that the Ctrlr panel shows 462-562 as the values for the mix parameter, for example, (which are the sysex values I am sending across the 10 bits) and the Hardware unit correspondingly displays 0-100%.

What I would like is to have the Ctrlr panel controls to reflect the “real” parameter values (i.e. 0-100%), so looking for a way to “map the displayed values”, or similar etc..

I’d also like those values and parameter names to be visible in the Audio Units Host, which appears broken (?), with every parameter showing up as “undefined” in my DAW (Logic Pro)

[zmix]

Ok, so I want to create a new “method”,, and call it something like “Add462”

What is the syntax to offset the sent value?

Add462 = function(–[[ CtrlrModulator –]] modulator, –[[ number –]] numericModulatorValue)
return numericModulatorValue
end

[zmix]

Yes, exactly… I’m using MS LS to send the values in the sysex stream, and setting the ranges to 462 – 562 (etc) for each parameter…

[zmix]

Perhaps I’m not being clear…

I’m already sending the proper parameter values via sysex (462 – 562, for example)

At the moment the Ctrlr panel fader is displaying those values (462-562) as I move the fader.

The displayed parameter range in the PCM-70 is 0-100.

I would like to have the numbers displayed on the Ctrlr Panel read 0-100, matching the values displayed in the hardware.

After reading the tutorial, I got the impression that the correct way to do this was to assign the onscreen fader’s range to 0-100 and then add 462 to it to transmit the correct values required for the sysex parameter range.

This is how the procedure was described in atom’s tutorials “Expressions in Ctrlr” as “modulatorValue+N”.

I just can’t see where in the editor to change or add to the modulatorValue itself..

I hope this clarifies my conundrum..!!

[zmix]

I posted the Sysex section of the manual in another topic I created when I joined here, but here is a link to the V2.00 manual, the sysex info starting on page 53 looks identical to v3.00

Curious why I can’t make a fader / modulator that goes from 0-100 and add 462 to it?

Is the modifier value for a modulator really limited to 7 bit numbers?

[zmix]

That is a very slick looking panel..!

I’ve tried to cannibalize it for my purposes, only to discover that the PCM-70 will only accept program changes when the “PGM” button on the front panel is lit, but once it receives a sysex message it goes into a sort of edit mode, the PGM button is de-selected and any further program changes are ignored… hmmm…

Possibly will have to proceed by requesting a sysex dump of some specific location (which is only 312 bytes) and then edit the parameters from there using the assigned faders…

I’m a bit unclear about how to map the actual parameter values to the onscreen fader values.. for example, the “mix” parameter, via sysex, has a range from 462 to 562, while the parameter on the PCM-70 displays a range of 0-100. I assumed I could set the onscreen fader to a range of 0-100 the add 462 to it for the sysex range.. It’s a procedure outlined in one of atom’s tutorials “Expressions in Ctrlr” as simply “modulatorValue+N”, but somehow this is not appearing to me in the editable controller settings…

[zmix]

Thanks again for the reply..

Yes, it’s basically using the same parameter numbers and nearly identical ranges, with slight variations from algo to algo..
I suppose Lua is inevitable.. I know *nothing* about it, though.. Looking at other panems will be a great place to start, though so thanks. I was looking at the Lexicon MXP panel when I began but I was unable to see any “code” and it says “Invalid Resource” on the panel itself. The Korg Minilogue panel has a button that requests the current program and loads it into the panel, might be an approach I can modify to my panel?

function loadProgramIntoPanel(midiSysExDump)
— Your method code here
modulatorValues = extractModulatorValuesFromMidiSysExDump(midiSysExDump)

for key, value in pairs(modulatorValues) do
local modulator = panel:getModulatorByName(key)
local component = modulator:getComponent()

if (component:getProperty(‘uiType’) == ‘uiListBox’) then
modulator:setValueMapped(value, true, true)
else
modulator:setModulatorValue(value, false, false, false)
end
–if (key == ‘vco1-octave’) then
–console(tostring(key) .. ” ” .. tostring(value))
–end
end
end

Is there a Lua “library” of such functions?

As an aside, I did discover what I think is a “bug” in that the Panel isn’t passing the parameter names to the DAW when using the Audio Units Component

( here )

So I’m a bit leary to program 7 panels of 29 faders only to have them appear as “undefined” in the control surface I’m using to adjust the parameters..

Is there any way you could verify / debunk this for me?

• This reply was modified 6 years, 7 months ago by zmix.
• This reply was modified 6 years, 7 months ago by zmix.

[zmix]

Thank you so much.. I’ll give this a try..!!

To be specific, I am trying to make it possible to access the basic algos in the unit by selecting a tab and then have the specific set of controls tailored to it

There are 7 different types of programs in the unit, and since there is no direct way to access the underlying algos I plan to have the selected tab send a program change to the unit to select the factory (ROM) preset, and then send the Ctrlr on screen Fader positions. Perhaps you have some procedural advice here, I’ve been unable to get the tab to send a simple program change (I’m such a newbie..!!). I’d like to understand the Ctrlr programming environment better.

[zmix]

The panels work fine both as standalone and within Logic. The assigned parameters are all able to be automated and also are able to be adjusted by using a control surface, such as the Mackie C4.

The issue is that the parameter names are not being passed to the Host DAW, so that rather than seeing a list of all the parameters you’ve assigned, numbered and named (in three places within Ctrlr), and whose names appear in the panel, you see a list of 64 parameters all named “undefined_x”

[Author]

Posts