Technically no, as it is based on native AE effects and some of them don’t support 32 bit.
But in practice, we haven't had any problems working with Moiré in 32 bits.
Best!
Thank you for sharing the link with us, and it's awesome to know Moiré can deliver on that visual style. Also, pronunciation quirks and accent placements aside, the tool seems intriguing for creating moiré patterns effortlessly.
Thank you so much for your support! Much appreciated! Looking forward to see your creations with Moiré. Best.
Hey, the scirpt creates 14 name errors in the expressions "Error : layer named MoiréControl_1 is missing or does not exist. It may have been renamed, moved or deleted, or the name may have been misstyped" but of course there is no issue in the naming of it, what can I do?
Hey, the scirpt creates 14 name errors in the expressions "Error : layer named MoiréControl_1 is missing or does not exist. It may have been renamed, moved or deleted, or the name may have been misstyped" but of course there is no issue in the naming of it, what can I do?
Hey, we apologize for the issues you are experiencing. I can't say for sure in your case what the cause of the problem is. But there is a known issue where the expressions lose connection with the null controller when you pre-comp the MoiréControl null or rename the comp the MoireControl was initially created in.
One way to fix this is to move the control null back to the comp the null was created in. You shouldn't need to move any of the other layers. An other way is to change the comp name in each of the expressions from the name of the comp name the moire-pattern was created in, to the comp name that the null now exist in.
"ReferenceError: Function item.name.endsWith is undefinedScript file: Moire.jsxbin
Error on line: 523"
Hello, we apologize for your inconvenience. This is strange, as it isn't an error we can replicate. Could you make a support ticket and provide full details of your language and after effects version.
I have been looked into this and you shouldn't get this error unless you using a version older than v13.5 (like 2015). But there is something you could try that I would like to know if it works.
Go to Edit > Project settings > Expressions, and make sure the expression engine is Javascript.
Unfortunately I still can't get this not to work (ie replicate the error). If I change it to Legacy ExtendedScript it still don't break for me. But there might be differences in versions of AE.
There is a updated version on it's way, so if this doesn't work, don't fret. The new version will avoid using this particular function.
"ReferenceError: Function item.name.endsWith is undefinedScript file: Moire.jsxbin
Error on line: 523"
Hello, we apologize for your inconvenience. This is strange, as it isn't an error we can replicate. Could you make a support ticket and provide full details of your language and after effects version.
Edit: we just released update 1.6. Try and see if that does the trick
How interesting. My studio time has often involved attempting to remove distracting moiré, banding and noise from older videos.
Hi Peter,
I would say it's like adding grain, lens flares, or chromatic aberration. Stuff that people really have been struggling with getting rid of in different eras, but today many like to add to make a scene feel more authentic or just more awsome.
https://forvo.com/word/moiré/
Yes! In the teaser and getting started video we’ve used it in the intro and outro logo animation
One way to fix this is to move the control null back to the comp the null was created in. You shouldn't need to move any of the other layers.
An other way is to change the comp name in each of the expressions from the name of the comp name the moire-pattern was created in, to the comp name that the null now exist in.
"ReferenceError: Function item.name.endsWith is undefinedScript file: Moire.jsxbin
ReferenceError: Function item.name.endsWith is undefined
Script file: Moire.jsxbin
Error on line: 523
Edit: we just released update 1.6. Try and see if that does the trick