aescripts + aeplugins

That's a bit strange. I've tested the script in CS4 before publishing, however I've just uninstalled CS4 a week ago and I can't test it again. Even if I could I expect it to work as it did before. The script is using quite a bit of trickery to do it's thing, so there may be something in your system that prevent's it to finish it's work. What's even more surprising is that you don't even get any error messages and the script still runs. This is most unexpected. I'm very sorry, but unless we schedule a TeamViewer seesion I don't think I can do much about it at this point.

Thanks. So glad you like it. If you have any feature requests make sure to post them here, or start a support ticket in the Support > Contact so we can work out the details.

Hey. You're doing everything right. It's a rare bug that shows up on some Mac systems. I've already pinpointed it. You're the second use to report it. The bug is fixed already. Just testing it now. I'll be publishing the updated and fixed version soon.

Please contact me on FB or Skype. I'll send you a fixed version to test before I publish. Just to be sure.

please advise...
-Jon

Please open a support ticket for direct help on this issue

This is great! I'd second the need for 32b snapshots - 90% of my work is in that and switching to 8b is just too time consuming on complex scenes (compared to old fashioned cmd+shft+4) and the snapshot won't look right in 8bit. I'd also like to customize the default saving path per project, and the name of the imported folder in AE. But total great stuff as is. Thanks for making it! 

good morning malty,

I just purchased your script. and it DON'T WORK :-(

I have After effects CC and FT Toolbar.

I can't get the control box back can't use alternative way to work.

I get message:

"unable to execute script at line 1. ) does not have a value"

can you help me ?

cheers

maxim

I'll see what I can do. I can't think of anything that could cause this at the moment. If you have skype we can schedule a meeting and use TeamViewer to pinpoint what the problem is. There is one known bug in FT-Toolbar (actually in Adobe Scripting language) that causes some command keys (CTRL, CMD, and others) not to "go through", but that still shouldn't make this error happen. I'n interested to see what the problem is. Look me up on skype. My ID is: maltaannon

Seems like Custom Path is a frequently requested feature. I'll make sure to add it in the upcoming version. For now remember that you can save your snapshots at Custom Location by holding ALT key while executing the scrupt. You can set that location to whatever you want and it will be remembered next time you decide to save at Custon Location.

Hi Jerzy,

I tried the launching the snap script through ftoolbar2 and couldn't get the ctrl key to work. The shift and alt is working. I am using cs6, cc and cc2014. I cant get ctrl to open the setting dialogue box. I am using MAC.

Regards.

Ben.

Hey Ben. I got reports about this issue, not only with Snapshot, but Simple Camera Rig as well. After contacting the author of ft-Toolbar we both came to a conclusion, that there's something in the ESTK itself that masks the Ctrl key on Mac's and they simply don't get "forwarded" to other scripts. This is strange, since it worked just fine in the first version of ft-Toolbar. The only way you can invoke the Settings dialog is to run the script via Scripts > Run Script and when the Open File dialog is on screen and the script selected, press and hold the CTRL (not CMD) key and click Run/Open while holding the key.

Are you sure you're doing everything as instructed? I just had an opportunity to test the script on a brand new workstation that never hd any scripts (mine or other) with a fresh install of CC 2014 and everything works as expected.

I'm sure you know this, but just for the sake of clarity - the script can be located anywhere, but I suggest the Scripts folder (not the Scripts UI) in the After Effects installation folder. After Effects should be set to allow scripts to save files (File > Preferences > General). Before you run the script you should save your project file. After that when you run the script you should get the window asking you to set up the script. After that the default behaviour is that the window will not show again. You can change that in the script settings (the window that you just was). If you wish to bring back the window at any time simply run the script holding the CTRL key.

All of this the script "checks" for and displays instructions if anything fails (if the project is not saved, or if AE doesn't have permissions to save files).

You can check if the script works (even if the windows doesn't show) by looking in the Info panel. It always shows the name of the file that was created when you executed the script. The file name follows a naming convention that you setup and it saves the files in the same folder that your project file sits in.

I can't really thing of anything else I can do to help you out with this.
Make sure to watch the tutorial again. Maybe you missed something. All the videos are available on the product page.

Hope that helps.

As you know there's no option to do that at this point, however that is a cool idea. I'll work it in the next release. Thanks for a great suggestion.

Any update on a new version with those features?

Not yet. Working on the new release of the camera rig at the moment.

So this works with CC2014.2 and CC2015?

Yes it does.

Oh. I didn't notice that. I'll see what I can do.

Hi