To answer your questions.
- I see that Florian’s timer continuously runs in the background. Eventually the line numbers will get pretty large if left unattended. Is this bad? Not a problem, however probably best not to have the log window open when running in production. The log window itself will consume some time.
- I am concerned that if the timer(s) runs it will possibly interfere with other midi messages going through BMT (when moving several faders, for example), though I haven’t really experienced any problems yet. How many continuous timers would be appropriate in order not to bog down BMT (if this is even possible)? This really depends on the overall MIDI traffic and perhaps if it it transmitted over MIDI DIN (slower) or USB (faster).
Other notes;
I’m not sure what you are using ga for. I see a few places where you have ga=pp (which overrides the incoming message) and pp=ga.
Translator 1 and Translator 4 both start at project open but since they are the same outgoing timer and delay, you are really only running 1 timer.
Translators 2 and translator 5 are both trying to update gr but with different increments and range. I’m not sure why you are doing this. My guess is you should only use translator 5 as it generates a wider range of notes (0-127 instead of 0-20). With translator 2 in place, you will likely get less “randomness”.
In general, it is probably best to.
- Start a random number generator at startup. (I would go with translator 5 instead of 1)
- Use incoming notes (or any other unpredictable input) to re-seed the value of gr. If the re-seeding of the random number of generator is in sync with the song, then it will make it less random.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz