midi Song Position Pointer message problem

[bik44]

Hello,
my main DAW is Pro Tools. It has such a "feature" that if it is looping, every time it starts the loop from the beginning it sends an SPP (Song Position Poiter) message "F2 00 00" and then Nerdseq stops! I can't play loop using midi clock from Pro Tools (possibly some other linear DAWs have the same "feature"). My other equipment, such as the Elektron machines and Erica Synths Black sequencer (lying on the shelf), do not stop.
Currently I am dealing with this way of filtering this message in BOME Midi Translator Pro but it is not a cool solution because it causes additional complications.
I would very much like to ask Nerseq to be insensitive to SPP (either permanently or by preference) or 
if there is any other solution?
I would be really grateful.

Hey. I am not aware of the NerdSEQ to stop or change on any SPP message.
I will check it out if they might be an issue.

To be precise the DAW when restarting the loop sends first a "stop message" 0xFC and then a "SPP" 0xF2 00 00. So I just filter out the 0xFC and then it works fine.
Propellerhead Reason and Cubase also send the same messages except that you can turn it off there.
I don't know what these messages are for and why some devices stop and others go on. Shouldn't it be that after 0xFC and 0xF0 the sequencer should keep playing?
If it is possible to do something about it, I would really appreciate it, if not, I can manage somehow. Anyway, Nerseq support jet the best in the world

Actually if the daw sends a stop then the sequencer has to stop of course. The SPP message is not a start command and should never start any device.
What I can imagine though is that your DAW sends a midi continue after the SPP which would probably explain  why some gear continues to run. I got to check but as far as I remember the continue command is being handled like a midi start in the NerdSEQ.
Else, can you maybe send me a dump of the midi stream if possible so I can find out which messages are being send exactly?

Now I can see that there's additional third message 0xFB "continue" after 0xFC 0xF2.

midi dump:
1: MIDI IN [IAC Driver Bus 1]: F2 00 00 -- start

2: MIDI IN [IAC Driver Bus 1]: F2 00 00
3: MIDI IN [IAC Driver Bus 1]: FA
4: MIDI IN [IAC Driver Bus 1]: F8
5: MIDI IN [IAC Driver Bus 1]: F8
6: MIDI IN [IAC Driver Bus 1]: F8
—————— a lot of F8
97: MIDI IN [IAC Driver Bus 1]: F8
98: MIDI IN [IAC Driver Bus 1]: F8
99: MIDI IN [IAC Driver Bus 1]: F8
100: MIDI IN [IAC Driver Bus 1]: FC -- loop 1 and then Nerdseq stops
101: MIDI IN [IAC Driver Bus 1]: F2 00 00
102: MIDI IN [IAC Driver Bus 1]: FB
103: MIDI IN [IAC Driver Bus 1]: F8
104: MIDI IN [IAC Driver Bus 1]: F8
—————— a lot of F8
196: MIDI IN [IAC Driver Bus 1]: F8
197: MIDI IN [IAC Driver Bus 1]: F8
198: MIDI IN [IAC Driver Bus 1]: F8
199: MIDI IN [IAC Driver Bus 1]: FC -- loop 2
200: MIDI IN [IAC Driver Bus 1]: F2 00 00
201: MIDI IN [IAC Driver Bus 1]: FB
202: MIDI IN [IAC Driver Bus 1]: F8
203: MIDI IN [IAC Driver Bus 1]: F8
—————— a lot of F8
271: MIDI IN [IAC Driver Bus 1]: F8
272: MIDI IN [IAC Driver Bus 1]: F8
273: MIDI IN [IAC Driver Bus 1]: F8
274: MIDI IN [IAC Driver Bus 1]: FC -- stop
275: MIDI IN [IAC Driver Bus 1]: F2 00 00