Yamaha O2R button fuctions

Hi,

I have a question about programma buttons from the Yamaha O2R

It seems the Sysex data from on/off buttons have 3 code's

Fader channel 1 button on/off

In on mode it's: (When channel led is illuminated from the O2R)

F0 43 10 3D 19 00 03 01 F7 F0 43 10 3D 40 03 0B 08 F7 F0 43 10 3D 19 00 03 00 F7

Off mode it's:

F0 43 10 3D 19 00 03 01 F7 F0 43 10 3D 19 00 03 00 F7 F0 43 10 3D 40 03 0B 00 F7

I want to use it as mute or on/off fuction in Cubase

Can you give me a suggestion how to write the correct translator code in Bome's midi translator pro?

 

Many regards,

 

Siem te Voortwis

 

 

 

Well it looks like 2 of the 3 sysex strings are the same so i would focus on the one that is different.

The string you want to manipulate is this one

For On pp would be

F0 43 10 3D 40 03 0B pp F7

Where value of pp is 08 for on or 00 for off

So your output would be something like this

F0 43 10 3D 19 00 03 01 F7
F0 43 10 3D 40 03 0B pp F7

F0 43 10 3D 19 00 03 00 F7

Setting pp to 08 or 00 depending on whether you want on or off

Not sure if the other  two message are required because I’m not familiar with what they do with your device.
I may be able to find out if the user manual documents it.

Here is a project file I use note on to mute and note off to unmute

 

If this solves your issue please mark as resolved.

Thanks for your help. I try it tommorow. 😉

Hi steve,

I am very new with working with sysex so far so good.
I have another question about setting up the pan controller for each channel.
I did it the same way like the fader setiings in midi translator rules:
pp=pp*16
pp=pp+qq.

With the pan dial on my O2r in cubase it flips immediately to the right channel
Maybe some rule change? The code from channel 1 pan is:

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

maybe you can help me with this?

Thank you!!

Well it looks like byte 8 is the most significant byte of the pan value and byte 9 is least significant value. Can you show me the values at: -far left -midpoint -far right I imagine we will need to set up a translator the does something takes a input value of 0-127 and then use that value to set up the values of byte 8 and byte 9 of the sysex messages above. We will need to figure based on what the 02R expects the values of these two bytes. The main thing that confuses me is the last value above.

Thanks for helping,

for the clearance i am sending the code from O2r to cubase.
The code you sent me was the other way arround

far left value is: F0 43 10 3D 00 04 1C 00 00 F7
midpoint is: F0 43 10 3D 00 04 1C 01 00 F7
far right value is: F0 43 10 3D 00 04 1C 02 00 F7

I send you the bome file what i have done so far
I did something different with the on/off function, but it works.

Greetings,

Siem

Thanks for helping,

for the clearance i am sending the code from O2r to cubase.
The code you sent me was the other way arround

far left value is: F0 43 10 3D 00 04 1C 00 00 F7
midpoint is: F0 43 10 3D 00 04 1C 01 00 F7
far right value is: F0 43 10 3D 00 04 1C 02 00 F7

I send you the bome file what i have done so far
I did something different with the on/off function, but it works.

Greetings,

Siem

OK so it looks like maybe byte 8 is 00 for left 01 for center and 02 for right. I suspect byte 9 will always be between 00 and 0F but this is still a bit of a puzzle I wold have thought far right bytes would have been 02 0F instead of 02 00. Is one stop down from far right 01 0F? Maybe 02 00 has some other meaning? Let me know and I will see if I can figure a solution.

I anticipate you want input to be from some controller with value of 0-127.

Try this in your fader 1 pan rules. Then use qq as your output value qq=qq*4 if pp==1 then qq=qq+64 if pp==2 then qq=127 I didn’t realize you were using the 02R for input and wanted to translate to some other cc/note on output. I thought it was the other way around.

I can’t figure this out. do I have to make 3 tranlator files for left center and right ?

I am totally new with this my apologize.

Maybe you can wright me the right file for me? And then I can try.

You should only have to have one but again, I don’t have the device so I cannot test. Maybe if you turn on logging and the copy and past the log file to a text file and add descriptions within showing what you are doing at various points?

Hi, I created the below file since I don’t have an 02R for testing.

Translator Emulator is meant to try and emulate the output of your 02R based on a general controller I’m using. It takes a controller input values of 0-127 and then tries to emulate the Sysex output of your 02R. I feed that back into BMT to do the testing for the other translator.  Sent to midi yoke1

Fader test is I believe close to what you want. It takes input from midi yoke 1 in the translator above and then turns it back to a cc value

 

I disabled your original fader pan translator

Hopefully this will help you.

 

Thanks! I Will try it tommorow. I let You know if it does the trick!

So I was curious and had to try it!
Cubase is responding to left and right. But the center is a little of in cubase. The center is now 1 to the right. and one dial to the right is R7 and one dial to the left is L6. I see that in cubase there are 99 steps to the left and 99 steps to the right. Something with the scaling isn’t the same as the O2r?

Well it appears that there is different precision withe the output of the 02R. It looks like 02R only has 32 settings and I’m pretty sure cubase would have 127 maybe more. Is there a way you can change the output of the 02R to have better precision? I find this by looking at values of your input 00-0F (only 16 increment left and 16 increments right) We would have to do some other range variation calculations to convert to 99 left and 99 right but the precision would not change.

I think you might be able to re-assign what the 02R send. Check out page 192 and 303 of you the Yamaha 02r96v2 guide. Without having the unit, it is difficult to me to understand or experiment.

I think older version of 02R you cannot assign controllers but I found this in the 02R1E manual. Maybe your faders need re-calibration Fader Calibration This operation allows you to calibrate the faders. 1. Turn the 02R power off. 2. Press and hold the [ENTER] button, then turn the 02R power back on. The faders will calibrate themselves. page 170 (pdf page 280) Maybe look and see if the output has changed after re-calibration.

I reset the faders from the O2r seems nothing changed. For me it’s only important that the Pan dial is properly scaled to cubase. If it is only 16 steps left and right so it be. I think that’s the limitation of the pan dial from the O2r. I can give you the log file with control output.
first wat I did is from center to left with this value range:

1: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0F F7, pp=0x00 qq=0x0F
2: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=60
3: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0E F7, pp=0x00 qq=0x0E
4: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=56
5: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0D F7, pp=0x00 qq=0x0D
6: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=52
7: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0C F7, pp=0x00 qq=0x0C
8: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=48
9: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0B F7, pp=0x00 qq=0x0B
10: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=44
11: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 0A F7, pp=0x00 qq=0x0A
12: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=40
13: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 09 F7, pp=0x00 qq=0x09
14: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=36
15: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 08 F7, pp=0x00 qq=0x08
16: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=32
17: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 07 F7, pp=0x00 qq=0x07
18: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=28
19: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 06 F7, pp=0x00 qq=0x06
20: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=24
21: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 05 F7, pp=0x00 qq=0x05
22: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=20
23: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 04 F7, pp=0x00 qq=0x04
24: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=16
25: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 03 F7, pp=0x00 qq=0x03
26: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=12
27: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 02 F7, pp=0x00 qq=0x02
28: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=8
29: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 01 F7, pp=0x00 qq=0x01
30: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=4
31: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 00 00 F7, pp=0x00 qq=0x00
32: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=0

Next from center to right.

1: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 01 F7, pp=0x01 qq=0x01
2: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=68
3: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 02 F7, pp=0x01 qq=0x02
4: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=72
5: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 03 F7, pp=0x01 qq=0x03
6: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=76
7: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 04 F7, pp=0x01 qq=0x04
8: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=80
9: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 05 F7, pp=0x01 qq=0x05
10: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=84
11: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 06 F7, pp=0x01 qq=0x06
12: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=88
13: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 07 F7, pp=0x01 qq=0x07
14: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=92
15: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 08 F7, pp=0x01 qq=0x08
16: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=96
17: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 09 F7, pp=0x01 qq=0x09
18: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=100
19: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0A F7, pp=0x01 qq=0x0A
20: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=104
21: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0B F7, pp=0x01 qq=0x0B
22: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=108
23: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0C F7, pp=0x01 qq=0x0C
24: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=112
25: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0D F7, pp=0x01 qq=0x0D
26: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=116
27: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0E F7, pp=0x01 qq=0x0E
28: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=120
29: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 01 0F F7, pp=0x01 qq=0x0F
30: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=124
31: IN 0.2 MIDI 10 bytes F0 43 10 3D 00 04 1D 02 00 F7, pp=0x02 qq=0x00
32: OUT 0.2 Control Change on ch. 1 with CC#:50 (0x32) and value:qq=127

Maybe you can do something with this?

So we are not done yet!! The Eq section is also al little complicated in my opinion.
But first finish the pan controls!! 🙂 🙂

I really appreciate that you spent some time for helping me setting up the mixer!!!

Many thanks!!

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

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

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.

it’s probably also a good idea to start a new question/answer thread for new (follow-up) questions.
Thanks.

Hi Steve,

That last code you send me did the trick according to the center pan.

I forgot to change the value to 124!!!

Nice job it’s perfectly centered now!!

Good to know. Thanks!