Tristan Summers
2
After Effects Coins
2
COW Coins
Forum Replies Created
-
Not much you can do with old machines. Nvme just for cache and don’t ever use h264 footage is my advice.
Ae needs the fastest single CPU core you can give it. 64gb of ram is fine for 32 threads. The GPU does very little.
Don’t use large source footage
Preview at 100% to cache timeline then Render to pro res then compress in media encoder. Faster and better quality.
Keep system clean.
.
Don’t store anything on it.
4TB nvme cache empty daily.
I’d just start again. Base any build on Puget advice.
I recently built a portable machine to take with me to studios.
It’s twice as fast my big recent threadripper. Just finished a 30min 16k@60p render on it.
Asus ap201 case
Msi pro matx mobo
Ultra 285k I think this is the main advantage. I undervolted so it didn’t throttle. Test with pugetbench and cinebench
128gb ram 2×64 as 4×32 didn’t work. More ram is always better than faster.
Inno3d 5080
Crucial t700 system drive and cache
Samsung 990 for storage and projects
Both 4tb
Everyone under estimates how important fast write speeds are.
Msi meg cooler
3 noctua f120 for the cooler
2 a120 in from base
1x a120 IN from the back.
-
I am not sure you ARE understanding things properly.
I would duplicate the person image and use tha as the matte for the wavy add layer.
That is what you would do in any compositing software to limit the edges.
I would Change the Transfer Mode of the wavy lines to Preserve Luminosity, then add a Shift Channels effect and take the alpha from luminosity, which is a nicer way to do it.
-
Also worth mentioning that the native data workflow is incredibly slow, heavyweight and clunky. I would definitely try Dataclay which is just so much more responsive and useable.
I think it is probably reading in the CSV data and carving it out in stone with a blunt chisel!
Assume you have an nvme OS, Storage and Cache drive? Helps with saving. A lot.
I have also found turning off Multi frame rendering speeds up expressions considerably.
-
Right now you will probably be fine with a base model Studio Max.
It is just a shame you can’t upgrade later, but you never know what OWC magic might happen.
Anything above the base model you are just over-paying mac tax in bucket loads.
FCP and Resolve are optimised for the M1 and always recommend transcoding to Pro Res anyway
Personally I am mostly After Effects and need RAM so won’t be jumping back Mac wards anytime soon. 128GB is actually NOT a lot of RAM these days and you can only get that with the Ultra. 64GB is fine for editing, but not for compositing and 3d really.
I also like to pick my processor and GPU , and run a decklink at proper throughput and dante card and nvme raid so prefer threadripper Pro, which, for the same money as the basic level Studio suits me better, but only just, and only because after 2013 I will never trust my business to Infinite Loopagain.
But that isn’t to say the Studio isn’t fast and does what it does well.
-
I do it by adding an invisible | to the beginning and end and kerning the first one outside the box.
Use an opacity animator, index 1, offset 1, to hide the characters. | Usually covers ascender and descender height.
I’ve also used ” to set the top right.
This way means you can add text boxes easily to the top and bottom
-
With a breakout box you can actually calibrate it properly. With a black magic one you can even use resolve.
Running three displays probably uses more pcie lanes than the processor has and you need them for any other thunderbolt devices. You could check if Apple bothered to tell you more details about their processors
People do it a lot and it seems to work for them. Been in loads of studios with 2 EXTRA UHD monitors on an iMac and hundreds of thunderbolt drives and converters. But that is really really asking for trouble.
-
I had to install. Uninstall. Reinstall and restart before resolve studio would open a project when i updated to 17.3 and 17.4.
I copied the .exe from the zip to the desktop and extracted/installed getting there.
-
Thanks for this, helped me. Why can’t it work on continuously rasterised?
Maybe an opportunity to reiterate the process of operations?
Layer sized effect can’t work if comp bleeding off edges?
-
So.
Your final deliverable will be 8 bit.
What ever it is finally viewed on will be 8bit.
Ideally you should have AE as a 32 bit project but the working space should be set to Rec709.
That way you will not be creating saturation that can never be in the final rec709 deliverable
Premiere works in Rec 709 by default. It is faking and fudging it HDR workflows
You don’t need to work in 8 bit AE project, keep it 16 or 32
Your system can handle it fine, just get as much RAM as you can, and maybe get a second NVME drive for cache
Export as Pro Res 4444 as RGB+Alpha and Trillions+ but be aware that this is full range RGB and your final video will probably be video range
You now have 10 bit clips with alpha that Premiere should interpret correctly
PNG are a bit didgy and the gamma gets misinterpreted a lot
Tiffs or EXR can be 32 bit but you don’t really ever need that and your system prtobably can’t play them properly
If you export Pro Res 422HQ Masters from Premiere and use AME to encode deliverables you should be seeing what you want. You should be judging on an extrernal monitor, ideally via decklink.
Be aware the viewer in Premiere is usually wrong.
In a year or so HDR workflows will mature and you will be able to have wider colour gamut RGB video deliverables but at the moment it is far far safer to stick to Rec709.
-
transcode to pro res and you can probably run it on your iWatch. Leave it as h264 and you will need a fast processor. smoothest playback I got was from a 4x ioFX raid0.
currently I would say (as in , if my machine died today, I would buy!)…
Processor : Threadripper pro 3995
RAM: 128GB
GPU: RTX 3080
Storage : 4 x Corsair MP600 RAID 0
Decklink 4K Extreme
Is a good place to start!
MOBO for the threadripper Pro should allow quad channel Ram and throughput to RAID should be pure PCIe
Bottom line. If it is laggy you need to transcode. Camera compressed data needs a fast processor with a large cache
side note: Afterburner card only helps with Pro Res Raw.