You didn’t need to modify the original Project file then. Just run the original one on the new system.
If it is still getting through on Pc B. Please open up Bome MIDI Translator Pro with the project file, open the log window, check Incoming, Outgoing, MIDI IN and MIDI OUT.
The send some data so that it can record what is happening. Copy and paste what you see into a text file and I will have a look. Make sure that if you are running Gig Performer on Pc B, you only selected virtual ports in Gig Performer and not the original RTP MIDI port.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
The log window (translates) for all ports 1-9. Im running Gig Performer on PC B buand have Bome Midi Translators 1-9 selected as midi input ports in Gig Performer, but if I don’t also select Faderfox as an input, then nothing happens in the midi “learn” feature
cheers
Jon BMT Pro Log Window.txt (7.6 KB)
Maybe you are looking at the wrong port in Gig Performer? What does your rig manager look like? Are you using it or are your MIDI input blocks hardcoded to the FaderFox?
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi Steve
The rig manager is setup the same as PC A, I believe this is for remapping individual controllers. I’ll contact Deskew (Gig Performer developer). BMT (I believe) Pro is outputting correctly according to the log window…why is this pc different??! Everything seems to be setup the same. Completely stumped
Can you look at the global MIDI monitor in Gig Performer to see if anything is coming in there?
Maybe you can show me the wiring diagram for one of the rackspaces so that we can get a better idea of a MIDI input block that you are using. You could also shoot me a copy of one of your rackspaces and I could take a look on my system.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi Steve
The global midi monitor only shows Faderfox (not translated).
Im not actually using midi input blocks as it happens, Im needing to configure panels that are connected to plugins on a long term basis, not just for an individual project. A preset basically so when you open the plugin, it’s all mapped already.
Many thanks
Jon
OK, so is this on a WIndows machine or a Mac? If on a Windows machine, could you check if any other MIDI applications are running that might be taking over these ports. Best for now to shut down any other MIDI applications besides Bome an GIg Performer. I’ve not seen any issues with GIg Performer not recognizing BMT ports.
You will need to disable FaderFox in Gig Peformer to see the BMT ports however if you are on a Windows machine because Bome needs exclusive access of that port. Maybe that is the problem.
Yeah its a windows pc. The only midi applications I have are the iconnectivity and (I dunno) is the Focusrite interface interfering possibly? The problem is, without those 2, I can’t control the midi on 2 machines, or if I deselect Faderfox from Gig Performer input, Im unable to do the midi “learn” on Pc B. I tried to do this manually but it doesn’t respond on the correct channel/controller.
Is Bome Network the best solution Steve, is there a a reason it didn’t pick up previously? It seems the same issue, that something is blocking it.
Many thanks
Jon
I think the issue we are dealing with is a Windows issue. on RTP MIDI, you need to send output to a port. I assume you are calling this port ‘FaderFox’. Then Bome MIDI Translator needs to be the only thing to access this port. You route using the project file to the various BMT ports in Gig Performer. After deselecting FaderFox in Gig Performer, restart Gig Performer and see if the BMT ports come alive in the GP MIDI monitor. Since the project sends only to BMT ports, this will be crucial. Note that only the BMT port selected with your project file will be sending any data to Gig Performer.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi Steve
I deselected Faderfox and then restarted GP but same result in GP Midi Monitor… I changed the port on rtp from 5020 to 5031, 5032, 3 and 4 but same also. I downloaded this Currpoints freeware and as far as I can see, nothing else was using these ports
Hi, is Bome Network running on Pc B? If it is, shut it down. Maybe it is holding some MIDI ports opened and I don’t think you are using it for anything else.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Just having a change of plan Steve, I’ll make a few changes/workaround and run the 1 BMT Pro from Pc B
I do very much appreciate you taking the time on this. Im with you as well (in my limited knowledge), it has to be a Windows thing. BMT Pro is doing what it’s supposed to do as per the log window. Please may I ask you though?..
Im going to read up and try learn Bome Network and Unlimited Midi Ports as best as I can. Am I right in thinking virtual ports 1-9 can be bundle into groups also? If I get stuck, please can I ask you again?
Many thanks though
Jon
Hi, I just tested your project file with Gig Performer on my PC and it works beautifully so I’m pretty sure something on Pc B is holding your BMT Port open. The only difference is that I use short names so maybe Gig Performer is having problems with the long names. I haven’t tested long names yet.
For your setup, since you are already using RTP MIDI with your iConnectivity (which cannot use Bome Network). I would suggest you keep your configuration as it is. We just need to figure out why it is not working on Pc B.
We can always come back to playing around with Bome Network as you want to expand things.
Can you try closing Gig Perform and then downloading Bome SendSX (free) and see if you can see MIDI traffic from Bome MIDI Translator Pro there?
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks Steve
If I select SendSX midi in as Faderfox, then it reflects partly the BMT Pro log window…but if I select Bome Midi Translator 1 it shows the message attached…
Many thanks
Jon
This confirms that some other application is holding your MIDI port open. Close all other MIDI related applications (except RTP MIDI) one at a time until the error goes away. For RTP MIDI, only leave your faderfox session open.
For Bome Network, go to the menu tray and make sure it is not running in the background.
If you see the icon there, right click on it and select exit.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
