I’m interested and I have some questions. I appreciate any additional information. So that I might avoid this disruption.
Is this after the update to 1.1?
How many tracks were you recording?
Was the scene save done during recording or during a break?
Have you contacted local distribution or A&H corporate tech support yet? What did they say?
I’m guessing some condition of the scene file reacting with the recording software is the root issue in this story.
It seems that a hard reboot (using the power switch or pull the mains cable) forcing the unit to completely rebuild it’s software o/s is the only thing that clears a vapor lock condition. I’m certain that tech support would never encourage a user to yank the plug. I of course, have never done such a thing with an expensive piece of electronics gear (cough, cough, look at my shoes)[ ]
I have just experienced the same thing last night. Have over 40 successful events to date until during setup last evening the desk froze and screen gives I/O error messages for awhile before blacking out entirely. Hard power reset and reboot brought it back to life, but made for an uncomfortable show due to concerns of repeat lockups mid performance. I noticed that the upper USB port wouldn’t read my thumb drive yet the lower port did. Was loading some library files from the drive to individual inputs at the time of crash. Reading all these reports makes me think there is a problem with the new firmware update and its I/O interface with the USB. Perhaps something more sinister? A virus from a competitor? No, but seriously, besides that issue last night the desk has functioned flawlessly. Any clues for a fix or work around to avoid potential disruption of an entire live show? And, since I am venting a bit, where the heck is the iPad app? Dammit… See pic for screen shot of error logs.
Ps - ok, just tried to upload a screen shot and get this HTML response, 500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
There is a known issue in GLD V1.10 firmware that we are currently working on. Some scenes, with names consisting of 14 characters (which is the maximum number of letters you can name a scene) can cause the GLD to crash and reboot if you store or paste into these scenes.
We will be fixing this in the next GLD maintenance release, but for the time being you can avoid this problem by re-naming any of your scenes to 13 characters or less.
We are very sorry for any trouble this may have caused, and hope to be releasing the new firmware soon.
Please see post by AndyH above for info and an interim work around.
As far as the 14 character scene name issue blamed for the crashes, I’m rather skeptical as I hadn’t either saved or named anything at that point. I had loaded some library files into the inputs for ch 1-7 on the drum kit when it occurred. I did notice the desk wasn’t able to read my USB stick in the upper port and the lower one worked, but after some time had past and I went to the library for a different file to use, on an input I wanted to modify, it couldn’t find the USB stick at all until I removed and replaced it. Not sure how a scene name could relate to the issue. Have been told that the desk needs to be replaced due to hardware issues. Bummer is I have a show scheduled withJeff Keith from Tesla on Thursday. Hope I don’t experience a recurrence mid show. Then I look like a tool behind the console, which totally sucks. I don’t want to be that guy really.
There is a known issue in GLD V1.10 firmware that we are currently working on. Some scenes, with names consisting of 14 characters (which is the maximum number of letters you can name a scene) can cause the GLD to crash and reboot if you store or paste into these scenes.
We will be fixing this in the next GLD maintenance release, but for the time being you can avoid this problem by re-naming any of your scenes to 13 characters or less.
We are very sorry for any trouble this may have caused, and hope to be releasing the new firmware soon.
i think its not an issue with the account of characters. I have used a USB-Stick (cruiser edge) only two shows on it - one is namend G8 and the second is named Ro4…no Templates on it, GLDfolders, ca. 4BG Wavfiles nothing else and i can quite reliable reproduce the freezing by stucking in that stick into the console…if it helps, i will send that Device by post to A&H.
That could be useful. Could you contact UK A&H Support (https://allen-heath.helpserve.com/), to arrange sending it. Plus include any additional information like when the issue started and if there is anything else required to cause the problem.
That could be useful. Could you contact UK A&H Support (https://allen-heath.helpserve.com/), to arrange sending it. Plus include any additional information like when the issue started and if there is anything else required to cause the problem.
Cheers,
AndyH
A&H
Hi Andy!
After crashing down my GLD completely (by changing the IP-address…[ ] ) I could “reanimate” it and with the Release 1.11 it is fast booting and stable again.
I Just Experienced the same problem with my console freezing.
I am running V1.3 of the firmware and did not have a USB stick in the console. I just ignored it and finished out service. We have people renting our building after us and I stayed for their service to show their sound guy the new gear and how to use it. After they finished their sound check i went to save a scene for their band and all of the previous scenes diapered off the list and the scene i was trying to save wouldn’t save. I then went to reset the console and it froze on a an error screen. so I had to do a hard reset.
I just wondering if anyone has experienced this problem with firmware V1.3 installed?
I’m running an GLD 112 with firmware 1.3. Yesterday the screen was frozen for 2 times in about half an hour! I was not in a live situation. Just playing with the desc. So i restarted the console with the power switch! After the second freeze the console wokrs fine.
No USB connected! No expansion card. Only AR-2412->AR-84 connected.
I think this is getting a major incident for A&H! That should not happen in a live situation!!!
Can I suggest that if your desk ever freezes that you capture the logs and send them to A&H via the support portal on the website. Otherwise they will never be able to investigate and actually fix the issues.
Quite natural! I will sent the log to A&H. But there is nothing special in it. Maybe it is possible to start the console in some kind of debug mode to get more log information or there are more log files in the underlying unix system. I will help where i can. In my second live i’m a computer scientist an i know how hard this problems can be. So if there is a way to send a system image to A&H i would do so.
for what it’s worth, I had something very similar to this happen to my Qu-16. I suspect some flakiness in the USB/Network area. Midi implementation is very weird, seems like beta to me.
]
] ) I could “reanimate” it and with the Release 1.11 it is fast booting and stable again.
]
