Yamaha O2R button fuctions

What does cubase need
Far Left
Center
Far Right

Sorry what I can do is send the cubase sysex from the pan midi. Left, center Right to the input of Bmt. Can You do something with this?

Maybe. So you are saying when your 02R is center, Cubase is reporting R1. Next increment to the right gives you R7 and 1 increment to left of center is L6?

This will be interesting as there are 32 stops and since it is an even number there will be no center . This might be a special case to define center.

Far left is: F0 43 10 3D 00 00 54 00 00 F7
Center is: F0 43 10 3D 00 00 54 03 0F F7
Far right is: F0 43 10 3D 00 00 54 07 0F F7

Hi try this for your pan test.

All I did is change one rule – I think we are close

From

if pp==1 then qq=qq+64

to

if pp==1 then qq=qq+63


Attachments:
1489437632764_Fader-1-Pan-test-2017-03-13..bmtp

I think I have some interesting discovery the center pan of cubase has a seperate value or something.

SendSX gives these values:

F0 43 10 3D 40 03 08 09 F7
F0 43 10 3D 40 03 08 01 F7

I found out because I never used to hold down the shift button and then pan with the mouse wheel. It gives a precise pan function. The ”C” from center is les lightened. Next step little more and then comes R1 or L1. It’s a little tricky to measure
I Don’t know if this has anything to do with the extra sysex lines.

That looks like entirely different sysex message only 9 bytes.

Also when did the 04 change to a 54? Are you now panning on a different channel? Also byte 8 is showing differently than last type right is now 07 where it was 02 before or are these just typos?

Sorry I didn’t mentioned that the sysex values above in previous message came from cubase maybe to understand what cubase does In Pan center that cubase apparently work with a different sysex in Pan center. These where no messages what came from the O2r.

If I ad up every sysex from the O2r there are actually 33 sysex lines. Somehow cubase can’t get the pan center correct. Logic it wil be 16 left and 16 right and 1 center?

This should be I think Pan far left: F0 43 10 3D 00 04 1D 00 00 F7
Pan L1: F0 43 10 3D 00 04 1D 00 0F F7
Center: F0 43 10 3D 00 04 1D 01 00 F7 and not value 64 because that’s first value from Pan left.
Far R1 F0 43 10 3D 00 04 1D 01 00 F7 and far right F0 43 10 3D 00 04 1D 02 00 F7

I don’t know if I understand it right.

I tryed qq=qq+63. Now center is L1. One right is R6. One left is L6

Well I counted 32 lines (0-31) which makes it difficult to get to exact center. I think the best you will be able to do is play with the value of qq in the above formula until you get it as close as you can. Maybe the device has some sort of fine control capability. What do you see if you turn very slowly from right and left of center?

Hi Steve,

Sorry but I counted 33 lines.

F0 43 10 3D 00 04 1D 00 00 F7
F0 43 10 3D 00 04 1D 00 01 F7
F0 43 10 3D 00 04 1D 00 02 F7
F0 43 10 3D 00 04 1D 00 03 F7
F0 43 10 3D 00 04 1D 00 04 F7
F0 43 10 3D 00 04 1D 00 05 F7
F0 43 10 3D 00 04 1D 00 06 F7
F0 43 10 3D 00 04 1D 00 07 F7
F0 43 10 3D 00 04 1D 00 08 F7
F0 43 10 3D 00 04 1D 00 09 F7
F0 43 10 3D 00 04 1D 00 0A F7
F0 43 10 3D 00 04 1D 00 0B F7
F0 43 10 3D 00 04 1D 00 0C F7
F0 43 10 3D 00 04 1D 00 0D F7
F0 43 10 3D 00 04 1D 00 0E F7
F0 43 10 3D 00 04 1D 00 0F F7
F0 43 10 3D 00 04 1D 01 00 F7
F0 43 10 3D 00 04 1D 01 01 F7
F0 43 10 3D 00 04 1D 01 02 F7
F0 43 10 3D 00 04 1D 01 03 F7
F0 43 10 3D 00 04 1D 01 04 F7
F0 43 10 3D 00 04 1D 01 05 F7
F0 43 10 3D 00 04 1D 01 06 F7
F0 43 10 3D 00 04 1D 01 07 F7
F0 43 10 3D 00 04 1D 01 08 F7
F0 43 10 3D 00 04 1D 01 09 F7
F0 43 10 3D 00 04 1D 01 0A F7
F0 43 10 3D 00 04 1D 01 0B F7
F0 43 10 3D 00 04 1D 01 0C F7
F0 43 10 3D 00 04 1D 01 0D F7
F0 43 10 3D 00 04 1D 01 0E F7
F0 43 10 3D 00 04 1D 01 0F F7
F0 43 10 3D 00 04 1D 02 00 F7

Right you are. Not sure how I missed one.

So center point should be somewhere between 60 and 64. Since output does not have a real center point 0-127 would mean 63.5. 127/2 .

It is really the precision, or lack thereof of the controller that is causing problems here. Is there anything you can do to the knob to make it output smaller increments? Maybe doing something like turning it slowly makes it output different values that we can use as a translator for fine tuning. I think I saw something in the manual regarding parmeter changes that manipulate bit precision other than byte precision. Does the knob ever put something out that looks like this?

F0 43 10 04 04 1D xx F7

Hi Try this.

Comments are in the rules

// Change to values 0-32
rr=pp*16
qq=rr+qq
if pp==2 then qq=32

// Now convert from range 33 to range 128
// Controller output will be 0-124 – Mid point
// Should be 62
// Since Bome does not handle floating point
// We multiply by 10000 then do the math and then
// divide by 10000 at the end
ss=qq*10000
// input range 0-32 = 33
ss=ss/33
// output rang 0-127 = 128
// note that value of larger than 124 will never
// be used so max should be 124 so we can get
// to a true center

ss=ss*128
ss=ss/10000

qq=ss

 

Attached is the project file


Attachments:
1489583506091_Fader-1-Pan-test-2017-03-15..bmtp

I can’t fined anything we’re stuck with this code

Pls see if my latest posted solution works better.

this becomes a little complicated for me right now haha

center from O2r is now L2 in cubase
3: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 00 F7, pp=0x01 qq=0x00
4: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=62

R1 in from O2r in cubase R2
17: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 01 F7, pp=0x01 qq=0x01
18: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=65

Bummer, Maybe you can talk to Yamaha to get some suggestions on how to interface your O2R with Cubase.
I can only work with the limited information (based on your posts) on the output of the O2R. Have you checked their forums/FAQs?

When you tested the new file, did you do a new midi learn in CUBASE?

F0 43 10 3D 00 04 1D 00 00 F7
F0 43 10 3D 00 04 1D 00 01 F7
F0 43 10 3D 00 04 1D 00 02 F7
F0 43 10 3D 00 04 1D 00 03 F7
F0 43 10 3D 00 04 1D 00 04 F7
F0 43 10 3D 00 04 1D 00 05 F7
F0 43 10 3D 00 04 1D 00 06 F7
F0 43 10 3D 00 04 1D 00 07 F7
F0 43 10 3D 00 04 1D 00 08 F7
F0 43 10 3D 00 04 1D 00 09 F7
F0 43 10 3D 00 04 1D 00 0A F7
F0 43 10 3D 00 04 1D 00 0B F7
F0 43 10 3D 00 04 1D 00 0C F7
F0 43 10 3D 00 04 1D 00 0D F7
F0 43 10 3D 00 04 1D 00 0E F7
F0 43 10 3D 00 04 1D 00 0F F7
F0 43 10 3D 00 04 1D 01 00 F7
F0 43 10 3D 00 04 1D 01 01 F7
F0 43 10 3D 00 04 1D 01 02 F7
F0 43 10 3D 00 04 1D 01 03 F7
F0 43 10 3D 00 04 1D 01 04 F7
F0 43 10 3D 00 04 1D 01 05 F7
F0 43 10 3D 00 04 1D 01 06 F7
F0 43 10 3D 00 04 1D 01 07 F7
F0 43 10 3D 00 04 1D 01 08 F7
F0 43 10 3D 00 04 1D 01 09 F7
F0 43 10 3D 00 04 1D 01 0A F7
F0 43 10 3D 00 04 1D 01 0B F7
F0 43 10 3D 00 04 1D 01 0C F7
F0 43 10 3D 00 04 1D 01 0D F7
F0 43 10 3D 00 04 1D 01 0E F7
F0 43 10 3D 00 04 1D 01 0F F7
F0 43 10 3D 00 04 1D 02 00 F7

so we can’t get this value in the middle F0 43 10 3D 00 04 1D 01 00 F7 because that’s the O2r center?

You can try and hard code to see if this works at the end of the rules
if qq===62 then qq=63
or
if qq===62 then qq=64
Since apparently 62 and 65 don’t hit center. These are the only options available to test center

Hi,

I read a thread about problems with pan center in cubase. Indeed the same problems. Also with other controllers. Soms use a dedicated button for the center. I go to look for it tommorow.
Thought to tell you about this.