For the past few weeks Keylight has been crashing on me constantly while i use Ram Preview. It's a right pain especially when you are working on a green screen heavy project with a deadline looming. Several weeks ago it worked fine, no issues. However recently its just been crashing non stop, after checking my events viewer every error log states 'KEYLIGHT' as the problem. I currently have the newest most up to date version of the the software, have tried uninstalling/reinstalling the software, tried downgrading to previous versions of After Effects and have even re installed windows several times. I even changed my graphics card in a hope that would solve the issue but nope. My new graphics card driver is up to date and I have tried the keylight 1.2v16 update via The Foundry
I have contacted Adobe Technical support but they said that it's an issue with Keylight and to take it up with the. I have tried to get in contact with the Foundry numerous times via male and phone... but to no avail.
AE CC 2015 is the first step in a major re-architecture, separating the renderer from the UI for the first time in AE's 20+ year history. This is a big job and it's clearly still in progress. It's a necessary
step for improving After Effects performance, but it's taking a while (and multiple versions) for them to get through it. So, during this time of transition as they're introducing elements of the new
I bet transcoding helps. A lot. The image quality coming out of H.264 may be just good enough to fool the human eye, but it's very computationally intense. The first thing I do when I get H.264 footage is transcode.
Thanks for all you suggestions so far. I have now tried transcoding the footage using various different codecs - Quicktime with both Pro Res and PNG and and DNxHD, and it still continues to crash. To say this is frustrating is understatement.
I have contacted Adobe Technical support but they said that it's an issue with Keylight and to take it up with them. I have tried to get in contact with the Foundry numerous times via e-mail and phone... but to no avail.
I also tried contacting the foundry via email. Just letting em know the specs of my computer, how new it was and what i was doing when keylight would crash (literally anything that involves moving settings or the timeline) and that there clearly was a bug.
Or, instead of buying a new plugin, you could try the Ultra Keyer in Premiere Pro. You would need to render the result with the alpha channel out of Premiere for further compositing in AE, perhaps, but that's easy to do. (QuickTime with the PNG codec set to RGB+A should do it.)
I haven't had any issues with Keylight in last 8 years but when I updated to the latest AE CC 17 I have crashes in every two minutes. My project contains multiple layers with Keylight and I can't even disable the plugins, it just shows error and lets me save another copy and then stops working every time I open the project. Same happening with new projects. Someone please fix this.
So I reinstalled and unchecked the box "use hardware acceleration" but still no luck. I did not get the timestamp error but AE just showed me the dialog box "you have one last chance to save your project..." and then it quit. My project's due date is in couple of days and I'm out of ideas. Have not had such issues with previous versions.
I still use Adobe cc 2015.3 (4). I have here massive crash-problems (nearly every move), too. I use keylight and several layers. I have the impression, it crashes more often, if I use pre blur. I also use matte and treshold. keylight I use in the "combined matte" view. codec: prores 4:2:2.. I am afraid to upgrade to cc 2017, because I have to finish projects till the end of this year and unexpected problems would be too much. Best greetz.
Remember, if you twirl down the "advanced options" and un-tick the box that removes older versions during the "update" to AE CC 2017, you can install the latest version of After Effects alongside the version you are currently using. (And, don't forget that you can also install older versions alongside the newer versions too including versions as old as CS6.) So, you can use CC 2014 to see if it crashes less (probably). And you can try CC 2017 to see if it crashes less (maybe).
When the pandemic started over a year ago, like most people, I transitioned to working entirely from home. Over the last year I've made some tweaks and improvements to my home office setup to make remote working a better experience.
I have a desktop at home that has a multiple monitor setup, and I knew from the beginning that I was going to want to use the desktop rather than hunching over the laptop. The only downside with the desktop was that I didn't have a webcam. After searching through cupboards and boxes I finally found a webcam from about 10 years ago:
The C920 has a 1080p resolution which is a massive step up in image quality from what I was using before. One of the challenges that still remained was the lighting in my home office. Depending on the time of day the image can be more darker and shadowy than I'd like. The image quality and resolution is much better compared to the old webcam, but I still have a fair amount of shadow on my face.
I stuck with this setup for a few months, but after a while I started to look at different lighting panels that I could use to improve the light in my home office. I kept getting drawn to the Elgato Key Light. It certainly isn't the cheapest option, but at the end of last year I bought a Stream Deck to use as a productivity tool which has been great. And whilst most LED lighting panels are just lighting panels, the Elgato Key Light has an API that I can integrate with the Stream Deck!
Elgato provides a Control Center application for Windows and macOS which can be used to control the device. As a Linux user neither of those work well for me, so instead I used the mobile app (available for Android and iOS) to original pair the device with my WiFi network.
At the end of 2020, I bought a StreamDeck to use as a productivity tool. I use the StreamDeck to provide quick and easy access to useful shortcuts, such as being able to turn lights on and off via Home Assistant, being able to toggle audio settings which on conference calls, or quickly changing Slack Statuses.
As a Linux user, there isn't any official software for the StreamDeck which lead me to develop DevDeck. It's open source and entirely plugin based. Part of the reasoning behind opting for the Elgato Key Light was so that I could control the light via the StreamDeck.
Whilst there doesn't appear to be any official documentation for the Key Light API, it's fairly straightforward and has been reverse engineered by a number of people who've developed various API client libraries for controlling the KeyLight.
With the API being very simple and straightforward to use, within a few hours I was able to implement and test DevDeck - Key Light which is a plugin for DevDeck that will provide a button for toggling a keylight on and off.
The Logitech C920 and Elgato Key Light has been a great addition to my home office setup. It has allowed me to improve the quality of my video calls and I like the fact that I can control the Key Light directly from my Stream Deck!
In this video Dave Geffin tells us all about 6 different ways to use keylight! With great lighting examples from Mark Raker, a cinematographer and NYU educator that we also featured in our Mimicking the Light in Paintings video.
The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
Pigeons were trained to match 2- and 8-s food samples. The delay on training trials was either 0s (group 0sF), 5s (group 5sF), or varied between 2 and 8s (M=5s, group 5sV). Testing at a delay that exceeded the training delay by 15s in each group revealed a robust choose-short effect in each group. The same pigeons then reacquired a previously trained matching task involving 2- and 8-s keylight samples. Different comparison stimuli were used on food-sample and keylight-sample trials. The delay on training trials was the same on both food- and keylight-sample trials. Extended-delay testing revealed a robust choose-short effect in all three groups when the durations were conveyed by food presentations, but only group 0sF revealed a choose-short effect when the durations were conveyed by keylight presentations. Hence, training with a nonzero delay, whether fixed or variable, reduces the choose-short effect with keylight durations but not with food durations. It was concluded that at least some of the psychological processes mediating performance differ as a function of the event that conveys the duration.
When multiple RhoElememts applications are running the following considerations should be made: The keylight settings are application specific. Switching to another application which uses the keylight module will cause the keyboard illumination settings to change to those of the application with focus. Only the application with Focus will have the ability to change the keylight settings.
The levels of supported keylight intensity is device dependant. When the Keylight module is first loaded it writes the supported levels to the log file as INFORMATION so you can determine the maximum setting from the log file.
b1e95dc632