[Mike Horn]

I just had the same issue on a short 5 minute wav file edited into many clips. As John Watts mentioned in his post above, my issue was caused by a Graphic Equalizer (10 bands) I added to each clip. It shifted all the audio within all the clips 15 frames early as if the slip tool was used. What’s strange is that it was playing back source audio content outside the in/out bounds of the clips (15 frames before the actual in point). I swapped out the Graphic Equalizer with a Parametric Equalizer instead, which appears to have no latency issues.

Other things to note: I also have a multi-band compressor sitting on an fx slot of my master audio channel in the Track Mixer. I’m on a PC with CUDA gpu acceleration enabled.

[Mike Horn]

To answer my own question again about targeting multiple properties… this might not be the best method, but simply copying and pasting another instance of the code for each property works. Here’s what I used to target each property of the 4 Corner Pin properties:

{
var myComp = app.project.activeItem;
if (myComp && myComp instanceof CompItem){
var myLayers = myComp.selectedLayers;
if (myLayers.length > 0){
var myLayer = myLayers[0];
var myProperty = myLayer.effect("Corner Pin")(1);
for (var i = myProperty.numKeys; i > 0; i--){
if (i%2 == -0) myProperty.removeKey(i);
}
}else{
alert("No layer selected");
}
}else{
alert ("No comp selected");
}
}
//
{
var myComp = app.project.activeItem;
if (myComp && myComp instanceof CompItem){
var myLayers = myComp.selectedLayers;
if (myLayers.length > 0){
var myLayer = myLayers[0];
var myProperty = myLayer.effect("Corner Pin")(2);
for (var i = myProperty.numKeys; i > 0; i--){
if (i%2 == -0) myProperty.removeKey(i);
}
}else{
alert("No layer selected");
}
}else{
alert ("No comp selected");
}
}
//

… and keep repeating as much as you want for as many different effects and properties.

[Mike Horn]

Actually, you already answered the first part of my question Dan… found it in another post of yours: you just add a negative infront of the “0” in line 9:
if (i%2 == -0) myProperty.removeKey(i);

I’m still curious how I’d write multiple properties though if anyone knows.

Thanks!

[Mike Horn]

Thank you Dan! This script just saved the day for me. What would I change to make to make it remove odd keyframes instead of even?

Also, is there a way to target multiple properties? For example I’d like to target all the properties within a corner pin effect so:
effect(“Corner Pin”)(1)
effect(“Corner Pin”)(2)
effect(“Corner Pin”)(3)
effect(“Corner Pin”)(4)

Or can you only specify one property at a time?

[Mike Horn]

I was able to fix it by running After Effects as Admin (on Windows 10). My port is still 5030. I also added the Cinema 4DAE.exe plugin and Cinema 4DLite.exe apps to my Windows Firewall approved apps list, although I’m not sure if this would have made a difference.

[Mike Horn]

Thanks for replying Ed, I don’t have SV3pro on the Mac, but I do have it on the PC as I also have Squeeze installed. However, the pro part doesn’t seem to be activated in Cleaner XL. I tried encoding with the same settings in Squeeze on the PC w/Pro options enabled, namely 2-pass VBR. The image quality and file size is more comparable to the Mac, but like Cleaner XL, it still fails with the deinterlacing. Fine lines, especially text and other rounded graphics, come out with jagged edges, while the Mac is able to render them smooth/anti-aliased. Squeeze also encodes very quickly (almost realtime). Overall, I’d say I’m being picky with the differences… it’s not as noticeable when comparing people and faces, but noticeable on objects with very defined edges.

For now I’m going to stick with the Mac Cleaner 6.0.1 (no SV3pro). It’s able to pack finer detail and smoother de-interlacing into a smaller file size, even though it takes 3x longer to encode.

I’m now curious how Cleaner 1.5 on Mac compares to 6.0.1 and to it’s XL counterpart on PC in regards to SV3 encoding.