Transport module
Low priority, but adding this module can wreck a project! I can think of a few safeguards - one would be to have the module default to the current project tempo - and possibly if you remove it, have the project go back to the prior tempo?
unrelated but related, the lack of a project level undo really makes it risky.
I get why, but having it included also breaks tap tempo. some additional features, like double or half time, (maybe other divisions) could aid in its usefulness. it can be hard to lock these intervals in by modulation alone.
Just ideas!
Comments
Thanks for bringing this up and unintentionally giving me the solution about how to control tempo with a midi controller.
I just added the module to my project and I too have some of the problems you are experiencing with it:
Your issues seem like real bugs to be dealt with @catherder do these projects involve other hardware or anything else that might be affected by a midi clock/tempo?
on my end it’s more about expected behavior and usability. I don’t think I’ve ever had this type of crash (although I haven’t used it all that much due to the previously mentioned issues)
I've got two synths (Arturia MicroFreak and Roland SH-01A) and two controllers (Novation Launchpad Mini MK3 and Launchcontrol XL3) connected. What happened was that the SH-01A got stuck and the Launchcontrol was no longer working when I started Drambo after adding the module. Oddly enough add the module, save the project, restart Drambo, load the project again and all is fine. I think I will need to investigate this further - not today because I need my setup tonight...
Ah ok - yeah, definitely a separate issue (and more urgently in need of a fix) than what I call out here.
I should have been more clear by what I meant when I said “wreck a project”. I just meant you lose the project’s tempo because it defaults to 120. So some practical changes to how the module behaves could make it more user friendly.