Gotcha!
Hi, I\'d like you to try a few things for me.
- Try the attached file. I went to the project level and checked the default ports for Push Port 1 Push User Port and Pyramid (both input and output). Hopefully this will force MT Pro to open all of these ports and keep them open so that Ableton Live or any other software or device should not be able to use them directly.
- See if you can move your Pyramid or Push to a different USB hub or directly to the computer. I suspect one of these ports may be drawing too much power forcing the other device to go offline when you open them. I\'ve seen this a few times before and maybe even with the Pyramid Squarp. I just can\'t remember. I have purchased a USB power monitor like this that tells me how much power a given device is drawing. I have a few devices that are a bit power hungry and sometimes cause adverse effects on other devices on the same hub. I well designed USB hub, however should prevent this.
PS. Except I probably should have used the aliases instead of the real ports. In my case I\'m using named virtual ports (a feature coming in Bome Network) since I don\'t have the real devices attached.
Attachments:
1586705117223_Queen-st-latest-2020-04-12.bmtp
](https://www.bome.com/wp-content/uploads/cma_attachments/1586705129524_ports-open-always.png){kind=link}
Thanks for your ideas, i tried with the checking the default devices to no effect. the ports still drop out on new one connecting. the new one can even be Ableton. i also tried this with the aliases checked instead then turned it off and on again but same result. it would work sometimes but always one of the pathways doesnt work.
push user port--> squarp
or
clock from pyramid -->Live
or
Push user port --> push user port for lights.
the one that drops out depends on which order they were started in.
i put one device on a powered usb hub and the other on the computer but that didnt change anything either. They still cycle their connections when i start the other. and Live always 'grabs' Abelton port 1 and 2 as default on opening. i cant stop this behaviour without removing the remote midi scripts from the Live folder. but this means i cant use push in Ableton.
I tried all this on the Beta from Florian.
Why would an output string say (port closed) in the Log window but open in the midi input section? this happens for one input at a time. can be squarp or push. it chnages with the order they started in.
i cant see why it will work for hours sometimes but then a save and set all to default setting and open it again the next day and it no longer works..appreciate all your time guys
thanks
brett
I’ll discuss with Florian Bomers to see if he has any ideas.
The MIDI input section information is derived from the MIDI engine.
The log window is derived from the user interface and is obviously not in sync with the MIDI engine if it shows it is closed wile the MIDI engine shows it as open.
Its working now! It still freaks out with starting programs and losing ports but it seems to regain them.
I think i have to have the Default Push Ports AND all the virtual ports they are using for access to and from Live Checked in Project default Midi Inputs and outputs. This seems to allow Live to access it to allow access and to functionality in Live and in MTP via the 'to/from push User port' alias.
I have also routed the inputs and outputs 'to/from Push Port 1' with "Bome Virtual port 1" to allow access at any time for Live.
FYI what i did included:
1-----installing Beta from Florian (thanks mate!)
2----cleaning up aliases-using clear names 'from......' 'to......'
3-----Check to enable Project Default Midi ports the following ports only.
(no aliases checked for Push or Pyramid)
-Ableton Push 1 (input and output)
-Ableton Push User port (input and output)
-Bome Midi Translator 1 Virtual In (input and output)
-Bome Midi Translator 1 Virtual out (input and output)
-Bome Virtual Port 2-->Bome Midi Translator 1 Virtual out (input and output)
-Bome Virtual Port 2-->Bome Midi Translator 2 Virtual out (input and output)
-Pyramid MIDI USB (Input and output)
***Im not sure if i need all of these checked and some might be responsible for the remaining port drop issue. But im stoked its working and im scared to change anything in the name of tidying it up. Having said that if you see any glaring things let me know.
4---- Routed the inputs and outputs of 'to/from push Port 1' with "Bome Virtual port 1"
5-----In Ableton select Push and BMT 1 connections in the 'control surfaces' section in Preferences. It will automatically map the Default ports in slot 2 for me with another Push selected. I have to manually change the second Push that appears with the default ports set (Ableton Push 1 and User) to 'None' but leave the default ports in place. Then save as default set. its holding at the moment but will change with updates.
Hope this helps if anyone has a similar issue. Steve and Florian were amazingly prompt and helpful. Kudos to the customer support at Bome and these forums. You the Bome!
Attachments:
1586753451425_Queen-st-latest.bmtp
](https://www.bome.com/wp-content/uploads/cma_attachments/1586754236466_Screen-showing-Live-Settings-and-Project-Default-Midi-settings.png){kind=link}
Hi, I did some testing on Live 10 with my Windows 10 PC today.
I found that once Ableton Live can open a port it will never release the port unless you restart Live. It also insists on defining a MIDI Remote Script if the device with a supported script is preset.
For instance. If I have an APC-MINI plugged in and Live sees it before the port is open, it trys to use the script and opens tries to open the port. If Ableton cannot open the port it just turns the port orange showing the error. You can then define another port (like BMT1) for the script.
However, if it successfully opens the APC-MINI port there is no way to close the port in Ableton Live shutting down and restarting Ableton Live again with the port being used by another application.
This means in MT Pro, at the PROJECT level, any ports you do not want Ableton Live to \"steal\", you must put a check mark by that port so that it is ALWAYS OPEN in MT Pro BEFORE opening Ableton Live 10. The second you close it in MT Pro, Ableton Live 10 will try to open it (unless you have redefined it to use another port) and then you will be hosed in MT Pro unless you close and reopen Ableton Live with MT Pro already having the port open.
In your case this means at the PROJECT LEVEL you must have Push 2 Port 1 - Push 2 User Port and Squarpy Pyramid open in MT Pro at the project level, before starting Live.
As far as I could tell the current Beta version of MT Pro (1.8.5) behaves correctly as far as opening and closing ports as long as you remember this rule. I have not tested with 1.8.4 yet but will try that tomorrow. I have also not tested either 1.8.4 or 1.8.5 (Beta) on Mac. I\'ve been using 1.8.4 with Ableton Live 9 on Windows 10 PC since it came out and never ran into this issue so I think it is OK. We are also not getting any reports of problems so maybe most people are still running Live 9 or earlier.
Until today I was running Ableton Live 9 so did not see this problem. It looks like Live 9 properly releases MIDI ports once you uncheck them.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Ha, it looks like our posts crossed paths. I’m pretty sure we are on the right track.
“You the Bome!” 
hehe. Happy to see you made good progress!