>>I found if I put the Nemo and P3 in series rather than parallel it fixes the clock issue.
Not sure if the clock can be switched off on the Nemo.<<
oohh! me! me! me!
(what does "parallel" mean in this context? the octopus allows the clock out to be disabled- has this fallen off the nemo?)
I've been using multiple hardware sequencers in midi rigs for over ten years. one of my p3's has a "clock-only" output instead of the 24/48 option, although I don't now use this.
maq, notron, p3, schaltwerk, zeit, octopus, mobius....
here are the things I had trouble with, which are now sorted:-
1) relative note-on timing.... seemed to depend on what was the master clock in a config, & how good/expensive the merge box was.
2) lost or corrupt data (esp. realtime CCs) through merge boxes.
3) things not stopping & starting in response to F8s/whatever, because although they passed clock, they weren't passing realtime commands onto midi-through connections.
4) things with clocked delays either not being clocked at all, or constantly glitching. (emu proteus, supernova, boss sx700, repeater)
until very recently, I was using ordinary merge boxes (a couple of frontline 2x1s, a philip rees 5x1, a couple of philip rees 3x1s with A&C-only-throughs, some other similar units).
eventually I got tired of having to set my emu synths to internal clock (for the delays) & then remember to change their internal midi tempo every time we did summat at a different speed with the sequencers. it helps if you know we do a lot of ratchetty berlin-school pulsey stuff with syncopated echoes.
so-
I bought, 2nd hand & quite cheaply, a "proper" midi router. this one's a MOTU micro express, the later version with usb, & can handle 4 midi inputs & 6 outputs, all of these with comprehensive filtering, merging & remapping. it took me a good long while to arrive at the right set of rules within the thing, but there was one thing that suddenly made it all work properly- filtering out ALL of the
erm....
after all that, I can't remember, & I can't open the config in clockworks (MOTU's setup s/w) without the box attached. the box is 200 miles away.
it's something like "realtime" which may or may not include running status bytes. anyway, my advice is to not skimp on the merge function like I did for years, but to go out & get one of these little MOTU efforts while they're still making them!
the results in our rig are now /almost/ as tight-sounding as an arp 1613 connected directly to a pro-1.
duncan.