Re: Bome Midi Translator Pro Crack
Donald
-it seems the way Windows is set up, whichever MIDI software is open first, gets access to MIDI ports. If another app is then opened, it can't access ports. This was illustrated best when I opened Studio One before bome. There was MIDI activity in the DAW, but none of the virtual ports were sending data to the instrument. Can bome be setup internally or with a script, to open a particular patch/translator at startup? I know there are options to start bome with windows. I am thinking about a scenario where I want certain translators functional when windows starts.
-this is tied into the above question. I came to the conclusion that virtual ports are created and routed at the global level of the program. So you can't have one port setup per project, so to speak. That's OK. Does that mean that if there are 10 virtual ports being fed by a single controller set up in the software; that will be how the program is configured at startup?
-I will be using virtual ports pretty well all of the time. Is there any chance of conflict between windows, Studio One and bome, if it is running continuously? I noticed minimal resource use. Is that generally the case?
- Performance - Anything you send through a loopMIDI pipe will make two calls to the operating system. Bome MIDI Translator virtual ports only make 1 call. In general this is not a problem but if you have a very busy MIDI system, this could affect overal performance.
And yes, for Windows, MIDI ports are first come first serve and exclusive. Bome MIDI Translator solves this by using it\'s MIDI router where you can split or merge into virtual ports and use virtual ports instead of the original port in your applications.
A: Overall, routing is static in MIDI Translator Pro if you are using the router. However you can through presets and translators create dynamic routes that can be changed with incoming MIDI messages or keystrokes. What you do is have different presets override the project default inputs and output and then enable and disable the presets you want depending on the route you want. The below tutorial explains this further.
Yes, we are working on a product extension for Bome Network that will allow unlimited and user named virtual MIDI ports with advanced MIDI routing capabilities (even outside of MT Pro). It is in Beta right now.
With v1.6 or 1.7 I used to be able to create a button on a midicontroller that would open and close specific windows on my windows computer, like "C:\Program Files", using a translator in bome, using the same button, going from "xx yy 7F" to "xx yy 00" (midi value going from 127 to 0), and the use of another translator using WM_messages.
This way I was able to open and close (multiple) window with one button(s). I was using 192 of these buttons in lemur to open specific applications, and/or open/close sets of folders and/or websites in one click, but sadly this is not working anymore the way it should as I am no loger able to close the windows on button up..
Now I know WM messages are no longer supported. But "execute file"+ "C:\Program Files"still works (for example). Is there a command for "close window C:\Program Files" that I can ad to a translator that would replace the WM command I was using before?
It looks like you are running Bome MIDI Translator Classic. You can send keystrokes and MIDI messages only. If you have a helper application that can take these keystrokes and change them into either command line output, or use Bome MIDI Translator Pro which can do command lines natively.
Actually, keystrokes, mouse movement and mouse clicks are WM messages and Bome MIDI Translator Pro version supports all of these, however not more complex WM messages like Close Window. Kill application etc.
For that you would aso need a helper application that translates what Bome MIDI Translator sends into the WM Actions you want. I typically do this in programs like AutoHotKey. I can set AutoHotKey to either:
Thanks, I\'m on Pro, but as you explained I would still need autohotkey scripts to close specific windows the way I was able to do in the older bome versions. The reason I asked is: I have everything I need already setup in Lemur: 192 named buttons sending midi notes. I also have a bome template that used to work (build with an older bome version). But I cannot use this older version of bome on windows 10. I guess I need to re-program everything in autohotkey, since I do not want to use two different applications for actions on the same button/midi note, it would get very messy to keep track of everything.. (this would be: bome for opening, and autohotkey for closing windows as indicated in your answer). I was just looking for a way to avoid this, but as I understand it\'s not possible anymore.
I'm not aware of any Bome Version that provided this functionality. Pro or Classic. Are you sure you weren't using some version of 3rd party software using MT Player instead. Maybe they enhanced their version for more capabilities.
No I,m 100% shure I used just bome for this. I could send you the file. For now an example: These scripts (a part of a larger file) used to open (on value 7F) AND CLOSE (on value 00) the "my computer" window and the "program files" folder:
Hi guys,
anybody have the Behringer X-Touch Mini?
I made some useful hacks with Bome midi translator to make the acceleration on the knobs works and also the LED feedback to remain after pressing the buttons, so if somebody is interested I can post it in here.
Also, would be cool if you have any other tip or trick regarding this controller or CSS in general!
Mauro.
Normally you set it to a Mackie compatible mode when connecting it and holding a button (or in the behringer software) , then it stays like that no matter what, and that mode is the only way to take over the leds properly.
I have a monitoring fx running in reaper, to do corrective eq on my speakers.
I am using an instance of the plugin "Pro-q" to tune my speakers to the room/compensate for my room. This is done by ear and with no measuring microphone etc.
"Monitoring FX" is a function in reaper where you can insert a plugin that is in the master audio path, but will not be rendered along with the audio (pretty clever).
Monitoring FX is *not* the same as simply monitoring an effect on a track, with an acitve input.
I would like to disable that whenever I use my headphones.
I have the ARC/totalmix set up so i press "snap2" for headphones and "snap3" for speakers.
Any way I could get the output of the arc into reaper?
That way, when I press snap2, I could disable the monitoring effects (corrective eq).
I have enabled it in settings in totalmix, but I get an error message in reaper, saying it can't "get" the midi connection from the ARC. (The following midi outputs and inputs cannot be opened : RME ARC USB). Probably because it is in use by totalmix?
Any way to duplicate the midi and send it out to a daw as well? Would be a great option to have
Thanks
Using the ARC as Midi controller is a workaround that probably doesn't work.
The more proper workaround is a Loopback in Totalmix.
Send the headphone signal straight out to the headphones and route the loudspeaker signal thru Reaper via Loopback.
Then toggle the two snapshots.
Ah ok, are you playing the music out of Reaper ?
You don't have a routing from Totalmix into Reaper for processing the signal yet ?
Then you have to send 2 signals out of Reaper to different output channels for further routing in Totalmix.
One pure (dry) and one processed (wet).
Use the room correction software as a send effect on its own track, this is the wet signal.
I already tried that but the arc is busy (controlling totalmix).
But I guess I could se totalmix up to use midi as well, and then set it to listen to midi from bome, and then do the same for reaper.