Q Light Controller+

So ran the file .. loaded alot faster Not sure which scene you're using that's crashing. Also do you have a repo of the images in ~/Downloads/Tools ?

It opened after quiet some time here ... performant system
Trying to have an overlook to the channels, in DMX MONITOR, that took me like 50s ... ow boy
-how many ungrouped channels did you create? Ergo: groups anywhere?

General question. Do I need both the Fixture Groups that I put together in the round shape and the fixtures under the Universe labels at the bottom? (Photo attached. I don't think I worded that well)

Edit: Here is a link to the resources folder with everything QLC+ looks at. Ignore the other QLC+ files in there as they are outdated. It is going to be the LR Redo one. https://drive.google.com/file/d/1EqQ6zt ... sp=sharing

sandinak wrote: ↑Thu Mar 02, 2023 7:43 pm So ran the file .. loaded alot faster Not sure which scene you're using that's crashing. Also do you have a repo of the images in ~/Downloads/Tools ?

You helped me out a lot with that. Performance was MASSIVELY improved. From something like a minute down to maybe three seconds? The file size is about half as well.

So toward the bottom of the Virtual Console, I have the Light Rounds Solo Frame. Any of the grey boxes in there (I used Fireworks yesterday for the crash) while the LR Dash Logo button to the right is on will cause a crash. Pretty much the LR Dash Logo is the logo for the organization I use the lights for and it is nice to have an animation running in the back with the logo in the front. This causes the crash though.

May I ask you to elaborate your last question? I am not sure if I am understanding what you mean.

Again, thank you.

GGGss wrote: ↑Thu Mar 02, 2023 7:56 pm It opened after quiet some time here ... performant system
Trying to have an overlook to the channels, in DMX MONITOR, that took me like 50s ... ow boy
-how many ungrouped channels did you create? Ergo: groups anywhere?

I don't think I understand what you mean by DMX Monitor. Are you referring to the fixture monitor where it shows all the DMX channels? It doesn't take long for me to load, honestly. It is a mess in there though.

What is the benefit of grouping channels? I know where everything is due to the labeling in the Fixture Groups section.

I am soaking up as much wisdom as possible from you folks. Your guidance has been tremendously helpful and it is very much appreciated.

General question. Do I need both the Fixture Groups that I put together in the round shape and the fixtures under the Universe labels at the bottom? (Photo attached. I don't think I worded that well)

Yes.. The universes are different from the FixtureGroups, so you'll have (at least) two entries for each Row.

May I ask you to elaborate your last question? I am not sure if I am understanding what you mean.

I need the included files you used as RGBMatrix->Image to test .. I think I have the logo from earlier in this post and will test that.

So running now on my desktop Mac, ( it's a big one 3.8Ghz 8Core with 128G memory and no crashes. Looks like it's using quite a bit of memory and at least 2 CPUs to run this: It's been running for about 20m now no crash. I do see a small creep in the Virtual Memory, now 39.8G. Not sure what size machine you're using, but that could be the limitations you're hitting. I let it run as long as it wants and see if it keeps creeping or dies. Updates to follow...

PS> this is WITH The DMX 2-d Viewer up and LR1 being displayed .. tho poorly If you make a fixture per row with relative sizes of the fixture, you can actually visualize one of these real time ... my stage with 1 step looks like this:

May I ask you to elaborate your last question? I am not sure if I am understanding what you mean.

I need the included files you used as RGBMatrix->Image to test .. I think I have the logo from earlier in this post and will test that.

I attached a link to a Google Drive folder that has everything I link to. The RGBMatrix I was using to test with was Fireworks which is one of the built in animations. The logo you have. Here's the link again to everything QLC+ references including the actual qlc+ file: https://drive.google.com/file/d/1EqQ6zt ... sp=sharing

sandinak wrote: ↑Fri Mar 03, 2023 3:22 pm So running now on my desktop Mac, ( it's a big one 3.8Ghz 8Core with 128G memory and no crashes. Looks like it's using quite a bit of memory and at least 2 CPUs to run this:

Code: Select all

  PID   USER       PRI  NI  VIRT   RES S  CPU%▽MEM%   TIME+  Command
  64011 branson     24   0 39.4G  644M ? 117.4  0.5  5:32.00 /Applications/QLC+.app/Contents/MacOS/qlcplus /Applications/QLC+.app/Contents/MacOS/qlcplus-launcher --open /Users/branson/Downloads/Dash Room Lights LR Redo.qxw

It's been running for about 20m now no crash. I do see a small creep in the Virtual Memory, now 39.8G. Not sure what size machine you're using, but that could be the limitations you're hitting. I let it run as long as it wants and see if it keeps creeping or dies. Updates to follow...

PS> this is WITH The DMX 2-d Viewer up and LR1 being displayed .. tho poorly
Screenshot 2023-03-03 at 10.24.08.png
If you make a fixture per row with relative sizes of the fixture, you can actually visualize one of these real time ... my stage with 1 step looks like this:
Screenshot 2023-03-03 at 10.26.06.png

Interesting. I was running the Fireworks animations for a few hours yesterday and it didn't crash. Only when I put the Logo on top of it using that second button did it begin to crash after about 10-15 minutes. I'm intrigued as to why that overlay would cause the issue. The machine I am using has 16gb of memory but it supports up to 64gb. I'm fascinated that this logo is causing this much issue. Putting it on top of a solid color doesn't do this.

I may look at the 2-d viewer stuff. It just seems like a lot of work lol.

FWIW .. ran for hours no crash. So you might check resources on the runtime device

sandinak wrote: ↑Mon Mar 06, 2023 2:19 pm FWIW .. ran for hours no crash. So you might check resources on the runtime device

Thanks for letting it run a while.

I did some experimenting this weekend. I am no longer experiencing crashes when using the built in RGBScripts and that logo but I do when I use a gif with the image on top.
I am likely going to create the same shape by making a scene and although it will take a while, this should prevent the crashing I am getting.

I got the crash from an M1 MacBook Air with 16GB of memory and the machine I typically use with is a couple generations old i7 with 16GB of memory.

Here is the crash log from the Mac.

@Jacob, please do not paste long logs. Use attachments instead

mcallegari wrote: ↑Tue Mar 07, 2023 8:03 am @Jacob, please do not paste long logs. Use attachments instead

Yes sir. No problem.

So I just purchased a machine with Intel Xeon E-2124G, Quadro P2000, and 64GB RAM. I made sure the case had plenty space for airflow. It should be in place by this Friday and I can share my results.

I would like to figure out system requirements for rising pixel counts. I absolutely adore what these pixels can do and plan to use them extensively.

SPOPATT wrote: ↑Tue May 02, 2023 1:57 am So I just purchased a machine with Intel Xeon E-2124G, Quadro P2000, and 64GB RAM. I made sure the case had plenty space for airflow. It should be in place by this Friday and I can share my results.

For that budget you have a Resolume / Unreal Engine license

Have fun

GGGss wrote: ↑Tue May 02, 2023 12:21 pm

SPOPATT wrote: ↑Tue May 02, 2023 1:57 am So I just purchased a machine with Intel Xeon E-2124G, Quadro P2000, and 64GB RAM. I made sure the case had plenty space for airflow. It should be in place by this Friday and I can share my results.

For that budget you have a Resolume / Unreal Engine license

Have fun

Honestly it is a situation where I am just tired of the stupid thing crashing and I want a reliable set up. lol

I just crashed with the new machine. I have no idea what is going on at this point. I was only at 8% Memory usage and the highest CPU usage peak was 40%.
This doesn't appear to be a hardware limitation at this point as far as I can tell but I cannot pinpoint the problem.

What else should I be looking for? See logs. I cannot figure this out.

error 0xc0000005 is "Access violation error", so memory is being accessed wrong in the QT5core.dll
Something for Massimo to look at.
You now need a process monitor and a lot of knowledge to debug further / deeper...

I am open to allow a remote session into the machine for investigation or downloading whatever that would help. I'm baffled at this point.

Got another crash. Was qlcplusengine.DLL this time.