w5 byte (RackAttack checksum)

[zeoka]

Hi Atom

Your checksum calculation as a byte in the sysex editor is a great idea and works as expected

However it seems it just lacks a byte  :

32(20h)+32(20h)+0(00h)+0(00h)+53(35h)=117 (75h) sound1 volume

ctrlr : 85(55h)   difference : 32 (20h)

32(20h)+32(20h)+5(05h)+0(00h)+87(57h)=156-128 ( if>127)=28 (1ch) fxmix sound6

ctrlr : 123(7bh)  difference : 32 (20h)

37(25h)+32(20h)+0(00h)+0(00h)+12(0ch)=81 (51h) fx1 delay:sync

ctrlr : 44(2ch)   difference : 37 (25h)

33(21h)+32(20h)+0(00h)+0(00h)+20(14h)=85 (55h) trigger A sound

ctrlr : 52(34h)   difference : 33 (21h)
–Checksum value at midi value 0

I could do that in” called when receive midi” but a different method could be more effecient

Please is it possible to add the first byte in w5 ?

Or a way to create own byte for the sys ex editor ?

Then the drumsynth could be used to automate as well as the Ctrlr gui or  NI’s vst controllers  too

PS : the last nightly(since1285) versions dump very well for me…….. incredible work !

I will upload the panel soon 🙂

 

[atom]

What if you use “w6” it will count 6 bytes, the x in wx is a variable.

[zeoka]

Thank you Atom

So w counts bytes before it. It does mean w6  works with the Waldorf Q series  too.

I’ve tried and changed many params yet.

Ctrl to RA way: it ‘s just perfect ( it seems the RA “prefers” checksum than f7)

RA to Ctrlr way : strange….

RA midi value: 0    Ctrlr : 127

RA midi value: 1    Ctrlr : 0

RA midi value: 1 to 64   Ctrlr :goes to 127

RA midi value: more than 64 Ctrlr : nothing

I’ve checked values and checksums from RA and all is correct except

some jump values from RA old encoders but it’s not a problem normally.

I don’t know what’s happen…

 

[atom]

If i can help somehow let me know.

[zeoka]

Cool

May be this byte is simply not done to receive data ?

Or i must do something in “called when panel receive midi” ?

I’ve done a correction for params that don’t start by 0 to receive the corect value ;may be i must do the the same thing but to assign to all my params it ‘s too long..

I’ve found a param that the checksum is identical to the value

and  Ctrlr count double   1=2 , 2=4  ,3=6 etc…

What can i do ?

 

[atom]

If i understood what you mean i’d help but i’m afraid i don’t. You need to explain this better to me.

[zeoka]

 

To be clear Ctrlr double the value of modulators(with w6 byte) when it receive midi from the synth.

Possibilty to divide by 2 in LUA ?

 

 

[atom]

Possibly didive by two in the expression property (there are 2 expression properties for each modulator, test them and see what you can achieve with them)

[zeoka]

Hello Atom !

I’ve tried expression for the first time , this is a cool thing .

I will use it instead LUA(LUA works well however)  for modulators

wich don’t start by zero and must be corrected to receive  right values from synth.

But not solve the problem i’ve .

Well i’ve understand what happens on those  3 modulators:

RA value=0  RAchksm=75    Ctrlr value=117 (75h)

RA value=0 RAchksm=76    Ctrlr value=118 (76h)

RA value=0 RAchksm=77    Ctrlr value=119 (77h)

It appears that Ctrlr has chosen the w6 as value !

 

 

[zeoka]

Hi Atom

midiValue/2 expression works only with mods that have checksum equal to value

it seem’s modulator receive xx + w6 like a value  but when i do

midiValue – (value of checksum at 0 value) this not working correctly or midiValue + (127 -value of checksum at 0 value)

i’m lost  , what can i do ?

Even if there  is a solution with expressions  i must do for all mods

Nothing to do at the panel level ?

 

[atom]

I fixed this issue, but you’ll have to wait for a new nightly build.

[zeoka]

Very nice Atom thank you !

 

[zeoka]

Atom

Oh i was stupid : you had writen in the sysex editor how the checksum byte works !

Can you say in this post or changelog when you update Ctrlr with your fix ?

Thank you

 

 

[atom]

This should be fixed in whatever nightly is the latest, give it a try.

[zeoka]

Thank you Atom it seems you have put the fix in Rev1334 or earlier

This is working  correctly and even good  , however there is a differerence of just 1 value

Ex : The device sends  a value of  85    Ctrlr display  a value of 84

This is great to use the device itself as controller for the vsthost a side of Ctrlr

An old dream that Ctrlr render possible !

[atom]

There might be a formula at play or something else. Remember that values start at 0 so 84 is really 84 if you count from 0.

[zeoka]

84 is the 85th value in ctrlr and 85 is the 86th value of rackattack  so i have a difference between the two.

I don’t use LUA for mods i had  checked .  Raaah just 1 value !

[Author]

Posts