Hello,
I wanted to share a problem I was having tonight. I've been composing a nice little Halloween Holiday show using QLC+ 4.8.1 on a Windows 7 64 bit machine. I've have great success. Tonight, I added another video function to my show. Everything was working ok up to that point. I had four previous video button/functions on my Virtual Console. I had to reset the computer and I'm not sure if I messed up and didn't properly close out of QLC+ or have otherwise caused the workspace file to be corrupted.
I thought it might be a bad reference to the AVI file, so I manually tried to delete any references/functions/buttons related to the last video I added. That didn't help. QCL+ still crashes when I try to load the workspace.
This is the crash screen:
Problem signature:
Problem Event Name: APPCRASH
Application Name: qlcplus.exe
Application Version: 0.0.0.0
Application Timestamp: 54380524
Fault Module Name: e131.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 543805bf
Exception Code: c0000005
Exception Offset: 000031a0
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: a7aa
Additional Information 2: a7aa91f17ea749d42a4de3b390fa5b3d
Additional Information 3: a7aa
Additional Information 4: a7aa91f17ea749d42a4de3b390fa5b3d
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I just feel like I goofed somehow. Only thing I can think of is that I did go back and change the file in the scene editor /video function to a different video. However, I've done that prior with no problem. I am happy that I made a recent backup, as I usually do, of the workspace file. I really only had a loss of a few buttons and restoring my show back to where I left off tonight took a minute. I'm just concerned with this event and wondering what part I had, if any, in causing this.
Hope it was noteworthy. I'm not much of a computer wiz. Hopefully, I've given enough information for it to be useful. I can upload the corrupt workspace file to anyone who might be able to assist. Maybe, it's just something obvious.
Thanks for any assistance that might be offered.
Grumpka
PS:
If helpful to know, here are my complete specs:
Intel i7 w/ 16gb ram
SSD 128gb HD
560ti Graphics card
E1.31 Bridge output for DMX
Midi input via Loopbe1
Windows 7 64 bit.
Issue: Corrupted QXW/workspace file
Hello, I've attached the qxw file. Thanks for looking at this. I'm really more so interested to know if it was me who caused this, or a QLC+ issue. I'm leaning towards something I've done.
Keep me posted. Thanks so very much for the help.
~Grumpka
Keep me posted. Thanks so very much for the help.
~Grumpka
- Attachments
-
- newhalloweenshow.qxw
- (3.92 KiB) Downloaded 50 times
I can open it on Linux.
Maybe I need to try on Windows as well ?
Is it correct that you have only Scenes and Sequences in it ?
Maybe I need to try on Windows as well ?
Is it correct that you have only Scenes and Sequences in it ?
Hi Massimo, The workspace has aprox 61 channels assigned to 61 'fixtures' as such. (all generic) There are dozens of scenes and sequences and a Virtual Console. No shows. I'm running is on windows 7 64 bit. Please don't worry too much about the file though, unless it proves helpful to the community and points to a possible bug. I've had no further issues after restoring from a backup file.
Thanks,
~Grumpka
Thanks,
~Grumpka
Hello, Sadly, I am having more issues with a qxw file not loading. Worse, I'm losing confidence. As prior, I'm using 4.8.1. Please help me if you can. Here is the file.
It's won't load. It just freezes the software dead in it's tracks. I pulled the backup file, loaded that, and it works fine. THANK GOD I'm making backups of everything. This is twice I would have lost my show. If this is related to my system, rather than an obvious bug, let me know. I would like to mention again, that I am using E1.31. I say this, as I wonder if the E1.31 address changing from time to time causes the crashes? (be kind, I'm not a programmer or a tech person, so this might be a stupid comment, but who knows)....
PS: I can't post the error screen, as I am running a Halloween Show in the evenings and don't want to disappoint those who come by to see the show. Tomorrow, I'll post a crash report.
Thanks,
~Grumpka
It's won't load. It just freezes the software dead in it's tracks. I pulled the backup file, loaded that, and it works fine. THANK GOD I'm making backups of everything. This is twice I would have lost my show. If this is related to my system, rather than an obvious bug, let me know. I would like to mention again, that I am using E1.31. I say this, as I wonder if the E1.31 address changing from time to time causes the crashes? (be kind, I'm not a programmer or a tech person, so this might be a stupid comment, but who knows)....
PS: I can't post the error screen, as I am running a Halloween Show in the evenings and don't want to disappoint those who come by to see the show. Tomorrow, I'll post a crash report.
Thanks,
~Grumpka
- Attachments
-
- HalloweenLightshow%201026%20dead.qxw
- (55.2 KiB) Downloaded 46 times
Hi Grumpka, you definitely spotted a bug and it's indeed related to the E1.31 plugin.
It seems the project tries to ouput on a non existant interface.
Resetting the IO mapping let QLC+ to open the project.
Attached.
In case it happens again (and until a bugfix is found), to reset the IO mapping you need to open the project and write this between the initial tags:
It seems the project tries to ouput on a non existant interface.
Resetting the IO mapping let QLC+ to open the project.
Attached.
In case it happens again (and until a bugfix is found), to reset the IO mapping you need to open the project and write this between the initial tags:
- Attachments
-
- HalloweenLightshow%201026%20fixed.qxw
- (33.83 KiB) Downloaded 48 times
Thank you so much Massimo. I suspect the cause was on part, as I was having IP address issues with the E1.31 bridge. I'm working on that now so the STATIC IP will stay just that, static. This certainly explains what happened. I'm relieved though. I can be more vigilant about IP's for the E1.31.
Thanks for the fix. I'll keep this info on hand. And thanks for fixing that qxw file. Much appreciated.
Kind Regards,
Grumpka
Thanks for the fix. I'll keep this info on hand. And thanks for fixing that qxw file. Much appreciated.
Kind Regards,
Grumpka