Cos I need to resize my layer's output according to this calculation... ... View more

Salut! After testing a bit more, it's true that my solution isn't that ugly 😉 I finally added an Idle Hook that can print a message in the info panel. So everytime frameSetup is called, I send the number of frames computed so far, in Idle Hook I update the message and the user knows how many frames have been computed and how many are still to go. It's not a progress bar, but at least it's something! Cheers, François ... View more

Hi, I got a problem with progress bar too... Not the same, but a solution to one of the issues could may be fix the other. I have a particule system plugin which needs to compute composition from frame 0, and I need to make most of my computation during FrameSetup, so I can resize my layer's output according to particles positions. And FrameSetup doesn't support PF_PROGRESS, and actually doesn't update the progress bar at all. I'd like to find a way to warn users that the plugin is computing something, and that it's not just stuck. I tried InfoDrawText, but it seems it doesn't work anymore... I finally found an ugly solution: I stop the computation after one second, then during render call return PF_Interrupt_CANCEL, frameSetup is called again and continues computation, and so on. It results in having the progressbar 'flashing' until computation is done, and it's over all slower because of the back and forth between framesetup and render... If someone has a better solution, I'd love to hear it! 🙂 Cheers, François ... View more

Hi Tom, Unfortunately, I'm not a premiere user, so I can't tell you. Hope someone here can! Cheers, François ... View more

Great! ... View more

Great! Looking forward to see that. Cheers, François ... View more

Hi Igor, from what I can remember, CS6' Glator is broken (I think it crashes if the source size is more than 1024 pixels wide or high). You definitely should use the latest SDK, even if you build your plugins fro CS6. Cheers, François PS: Zac, when do you think the new SDK will be released? ... View more

Hi! There is a plugin called GLator in the sample effects of the SDK. It shows how to use OpenGL inside AE. To the best of my knowledge, this is the only example of effect using the GPU. Cheers, François ... View more

These Macros are just a kind of 'short cut' to usual suites. For example PF_Fill() is the same than FillMatteSuite2()->fill() and PF_COPY() is WorldTransformSuite1()->copy() I copied it from the CC 2015 SDK documentation. If it doesn't appear in the CS6 SDK, just search for fill or copy directly (without the PF), you'll probably find what you're looking for. Cheers, François ... View more

Hi, they're both in AE_EffectCB.h But generally speaking, when you hit a MACRO you don't know about, just right-click it and select 'jump to definition', it'll open the document where it's defined. Cheers, François ... View more

Then you'll have to try with options available in CS6... Check in the list above, you'll find what you need. Cheers, François ... View more

Hi James, glbinding is only one way to handle openGL textures and contexts in AE. Personnally, I do it like this: _I share one context for all my plugins instances, and each instance has its own textures. _I store everything in GlobalData, everything related to the context on one side, all the textures in a std::vector It's easier to handle (you store everything yourself so it's 'human readable'). To keep track of instances, I just use an int in GlobalData called instanceG, and one in sequenceData called intanceS. Everytime SequenceSetup is called, I increase instanceG, and copy its value in the newly created instanceS. Everytime SequenceSetDown is called, I decrease instanceG, and instanceS is cleared. This way, you'll get more sequenceData than the actual number of effects, cos' AE will create one for render and one for UI, but as long as you use your data only in the Render thread (which you should!), it won't really matter (UI instances only have 1 int to store int his case, not a real loss). Then each instance can simply acces its textures in the std::vector with index [instanceS]. Note that it is only one way to do it, there are probably smarter ways, but this one does work. And this way, my plugins weigh only a few hundred Ko. Anyway, though the new GLator is much better than the old one, it's structure won't be supported by all graphic cards / computers. Some users reported bugs with my plugins, and I had to switch back to my good old personnal structure... and it fixed it. Hope it helps! François ... View more

Hi tomb23568765! there is one workaround: expressions can read a file, and grab data from this file, like this: $.evalFile("~/Desktop/myFunctions.txt"); So, you can write an AEGP plugin that creates a "myFunctions.txt" file on your desktop, and fill it with anything you want, like: function getThingamabob(num, question) { if (num == 2 and question == 'yes') {           return true;      } else {           return false;      } } Then, your expression will look like this: $.evalFile("~/Desktop/myFunctions.txt"); getThingamabob(2, 'yes') Cheers, François ... View more

It was very promising... Probably too much 🙂 ... View more

Hi Toby, Do you mean expressions can call commands just like scripts? It's very interesting! 🙂 How do you actually do that? Cheers, François ... View more

Baking can be long, but may be not as much as you expect (I was surprised too!) The best solution I found is to actually keyframe only current time when the user's doing something (so it's lightning fast), then bake 'in the background' at idle time, one portion of the workarea after the other. This way, if the user modifies something while baking is still occuring, I can cancel keyframing and update. But in your case, if you only modify a float slider, I guess it'll be super fast anyway and you won't have to deal with delayed baking... One more thing: if you delete the keyframes (not sure you need to...) if you follow the normal way, it'll be super long (no idea why, by the way) but if you use the workaround described in the thread above, it's almost instant. Cheers, François ... View more

The plugin doesn't render any images, so I had to find an alternative to watermark for the demo version... So it only bakes one second. But full version bakes the full work area. Cheers, François ... View more

I see... My plugin is BAO Mask Avenger 2 - aescripts + aeplugins - aescripts.com The first version was modifying the mask at render time (a maskShape is a stream too). But since CC 2015, I had to do it another way. So the plugin is not 'dynamic' anymore, meaning it doesn't modify the stream at render time. But of course it is still updated when something changes. Instead, it 'bakes' the mask in the work area. With the help of Shachar, I could make it 'kind of dynamic': when the maskshape needs to be updated, all the keyframes are deleted and baked again. The deleting/baking occurs during ParamChange call of course (baking current time only, for speed reasons), but also at Idle time (it allows updating the mask even if it is modified by an expression that doesn't trigger paramchange... and bakes the remaining keyframes after ParamChange) If you want details, you can check these threads: Re: Deleting all keyframes Re: PF_ABORT and PF_Cmd_USER_CHANGED_PARAM Hope this helps! François ... View more

Hi James, I had one plugin working this way, and I had to re-write it all... with a lot of workarounds to avoid this issue. Also, keep in mind that setting a stream's value invalidates the previously rendered frames... What kind of stream do you need to set? And for what purpose? Cheers, François ... View more

Thanks 🙂 May be the layer's matrix could give you some informations, and compare it to comp's size... Just a thought though, not sure at all. Cheers, François ... View more

Hi James, I might be wrong as I'm not using text layers, but aren't text layers 'collapsed' layers (like shape layers)? Then when you check it out, it gets the composition size instead of layer size. Cheers, François ... View more

I don't know if you can pass a pointer (I doubt it, but you can try!)... Can you give more details about what you try to achieve? There must be workarounds to find... May be you can just delete the effect at idle time and do all the rest during paramChange (this way you have access to the data you need). Cheers, François ... View more

I don't know what kind of data you want to pass... But for example, if you want to pass a simple number, you could add a hidden parameter, set its value on param change, and check the parameter's value at idle time. If you want to pass more complicated data, well, you can add more parameters... If you want to re-render, you could also add a hidden paremeter and change its value at idle time, it will trigger a re-render. Cheers, François ... View more