@Gyp080 the last software update was this year in February, most definitely the LoopA project is not on hiatus - why would you say that? Which parts of the workflow are unpolished in your opinion?
LoopA will be continued to be developed and i’d expect about yearly software updates, but as always we will carefully consider which features are beneficial for the user base and which features would bloat it up and take away from its ease of use, which is its major advantage over more complicated sequencers - therefore, by design it should not be complicated.
Regarding MIDI clock, the answer correlates to that, it should not be complicated, so it will be automatically “slaved” to inbound MIDI start/stop and clock packets, if and only if it is configured to listen to MIDI clock packets from the MIDI IN port receiving these packets. Could you describe a usecase when received MIDI clock processing would be necessary while LoopA’s sequencer engine is not running? If the sequencer engine can be running, then you could use the default MIDI slave clock mode as described. If it should not be running, then MIDI clock packets would not have any effect on LoopA and you could just disable that port MCLK IN in LoopA’s setup screen.
Best regards,
Peter
