Hi,
I just wanted to document my experience with GLM 5.1.1. When we tried to calibrate, it emits a series of test tones for the center channel and then crashes with some sort of premature error. It never gets to the next speaker.
We performed the same task on two different Macbooks (not Sonoma) and it worked fine.
Thanks,
-Clint
0
Comments
Hi Clint!
Can you please do the following?
- Close GLM
- Delete the complete DSP folder under User > Documents > Genelec > GLM4/5
- Re-start GLM
Greetings!
Thank you! I will give this a try and report back!
Marcel,
I did try removing the DSP directory.
Here's what I get on my laptop. It just fails to get any data on the first speaker and quits.
-Clint
Are you using the default installation path and location of "Documents"? If these are moved, for example to a folder in the cloud, it would fail. Just let us know!
Yes, I'm just using the default locations for everything on the Mac version.
OK, I see. And I guess there is no firewall active preventing GLM from accessing the Documents folder, right? You can also check manually if Read & Write access is possible for the Genelec folder in Documents. Greetings!
No, I don't believe so. In fact I copied over a sam file from a computer that worked and loaded it on this machine. It had to be located in:
/Users/<user>/Documents/Genelec/GLM5/Setup Files
in order for GLM to find it.
I'll transfer this into a support ticket, Clint!
Greetings,
Marcel
Hi, I have this exact same issue, was wondering if a solution that can be shared was found?
For him it was the operating system in the end ...
Did you already try out the following?
Delete the DSP folder under User > Documents > Genelec > GLM5.
You can also try to delete the config-file (GLM5.cfg) under
C:\Users\username\AppData\Roaming\Genelec (Windows)
or ~/Library/Application Support/Genelec (Mac)
Make sure that you're using the default installation folders (no cloud folders) and that no firewall is blocking the communication of GLM with our cloud services ...
Greetings!
Ok, thanks, will try that. :)
I needed to reboot the computer for the above fix to work, all sorted out now. :)
Perfect, you're welcome!
Please sign in to leave a comment.