... this force reloading all dsp and reinitialise asio...
i think there's two parts on ASIO, let's name them a host and a guest. Host part can be rest, but the guest will be engaged by the sequencer.
If the sequencer crashes (closes without closing the guest) it will be unable to re-engage the guest- it's already been used by 'another program', ASIO.
You will need to reboot in that case to properly close down all ASIO 'guests links'.
If, in another case, the Pulsar is synced to a sampler and Pulsar looses sync, ASIO will give an error, but not crash (ie. 'ASIO driver not available'). You can leave the sequencer waiting on it's ASIO host. In the meantime, reset Pulsar's DSP (by switching master/slave or changing sample rate) and select ASIO again in the sequencer. Should work fine.
In the third case, Pulsar DSP crashed. If you're lucky, you can reset the dsp as described above. Re-engage sequencers' ASIO by selecting again. If that don't work, close all appz you can and reboot.
As a matter of fact, you'll learn by experience. It might work, it might not, all depending on OS (Pulsar & pc), drivers, pc setup,...
That's how I see it, might not be right. Anyone else wanna give it a try?
atomic.
that really solves it!