OpenGL and Timing Tracks

[joelchristmas]

I posted this in the Facebook group and posted my workaround.  I've had this issue since at least 2019.20.  Thought it'd be helpful to throw this one to the experts here as well.

My timing marks do not show up in the sequence tab unless I select OpenGL 1.x/2.x.  OpenGL 3.x or Auto OpenGL modes will not show the timing marks.

This is true on all three of the Macs I use (work, laptop, and home).  All three are running Mac OS 10.14.4.  All three will demonstrate this bug in every version past 2019.20...I haven't tried before that because, well, it's a pain to download and install that many versions on three different machines.   

I've attached an Auto OpenGL and OpenGL 1.x/2.x screenshots so you can see what it's doing.

There are no crashes associated with this visual error.

Thanks for any help or direction.

[Gilrock]

Maybe you should post some details about the MACs besides which OS you are running.  Pretty sure my 2009 MacBook Pro would have issues as well.

[joelchristmas]

What information would be helpful?

Each of my Macs is very different.  Two are about seven years old (iMac and MacBook Pro) and one is two years old (iMac).

[Gilrock]

I have no idea but one of the developers is a MAC user and I know he doesn't have these issues.  Unless you can tell him details about what you own we can just all move along and forget about this.

[joelchristmas]

I’ve got an acceptable workaround, but I know it’s not how the software is meant to operate.

If my problem was on one machine or in one file, I wouldn’t think anything of it.

But it’s across three Macs of various builds on all sequences (even purchased and imported) and I can reproduce it 100% of the time—even on version 2019.23—by selecting an OpenGL setting other than 1.x/2.x.

That’s why I posted it here.

[keithsw1111]

I cant reproduce it on my windows laptop so not much i can do about it.

[dkulp]

I cannot reproduce it on my main Mac either (2018 MacBook Pro 15").   I've tried both the AMD discrete graphics card as well as the Intel integrated and both displayed the timing marks find.   I'll try my other 3 Macs later this week, but I'm too busy with other stuff right now between scouts/baseball/LAX/work.

[joelchristmas]

I cannot reproduce it on my main Mac either (2018 MacBook Pro 15").   I've tried both the AMD discrete graphics card as well as the Intel integrated and both displayed the timing marks find.   I'll try my other 3 Macs later this week, but I'm too busy with other stuff right now between scouts/baseball/LAX/work.

Hmmm...are there any logs, files, or information I could upload that could help figure this out?  Surely, I'm not the only one having this issue, but it definitely seems to be something affecting a (very?) small number of (Mac) users.

The fact that I have this problem on all my machines lead me to believe it's a setting in my xLights or a conflict with some software.

With version 2019.24, I have a variation on this issue.  If I'm back in Auto GL mode, the timing marks will show upon opening a sequence, but as soon as I zoom in, they disappear...and don't reappear again in that sequence until I restart xLights.  Interestingly, I now have one sequence where the timing marks will persist. 

Still showing with no problems in 1.x/2.x mode.   

[Gilrock]

You should goto Tools -> Package Log Files and post the zip file created here.  Then anyone that wants to help can load up your show folder and see if they experience the issue.  It also can be very revealing.  I've seen users complaining about issues and then they finally give us the show folder and I'm like holy crap dude do you know  how much memory that layout is using.  Or xlights keeps crashing and you find out they have a 4 hour sequence.  In any case you almost always should post the package log files output or package sequence output if its sequence related if you need help.  Otherwise we just sit here guessing and asking questions.

[joelchristmas]

You should goto Tools -> Package Log Files and post the zip file created here.  Then anyone that wants to help can load up your show folder and see if they experience the issue.

Ah ha!  Didn't know that feature was there.  I've uploaded my log files with this post.  Thanks!