Search
156 results for “stooovie”
-
And the new Quick Apply feature is fantastic! I wouldn't use #AfterEffects without FX Console but this can apply the filter to a new solid or adjustment layer without having to create it first! Great idea!
It even names the newly created layers after the applied filter!
-
Object Matte (Roto Brush 4) in new #AfterEffects beta is cool but why does it run only on two cores and uses no GPU? Surely it could be paralelized further?
-
An amazing plugin for #AfterEffects that procedurally simulates torn paper edges.
-
3D Camera Tracker in #Aftereffects 26 stuck forever on Initializing. Working fine on the same footage in 25.
-
When I retire, I'll finally have time to organize my #AfterEffects scripts.
-
Typical #FCPX bullshit. Missing but not really, and can't be relinked.
And no, dragging the original (which CAN be Revealed in Finder) doesn't fix it.
-
Transcript Search in #FCPX! Hosanna! Coming right in time.
EDIT: aaand it's English only, so useless for me. I'll throw it onto the big pile of other features I pay for and cannot use.
-
Just adding Hue/Saturation Curves adjustment to a clip in #FCPX changes the levels. Without actually adjusting anything. Crazy.
-
I HATE when apps assign keyboard shortcuts nominally (which vary with keyboard locale) and not based on physical location, so I have to remap everything for my keyboard locale. And in some advanced apps, that's dozens if not hundreds of shortcuts.
Example: #Resolve uses opt+number for targeting tracks, but Czech QWERTZ uses shift for numbers, so "opt-2" is actually "opt-ě" on the physical keyboard. #FCPX doesn't have this issue.
-
This fucking thing in FCPX multicam UI is the bane of my existence. I don't switch audio with video, EVER. It randomly resets.
-
I've made a #Keyboardmaestro macro that allows me to get a transcribed clip from a timeline imported from #Resolve and match it back to the original multicam file in #FCPX :))
30 keystrokes replaced by one!
This would be impossible with Resolve itself as it's not as driven by keyboard shortcuts as FCP!
-
#FCPX 11.1.1 on Sequoia 15.6.1 started hanging on every launch, regardless which library is getting open (even completely newly created ones). Sometimes it helps to open the library file while holding Optinstead of launching the app, but not always.
Resetting prefs, reinstalling FCPX or revalidating AUs don't help.
-
#FCPX proxy workflows are broken beyond repair.
If your library has a substantial number of ranges, markers, smart collections (which is very normal in doco editing), it WILL crawl to a halt, beachballing on every step. This does NOT happen when original footage is present.
This is a new Library made with 11.1.1, proxies made by FCPX. Nothing is on cloud or network, no weirdness. Happens on EVERY project for years.
-
Oh god there's "Select Next/Prev Color Correction Effect" in #FCPX. How did I miss that? No need to mouse around.
-
Get the amazing Max Mustard for #QuestVR at 90% discount.
I tried it, working even in EU. Very well worth it. It's a great Mario clone built for VR.
-
I have a new, massive issue in #FCP 12.x.
Playback in the Viewer doesn't follow the active panel (Browser or Timeline) when in List view. If I match frame ("Reveal in Browser") from TL, or switch to it with keyboard shortcut, the Viewer continues displaying what's in the Timeline instead playing what's in the Browser. Unless I physically move the cursor into the Browser area, Viewer doesn't play its content.
Trashing FCP prefs didn't fix the issue. FCP 12.2 on Tahoe 26.4.1.
Anyone else?
-
Pretty detailed writeup on video editing with #FCP on Macbook Neo
https://volatileinputs.com/2026/04/some-notes-on-editing-4k-video-on-the-macbook-neo/
-
For whatever reason the name Kanen Flowers popped up to my mind - a former prominent VFX artist and #FCP evangelist, later a finance bro, now arrested for AI and crypto schemes and fraud.
Heh.
-
#FCP on a M4 Max Studio exporting a 50m timeline inside three minutes is really something to behold
-
Free and local automation plugin for #FCP - profanity bleeping, silence removal, non-english subtitle generation...
-
#FCP 12. Analysis for Visual Search fully completed. No search returns any matches. Upon restart of FCP and retrying, FCP hangs for a minute or two on search, and then returns nothing anyway. New install of Tahoe 26.2 on a new Mac Studio M4 Max 🤷
-
For some time now, to switch to the Browser and actually see the playing source footage in #FCP, I need to move the cursor there. Just switching with a kbd shortcut only plays audio. Focus switches there but image in Viewer doesn't. This is a new, fresh install of both FCP and MacOS on a new Mac but happens on my other Macs too. Not new in version 12. Been the case for some months. Maybe related to Tahoe (26.2 now)?
It's extremely annoying and it slows me down af
Anyone else?
-
Beat Detection crashes #FCP 12 👍️
-
-
Also, the usual advice of zipping the older version of #FCP to get back to it is moot as it always says "FCP is damaged and can't be opened". Hasn't worked for me for quite some time. And yes, Gatekeeper IS set to allow all sources.
Restoring from Time Machine does work.
-
Okay, so transcription in #FCP 12
- English only
- no transcription of multicams or synced clipsIn other words, 100% useless to me
-
The downside of having your blood glucose in check is that when you inevitably don't for a bit, you feel like absolute dogshit. #t1d
-
@stooovie good call! Migrated away from my armada of #raspberrypis last year (to an old zotac, which runs only #homeassistant, a dedicated #nas and a beefy optiplex for #plex et al.) and have never looked back. I guess running constantly at the limits of performance is not good for any system. #proxmox is nice but centralisation of everything on one machine, even in containers and virtual machines, has not worked well for me. I hope you have better luck!
-
@stooovie good call! Migrated away from my armada of #raspberrypis last year (to an old zotac, which runs only #homeassistant, a dedicated #nas and a beefy optiplex for #plex et al.) and have never looked back. I guess running constantly at the limits of performance is not good for any system. #proxmox is nice but centralisation of everything on one machine, even in containers and virtual machines, has not worked well for me. I hope you have better luck!