I am only able to start BMT once after install, then it refuses to start on any subsequent attempts. I can only get it to run again by removing it using App Cleaner to get all associated files, restart the computer and re-install. Then it will ony run only the first time again. After that it just shows the splash screen and gets no firther. I have to force quit.
Running OS X Mojave and latest BMT version.
I hope you can help. Let me know if you need a crash log (and where to find it). Thank you
Hi,
Try removing the .bmts files from the folder /Users/USERNAME/Bome and then restart MT Pro.
My guess is you have a corrupt .bmts file in that folder.
Also, when you open an a project. Try a different project than the one you were working on. If for some reason, you did something that causes a race condition in the project, you will continue to have problems. If you want you can post your last project file here and I can have a look at it and see if there is something abnormal causing this problem.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Any luck?
Sorry, it's been AGES until I was able to get back to the computer that was having issues. I have no Bome folder in my user folder any more but it still won't start up
Dan
Sorry the files to remove are in
/users/Username/Library/Application Support/Bome
You should be able to remove that entire folder and then re-install MT Pro.
If there is a specific project file that is causing this problem, please post it. First try opening a different project file.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Absolutely no luck. I’ve deleted all associated files, including the folder mentioned in my user/Library/Application Support. Removed all presets and restarted. But I get the same behaviour. I can start Bome once, but not a second time. Even if I don’t create any presets, so it should just be loading in it’s blank, innitial state on the second load. It just hangs completely and has to be force quit.
MacOS Mojave 10.14.6, most recent version of MT.
Really hope you can help solve this
Hi,
Two things to look at.
/Users/USERNAME/Library/Application Support/Bome/Bome MIDI Translator Pro.bmts
2. Try disabling your computer antivirus program temporarily to see if this fixes the issue. Check to see whether Bome MIDI Translator Pro was quarantined by your antivirus software and if it was, add an exception. I've not seen this with MT Pro in the past but I guess there is always a first time.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
There are currently 3 .bmts files in that folder. This is after another clean install and restert, succesfully opening BMT only once, then trying to open again to make sure the problem still existed. I've not edited a preset or made any changes while the program was open. I then removed all MIDI devices from my system and attempted to open one more time, still unsuccesful.
I don't have any virus software on this mac yet, it's been on my to do list, but as I've not got around to it it won't be causing problems just yet.
The only MIDI prost showing on my system now are virtual ports created by Neyrink V-Control for my Raven.
Thanks for your help
Dan
Can you see the process "MIDI Translator" in your Activity Monitor? Is there a MT Pro Icon on the top of your screen or in your menu tray?
No, no running process for Bome
Sorry, MIDI Translator
So I just tried starting the mac in safe mode, and MT loaded no problem, straight away. I restarted normally and set my Raved drivers and V-Control to not load, restarted again in case it was this that MT was clashing with, but MT still won't start.
I have it now showing as Not Responding, and I opened MIDI Monitor, I can see the Bome MT 1 virtual MIDI port, so it is getting as far as creating that on the system before it stops responding. But clearly there is something that is not present in safe mode that it's not happy about. I don't know if this info is in any way useful, I'm just trying what I can to fault find the issue.
It does seem odd to me that it will run perfectly happily (one time) after I remove all traces of it and do a fresh install, but then won't start again.
Dan
Hi Dan,
yes, this is very useful! We once had the case where another MIDI software would hook into all other processes which use MIDI and tap into their MIDI threads. Because MIDI Translator Pro uses memory-optimized threads for the MIDI ports, this other software made MT Pro crash because it used too much of MT Pro\'s stack memory. MAYBE something like this is happening.
Crash reports are usually here:
~/Library/Logs/DiagnosticReports
(note the ~ tilda at the beginning. Use Finder\'s Go to Folder function to go there if hidden)
Another thing to try is to start MT Pro in debug mode. Open Terminal and run this command:
"/Applications/Bome MIDI Translator Pro.app/Contents/MacOS/MIDITranslatorPro" -debug
Then post the output here.
Thanks!
Florian
Oh, that process that tapped into MT Pro’s MIDI ports was an audio plugin. Maybe check out this folder for plugins:
/Library/Audio/Plug-Ins/HAL/
or in any other sub folder of
/Library/Audio/Plug-Ins/
Thanks!
One of the reports in the diagnostic reports folder is attached, I just tried loading it again and no new report was made. This might be from the last time I created a fresh install and the application actually finished opening, but I can't really tell just from looking at the timestamp.
My HAL plugins folder has - ACE Driver, AirPlay.driver, AppleAVBAudio.driver, AppleTimeSyncAudioClock.driver, BluetoothAudioSP.driver, iSightAudio.driver, and InstantOn.driver. The last one is the only one I know I installed, it is part of Rogue Amoeba Loopback and Audio Hijack. The rest I've had no input in (at least not that I'm aware of, I don't own an AVB interface for example)
Here is the output of the debug up until the application becomes unresponsive:
Using JRE: /Applications/Bome MIDI Translator Pro.app/Contents/PlugIns/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jli/libjli.dylib
Launching runtime (15 args)...
Using JRE: /Applications/Bome MIDI Translator Pro.app/Contents/PlugIns/jdk1.7.0_80.jdk/Contents/Home/jre/lib/jli/libjli.dylib
Launching runtime (15 args)...
05-04 09:22:03 INFO : Bome MIDI Translator start.
05-04 09:22:03 DEBUG [MidiTranslator] : Loading native lib: /Applications/Bome MIDI Translator Pro.app/Contents/MacOS/libmt.so
05-04 09:22:03 DEBUG [MidiTranslator] : Native lib: RELEASE
2020-04-05 21:22:03.359 MIDITranslatorPro[5611:198052] BomeInstaller: bundlePath=/Applications/Bome MIDI Translator Pro.app
05-04 09:22:03 INFO [Constants] : Exe File:/Applications/Bome MIDI Translator Pro.app
Bome MIDI Translator Pro start.
05-04 09:22:03 INFO : load settings OK: last modified=2020-04-05T17:06:19Z filesize=1142 entryCount=58 filename:/Users/limitedheadroom/Library/Application Support/Bome/Bome MIDI Translator Pro.bmts
load native settings OK: last modified=2020-04-05 18:06:19 filesize=1142 filename:/Users/limitedheadroom/Library/Application Support/Bome/Bome MIDI Translator Pro.bmts
Settings loaded successfully from /Users/limitedheadroom/Library/Application Support/Bome/Bome MIDI Translator Pro.bmts.
05-04 09:22:04 DEBUG [h] : Supported incoming event: Disable/Enable Processing
05-04 09:22:04 DEBUG [h] : Supported incoming event: Key Stroke
05-04 09:22:04 DEBUG [h] : Supported incoming event: MIDI Message
05-04 09:22:04 DEBUG [h] : Supported incoming event: None
05-04 09:22:04 DEBUG [h] : Supported incoming event: Preset Change
05-04 09:22:04 DEBUG [h] : Supported incoming event: Serial Port
05-04 09:22:04 DEBUG [h] : Supported incoming event: Timer
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Apple Script
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Disable/Enable Processing
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Execute File
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Key Stroke
05-04 09:22:04 DEBUG [j] : Supported outgoing action: MIDI Message
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Mouse
05-04 09:22:04 DEBUG [j] : Supported outgoing action: None
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Preset Change
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Serial Port
05-04 09:22:04 DEBUG [j] : Supported outgoing action: Timer
05-04 09:22:04 DEBUG [e] : Loaded images.
Now using 1 virtual MIDI ports.
05-04 09:22:04 INFO [b] : Updated virtual MIDI ports: from 0 to 1 ports
Hi Dan, thank you for the fast reply.
The diag file does not tell me much about the possible cause of the freeze, unfortunately.
Looking at the output of the debug run: the next step would be initialization of the MIDI subsystem. So it is likely that the freeze has to do something with your MIDI configuration. Would it be possible to temporarily disable or uninstall the InstantOn driver?
One other thing to try is Activity Manager’s “Sample Process”, as explained here:
And/or use Activity Manager’s Force Quit on the frozen MIDI Translator process. When it asks you to send the crash report to Apple (or similar), click on “report”. Hopefully that creates a more meaningful crash report. That report might also be generated without a prompt and copied to ~/Library/Logs/DiagnosticReports .
I’m sorry for all the inconveniences, but your computer has a very unusual symptom…
Hi, sorry I wasn't able to respond to your request, then it slipped my mind with everything that's going on. Was reminded as I tried to do something with MIDI on my system that needs some BMT action.
I tried removing the 'ACE' and 'Instant On' plugins from the HAL folder as suggested, they are both part of the system used by Rogue Amoeba's Audio Hijack, disconnected all MIDI hardware, just in case, disabled the IAC module in Audio MIDI setup, restarted my computer, and then tried to load BMT, but got the same behaviour as before.
Attached is the report from 'Sample Process' in activity monitor (generated under the conditions described above). It doesn't ask me to send a crash report when I use Force Quit for some reason. I turned on all the analytics under Privacy, but it still didn't ask me to send a report so not sure about this one.
FYI, in case it has any bearing. There are two items I can see in activity monitor besides BMT when I search MIDI, MIDIServer, and VCPmidi. which must be a driver for V-Control Pro, which is used with my Raven controller. I did try with VCPmidi closed as well, but it made no difference.
thanks, Dan
Hi Dan, my apologies for never getting back to you. We had analyzed the freeze dump file (thanks a lot!) and discussed internally, but could not find anything that could have caused it.
Have you ever been able to find a solution or workaround?
The only clue seemed to be something with Accessibility. Do you have enabled anything accessibility-related?
Thanks (and apologies again!)
Hi Florian,
I did find a work around. I discovered that if I unplug and then re-connect any piece of USB midi gear connected to the computer MT would start as normal. Not sure what that means, but it’s not a particularly difficult work around, there is a keyboard on the desk right in front of me so I just have to pull out and reconnect the USB on the back of it. The issue doesn’t exist on my laptop, so when I’m using MT for on site work it’s not a problem. I can open MT sessions created in the studio and everything works as expected.
Thanks for looking into it.
Dan
Excellent, thank you very much! I hope this will help us find the cause and fix it.