To de-activate a computer associated with your license and free-up an activation slot, you need to log in to the license manager using your Order ID and e-mail address: https://imimot.com/cogevj/myorder
Your can find your Order ID in the subject line of the fulfilment e-mail. If you lost your fulfilment e-mail, please let us know, so we can resend it to you.
After login, you will see the computers currently associated with your license. The de-activate any of them, move your mouse over the "Active" field, and click on de-activate.
In case you cannot activate your copy because there are no more seats available, but the License Manager says you have free activation slots, please try empty the cache of CoGe on your computer. To do this:
On the software side, with Syphon Recorder: http://syphon.v002.info/recorder/
You can even use capture cards or multimedia recorders on the hardware side.
Drop us a message with your order details (e-mail or Order ID).
CoGe does not support OS X 10.8 anymore starting from version 1.8.5, however you can still download CoGe 1.8.4 which runs on OSX 10.8: https://dl.imimot.com/CoGe1.8.4.dmg
CoGe does not support OS X 10.7 anymore starting from version 1.7, however you can still download CoGe 1.6.6 which runs on OS X 10.7.5: https://imimot.com/versions/CoGe1.6.6.dmg
CoGe does not support OS X 10.6 anymore starting from version 1.6.1, however you can still download CoGe 1.6.0.2 which runs on OS X 10.6.8: https://imimot.com/versions/CoGe1.6.0.2.dmg
What should you do before upgrading to Mavericks?
Is CoGe compatible with High Sierra?
Yes, version 1.8.1 is compatible with macOS 10.13 High Sierra, but in case you are running into any issues, please get in touch with us.
Known Issues
Is CoGe compatible with Sierra?
Yes, it is from version 1.7.0.3, but if you are running into any issues with CoGe on macOS 10.12, don't hesitate to get in touch with us.
Known Issues
Is CoGe compatible with El Capitan?
Yes, basically it is from version 1.6.3, but if you are running into any issues with CoGe on OS X 10.11, don't hesitate to get in touch with me.
For the best performance on fullscreen, make sure the "Displays have separate Spaces" option in the "Mission Control" section of System Preferences is disabled when using external displays.
General Issues
Quartz Composer effects and Core Image filters are leaking memory in most of the circumstances, this is a system-wide general issue on OS X 10.11. We suggest to use ISF filters instead of Core Image and Quartz Composer, whenever it is possible.
Known issues
Some QC modules seems to not working anymore on OSX 10.11 because of some OSX Core Image bugs:
The following Quartz Composer effects leaking memory which sooner or later results in a crash:
Some 3rd party QC FX not working, because of some new Core Image/Quartz Composer bugs:
Is CoGe compatible with Yosemite?
Yes, basically it is from version 1.5.2.2, but if you are running into any issues with CoGe on 10.10, don't hesitate to get in touch with me.
If you are using Hap codec, make sure you have the latest and greatest version installed: https://github.com/Vidvox/hap-qt-codec/releases
For the best performance on fullscreen, make sure the "Displays have separate Spaces" option in the "Mission Control" section of System Preferences is disabled when using external displays.
It seems 10.10 finally fixing the OpenCL Core Image memory leak which has been introduced on 10.9.
Is CoGe compatible with Mavericks?
Yes, basically it is from version 1.4.3.2, but if you are running into any issues with CoGe on 10.9, don't hesitate to get in touch with me.
If you are using Hap codec, you need to update it to make it work on Mavericks: http://vidvox.net/download/Hap_Codec_2.dmg
For the best performance on fullscreen, make sure the "Displays have separate Spaces" option in the "Mission Control" section of System Preferences is disabled when using external displays.
There is a system bug in OSX 10.9.0-10.9.5 where some Core Image filters results in a crash sooner or later because of a memory leak. All the Core Image blurs are affected, as well as the Chroma Key mixer. Maybe some of the blend modes too, but since Core Image can fallback to use OpenCL - which is the root of this issue - on 10.9 without any notice, anything which is Core Image related is probably dangerous on 10.9.
Still stuck? How can we help?