load times will depend on size of projects, but in my experience its a few seconds, so not ‘instant’, but not minutes.
as far as I can see, the bpm of the clock is changed as soon as the project is loaded. i.e. before you hit PLAY.
currently, I guess this kind of makes sense since sync load and sync stop are related.
ie for syncl oad to ‘work’ as you expect, sync stop also needs to be on.
otherwise, when the new project is loaded, it immediatly stops sending clock, since the transport is not running.
this means in turn if sync stop is ON, then of course, it starts sending the new clock because the transport is running
if you need something different, you could sent a feature request to squarp via the contact form
perhaps sync load, could continue you to use the ‘old BPM’ , if sync stop is off ?
no - there is not currently a feature to ignore the bpm of the project being loaded.
again, you could send a feature request for this if its necessary
(perhaps sync load, could have OFF, ON, RETAIN BPM)
another way around all of this might just be to have another device run as your master clock.
(this seems to make sense if you dont want to use the pyramid project bpm)