Unfortunately that didn't work either.
Weirdly I only have terminal.app under automation and not systemevents.app
I'll contact my local MA distributor and see what they suggest.
Unfortunately that didn't work either.
Weirdly I only have terminal.app under automation and not systemevents.app
I'll contact my local MA distributor and see what they suggest.
Hi All,
Sorry for the delay. The OnPC rig with the issue is only available for me to use in the afternoon.
Unfortunately launching the app in clean start still crashes on start. Even moving the folder to backup and reinstalling has the same error.
This is the latest error I have when looking at console:
Do you have multiple network interfaces sharing the same ip range?
I Did, however I have just removed them to see if that was causing the issue. With these disconnected / turned off, the app still crashes. GrandMA3 1.6.7 booted fine with multiple network adapters on the same IP range.
Hi All,
I have an issue where 1.7.2.0 crashes upon start. It doesn't open any window, but imdeatelly brings up the crash box, saying MA has crashes, would you like to restart. The terminal app shows the below:
/Applications/grandMA3.app/Contents/MacOS/gma3_1.7.2/app_terminal
SetSockOption:Invalid argument
Failed to set option SO_LINGER on socket Noname (22)
TerminalApplication has created components
TerminalApplication is starting components
TerminalApplication has started components
Could not open optional file /Users/stjohnscontrol/MALightingTechnology/gma3_1.7.2/terminalapp/config/Console.dat for reading
Terminal started. type 'exit' to quit
Unconnected>IP addresses from different interfaces are using the same network! (192.168.1.200/24 vs 192.168.1.100/24)
IP addresses from different interfaces are using the same network! (192.168.1.100/24 vs 192.168.1.200/24)
The console app shows me:
Any Ideas of how to sort this or what to look into? - I've deleted 1.7.2.0 and tried to reinstall. Currently I'm using 1.6.7 so its not massively urgent however I would like to get this sorted if possible.
Ok.
Thanks Lars
Hi everyone.
I'm trying to send timecode to my DOT2 onPC so that it can trigger a sequence for an intro. I have timelord running on one PC sending timecode out to another PC running WYSIWYG and OnPC.
I can't seem to get the SMPTE Timecode to lock onto the signal being send. Does anyone know if there is a certain way I need to get it to see it. I've got TimeLord outputting SMTPE LTC out of the headphone jack of my laptop on the left channel which goes into the mic input of my main desktop running OnPC. Is there anything else I need to d to make OnPC see the timecode or is that it? I can see that the mic input on my desktop is retrieving the signal for timecode.
Thanks for your time guys.
Hi;
Does anyone have a fixture profile for the SGM LT-100s.
They are an LED bar with 27 x RGB pixels. So all together they have 81 DMX channels.
If anyone has a patch they can send over, it would be very helpful as I don't fully understand the fixture builder yet.
Thanks.