Suggestions appreciated on other software able to do this.
EDIT: It seems that MidiFire is able to generate midi clock. Can someone confirm that the following is possible with MidiFire?
-Have MidiFire listen to midi clock from Ableton and sync its clock to ableton -Have MidiFire send out midi clock and keep sending it according to latest incoming BPM, even when Ableton Midi Clock is stopped -Type in BPM in MidiFire and send out midi clock accordingly, however prioritizing and syncing to Ableton, when it's sending out it's midi clock. (even better would be the ability to set the bpm via a midi command, however I can go around it, so not necessary)
Yes, the BPM value in MidiPace is read-only as it was only designed to stabilise, track and distribute an incoming clock signal (rather than diverge from the original).
MidiFire includes the Dynamic Clock module which can be started, stopped, sped up, slowed down or configured with an exact tempo with MIDI messages. However, 'out of the box' the Dynamic Clock does not sync to an incoming clock signal; it expects to be the master.
You seem to require a mix between the two. I think MidiFire could do it but will need some Stream Byter code to replicate part of what MidiPace does: monitor incoming clock and start the MidiFire clock at the right time and with the right tempo.
I can probably whip up some Stream Byter code to do this if requested.
Actually I don't even need to be able to separately start/stop the MidiFire clock. It can send out it's clock at all times, and simply sync to ableton's clock whenever ableton is sending out. Don't know what this requires on coding side of course, and how hard it will be.
BTW, does using Stream Byter code in MidiFire require me to purchase both, MidiFire and Stream Byter? I will of course if necessary, and I like supporting developers of this kind of software anyway, as there aren't too many. I just happened to spend all my money on new gear, so I'd have to wait a couple of weeks for my next payday.
There is a nasty bug in the current release of MidiFire that is going to affect this. This bug is fixed and will appear in the next MidiFire update, but until then I am going to have to ask that you bear with me until then.
I'm on the home stretch for this release. I'm hoping to have it available in about 2 weeks time if all goes well.
Once the new version is available I will revisit this thread and provide the solution. My apologies, but there is no point in giving you something that I know is not going to work properly.
Thanks for the update! While this functionality is very important to me, I'm not in a rush as I've got so much work with setting up my new gear to work anyway. Glad to hear this will be possible and I appreciate your work! I've suscribed to this forum, so I'll get notified for any updates. I'll follow your progress here.