dsol21
Explorer
dsol21
Explorer
Activity
‎Feb 18, 2025
03:43 AM
OK, I might be wrong, but as far as I can tell there's no point feeding ACES material into the existing Add Grain effect as it'll just clip HDR values. Converting it to Log (flat profile) adding the grain, then reconverting it back to the original space is clearly a bodge (and will clip/quantise some colour values) but it's still the best way to do it until Adobe pulls their finger out and adds a proper 32 bit float version of the Add Grain effect
... View more
‎Jul 19, 2024
08:12 AM
Actually, I was wrong - you can access Presets from FX Console. I was just saving the preset to the wrong folder! Thank you for the original suggestion
... View more
‎Jul 19, 2024
08:05 AM
That's a really good suggestion! Unfortunately, I don't think Effect presets can be launched from Video Copilot's FXConsole, only actual effects (FXconsole is so useful, I wish Adobe integrated that kind of functionality directly into After Effects)
... View more
‎Jul 19, 2024
02:58 AM
1 Upvote
The "solid Composite" effect is something I use all the time (it's very handy for making sure blend modes work correctly for lighting effects). However, for some unknowable reason, the default color it's set to use is white, not black. Can this be changed to black? It would probably end up saving me (and others!) hours of work over the course of a year!
... View more
‎Jul 09, 2024
08:56 AM
I've noticed an intermittent but extremely annoying bug that seems to have crept into the last few version of AE, whereby the effect controls panel will sometimes fail to update to show the currently selected layer.. When you click on a layer with an effect on, it briefly updates then immediate reverts to referencing another previously selected layer in another comp. This is a very annoying bug and sometimes it cause the AE UI to get stuck in a loop jumping constantly between two layer references, like two different processes are trying to acccess the same window component. It's hard to reproduce as it seems to happen randomly every now and again for me, but it's annoying enough that I wanted to report it! The only fix right now is to click on the effects control panel top, and it will open up the comp that had the layer its referencing. Then if you close that, it seems to fix the issue temporarily. I hope that the team can identify this issue! I've attached a screen recording showing the issue. This is on an intel iMac with MacOS 14.5
... View more
‎Mar 19, 2024
04:21 AM
5 Upvotes
It's absolutely maddening. Right now, the solution I use is to convert the colour space to Log (using the color profile converter), apply grain, then reverse the colour conversion. But this is a pretty shonky way to work and if your HDR values are high enough you do lose some fidelity. C'mon Adobe - this is basic stuff!
... View more
‎Nov 23, 2023
08:33 AM
1 Upvote
I think I might have found a solution of sorts for this issue, using a terminal command. I actually learned about this while I was installing some Insydium plugins for Cinema4D. Here's the command: sudo xattr -r -d com.apple.quarantine <After Effects plugin folder> (top tip: just paste in the first part up to the end of "quarantine" in terminal and add a space at the end - then, drag the plugins folder to the terminal window and it will add the correct pathname to the command). This command invokes SUDO (temp admin priviledges) so you'll need to put in your admin password. I already signed off the plugins via the security panel in macOS, so I can't test it right now. But as soon as I have this issue again, I will give it a whirl (probably when the next major release of AE comes out)
... View more
‎Aug 21, 2023
09:59 AM
I feared it might be an OS/Apple mandated thing. I'll have to see if there's any other way of easily "blessing" that cluster of plugins that seem to fall afoul of it, so this issue doesn't keep happening every time I update. Thanks for responding!
... View more
‎Aug 21, 2023
04:11 AM
Since the release of After Effects 2023 on Mac OS, I've been plagued by issues launching it every time I do an update. The issue seems to be some new security protocols that have been implemented, which mean that older plugins (which haven't been compiled using the more recent versions of Xcode) trigger a security alert on launch - bringing a up a popup window that says "Plugin: xxxxx is from an unidentified developer" and the option to cancel or move that plugin to the bin. You can force it to ignore this by opening security preferences in system preferences and then manually approving it for each individual plugin (by clicking "cancel" on the popup, then clicking "allow" in the security pref pane). As you can imagine, if you've got a couple dozen plugins that trigger this, it's a bit of a pain in the bum. Now, I'm sure some white knight will now speak up and say "Well, Dan - just update your plugins, you dinosaur!" But it's not as simple as that. This issue affects many popular free plugins, like VC Sabre and Orb. And I've got older commercial plugins that are still useful but aren't being developed any more. I just want a way to just tell After Effects / Mac OS to stop nannying me about my plugins. Honestly - they're good. They're not harming anyone! Here's a video showing the issue: https://youtu.be/IczJ5G3Or5A
... View more
‎Sep 28, 2022
03:24 AM
6 Upvotes
There's still so many essential plugins that still don't support 32bit float (or work unpredictably in colour managed space), but this is probably the most egregious omission. And GPU acceleration would be a huge boon too.
... View more
‎Apr 12, 2022
03:18 PM
Content Aware fill really doesn't like long sequences. I've been trying to use it to remove some burned in camera HUD stuff from a misrecorded take on a show, and it can't process more than a minute or two's worth of footage (in 1080i) without sucking up all system application memory and then crashing. Hopefully future versions are a bit more robust. This is a really interesting area of technology though, so I hope Adobe keep at it with their ML based development (and make better use of GPUs - as far as I can tell, CA fill in After Effects barely touches the GPU)
... View more
‎Jul 27, 2021
08:28 AM
I've been having issues, especially with small comps (eg tiny 128*128 pixel ones uses as a particle texture source). While working with them, sometimes the comp viewer window will go blank, and you can only see the content of that comp by changing the magnification (zoom level) of the comp window. I've recorded a screen capture showing the issuse in action: https://www.youtube.com/watch?v=SDFLoYdjXmc This is on an iMac running Big Sur (11.4) and the latest stable build of After Effects (18.4.0). Anyone else getting this? The problems seem to be reduced if you turn off hardware-accelerated UI windows in preferences. The iMac has a 16GB 5700XT, so can't imagine its a GPU memory related issue
... View more
‎Dec 03, 2020
09:49 AM
That's not very helpful. And I haven't found a decent USB mouse yet. I've got a Razer on my other PC, and it's far less pleasant to use than the Magic Mouse. Surely adding a user option to at least disable scroll wheel zoom (and the scrolling over tabs) would not be a crazy thing to ask for?
... View more
‎Aug 28, 2020
08:00 AM
They've done similar things in After Effects (and other apps too, I assume). It's very irritating. There's some marketroid who's decided they wanted to boost the adobe website "engagement" by making users constantly click on the homescreen button by accident. After Effects added a preference to remove this icon/homescreen after users complained. If you want them to do it for Illustrator too, you'll need to let them know too via the feedback form
... View more
‎Jul 27, 2020
10:12 AM
I'm having the same issue here with Photoshop 2020 - it's not refreshing the comp buffer after moving a layer. Turning the layer on and off doesn't remove the "ghost" layer, but alt-clicking on the layer to turn off everything but the layer on and off does fix it. I've done a screen recording showing the issue. This utterly breaks Photoshop for me and is a critical bug
... View more
‎May 01, 2020
03:51 AM
I saw a similar effect in a music video called "Eye of the storm" - there's a making of video here, which shows how they did it https://www.youtube.com/watch?v=fX-WJxkE2ks
... View more
‎May 01, 2020
03:09 AM
Yeah, this would involve a ton of roto if you haven't shot the footage with this effect in mind. If you do decide to roto it, I'd highly recommend using Mocha to do it - it can track splines, which will greatly speed up the process. The only other way might be to use edge detect filters, like the old Cartoon Edges effect. Though the results of that won't ever look really great, you might get somewhere in the ballpark of the look you need if you crush the levels enough (and maybe add some glow after)
... View more
‎Apr 24, 2020
05:06 AM
Thanks for getting back to me Nishu. I don't know if this issue existed on all versions of 2020, but I know it was doing it in 17.0.5 as I updated to 17.0.6 to see if that helped (it didn't). I've contacted Rowbyte, developers of Plexus, and they said it's supposed to work in 2020 (which it does - but just crashes a lot). I will try reaching out to VideoCopilot too. I'm running the latest version of OSX Mojave, but all GPU driver updates are handled by the OS updates on MacOS. Here's my GPU info from System Report: Radeon Pro 580: Chipset Model: Radeon Pro 580 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 8 GB Vendor: AMD (0x1002) Device ID: 0x67df Revision ID: 0x00c0 ROM Revision: 113-D000AA-931 VBIOS Version: 113-D0001A1X-025 EFI Driver Version: 01.00.931 Metal: Supported, feature set macOS GPUFamily2 v1
... View more
‎Apr 23, 2020
06:37 AM
I've found After Effects crashing near constantly on some recent projects using 3rd party plugins that use the GPU. I was doing a project using Plexus about a week ago and it would crash randomly, while working - and also during final render (again - randomly, not on a certain frame). I'm doing another job at the moment using a lot of Element 3D, Optical Flares and Magic Bullet Looks and I'm having a similar set of problems. It's crashing constantly. I saved out the project as a CC2019 one and been working on it in that instead, and so far it seems pretty stable in comparison. I'm using a 2017 iMac with 64GB RAM, 8GB Radeon 580 Pro, running Mojave 10.14.6 and latest version of After Effects 2020 - 17.0.6. Anyone else having similar issues? I'll have to work in 2019 until I know there's a fix. It seems like a GPU resource contention issue
... View more
‎Sep 12, 2019
08:52 AM
You might want to look into a tool like Open Sesame, on AEScripts. Though reading in CSV files isn't too hard with scripting. The only thing that makes it tricky is the lousy built-in IDE - ExtendScript. https://aescripts.com/pt_opensesame/
... View more
‎Dec 06, 2018
04:30 PM
Really? Was the addition of the home icon in place of the most-used function in after effects listed as one of the new features in any of the documentation ?
... View more
‎Feb 24, 2017
09:52 AM
I'm currently trying to batch some DPX's in folders to Quicktimes (using the folder names as filenames). David's Script looked really useful, but I had a few error messages when I tried to run it (first due to the position of the Undogroup, then afterwards due to it not ignoring mac .DS_Store system files). I've done some small bug fixes now and here's the updated script, which seems to work OK. I've also moved the "GlobalFPS" variable into the user variable section at the top (should really make that a dialog box too, I guess) Here's the updated script (tested in CC2017): { try{ /* MANUALLY TYPE IN THE VALUES FOR THE NEXT VARIABLES-------------------- */ var renderSettingChoice = "Best Settings"; var outputModuleChoice = "ProRes4444 trillions"; // type in the name of the default output module you want to assign here var fileNameExpression = "[projectName]_[compName].[fileExtension]"; //Uses After Effects "Output To" syntax var globalFPS = 24; // moved this into the user variables - set the correct frame rate here /* END USER INPUT-------------------------------------------------------------------------------- */ var os = ($.os.indexOf("Mac") != (-1)); //True is MAC, false is PC var sep = (os == true) ? "/" : "\\"; var dpxFolder = Folder.selectDialog("Choose folder containing source DPX folders."); var renderToFolder = Folder.selectDialog("Select folder to render to."); if(dpxFolder != null){ if(renderToFolder != null){ app.beginUndoGroup("Convert DPX to QT"); //Declare Variables var allSubFolders, allSubFoldersLen, curFolder, dpxFrames, dpxFramesLen, curDPXFrame, nameSplit, dpxFramesCollect, dpxFramesCollectLen, dpxName, dpxDuration, dpxStartFrame, dpxFPS, io, dpxImported, newDPXComp, newQueueItem, fullFilePath; allSubFolders = dpxFolder.getFiles(); //Get all files inside folder allSubFoldersLen = allSubFolders.length; dpxFramesCollect = new Array(); //Process Main folder for(var f=0; f<allSubFoldersLen; f++){ dpxFramesCollect.length = 0; curFolder = allSubFolders ; dpxName = curFolder.displayName; //Begin per DPX seq processing if(curFolder instanceof Folder){ //Verify item is a folder object otherwise skip to next item dpxFrames = curFolder.getFiles(); //Get all DPX frames dpxFramesLen = dpxFrames.length; for(var d=0; d<dpxFramesLen; d++){ curDPXFrame = dpxFrames ; nameSplit = curDPXFrame.displayName.split("."); ext = nameSplit[nameSplit.length-1]; if(ext == "DPX" || ext = "dpx" && ext != "DS_Store"){ //Verify file is a DPX frame dpxFramesCollect.push(curDPXFrame); } } dpxFramesCollectLen = dpxFramesCollect.length; dpxFramesCollect.sort(); if(dpxFramesCollectLen > 0){ //Checks if more than 0 DPX frames exists. firstFrame = dpxFramesCollect[0]; dpxFPS = globalFPS; io = new ImportOptions(firstFrame); io.sequence = true; dpxImported = app.project.importFile(io); dpxImported.mainSource.conformFrameRate = dpxFPS; newDPXComp = app.project.items.addComp(dpxName, dpxImported.width, dpxImported.height, dpxImported.pixelAspect, dpxImported.duration, dpxFPS); //Makes new comp dpxStartFrame = (Number(firstFrame.displayName.split(".")[1]) * newDPXComp.frameDuration) + 0.01; //0.01 helps fix (mostly) the frameDuration math newDPXComp.displayStartTime = dpxStartFrame; newDPXComp.layers.add(dpxImported); //Adds footage to comp newQueueItem = app.project.renderQueue.items.add(newDPXComp); //Adds comp to renderqueue newQueueItem.applyTemplate(renderSettingChoice); newQueueItem.outputModule(1).applyTemplate(outputModuleChoice); fullFilePath = renderToFolder.toString() + sep + dpxName; if(!fullFilePath.exists){ //Creates render folder if it does not already exist Folder(fullFilePath).create(); } newQueueItem.outputModule(1).file = File(fullFilePath + sep + fileNameExpression); //Sets Output To file } } } app.endUndoGroup(); }else{ alert("Folder selection for rendering was canceled."); } }else{ alert("DPX folder selection was canceled."); } }catch(e){alert(e.line.toString() + "\n" + e.toString())} }
... View more