Crash when importing Settings

Bome Products
1

Hi Folks -

I am getting a hard crash when I import settings.

Earlier, I did notice that, when I was importing settings, the List of MIDI connections available on the input side (at least) was ‘messed up’ in Bome MIDI Translator … most were missing. That issue was cured by shutting down BMTP and restarting it, which would have the correct (i.e. imported) settings and all was AOK.

Now I am getting a hard crash. The MIDITranslator.exe.4892.dmp was the first crash when BMTP had been running quite a while when I imported the settings. The MIDITranslator.exe.14176.dmp was a crash when I loaded PushLapLLB_Husky.bmtp and then immediately tried to import BMTSettings_PushLapLLB_RBB-DEV_WS.bmts.

Here is a Dropbox directory with the files, in case they don’t make it through this submission form: https://www.dropbox.com/scl/fo/zvg1a9kbjii0lzpzanuq7/AIvpmJMcUIBtqg7PRgOgJzM?rlkey=ce6nhdb7i30qehn8va4i05gt3&dl=0

I tried using the contact form, but the 16MB .dmp file is too large to upload (go figure!) … and then I could not delete the .dmp file from the contact form, so I had to start over with a new contact form …

Hope you can figure it out!

  • Clint Goss
2

And, by the way, if I load the .bmtp file I sent, export a .bmts file, then immediately re-import that same .bmts file, I get a similar-looking crash.

3

Hi,

We’ve not seen this before but I suspect that you are importing your settings while Bome MIDI Translator Pro is actively processing. Try hitting the Stop Sign (Panic), to stop Bome MIDI Translator Pro from processing while you import your settings. After that, hit the Go button to start it up again. Let me know if that helps.

Steve Caldwell
Bome Customer Care

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

Thanks Steve!

I hit [Stop], then imported. No more Bome Boom boom. Worked like a charm … except …

Before import, my project MIDI ports looked like this:

Screenshot 2025-05-10 161210
Screenshot 2025-05-10 1612101920×1307 213 KB

… lots of ports … After the import, it looks like this:

Screenshot 2025-05-10 161110
Screenshot 2025-05-10 1611101920×1307 202 KB

Is there a reason for this that I am missing?

5

Aliases are contained in the .bmts file. If your imported settings do not contain aliases in the current project, then they will disappear. Then if you have ports defined in your project that are not all physical ports and not in your .bmts file , you will be prompted for adding or ignoring them again.

Steve Caldwell
Bome Customer Care

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

OK … but … this was a file I exported from this project, then re-imported it … should this happen in that case??

7

My guess is when you exported the file, it did not capture the aliases you had labeled as “ignore don’t ask again”.

Steve Caldwell
Bome Customer Care

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

I don’t think I ever use ‘ignore, don’t ask again’.

In the first screenshot, notice that I have a LOT of Project MIDI Ports prior to the import (notice the slider to the right of both the input and output ports). After import, I seem to only have those that are in use.

I was planning on using this Export/Import feature to manage the various ways that my Rig can be set up, but this issue or quirk with Import could be a problem …

I am thinking that if I am in a project and do an [Export] of the Settings followed immediately by an [Import] of that same setting file, that my project should look exactly the same?

9

So now BMTP is crashing on every [Import] of Settings, even if I stop the processing.

(When you provided the ‘stop the processing’ solution, it did work … once. I had assumed that the solution was to ‘stop the processing’, since it was always crashing before. However, now, even when I stop the processing, it is crashing).

I have tried it many times, and BMTP always crashes. Don’t have time now for dumps and screenshots and such … counting down to our show. …

10

OK, I just exported and the re-imported settings. Then I exported again and ran a ‘diff’ on the two files and here were my results.

$ diff *.bmts
37d36
< SettingsFilename=C:\Users\Steve\Documents\settiings_export-2025-05-11.bmts
59c58
< ScrollPosProjectEditor=360
---
> ScrollPosProjectEditor=179
185,186c184,185
< Left=548
< Top=369
---
> Left=631
> Top=350

The differences were explainable to the minor changes in positions between the two exports.

Are you running more than one instance of Bome MIDI Translator Pro ? Do you have this checked?

image
image531×353 9.85 KB

Steve Caldwell
Bome Customer Care

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

For when you get back, maybe you should use the suggestion. on page 105 of the manual. Especially if you are going to run multiple instances of Bome MIDI Translator Pro. It talks about create different executables under different names of Bome MIDI Translator Pro , each which use their own settings file.

Steve Caldwell
Bome Customer Care

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

Thanks Steve!

Performance was a blast - 175 people (a lot for me).

I have had that [Only allow one instance] option turned OFF in the past, in order to do copy-paste of presets. However, that option is now ON and only one instance of BMT has been running in all the tests over the past few days (confirmed by the Task Manager) …

I’m back in the Lab now, and have tried dozens of settings [Import] actions trying to narrow down when it crashes. Crashes happen about 50% of the time, but I can find no definitive pattern.

  • I have had crashes with or without my Push3 sending a stream of MIDI Synch messages.
  • I’ve had with BMT processing ON and OFF.
  • I have had crashes with and without Bome Network running.

===

On the other issue of the effect of a settings import … here is a snapshot of my Project Default MIDI Ports before a settings import:

Before Import Screenshot 2025-05-12 044855
Before Import Screenshot 2025-05-12 0448551588×3294 783 KB

… and immediately after importing the settings file I had just exported:

After Import Screenshot 2025-05-12 045010
After Import Screenshot 2025-05-12 0450101588×3294 658 KB

So the [Import] seems to leave me with only the Aliases showing. No closed MIDI ports are shown. This makes it difficult to change alias mappings. The cure is to re-launch BMT and all the closed ports re-appear.

So I might go down your suggested path of separate executables for each configuration. That’s daunting, because I am planning on using all combinations BMTP projects A, B, and C with settings 1, 2, and 3. This is workable with 3 projects and three settings, but not so good with 9 separate executables. Modifications would need to be made in parallel on multiple executable environments, and the chances of keeping all that straight are nil.

14

Are you running Bome MIDI Translator Pro version 1.9.1 build 1064. I have yet to duplicate the problem so maybe a re-install of Bome MIDI Translator Pro will help.

Steve Caldwell
Bome Customer Care

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

I am on 1.9.1 build 1060.

16

Yes, then please download the latest which is build 1064 and see if that fixes the issue.

Steve Caldwell
Bome Customer Care

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

I’ve installed build 1064. No Joy.

BMT still dumps core on a Settings Import whether or not I have stopped processing. Even tried launching BMT right after a clean boot.

I have updated the Dropbox directory with these files:

  • MIDITranslator.exe.18568.dmp: Crash dump using build 1064 from /Users/Clint/AppData/Roaming/Bome/CrashDumps

  • PushLapLLB_Husky.bmtp: the BMT file that I’m running when it crashes.

  • za1.bmts: The settings file I am trying to import.

Link (same as before) to the Dropbox folder containing these files: https://www.dropbox.com/scl/fo/zvg1a9kbjii0lzpzanuq7/AIvpmJMcUIBtqg7PRgOgJzM?rlkey=ce6nhdb7i30qehn8va4i05gt3&dl=0

NOTE: I have now just tried bringing down Bome Network and doing the import, and BMT has not crashed in four sequential imports. With Bome Network running, it did crash 6 times in a row.

Because of this new piece of Info, I have just added:

  • BomeNet_2025_0512crash.bmts: Bome Network settings file in /Users/Clint/AppData/Roaming/Bome that is associated with the crashes of BMT when an Import is performed.
18

Asking Florian to look at your crash dump.

This may be important. Thanks for adding this information!

I also noticed you are at 150 % zoom, does it crash at 100% zoom settings?

Finally, I noticed this entry in the .bmts file

CurrentProject=C:\SoundLib\Bome\PushLapLLB_Husky.bmtp

Is this the current project when importing back? I’m not sure why this is used and maybe should be discarded upon import in case you load the .bmts file into a different project. This may mean nothing but to me it is suspect because I get an error when importing into my project (of a different name).

Steve Caldwell
Bome Customer Care

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

What version of Bome Network are you running?

20

I have Bome Network 1.6.0 with the UNMP and Pro add-ons.

BMT still crashes at 100% zoom as well as 150% and I’ve also had crashes at 200%.

I too have seen odd (outdated) files referenced by the entry …

CurrentProject=C:\SoundLib\Bome\PushLapLLB_Husky.bmtp

… and wondered what might be the consequences … However, I have never seen an error message relating to this entry.

I just brought down Bome Network, successfully imported settings into BMT three times, brought Bome Network up, and then crashed when importing settings into BMT. It’s something to do with the BMT-Bome Network interaction …

21

Could you share a screenshot of the Bome Network named ports that you have?

Steve Caldwell
Bome Customer Care

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