This was similar requested many times. Let's keep it easy for the beginning - not asking for - dynamic zoom like in Illustrator - or finer zoom control JUST add 75% zoom level. 50% is so small, 100% cuts of the edges. 75% would be such a pleasure to work with! ... View more

Would love to see this! At least, give us 75% instead of only 100 and 50% (and decreasing). ... View more

Well done! That's the most straight forward way using expression.   To create null objects from the *.csv data, you will need a script. Expressions cannot create objects, just manipulate the ones which are already there.   *Martin ... View more

Instead of   prevAnimations += thisComp.frameDuration;   you can add somevalue which represents the grow speed of the bar (e.g. 10px / sec) and instead of putting this to time remap, the expression controls the size or position of the progress bar. It's nearly the same code and would not require a pre-animated progress bar. If some value is now dynamically, e.g. depending on the duration of the current pre-comp, this would be the highest level of automation I can think of in a real-world scenario. In the end, you can also define other triggers to start/stop the grow, so you even don't need keyframes on the checkbox. But of course this highly depends on the use-case. A bit more code, but for sure possible. *Martin ... View more

A bit sluggish controls are usual for DUIK. I worked with 4k characters and a head rig and at some point during the project, everything get huge and the head controls and the head movements became out of sync, while dragging them. It's no wunder if you have hundreds of expressions working in the background.   I have no idea, how bad it is on your side. If you cannot process working anymore, go back to one of your backups and have a closer look to what you have added/altered in the last time. Sometimes, just a bad file can cause this, or a heavy expression.   *Martin ... View more

If you create the project in native 2k - including comps, layers, footage - it will render faster then a native but scaled 4k project. AE have to deal with the 4k items at some point of the rendering, even if you scale them down to 10% at the end.   *Martin ... View more

If you have a comp with a text layer on top, and all the audio layers beneath, you can put this expression to the text layer:   for (i = 1; i < thisComp.numLayers; i++) { songname = "None"; if (thisComp.layer(index + i).audioActive) { songname = thisComp.layer(index + i).source.name.split(".")[0]; break; } else { continue; } } text = "Now playing: " + songname;   No need for additional files, just make sure the song names in projekt panel (or OS) are correct.   *Martin   ... View more

Scripting isn't to hard, but 2000 comps are no fun in AE.  Try to just replace a placeholder with the image and put this comp into the render queue. You can apply a render preset and invoke the renderer from script. I'm sure you can add a filename dynamically, so even no need to rename the comp.   I'm not sure if 2000 images linked to AE is a good idea, either, so maybe just load, process, render, delete, repeat. If you point the script to a "source" folder, you can easily redo a single image or a bunch of images by just putting this or them into the source folder.   Share your script, if you don't mind. It's always helpful for one or the other.   *Martin ... View more

Can't you create the effect on transparent and use PS for compositing? It's pretty easy to set up such an action in PS, but to do this with AE, you need to write your own script.   *Martin ... View more

You can use this toggle to show/hide hidden layers in the compositions layers stack. If you look at the layer indexes, you'll see that there are gaps between the numbers (26, 27, 33, ...), meaning those layers are hidden.   From the follow up screenshots, I can see that you crashed the expressions. Open the template as new from source, press the toggle and don't delete the layers, but just make them invisible.     *Martin ... View more

It's been a while I've done this, but as far as I know, you need to set fields and render to i-Codec.   *Martin ... View more

You can extract the controls from the sub-comp into the main-comp. DUIK offers this options in its menu. As an alternative, which is less invasive, you can just create the slider or control you want and link the DUIK controller to this slider using expressions or just the pig whip.   In all cases, make a backup. DUIK uses a lot of expressions and its easy to mess things up when playing around with the controllers.   *Martin ... View more

Collapse transformation is activating continuous rasterization. I think, if the layer is 3D, it's CT, and if it is a vector layer, it's CR. If a layer is set to shy, CT/CR will ignor this layer. This was a hot fix to deal with effects which got broken when using CT/CR.   Motion blur not applied, but enabled. It is not an effect, but the layer option. The script is always affecting all layers. However, if the layer isn't moving, there will be no motion blur, even when it is enabled.   *Martin ... View more

I only see one set of keyframes, but you said there are two layers animated. Don't crop your screenshot and make sure it contains all altered properies (hiting u twice will reveal everything).   *Martin ... View more

If the shape is a basic (triangle, circle, and so on), you can set the corner radius in the shape options.   When this isn't working, you need to modify the path and make the animtion with keyframes. The path property can be keyframed. The process is to have the sharp * path at the start and the round * path at the end. AE will interpolate between both shapes. You might need to finetune the path points in between to make it look good.   *Martin ... View more

You need an image of the Swedish plate, just a simple flat front shot.   The replacemant should work good with Mocha. You can track the plate and insert the image. All movements and perspective changes should be covered by Mocha.   The one static shot with the kids in front of the car needs a moving mask. You need to rotoscope this one. AE should offer a good roto tool for that.   *Martin ... View more

The color change is most likely due to unmatched color spaces. Check what setting is applied in AI and AE.   The line comes from puppet tool and wrong application of it. How is the character layered, precomped and where is puppet tool applied to?   *Martin ... View more

Here is my script which I still use to enable MB (and other stuff) on all layers. It works recursivly Just grab the recursiv function and the MB part and add a check for keyframes with an if-statement.   https://github.com/mrtnRitter/OptAllLayers   *Martin ... View more

"so the layer index plus the result of the random give me one unique number" - yes, that is true and you'll get the same result just using the random in a range of 0,25. It's easier, less lines, more logic.   However, none of those approches will prevent you from getting repeated postions, because 7.4566 and 7.1293 are two unique random numbers, but math.floor(random(...)) will make both of them to 7. Using Math.round() might be a better approach, but still not a bulletproof solution (7.64 and 8.001 will be both 8).   This is a good example why expressions really should have global variables...   My recommendation is to just shift the colors, not the squares, because you cannot easily prevent having double integers, as I stated above. When only shifting colors, however, you can prevent a visual "black hole" - instead you will only get same colors two times which is hard to notice anyways.   One last glimps of hope is, that expressions might be evaluated layer by layer and not parallel for all layers. I'm not sure about this, but if AE is evaluating layerwise, you can check if another layer is already at the postion you want to set the current layer to. In this scenario, you need to know if AE evaluates from top to buttom of the layer stack, or buttom to top. Taking the second case, a layer could questioning: "I picked a random number and this turns out to a given position, is a layer below me already at this position? If yes, I pick another random number and ask again - if not, I take this position".   *Martin ... View more

I think those lines are creating the overlapping squares: if (sliderNulo+miIndex >= 24){    x=(sliderNulo+miIndex) - 24;    pos=x;   If you exceed 24, you are starting at 0 again: 24 >= 24: 24-24; x = 0 25 >= 24: 25-24; x = 1 and so on   The code is a bit confusing... if you just want to collect all positions from all layers and randomly pick one postion for each layer, who not just:    myArray=[];    for (var i = 1; i<=24;i++) {       myArray.push(thisComp.layer(i).position.key(1));    }      rndIndex = Math.floor(random(0,25));    myArr[rndIndex];   I think you can even randomize the array (https://stackoverflow.com/questions/2450954/how-to-randomize-shuffle-a-javascript-array) and take each layers index as array index to easily avoid douple postioning.   If you just aiming for shuffling colors, just randomize the color of each square.   Give us more details, so maybe we can point you to a better/working solution.   *Martin ... View more

This is just the bounding box displayed by AE. You only see them for selected layers, pressing CRTL+SHIFT+H will hide this UI overlayer.   It looks like the path is cut away because it is larger then the pre-comp. You just need to activate continous rasterization to get rid of it.     *Martin  ... View more

And what's the issue?   *Martin ... View more