Have you had a look (with a midi monitor on your computer) at what Reaper is sending?
I just played with this with Ableton Live, and Live doesn’t really work with loop points and external clocks “properly”
in Ableton, If you set a loop point , basically it doesn’t send a MIDI START
it only ever sends a MIDI START, if you have the play position at 1.1.1 and hit play.
so really, the Hapax can do nothing (*) as it never gets told to start.
(*) obviously something different here, as Hapax does NOT crash/stop responding, it just simply does not start the play head. if as you say Hapax is crashing, it would be good to get a midi log from your computer to see exactly what was sent to the hapax that it didn’t like.
anyway, in the case of Live, unfortunately is not a Hapax ‘bug’…
I think the only ‘solution’ in this case, would be for Hapax to allow for a manual start of the transport… but of course, that would require the user to ‘manually’ sync.
this has ability to always control transport on Hapax, has already been put forward as a Feature Request.
similarly, the transport not being able to be started with MIDI start/stop = OFF has also been reported as a bug,
I guess we could test with other DAWs, as I suspect they probably all act a bit different in this area.
a couple of other bits
a) if Im slave to live, and have transport running… so hapax is running fine.
as soon, as I tell live to go into a loop point, it sends a STOP to hapax, and never restarts
b) workaround - use hapax as master
unfortunately, only workaround I found was to slave Live to Hapax, then Hapax runs transports and within Live can select loop points, and it doesn’t complain.