URGENT Nomad on Mac crashes permanent !!!

HI,

I have a big problem with my ETCnomad software (2.3.2) which is running on Macbook Pro 13" (2011, OS X 10.11.2 Beta). The application crashes meanwhile three times while rehearsals and the show starts today here at 19:00 in Helsinki, Finnland. There were two crashes of the application itself (log files attached, it happens after some hours of working with the software) and one times there was a complete crash of the system. Maybe that is a problem of my new nomad dongle (512 parameters) I get some weeks ago? There are many known problems with Mac and USB. That is the first time i have this problem.

ETC_Logs_Mac_Primary_11262015_125722.tar.gz

sclausen over 9 years ago

Please contact technical support immediately. The forums are not the place to solve show critical problems such as these.

You can contact our distributor in Helsinki (Studiotec) at Tel: +35 895 123530.

Or you can contact ETC at one of the numbers below:

For technical support in the Americas,
please call 608-831-4116
or toll-free in the U.S. at 800-688-4116 FREE
service@etcconnect.com

For technical support in Europe, The Middle East & Africa
please call (+44) 20 8896 1000
techservltd@etcconnect.com

For technical support in Germany, Austria, Switzerland, Eastern Europe & Russia
please call (+49) 8024 4700-0 during working hours or (+49) 171 733 15 33 for emergency cases after hours.
techserv-hoki@etcconnect.com

For technical support in Asia,
please call (+852) 2799 1220
techservasia@etcconnect.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
hydrogen over 9 years ago

I have no idea if the crash is related in this instance or not, but I will say that running a beta version of the OS on a mission critical system is just asking for problems...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
sstaub over 9 years ago in reply to hydrogen

Sorry, I forgot that the version on the production laptop (were the Nomad runs) ist not a beta and the last official build from Apple.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Anne Valentino over 9 years ago in reply to sstaub

Thanks for the logs. We will look at this asap and get back to you.
Best,
Anne
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
sstaub over 9 years ago in reply to Anne Valentino

Hi Anne, I installed the last sentinel drivers, but when I test the EOS software the computer crashed complete after a while (crashlog attached). Sorry but the version is 10.11.2 prerelease 4. I got a laptop with mavericks from the theater and it works fine.

apple_ceash_log_30112015.rtf.zip
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Anne Valentino over 9 years ago in reply to sstaub

Thanks. We found the crash, but need a developer to look into it. Is it possible to try downgrading your Mac (or upgrading the theatre Mac) to 10.11.1 to see if you can reproduce this? In the meantime? If there is an issue, better to find out about it before the next OS upgrade goes public! So thank you for your patience with this.

Anne
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
sstaub over 9 years ago in reply to Anne Valentino

Hi Anne, I tested the new Beta 10.11.2 prerelease 5 today, with the same result, crash after a while. So I will roll back my Software to 10.11. and 10.11.1 to see if the problem gone. It will take some days to do the backup of my system and reinstalling it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
sstaub over 9 years ago in reply to sstaub

I updated to the official release of 10.11.2, reinstalled EOSnomad 2.3.2, but the crash still occurs.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Nick Simmons over 9 years ago in reply to sstaub

Unfortunately Apple like to change in each release which breaks other software.
Apple seem to be able to break Catalyst with each version of OSX.
I've also had problems with vectorworks in the past not working on new OSX.

After being burnt a few times I no longer update my OSX for at least 6 months and actually I'm still on Mavericks because I know everything works.

I'm sure the developers will try and get this fixed in the next Eos software.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel