Playhead Starts Itself?

Hi.

I am seeing the GP playhead start (go to On) seemingly on it’s own. Logically, that should not be possible, but that’s the way it seems.

I’ll be playing on my Seaboard and out of the blue the playhead comes on (triggering a count-in, which I have scripted to happen when the playhead comes on). Link is not on, the only data arriving in GP AFAIK is the data from my Seaboard.

I am writing to ask if anyone else has ever experienced this, and if so, do you remember what the actual culprit was? Thanks.

Spacebar will toggle it on/off.

Your count-in is done my the GP metronome? Maybe you could share an excerpt of your script?

Indeed, but I’m not touching the spacebar in these cases.

I am touching the Seaboard. Something is happening (repeatedly, but not consistently) when I play the Seaboard, resulting in the playhead coming on.

True, but that doesn’t mean the keyboard isn’t sending out a spacebar command due to a malfunction. Just to be on the safe side, I would disconnect it while experimenting to remove it as a possible source of the issue.

I’m also curious to see if, after the playhead turns on, you keep playing and at some point it gets turned off.

No, it stays on until I manually turn it off.

That would suggest its not some random toggle, since it would be just as likely to toggle off at some point.

Is there a line(s) in one of your scripts where you have EnablePlayhead(True) ?

Thanks for the suggestion, but that line is not found in any of my scripts.

FWIW, I do check the Playhead status, which shouldn’t matter.

TrippleB: Here is my rackspace script, imperfect as it may be.

MFP Start with CountIn 05.zip (2.2 KB)

I didn’t see anything obvious (though I’m hardly a decent script diagnostician).
I guess my suggestions are remedial at this point. Start simple, with a blank gig. Add things slowly until you can reproduce the issue. :man_shrugging:

1 Like

OK, I have now managed to demonstrate the problem happening in a New Empty Gig.

IOW, from a New Empty Gig, with the Seaboard’s MIDI In port enabled, I play the Seaboard and eventually the playhead will come on.

With that port disabled, I can play the Seaboard indefinitely w/o the playhead coming on. (I would say “obviously” here, but I’m trying to avoid all assumptions!)

(upload://6TlgGzzZmsU7qERM0NblAuqKv3J.zip) (4.0 KB)

Here are a couple of Global MIDI Monitor reports of data streams prior to and including the playhead coming on.

Seaboard MIDI Stream 01.zip (4.0 KB)

Sigh - there’s no magic here — something is responding to your input and triggering the playhead.

  1. Have you assigned anything to the Play/Stop global assignment?

Thanks for the suggestion, but no, I have not.

So with no scripts present, and hardly anything in the Wiring Diagram, where else to look?

Maybe start the global midi monitor, play until it happens and then try to find some anomalies in the list around that position…

That’s exactly what I’ve done, and posted two as-reported data streams above. I don’t see any anomalies so far (e.g. MIDI start/stop messages)

Is it considered absolutely certain that every MIDI message gets reported by the global midi monitor?

Does anybody else around here have a Seaboard Rise 2?

No, a few system messages get intercepted too early. I don’t think Start/Stop get tracked. If your seaboard is sending those out, that would definitely trigger the playhead

OK, nothing in the Seaboard docs or in the Roli Dashboard UI indicates any sending of MIDI Start/Stop/Continue.

However, examining my Roli Dashboard did reveal to me a couple of “anomalies”.

I don’t know how those got that way, but I undid them by invoking the Roli Dashboard ‘MPE - default’ preset and (fingers crossed!) that seems to have solved the GP playhead starting for no obvious reason. I will report back if I see otherwise going forward.

I’ll express that for diagnostic and troubleshooting purposes, I think it would be helpful if somehow it were possible to see absolutely all MIDI incoming to or outgoing from GP.

Whether this would be in the Global MIDI Monitor (by default, or as an option), or whether certain “pre-processing” messages were somehow separately displayed, knowing for certain exactly what MIDI is there or not there at the in/out boundaries of GP is desirable, IMO.

Just use Protokol for such things.

1 Like

That’s a worthy thought to add to this thread. Sometimes Protokol may help and people should know about it.

Notable also though, is that a list of what X sends (which is what Protokol offers) is not the identical thing as a list of what Y receives. Only Y can actually supply that.

I’m for shining the light in every corner!

I suppose resetting to the “default” setting could have corrected something else that was causing the issue too. (?)