When I open this project the “On Activation Of This Preset” Translator is firing off even though the Preset is already activated. The mouse moves to the centre of the screen on opening the project. AFAIK this shouldn’t be happening.
Test.bmtp (751 Bytes)
Hi,
If you deactivate the preset and then save the project file before closing it. When you open it again, it will stay deactivated.
Upon project open, presets stay in the state that they were last saved when the project was closed, unless there is a translator that has an action that does otherwise. So when Bome MIDI Translator opens the project, the preset considers itself activated.
If you want the preset to be inactive when open, either deactivate it and save it before closing or add a translator to deactivate it.
I typically have an ‘Init’ preset that remains always active but doesn’t have a ‘Upon Activation’ translator. I then use ‘On projected Open’ trigger to activate or deactivate other presets or to call a ‘Perform’ Action that does the same.
Steve Caldwell
Bome Customer Care
Hi, and thanks for the reply.
Sorry I didn’t make myself clear. To put it another way:
The project was saved with the Preset in the Active state, and, since the project has been opened, the Preset has not been manually or automatically activated i.e. it remains in the Active state. So the Translator inside the Preset should not be firing off.
Thanks again.
Yes, I understand but currently Bome MIDI Translator Pro always re-activates all active presets when it a project is opened. I understand that this has always been Bome MIDI Translator Pro 's behavior but I can see why this might be confusing and also can see your point why you would not want it to work that way.
Steve Caldwell
Bome Customer Care
Wow, that is a strange behaviour to program into a piece of software, there must be good reason for this. I’m surprised my project with 650 + Presets behaves so well and I’ve never noticed this.
Thanks again.
Yes, I never noticed it before either and I’ve been writing projects for years. I will keep you informed.
Steve Caldwell
Bome Customer Care
Just a clarification: we try very hard to make MT Pro’s processing behavior consistent and sensible. I acknowledge that our choice of ‘sensible’ can sometimes differ from what users would consider so. When designing new features, we work closely with the users who proposed the feature and our beta testers to make the user interface and behavior as intuitive as possible. Also note that some features, like the ‘On Activation’ trigger, have been designed a very long time ago, so we want to keep its behavior consistent to how it has always been so that existing project files don’t break – even if we would like it to behave slightly different nowadays. So we cannot really change this here.
Having said that: the logic here is that while a project file is loaded, all presets are not active (project is in ‘loading’ state). Then, the project is started in a separate step, and all presets that were saved as active are activated now, causing the respective triggers. The Log Window also logs all these activations. So this is not accidental behavior, but a different way of how the processing engine works internally than what you expected. At least, it is consistent… You can also invoke ‘Restart Project’ in the File menu, and you will see that all respective ‘Preset Activated’ events will be triggered.
I hope this makes a little more sense now and that you can design your project to work well with this behavior.
Thanks for the reply.
There’s no problem at all. I hadn’t noticed this behaviour until 2 days ago and I’ve been creating a monster project for about 3 years.
Did I hear that there was going to be an update after NAM?