Writing quality software is not a race. Aescripts.com was not created to make money, it was created because we are all After Effects users and created tools that solved real work issues we were facing. To make the tools effective and bug-free takes a lot of time and care and it is the main reason aescripts.com has been successful. I think you guys are sending the wrong message here. By encouraging users to “race” and set prices low all you are doing is encouraging low quality products that don’t benefit anyone. The After Effects community has been built around sharing and collaboration and not sales so please don’t go in this direction. It’s not good for anyone. I urge you to reconsider.
Would need to see the before and after expressions but can’t see how universalizing it would mess it up unless the expression refers to itself using the localized names. In that case I would suggest the expressions be re-written properly.
From looking at your image it looks like the Fill effect is renamed -> Fill 3 which is probably why it’s giving the error. The only effects that can be renamed are the Expression Controls.
I used the script in a recent template and receive good feedback from a Spanish users.It is important to understand that the script will work only with the expression control effects,(color, angle,slider…)I m planing to use it for other templates,since it can make the life really more easy for the international users.
@Ben, +1 on the universal tag. @Mark, want to have a lot of universal proj ?
Create a badge.
That is not correct. The script will work with any effect, the exception is when the effect has been renamed, in this case only expression controls are supported. The easy and obvious workaround is to run the script before renaming your effects. After the expressions have been universalized then you can rename any effect you want and everything will still work in every AE language.
I also think the Universal tag is a good way to go.
I am in the process of finishing a script that will translate expressions written in a localized language (including English) and will translate them into universal code that will work in any language. This should fix any issues you’ve ever had with users purchasing your templates and attempting to run them in a different language than it was written in.
I am looking for testers that can test right away so if you can’t do it this week then please don’t respond. I am also mainly looking for Windows users.
Please email me if you are willing and able to test this week.
I just finished writing a script that will be the cure to your issues. There is actually an under-the-hood way of writing expressions that is universal to any language. It’s the way AE works beneath the surface. The problem is that they are not very friendly names which is probably why AE has the localized more friendly names on the surface. Of course, as you point out, this means that they break when changing languages. What this script does is it scans the current comp or whole project and converts all localized expression calls to their under-the-hood match names.
I am in the final stages of the script so if anyone would like to help me beta test it please get in touch.
Thanks for the kind words Mark and yes, if you have a script you would like to sell please get in touch. While most of our scripts are “Name your own price” we also have a system for pay-only scripts which includes an automated serializing server that issues customized serial numbers immediately after purchase. Immigration is an example of a pay-only script: http://aescripts.com/immigration
To get in touch please email us.