2016.19 and Greater - OpenGL Versions on MacBook Pro Mid 2014 Not Working

[byaky]

I have been unable to get the OpenGL versions working on my MacBook Pro 15" Mid-2104.  The most latest version that is working for me is V22 - Non-OpenGL.  The symptom that I am experiencing is that on saving or render all the application would hang.  I have tried changing to all the versions of OpenGL by rebooting both the app and pc but symptom remains.
I have tried loading xlights V26 in a Win7 Bootcamp on the Mac and the application hangs as well.
Attached is the Problem zip file.

[bravado67]

I have been unable to get the OpenGL versions working on my MacBook Pro 15" Mid-2104.  The most latest version that is working for me is V22 - Non-OpenGL.  The symptom that I am experiencing is that on saving or render all the application would hang.  I have tried changing to all the versions of OpenGL by rebooting both the app and pc but symptom remains.
I have tried loading xlights V26 in a Win7 Bootcamp on the Mac and the application hangs as well.
Attached is the Problem zip file.

Interesting. I just installed 2016.26 on the same MacBook Pro 15 Mid 2014 and have no issues. While it takes long time to save my 12 minute show everything else is good. Are you running 16gb memory?

Ron

[dkulp]

The opengl stuff should certainly not have any effect on the saving/effect rendering.    We'd likely need to see the sequence that is causing the problem.

You can also try doing a "killall -3 xLights" from the command line and then copy/pasting the stack traces from the dialog that should pop up.  That MIGHT help.   Not really sure.

[bravado67]

The opengl stuff should certainly not have any effect on the saving/effect rendering.    We'd likely need to see the sequence that is causing the problem.

You can also try doing a "killall -3 xLights" from the command line and then copy/pasting the stack traces from the dialog that should pop up.  That MIGHT help.   Not really sure.

I think it's a memory issue. I imported effects from a .lms and applied then to my props. Add in 28,000 P10 matrix along with a 12+ minute soundtrack and I  pegging some memory. If you think there is something out of the ordinary I am happy to resolve it. After all this show will not run on a pc due to memory.

Ron

Sent from my SM-G920V using Tapatalk

[byaky]

Here are my files and stack traces. My sequence on V22 non-OpenGL is about 18.3 sec to save.

[byaky]

I am able to create a new sequence from scratch on V26 and Save it.  Therefore, it must be something that is not porting from the V22 - Non-OpenGL app to V26.

[Gilrock]

I don't know of anything we do I would consider "porting".  The effects haven't changed just the way we render things to the screen so its more likely the fact that a new sequence doesn't contain the effect(s) that was causing a problem during save.  I quickly browsed your sequence file and I counted about 12 MP4 videos.   I've never tested that many in one sequence.

[byaky]

So are you saying there is a difference between V22 and V26 with how it handles MP4s?  As previously stated I can save the sequence on V22 with the MP4s in about 18 seconds.  Should I covert the videos to a different format?

In case you want to see sequence:
https://vimeo.com/165807923

[Gilrock]

No I'm just saying that's a lot of video files and I have no idea how much memory you are using to process that many videos in one sequence.  If you were near a boundary just adding a print statement could push it over the edge.  If it was me I'd try to isolate which effect might be causing a problem.  Delete half the effects then try to open the sequence in the new version.  Then delete the other half.   Then if you find a half that works and a half that fails you take the half that fails and split it in half.  Repeat until you are down to 1 effect.

[byaky]

I deleted all the videos and the sequence now saves in V26.  I will slowly add them back to see what happens.

[byaky]

The video effect is definitely the issue on my mac on V26.  I created a new sequence with only one effect which was video.  It was choppy using avi or mp4 and would shake at the end of the video.  Could not get it to loop.  The strangest effect was that when replacing one video file with another and then Update, it would play second file which was shorter and then continue with the first one.  I set to the various OpenGL versions but behaviours were the same.

[byaky]

Tested new V27 with only the one video effect in the sequence.  It appears the the video is now behaving properly in that the selections of normal, loop and slow/accelerate now work identical to V22 non-OpenGL.  The issue to be solved now is that this file saves in 3.8 seconds on V22 but 33.1 on V27.  Definitely progress.

[Gilrock]

I don't see any changes that were checked in since version 26 that would have had any effect.

[byaky]

I posted V26 and V27 video for you have see what I see:

V26 - https://vimeo.com/166132680

V27 - https://vimeo.com/166132700

[Gilrock]

Well you can goto this link and look for the commit that says 2016.26 and then browse all the commits till it says 2016.27 and see everything that changed.  Only thing I could see having an effect may be Keiths fix for video seeking.
https://github.com/smeighan/xLights/commits/master