I am very new to QLC+. Having issues when I use Simple Desk. When I use the record or edit cue buttons the application crashes and gives the following bug report. This happens on two different computers, both running 10.9.5. I do not see any tunning items that I should use to fix this issues. It also happens when I am using my DMX output or when it is not attached.
Looking for any suggestions for where to look for help.
Thank you!
QLC + Crashing on OS X 10.9.5
-
Massimo Callegari
1- Hello to you
2- Please DO NOT post very long logs as you did. Use attachments. It went into spam and I realized only today it was there
3- please provide the QLC+ version you're using and the exact steps to reproduce the issue from an empty project
2- Please DO NOT post very long logs as you did. Use attachments. It went into spam and I realized only today it was there
3- please provide the QLC+ version you're using and the exact steps to reproduce the issue from an empty project
-
Fastler
I am in the same boat. Trying to switch control software to QLC+ and it is crashing incessantly.
I am using OS X 10.10 though. I attached my own crash log, and can show how to reproduce.
I did see on the forums a similar issue that was solved by installing OLA, and tried to do that, but even with OLA installed, the issue is unchanged.
Using QLC+ 4.8.1, steps to reproduce:
1)Start from new workspace, everything default, etc.
2)Go to simple desk
3)Hit record cue
4)Hit Edit Cue (Which incidentally causes a graphical glitch in the sliders if you have anything patched in)
5)Close edit window.
6)Everything locks up, and crashes about 2-3 seconds later.
If that doesn't do it, clicking the edit button again definitely will.
At times it has done the same thing when I record a second or third cue, and while I haven't nailed it down, it also happens if I do something with recording functions.
Needless to say, this is a problem, because it prevents me using the program at all because I can't record any cues!
Any help would be appreciated.
I am using OS X 10.10 though. I attached my own crash log, and can show how to reproduce.
I did see on the forums a similar issue that was solved by installing OLA, and tried to do that, but even with OLA installed, the issue is unchanged.
Using QLC+ 4.8.1, steps to reproduce:
1)Start from new workspace, everything default, etc.
2)Go to simple desk
3)Hit record cue
4)Hit Edit Cue (Which incidentally causes a graphical glitch in the sliders if you have anything patched in)
5)Close edit window.
6)Everything locks up, and crashes about 2-3 seconds later.
If that doesn't do it, clicking the edit button again definitely will.
At times it has done the same thing when I record a second or third cue, and while I haven't nailed it down, it also happens if I do something with recording functions.
Needless to say, this is a problem, because it prevents me using the program at all because I can't record any cues!
Any help would be appreciated.
-
Massimo Callegari
Hi, can you please try this development version to see if it crashes as well ?
https://sourceforge.net/p/qlcplus/discu ... /5ed9680a/
https://sourceforge.net/p/qlcplus/discu ... /5ed9680a/
-
Fastler
Actually, that seems to be crashing on startup... Though good news, I figured out what was actually causing the crash. It seems that when you close a window inside of QLC+ with the little red x in the corner, it crashes a couple seconds later. I switched to closing windows with the same button I used to open them and crashes went away.
I only noticed this because of the option to use the little red x was greyed out in versions before 4.8
So something is funky there, but disabling the ability to use those window buttons again will get rid of the crashes, which incidentally I got to happen on OS X 10.10, OS X 10.9.8, AND windows 7. So it seems pretty ubiquitous, but the only reason not many people are running into is that everyone is used to using the QLC buttons not the OS buttons.
I only noticed this because of the option to use the little red x was greyed out in versions before 4.8
So something is funky there, but disabling the ability to use those window buttons again will get rid of the crashes, which incidentally I got to happen on OS X 10.10, OS X 10.9.8, AND windows 7. So it seems pretty ubiquitous, but the only reason not many people are running into is that everyone is used to using the QLC buttons not the OS buttons.
-
Massimo Callegari
Fastler, it took me a while to understand the issue you are experiencing, because we use different naming.
What you are referring to is called "Speed dial window".
Yes, before 4.8.0 it wasn't possible to close it with the OS window button (which is not red on most operating systems by the way)
I just tried on Linux and it works without crashing. It might be another OSX-related issue. I'll have a look into that.
Do you experience the crash all over QLC+ ? I mean even with the Scene or the Chaser editors ?
Also, have you tried the development version I suggested above ?
What you are referring to is called "Speed dial window".
Yes, before 4.8.0 it wasn't possible to close it with the OS window button (which is not red on most operating systems by the way)
I just tried on Linux and it works without crashing. It might be another OSX-related issue. I'll have a look into that.
Do you experience the crash all over QLC+ ? I mean even with the Scene or the Chaser editors ?
Also, have you tried the development version I suggested above ?
-
Fastler
As I said, I replicated the issue on a windows 7 machine I booted up while trying to get it to work.
I swear it happened somewhere else in the program as well, but right now I can only replicate it with the "Edit Cue Stack" Window (Which I will try to call Speed dial from now on) on the simple console.
And I did try the development version, but it seems to crash on startup. Around the MIDI load point.
And incidentally, because as long as I don't use the OS buttons, it is stable, I have started using the program, and it is already so much better then what I was having to use before (MagicQ is insanely convoluted). So thanks for all your work on this.
I swear it happened somewhere else in the program as well, but right now I can only replicate it with the "Edit Cue Stack" Window (Which I will try to call Speed dial from now on) on the simple console.
And I did try the development version, but it seems to crash on startup. Around the MIDI load point.
And incidentally, because as long as I don't use the OS buttons, it is stable, I have started using the program, and it is already so much better then what I was having to use before (MagicQ is insanely convoluted). So thanks for all your work on this.