Different behavior if bome box connecte dto pc or in live mode

SteveC · July 5, 2022, 6:03am

Well my nanoKontrol2 conteoller sends channel select when moving the fader. Maybe your Presonus is also doing that. This will change the Mix selection Using 4.0 through 4-5. So maybe your preset is changing and that is why you can’t get any of the rest to work.

Here is what the log is showing me when I move the first fader.

1: IN   1.0  MIDI 90 18 7F,  vv=0x18
2: IN   1.1  MIDI 90 18 7F,  vv=0x18
3: IN   1.2  MIDI 90 18 7F,  vv=0x18
4: IN   1.3  MIDI 90 18 7F,  vv=0x18
5: IN   1.5  MIDI 90 18 7F,  vv=0x18
6: IN   4.0  MIDI 90 18 7F
7: 4.0:3 ***********SELECTION AUX 1***********
8: IN   4.12  MIDI 90 18 7F
9: IN   9.10  MIDI E0 5F 5F,  oo=0x5F vv=0x5F
10: OUT  9.10  MIDI 9 bytes: B0 63 00 B0 62 17 B0 06 5F
11: IN   9.26  MIDI E0 5F 5F,  oo=0x5F vv=0x5F
12: IN   9.42  MIDI E0 5F 5F,  oo=0x5F vv=0x5F
13: Activated preset 10: Faders Aux 1
14: IN   10.0  on activation of this preset (Faders Aux 1)
15: 10.0:1 ---------DESACTIVATION MAIN LR----------
16: IN   10.1  on activation of this preset (Faders Aux 1)
17: 10.1:1 ---------DESACTIVATION AUX 2----------
18: IN   10.2  on activation of this preset (Faders Aux 1)
19: 10.2:1 ---------DESACTIVATION AUX 3----------
20: IN   10.3  on activation of this preset (Faders Aux 1)
21: 10.3:1 ---------DESACTIVATION AUX 4----------
22: IN   10.4  on activation of this preset (Faders Aux 1)
23: 10.4:1 ---------DESACTIVATION AUX 5----------
24: IN   10.5  on activation of this preset (Faders Aux 1)
25: 10.5:1 ---------DESACTIVATION AUX 6----------
26: IN   10.6  on activation of this preset (Faders Aux 1)
27: 10.6:1 ---------DESACTIVATION AUX 6----------
28: IN   10.7  on activation of this preset (Faders Aux 1)
29: 10.7:1 ---------DESACTIVATION Dafers FX 1----------
30: IN   10.8  on activation of this preset (Faders Aux 1)
31: 10.8:1 ---------DESACTIVATION Faders FX 3----------
32: IN   10.9  on activation of this preset (Faders Aux 1)
33: 10.9:1 ---------DESACTIVATION Faders FX 4----------
34: OUT  4.0  activate preset "Faders Aux 1" (10)
35: Deactivated preset 9: Faders LR
36: OUT  10.0  deactivate preset "Faders LR" (9)
37: OUT  10.1  deactivate preset "Faders Aux 2" (11)
38: OUT  10.2  deactivate preset "Faders Aux 3" (12)
39: OUT  10.3  deactivate preset "Faders Aux 4" (13)
40: OUT  10.4  deactivate preset "Faders Aux 5" (14)
41: OUT  10.5  deactivate preset "Faders Aux 6" (15)
42: OUT  10.6  deactivate preset "Faders FX 1" (16)
43: OUT  10.7  deactivate preset "Faders FX 2" (17)
44: OUT  10.8  deactivate preset "Faders FX 3" (18)
45: OUT  10.9  deactivate preset "Faders FX 4" (19)
46: IN   10.10  MIDI E0 5E 5E,  mm=0xE0 oo=0x5E vv=0x5E
47: 10.10:5 mm : 224

So the fader doesn’t move because you have switched to a different preset than 9.0. What happens if you disable translators 4.0 through 4.5 and translators 9.26 through 9.57 (which would just duplicate and confuse translators 9.10 through 9.25.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 5, 2022, 7:56am

On developement PC I have no trouble. faders move fast when I use translator pro software instead of box.
not for me when I move faders 1 on LR preset this is waht I have

Blockquote1: MIDI IN [PreSonus FP16 1]: 90 68 7F
2: IN 1.0 MIDI 90 68 7F, vv=0x68
3: RULE 1.0:3 condition satisfied: if vv>23 then exit rules, skip Outgoing Action
4: IN 1.1 MIDI 90 68 7F, vv=0x68
5: RULE 1.1:2 condition satisfied: if vv<120 then exit rules, skip Outgoing Action
6: IN 1.2 MIDI 90 68 7F, vv=0x68
7: RULE 1.2:3 condition satisfied: if vv>15 then exit rules, skip Outgoing Action
8: IN 1.3 MIDI 90 68 7F, vv=0x68
9: RULE 1.3:3 condition satisfied: if vv>82 then exit rules, skip Outgoing Action
10: IN 1.5 MIDI 90 68 7F, vv=0x68
11: RULE 1.5:3 condition satisfied: if vv>85 then exit rules, skip Outgoing Action
12: IN 10.10 MIDI 90 68 7F, mm=0x90 oo=0x68 vv=0x7F
13: 10.10:5 mm : 144
14: RULE 10.10:6 condition satisfied: if mm<224 then exit rules, skip Outgoing Action
15: IN 10.15 MIDI 90 68 7F, mm=0x90 oo=0x68 vv=0x7F
16: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
17: IN 10.16 MIDI 90 68 7F, mm=0x90 oo=0x68 vv=0x7F
18: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
19: MIDI IN [PreSonus FP16 1]: E0 35 67
20: IN 10.10 MIDI E0 35 67, mm=0xE0 oo=0x35 vv=0x67
21: 10.10:5 mm : 224
22: RULE 10.10:8 expression: (mm=mm-224) = 0
23: RULE 10.10:9 expression: (oo=64+gs) = 64
24: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 67 F7
25: IN 10.15 MIDI E0 35 67, mm=0xE0 oo=0x35 vv=0x67
26: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
27: IN 10.16 MIDI E0 35 67, mm=0xE0 oo=0x35 vv=0x67
28: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
29: MIDI IN [PreSonus FP16 1]: E0 7B 66
30: IN 10.10 MIDI E0 7B 66, mm=0xE0 oo=0x7B vv=0x66
31: 10.10:5 mm : 224
32: RULE 10.10:8 expression: (mm=mm-224) = 0
33: RULE 10.10:9 expression: (oo=64+gs) = 64
34: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 66 F7
35: IN 10.15 MIDI E0 7B 66, mm=0xE0 oo=0x7B vv=0x66
36: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
37: IN 10.16 MIDI E0 7B 66, mm=0xE0 oo=0x7B vv=0x66
38: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
39: MIDI IN [PreSonus FP16 1]: E0 41 66
40: IN 10.10 MIDI E0 41 66, mm=0xE0 oo=0x41 vv=0x66
41: 10.10:5 mm : 224
42: RULE 10.10:8 expression: (mm=mm-224) = 0
43: RULE 10.10:9 expression: (oo=64+gs) = 64
44: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 66 F7
45: IN 10.15 MIDI E0 41 66, mm=0xE0 oo=0x41 vv=0x66
46: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
47: IN 10.16 MIDI E0 41 66, mm=0xE0 oo=0x41 vv=0x66
48: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
49: MIDI IN [PreSonus FP16 1]: E0 15 66
50: IN 10.10 MIDI E0 15 66, mm=0xE0 oo=0x15 vv=0x66
51: 10.10:5 mm : 224
52: RULE 10.10:8 expression: (mm=mm-224) = 0
53: RULE 10.10:9 expression: (oo=64+gs) = 64
54: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 66 F7
55: IN 10.15 MIDI E0 15 66, mm=0xE0 oo=0x15 vv=0x66
56: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
57: IN 10.16 MIDI E0 15 66, mm=0xE0 oo=0x15 vv=0x66
58: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
59: MIDI IN [PreSonus FP16 1]: E0 78 65
60: IN 10.10 MIDI E0 78 65, mm=0xE0 oo=0x78 vv=0x65
61: 10.10:5 mm : 224
62: RULE 10.10:8 expression: (mm=mm-224) = 0
63: RULE 10.10:9 expression: (oo=64+gs) = 64
64: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 65 F7
65: IN 10.15 MIDI E0 78 65, mm=0xE0 oo=0x78 vv=0x65
66: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
67: IN 10.16 MIDI E0 78 65, mm=0xE0 oo=0x78 vv=0x65
68: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
69: MIDI IN [PreSonus FP16 1]: E0 3D 65
70: IN 10.10 MIDI E0 3D 65, mm=0xE0 oo=0x3D vv=0x65
71: 10.10:5 mm : 224
72: RULE 10.10:8 expression: (mm=mm-224) = 0
73: RULE 10.10:9 expression: (oo=64+gs) = 64
74: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 65 F7
75: IN 10.15 MIDI E0 3D 65, mm=0xE0 oo=0x3D vv=0x65
76: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
77: IN 10.16 MIDI E0 3D 65, mm=0xE0 oo=0x3D vv=0x65
78: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
79: MIDI IN [PreSonus FP16 1]: E0 20 65
80: IN 10.10 MIDI E0 20 65, mm=0xE0 oo=0x20 vv=0x65
81: 10.10:5 mm : 224
82: RULE 10.10:8 expression: (mm=mm-224) = 0
83: RULE 10.10:9 expression: (oo=64+gs) = 64
84: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 65 F7
85: IN 10.15 MIDI E0 20 65, mm=0xE0 oo=0x20 vv=0x65
86: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
87: IN 10.16 MIDI E0 20 65, mm=0xE0 oo=0x20 vv=0x65
88: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
89: MIDI IN [PreSonus FP16 1]: E0 03 65
90: IN 10.10 MIDI E0 03 65, mm=0xE0 oo=0x03 vv=0x65
91: 10.10:5 mm : 224
92: RULE 10.10:8 expression: (mm=mm-224) = 0
93: RULE 10.10:9 expression: (oo=64+gs) = 64
94: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 65 F7
95: IN 10.15 MIDI E0 03 65, mm=0xE0 oo=0x03 vv=0x65
96: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
97: IN 10.16 MIDI E0 03 65, mm=0xE0 oo=0x03 vv=0x65
98: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
99: MIDI IN [PreSonus FP16 1]: E0 66 64
100: IN 10.10 MIDI E0 66 64, mm=0xE0 oo=0x66 vv=0x64
101: 10.10:5 mm : 224
102: RULE 10.10:8 expression: (mm=mm-224) = 0
103: RULE 10.10:9 expression: (oo=64+gs) = 64
104: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 64 F7
105: IN 10.15 MIDI E0 66 64, mm=0xE0 oo=0x66 vv=0x64
106: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
107: IN 10.16 MIDI E0 66 64, mm=0xE0 oo=0x66 vv=0x64
108: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
109: MIDI IN [PreSonus FP16 1]: E0 57 64
110: IN 10.10 MIDI E0 57 64, mm=0xE0 oo=0x57 vv=0x64
111: 10.10:5 mm : 224
112: RULE 10.10:8 expression: (mm=mm-224) = 0
113: RULE 10.10:9 expression: (oo=64+gs) = 64
114: MIDI OUT [BomeBox: dLive PAT]: F0 00 00 1A 50 10 01 00 00 0D 00 02 40 64 F7
115: IN 10.15 MIDI E0 57 64, mm=0xE0 oo=0x57 vv=0x64
116: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
117: IN 10.16 MIDI E0 57 64, mm=0xE0 oo=0x57 vv=0x64
118: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action
119: MIDI IN [PreSonus FP16 1]: 90 68 00
120: IN 10.10 MIDI 90 68 00, mm=0x90 oo=0x68 vv=0x00
121: 10.10:5 mm : 144
122: RULE 10.10:6 condition satisfied: if mm<224 then exit rules, skip Outgoing Action
123: IN 10.15 MIDI 90 68 00, mm=0x90 oo=0x68 vv=0x00
124: RULE 10.15:2 condition satisfied: if go!=16 then exit rules, skip Outgoing Action
125: IN 10.16 MIDI 90 68 00, mm=0x90 oo=0x68 vv=0x00
126: RULE 10.16:2 condition satisfied: if go!=32 then exit rules, skip Outgoing Action

patrice.cognet · July 5, 2022, 8:32am

It’s very strange.
Connected to my developemnt PC, it’s working.
I mean
Translator pro open with program connected to lan
Bome box connected to lan and no project running
Presonus connected to usb hub powered and this hub connected to developement PC
Dlive connected to lan.
Everything works perfectly.

Maybe router problem ???
I have to check config of wifi routeur.

Peter.Ostry · July 5, 2022, 10:08am

Do you need WiFi for this installation? If it is possible to work locally (cabled) without WiFi, you may try one of those small Ethernet switches you can get everywhere. This gives you a stable independent LAN.

patrice.cognet · July 5, 2022, 1:08pm

I don’t neeed wifi for this part by I need it to conencted the ipad apps from allen and heath.
for presonus, I use only wire. I’m doing some test.
on my dev PC with presonus connected to box and translator running on box, it’s seems working fine.
On live router and with translator running program, I have problkem.
Very strange. no rule on this router. BI grouter with quand core made for gamer. No routing, not firewall.
what is very strange is only for faders from presonus to dlive.
in the oposite side it’s working perfectly.

SteveC · July 5, 2022, 3:12pm

Hi, could you try putting an outgoing delay on translator 10.10 of 100ms then try fader 1 again and see if that helps? Maybe BomeBox is sending SysEX faster than the dLive can handle it?

Again, according to you log, this is not using Faders LR preset (9). It is using Faders Aux 1 preset (10).

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 5, 2022, 4:23pm

For debug I installed the translator pro on my live PC. How can I move my licence from my dev PC to live PC for test ?
Thanks

SteveC · July 5, 2022, 4:28pm

Hi,

Just log into your Bome Account and go to your “Products” Page.

The Bome Account is not automatically created with purchase. Just create one here:
https://www.bome.com/account
Normally, your product license and download will be automatically accessible. Only if you’ve used a different email address at time of purchase, just create an account with your current email address and then use the Add Product function in your user account to claim your license.

Note: after creating your account, your licenses will only be available after clicking the activation link in the activation email! You can also use the Lost Password function to activate your account.

Only when your account is activated, you can view your license(s), download the latest version, and add missing licenses

You can load MT Pro on multiple computers but should only use on one at any given time (unless you have purchased multiple licenses.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 6, 2022, 8:12am

Hi steve,

Definitevely the problem come from the box. I installed trasnlator pro on my live pc, here after conf :

PC on routeur
bome box on routeur via ethernet
presonus connected to PC via USB
translator running on pc
ipad connected to rtouer via Wifi
Dlive director open on PC

Everyhing working well.

If I connect presonus via usb hub powered and load the project into box, shutdown translator and bome network, then It’s working jerkly and slowly.

Any idea ?

SteveC · July 6, 2022, 3:04pm

OK, I’m beginning to think that this may be network related.

In the configuration without your BomeBox you are connecting to dLive using dLive Director only and not the BomeBox to dLive interface.

In the configuration with the BomeBox, it appears you may have 3 separate dLive connections.

From dLive Director to dLive
From BomeBox to dLive.
dLIve Mixpad to dLive

I assume that your iPad is communicating with dLive through dLive director through the A&H protocol so that when you additionally connect your BomeBox, there may in fact be 2 different connections formed that are interfering with each other? I really don’t know how dLive director works so maybe there is something there that needs to be re-configured to communicate to dLive using the BomeBox interface instead of direct wireless interface. I’m just speculating here as I really don’'t have the gear that you have to test this configuration.

Do you know:

How dLive director connects between your PC and your dLive device?
How your iPad connects with dLive Director?

Maybe looking at your open network connections and ports using your PC could get to the bottom of this.

I suspect there are conflicting MIDI message coming over different interfaces when using BomeBox.

I will escalate this issue to see if additional help may be needed.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 6, 2022, 4:23pm

Dlive directr is connected via Ethernet connexion. When We open the software, we can conenct to dlive by the IP adress.
Ipad is connected to dlive not on dlive director. I can stop dlive director and work with ipad or stop ipad and work with dlive director.
This is made for using several ipad and different dlive director.
it is mention of support, Dlive can accept 40 TCP connection.
the quick fix is to use with PC during the time we find the problem but I want to remove pc one day.
Thanks,

SteveC · July 6, 2022, 4:41pm

I suspect that maybe dLive is sending MIDI back to iPad on one network connection and also sending MIDI back to BomeBox on another midi connection which is then also trying to update iPad data. I’m not sure, I’m glad it is working with PC and have escalated the issue to see if we can figure out why it is not working on BomeBox.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 7, 2022, 7:34am

Hi steve,
I’m not sure about your theroy because when I use the PC, I also open Dlive director and ipad. And I have no problem. It is when I put my project into box. the only change is project runing on pc it’s working, project running on bow doesn’t work. But Maybe I’m wrong.
regards

SteveC · July 7, 2022, 4:14pm

Hi, you may be right but here are some steps we can take to attempt to isolate the issue.

First of all set up your BomeBox as follows:

Unload/Close the project file
Disable Automatic Routes
Allen&Heath Page, disable Auto-Create MIDI routes

Then try running these tests

A) A&H connected to BomeBox, Presonus connected to computer
B) A&H connected to BomeBox, Presonus connected to BomeBox

Use Bome Network Remote Direct MIDI to connect the from computer to the MIDI devices.

They should show up similar to the below but with the names of your devices.

Bome Network with Presonus connected to BomeBox (in my case, nanoKontrol2)

MT Pro Alias Setup

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz

patrice.cognet · July 8, 2022, 3:13pm

Hi steve,
in the test with everything connected to bome box, I close Bome network and MT pro software right ?

Thanks,

patrice.cognet · July 8, 2022, 3:38pm

Ok I understand.
My bome box connected to my router and to dlive.
Test A) everything works
Test B) slow and jerky.

Pat

SteveC · July 8, 2022, 8:27pm

OK, so in both cases, you were running the project on your PC right?

Steve

patrice.cognet · July 9, 2022, 6:25am

Yes.
A) Bomebox connected to dlive on In port and out port to routeur, presonus connected to PC usb port.
MTP on PC

B) Bomebox connected to dlive on In port and out port to routeur, presonus connected to BomeBox usb port.
MTP on PC with alias change for presonus

SteveC · July 14, 2022, 6:24pm

@patrice.cognet

Could you put a 50ms delay on the output of translator 9.10 while running on BomeBox and see what happens? This should be Faders LR Fader 1.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services: bome@sniz.biz