Composer Pro 2.x patch by MeeKaH
Quote from rlonnborg on September 25, 2018, 10:26 pmAre you able to use these steps to patch 2.10?
No, I got too busy with other things and didn't get chance to further research this. If you do succeed in getting it working, I would appreciate a solution post.
Quote from rlonnborg on September 25, 2018, 10:26 pmAre you able to use these steps to patch 2.10?
No, I got too busy with other things and didn't get chance to further research this. If you do succeed in getting it working, I would appreciate a solution post.
Quote from c4jedi on October 8, 2018, 3:14 pmI have done this successfully in the past.. but I has been awhile. I'm trying to get 2.5.3 to load and get the following error when I try and open to put my login info in.... please see photo
I have done this successfully in the past.. but I has been awhile. I'm trying to get 2.5.3 to load and get the following error when I try and open to put my login info in.... please see photo
Uploaded files:Quote from Bruins44 on November 22, 2018, 11:39 amhaving trouble finding the folders to place the files in
any help would be appreciated
thanks
having trouble finding the folders to place the files in
any help would be appreciated
thanks
Quote from Redkrine on January 23, 2019, 7:44 pmFor those who are still struggling with Composer, check your computer clock. On top of following the disable/enable Director and Broker services from System Manager (and applying the Meeka patch), I was receiving the "Cannot connect to <IP Address>" error, because the clock of my VM was not right. After I changed the clock, I got the script error.
I also notice that the software seems to create a new set of certificates on the Composer folder (on Users/App Data/Roaming/Control4). I've checked which certificates were created in the last Composer access and delete them.
I'm back using Composer 2.10.4.
For those who are still struggling with Composer, check your computer clock. On top of following the disable/enable Director and Broker services from System Manager (and applying the Meeka patch), I was receiving the "Cannot connect to <IP Address>" error, because the clock of my VM was not right. After I changed the clock, I got the script error.
I also notice that the software seems to create a new set of certificates on the Composer folder (on Users/App Data/Roaming/Control4). I've checked which certificates were created in the last Composer access and delete them.
I'm back using Composer 2.10.4.
Quote from Heatvent on July 5, 2020, 8:34 amHi, any reason after updating the country keeps getting erased and now when I play pandora it is garbled (have HC300, EA3 and 4 room amplifier using v2.82).
Edit:
I found a workaround. Apparently the HC300 was the input to the amp. I switched to the EA3 being the input (probably better anyway) and issue is gone. Not sure what changed on the HC300 to cause this but this setup seems to work.
Are you OK to upgrade director/controller versions? Any guidance steps for doing so? I seem to have seen instructions somewhere to install composer pro (newer version) and use that version to update although the update manager from 2.8.2 seems to want to update as well.
Hi, any reason after updating the country keeps getting erased and now when I play pandora it is garbled (have HC300, EA3 and 4 room amplifier using v2.82).
Edit:
I found a workaround. Apparently the HC300 was the input to the amp. I switched to the EA3 being the input (probably better anyway) and issue is gone. Not sure what changed on the HC300 to cause this but this setup seems to work.
Are you OK to upgrade director/controller versions? Any guidance steps for doing so? I seem to have seen instructions somewhere to install composer pro (newer version) and use that version to update although the update manager from 2.8.2 seems to want to update as well.
Quote from Heatvent on July 11, 2020, 12:25 pmJust wondering if it is safe to upgrade the directors/controllers from 2.8.2 or if there is risk of breaking something.
Thanks
Just wondering if it is safe to upgrade the directors/controllers from 2.8.2 or if there is risk of breaking something.
Thanks
Quote from brians2803 on August 27, 2020, 6:20 pmAs far to upgrades as long as your hardware support it you can go to the current version with following the instructions hear
As far to upgrades as long as your hardware support it you can go to the current version with following the instructions hear
Quote from Heatvent on August 27, 2020, 10:05 pmThanks for confirming. I gave it a try and ran into issues. The EA3 updated but when trying to continue the update, the touch panel would not update and I was getting an error:
Unable to authorize update. Connection to the authentication server failed: licenseUrl =
There were some posts online saying this was a registration issue. My controller is registered so I tried unregistering it thinking I would be able to re-register. When I type the registration code into the touch panel it tells me there was an error while communicating. So my panel is stuck at 2.82 with EA3 at 2.91 and not able to register. Any advice would be appreciated.
Update: Even though I wasn't able to register from the touch panel, I saw this post (https://www.davidsonfamily.ca/discussion-board/topic/cant-register-controller/) and noticed they were able to access Account Services in Composer 2.5.3 without dealer credentials. Using 2.5.3 I was able to register the controller and update the touch screen.
Thanks for confirming. I gave it a try and ran into issues. The EA3 updated but when trying to continue the update, the touch panel would not update and I was getting an error:
Unable to authorize update. Connection to the authentication server failed: licenseUrl =
There were some posts online saying this was a registration issue. My controller is registered so I tried unregistering it thinking I would be able to re-register. When I type the registration code into the touch panel it tells me there was an error while communicating. So my panel is stuck at 2.82 with EA3 at 2.91 and not able to register. Any advice would be appreciated.
Update: Even though I wasn't able to register from the touch panel, I saw this post (https://www.davidsonfamily.ca/discussion-board/topic/cant-register-controller/) and noticed they were able to access Account Services in Composer 2.5.3 without dealer credentials. Using 2.5.3 I was able to register the controller and update the touch screen.