I'm having the same flickering on iPhone -- even with the preventDefault and return false options of canceling the default click event. It appears that on the device it tries to go back to the top of the page before scrolling. If you have both a scrollTop and scrollLeft animation going on it really gets buggy. It's jQuery's issue.. I've seen a scrolling method with mootools that doesn't have this issue. See this page:
Thanks for making a very cool plug-in!
This makes creating and manipulating a nice looking flicker effect very quick and easy. However, I have 2 important questions:
1) Is there a way to see the dimmer value of the light running the effect?
In the picture below I have Dim 1 running a normal phaser effect, while Dim 2 & Dim 3 are running your MyFlicker plugin. The white square in the far left column and the orange dimmer bar in the Dim column depict the light flickering away, but since no actual values are shown, I am unable to tell what the actual levels are. (e.g.: My gaffer might ask me what are the High and Low values for Dim 2, and I won't be able to tell him)
2) Is there a way to adjust the existing parameters of a light running your plugin?
As far as I can tell (and I may be missing something), I cannot seem to view or edit the existing parameters of a light running the plugin. I can certainly select the light and run your plugin again, but that will snap the values of each parameter to whatever they were the last time I used the plugin, and NOT to what the light was actually running before.
Example: I have light in Dim 3 that's very close to the actor's face, just out of frame. I use MyFlicker to give it a nice subtle 5-10% flicker.
Then I've got a light in Dim 2 shining against a background wall, and need a much brighter flicker, so I select that light and use MyFlicker and adjust the settings to give it a bright 90-100% flicker.
Now I need to go back and adjust the parameters of Dim 3. If I select that light and hit MyFlicker, the light will slam to 90-100% and blind the actor, since those were the parameters last time I used the plugin. Is there any way around this?
I think the solution here is to store your flicker to a preset before storing it to the cue. That way you can go back to the preset when you want to edit, as opposed to recreating the flicker, which is what you're doing when you call the plugin a second time.
Thanks for the quick update Andreas
jfarrow Sure I can save the generated 64-step phaser effect to a preset, but editing that phaser to adjust something equivalent to what was once the High or Low value is a pain. A lot of gaffers I've worked for like to have very specific and granular control over the effect, such as: "let's see a flicker between 30-50%, okay bring the top end down to 45%, alright let's try bringing up the bottom to 35%" and so on...
Having to dive into the phaser editor and manually grab all the highest points in the graph and try to drag them downwards a couple points is not efficient.
I've worked on period films and projects that are lit entirely by candlelight/lanterns/etc, so I may have a couple hundreds lights in a scene all running some variation of a flicker, and I need the console to allow me to tweak those settings for each light on the fly.
Description XEffects Insta Splits are a set of animating grid layout plugins for Final Cut Pro. They have been designed especially for vertical video (9:16) projects. Build your split grid from halves, thirds, quarters, sixths, eighths...
Description XEffects Tracking Callouts are a set of callout title plugins for FCPX that feature built in object tracking. Just select an area and then let the plugin analyse movement of the object...
Description XEffects Messages are a set of Final Cut Pro X plugins that emulate an onscreen conversation via SMS, iMessage, Facebook and WhatsApp. NEW! Messages 2 adds tracking to individual messages and...
Description XEffects Insta Transitions are a set of transition plugins for Final Cut Pro that have been designed especially for vertical video (9:16) projects. Vertical video is becoming more popular every day...
There is nothing worse than having nasty flicker on your images, and I think a lot of people are unaware that there are ways of reducing it, or in a lot of cases getting rid of it entirely. Flicker Free from Digital Anarchy was originally designed for de-flickering time-lapse shots, but the company actually found it worked really well for getting rid of flicker that occurs in many other forms.
Sensitivity
This affects how much of the image Flicker Free is looking at. Usually set this between 10 and 30. If the flicker is affecting the whole frame, higher values are required. For smaller areas, set to a low value.
As I mentioned earlier, flicker can occur from a wide array of shooting scenarios. Flicker is sometimes very obvious and easy to see, but if you happen to be shooting in say 25p 1/50th shutter in a country that is 60Hz, you can get flicker in your images that is not evident on your monitor or viewfinder at the time of shooting. Flicker Free can get rid of this very easily.
A time-lapse video requires taking a photo or a video frame at set intervals (eg. 1 sec., 10sec. 1min etc) and combining them to make a video. The biggest problem with doing this is that the exposure tends to change between frames. When played back this exposure change shows up as a kind of flicker in your final result.
Digital Anarchy has developed a plugin called Flicker Free. Working with FCP, Premiere Pro and After Effects (among others) it very effectively removes flicker from time lapses, slow motion and refresh rate phasing (LED lighting and monitor screens).
Time-lapse is a widely used filmmaking technique. It was first made popular during the video DSLR movement and since then a multitude of accessories and software support to improve the workflow has been developed. One aspect of these is flicker reduction software, smoothing out exposure shifts over a long period of time.
LED and monitor screen flicker modulate and band. Slow motion can also, stem from light sources and can be a lot more prominent than exposure shifts within time lapses. For these reasons, the same flicker reduction tools have not always been effective. Where these time lapse-specific flicker reduction tools fall short, is where Flicker Free steps in.
Philip Bloom made a tutorial on a DIY method for slow-motion flicker removal. This is only effective with certain types of slow-motion flicker, where the conflicting light source is strictly on/off (no modulating). Opacity blending frames can also create a kind of motion blur, so the technique is not always effective.
The plugin by Digital Anarchy is quick and simple to use, working seamlessly with your parent NLE system. It contains a few presets including time-lapse, slow-mo and a few different types of LED lights and monitor screens. It then has a few parameters including sensitivity, threshold, time radius, and ability to analyze channels independently/together. I strongly recommend checking out the instruction manual found here for explanations of how each parameter affects your outcome.
I'm trying to clean up some footage shot under flourescent lighting. I've downloaded the Flicker Free plugin, but it's not coming up in effects. I've done all the steps in this post, but it's still not showing. Any advice?
You have to purchase the plugin and install it. If you have purchased the plug-in and installed it according to the instructions then you may need a reboot or a compatibility check. If that fails, contact Digital Anarchy.
My camera recorded flickering (black flashing) video, maybe due to low-lightened room. I cant purchase the de-flicker plugins to fix the that video.is there any free solution to fix that, with plugins or filters?
No need to reinvent wheel, there are priced plugins for it. I can't remember but there was a good plugin in market, named "de-flicker" or "anti-flicker" with free trial to test, which did excellent job!
As of X-Plane 12 beta 1, cockpit displays and 2D windows produced by third party plugins (like AviTab or FlyWithLua; whether XP12 compatible or not) do render, but flicker. The frequency of said flickering is not constant and somewhat depends on which direction I'm looking and (oddly enough) what's going on outside (like rain).
That's not actually correct. The overall rendering does use Vulkan, and any plugins that want to place elements in the world would need to use Vulkan. But plugins can (and mostly do) still use OpenGL to render their displays, there are still compatibility bridges for that in place.
Is Laminar even aware of this? Besides of the interactions on the mesa bug-tracker, I see no mention of Vulkan AMD related issues on the know bugs in release notes for the beta. Again, because it is something that happens between the 3rd party plugins and the sim we are in a kinda of limbo. Laminar tells us not to report 3rd party bugs, and because the issue happens across a large variety of 3rd party plugins the devs themselves will direct us to Laminar.
The funny thing about the flickering is that I can minimize it for 2D windows by filling the view with close-in geometry, i.e. by looking at the cockpit back wall and therfore driving up framerates to my monitor's refresh rate limit.
aa06259810