MidiSync got a firmware update to version 1.12 that adds the following functionality:
- Start and Stop hold modes are now controlled independently
- Added ‘hold until the next beat’ option, previously it could hold until next bar only
- Added Restart action that sends MIDI Stop/Start to restart downstream devices (thanks to PaulS), also optionally delayed until next beat or bar.
Finally, MidiSync firmware got a proper manual.
MidiSizer 
Hi Pete,
Thanks for this new version
Recently been trying a few things, with the Hold Start and Hold Stop set to Bar works as I expected using the unit push button switch
Using an external MIDI input, Start command works correctly but Stop command stops immediately instead of continuing to the end of the bar before stopping as I would have expected?
Not sure if this how it was intended to work?
Regards, Bob
This is by design. The Stop event quantization is controlled by the dedicated page HoldStop.
Hi Pete,
Thanks for the quick reply.
With both the HoldStart and HoldStop pages set to Bar it works correctly when using the push button switch to start and then stops at the end of the bar when pushed again.
With the same page configuration but instead of using the push switch, using an external MIDI controller to generate system messages, starts correctly at the beginning of a bar sending it a MIDI Start message (FA)
My question is why when sending a MIDI Stop message (FC) does it stop immediately rather than continuing to the end of the bar?
Perhaps it’s my understanding that is incorrect, currently experimenting with both a MIDI sequencer and one controlled by the discrete clock and other output signals
I could just add a foot switch in parallel with the existing switch which would do what I want, but would be neater to do it simply by sending the MIDI messages
Bob
That sounds like a bug to me — receiving a MIDI Stop message should be quantized as well. I’ll check.
Answering my own query, a MIDI Stop command stops all MIDI activity immediately, that’s it’s function, so the setting on the HoldStop page does not have any effect on the way it works if controlling the clock from a separate MIDI input
Does what I want using the push switch, monitoring the MIDI output from the clock the MIDI Stop command is only sent at the end of the bar
Got a better understanding of that MIDI function now, sorry for wasting your time. Thanks again Pete
Thanks Pete, that’s the way I hoped it would work based on Beat or Bar but as the MIDI Stop Message is passed straight through also to control downstream devices then perhaps that’s not how that message is intended to be used
For my use it would be great if the MIDI Stop was delayed until the end of the bar and then the massage sent to the output
Similar thing happens with your Sequencer, MIDI Stop halts it immediately, would be nice if it continued to the end of the sequence before stopping. I did also try sending the CC code to Stop but again the sequence stopped immediately. Maybe in that case the response to the CC Stop could be modified to wait until the end of the sequence, that way does not affect any MIDI Stop commands?