Hi, Try assigning your problem aliases to other names that are not "automatically create" by the BomeBox. Instead of "BomeBox - Net" which is an automatically assigned alias, try "My BomeBox" or some such. With that said, when running on BomeBox, you probably would not bye using an aliases with BomeBox in it so just give it some other generic name.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
OK, I’ve fixed the aliases. But my main problem continues as it has for months. Can you address it and the screenshots I posted at Elektronauts?
I provided the same answer there. I’m really not wanting to double post as this is our official support forum.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
After re-assigning the aliases you will probably need to manually assign once more but then it should remember them after that.
My main problem is not about aliases, it\'s about the Bome Box failing to maintain the currently loaded configuration after power cycling. That\'s why this thread is entitled \"suddenly my project won\'t load.\" This minor alias problem is now fixed, but I\'ve had this ongoing problem that I\'ve put a lot of effort and expense into trying to fix, and now that I\'ve re-configured everything, the problem continues to happen, that is, the problem of failing to re-load after power cycling.
Also, you do not have any other port assignment in your project at the top level so you need to assign your desired input and output ports there as well. The presets and translator assignment can override these however.
For instance you don't have a defined input ports assigned in presets 1 or 2 of the presets or at the project level.
When I'm running BMT, should I just select "BomeBox - Net" in both the MIDI Input and MIDI Output sections?
Hi, I can understand your frustration, however if ports and/or aliases are not defined in your project file, you will ALWAYS be prompted for them when you reload your project.
I haven't analyzed the files to your intent so at the project level, I recommend you set up and check aliases for "all ports" that you will be using. Then override as appropriate at the preset and translator level depending on your desired routing. Always use aliases an not real port names as your project file will not be portable between your computer and BomeBox if you do not. Also always use aliases that are not "auto assigned" by BomeBox.
I hope this helps!
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
To be honest, I don\'t fully understand what you mean. Can you spell it out in gory detail or recipe format? Sorry about this--I\'m not a total dummy because, as you can see, I\'ve put together detailed patches, but somehow I just don\'t seem to get this MIDI routing issue. Doing what I\'ve done, I\'m able to test while using BMT (though I have that latency issue), and then transfer to the Bome Box, where everything continues to work as expected, except for that power cycling issue. Since everything basically works, I don\'t understand what I\'m not doing right. It sounds like you\'re implying that getting the MIDI configuration issue correct in BMT may fix the power cycling problem, so I\'m asking for a n00b-level explanation. Can you edit my bmtp file and send it to me?
When a project is loaded on BomeBox, it first looks for all real ports assigned and tries to assign them. However it is most often the case that the real ports on BomeBox are not the same real ports on MT Pro. This is where aliases come in.
So once BomeBox assigns any real ports it looks to see what is left and assumes they are aliases. If the aliases are previously known, it just re-assigns them based on the last loaded configuration. Keep in mind that if you have multiple projects that use the same aliases with different assignments, BomeBox may assign them wrong.
If it cannot find an alias, it prompts you to assign it in the configuration screen you showed me. That assignment should be persistent across re-starts. Keep in mind, that if you use a different project file, with the same aliases and different assignments, it may assign them incorrectly so it is best to keep your project file aliases different unless you always want to assign the aliases the same.
There are some auto-aliases assigned by BomeBox for network ports. For instance if you have a BomeBox called "BomeBox1" on your network, it will be assigned "BomeBox1 - Net". You should avoid using these alias names and treat them more like "real port names".
As far as your project file, let me know the real names of the input an output ports you want to use and an alias name you want to assign it at all level, and I can update the project file accordingly.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
My input port is the Bome Box's MIDI in DIN, and my output port is the Bome Box's MIDI out DIN. I will only ever have one project file. I would like to assign the name "ThisIsTheCorrectPortToSelectPerSteve" to the correct port to select.
Here is the project file.
Again, you will be prompted to assign these aliases the first time you load it on BomeBox. After that it should remember the former assignments unless you change them again.
I've downloaded and opened it in BMT. I should now simply assign both in and out to "BomeBox - Net"?
Yes if running on your PC, however if running on BomeBox since you are using MIDI DIN ports assign them to your MIDI DIN ports instead.
That was my toy file. I believe I've now made the necessary change to my production file, which I've attached here. Can you please verify?
No, you need to go through the entire project file at the project, preset and translator level and change any reference from "BomeBox - Net" to "ThisIsTheCorrectPortToSelectPerSteve". Uncheck any Boxes that show "BomeBox -Net" and instead check the boxes "ThisIsTheCorrectPortToSelectPerSteve"
See the below video for how to manage your inputs and outputs at project, preset and translator level.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
I've watched the tutorial, and I think I'm starting to understand where I've gone wrong with the MIDI routes stuff. However, may I please n00b-out one more time and ask you to add the "ThisIsTheCorrectPortToSelectPerSteve" to my production file that I've now cleaned up and attached?
I'm asking for hand-holding here because 1) I won't fully understand the tutorial for a while; 2) I think this will be a once-and-for-all-time solution because my Bome Box has only ever been dedicated to adapting one controller's (Zendrum's) velocity response to my sound modules; and 3) based on experience, I wouldn't be able to rule out the power cycle issue for days to months, and I don't want the toy file to block me from using my stuff if that's not necessary.
OK, here\'s what I\'ve done.
1) I went through every patch to make sure it selected only default MIDI ports.
2) I loaded your version of the toy project, and BMT prompted me to assign the ThisIsTheCorrectPortToSelectPerSteve alias. For both input and output, I assigned it to \"BomeBox - Net.\" That created the alias, which is now available in BMT regardless of which project I load. My earlier problem of not being able to delete an alias was apparently because the old alias had been created on two different computers. I\'d deleted it on one, but not the other, so it had to be deleted twice. I didn\'t realize these aliases are BMT\'s and not the project file\'s.
3) I went to the Project Properties page and selected ThisIsTheCorrectPortToSelectPerSteve for both input and output.
4) In all my time with BMT, I\'ve never changed--or even thought of changing-any translator from its default choice of MIDI ports, but I went through every translator in every patch to verify that each one selects \"Project/Preset Default Ports\" for both input and output. This was not applicable in the case of patches involving only the USB keyboard. I scrolled through fast, but I expect I didn\'t miss anything because, as I said, I\'ve never ever made a change here in any translator.
5) I uploaded to the Bome Box, selected, and assigned \"ThisIsTheCorrectPortToSelectPerSteve\" to \"BomeBox DIN\" for input and output.
Everything works as expected, but that doesn\'t mean the problem is solved. We\'ll now see if the configuration file gets loaded at each power cycle. I do verify that the WiFi latency problem continues as it always has. It could be hours to months to verify the power cycling issue. If it survives the first power cycle (as I\'ve now verified that it has), then that has always implied that it will continue to work at least until some change is made to the project file, and I might not be making any changes for a while. Even then, the failure-to-reload-on-boot problem has only ever begun suddenly--the first time after two months--but once it happens, it continues to occur on virtually all subsequent power cycles, making the problem intractable.
I\'ve attached my current project file for you to look over. If it\'s OK, I apparently don\'t need you to edit the one above for me.
Good Job! I believe this will fix your problem.
It failed in the usual way on the first power cycle.
Then, as usual, I manually selected the lone project, manually configured the MIDI ports, and verified everything worked normally. Then I power cycled again, and it survived. Later, I power cycled again, and it failed in the usual way. I haven\'t power cycled since. It\'s a fail.
I just got an email that Florian Bome reports there\'s a firmware update, so I guess I\'ll try that. I wonder if it addresses the WiFi latency that I\'ve had out of the box. The email says it\'s a reply to this thread, but for the life of me, I can\'t find it. As we\'ve discussed, this forum software is rather confusing--I\'ve never seen a forum with this kind of layout in years--which is why we were using Elektronauts. I was surprised when, a couple days ago, you wouldn\'t continue using out Elektronauts thread, but I went with it.