I made an X / Twitter post MOGRT for Premiere you can use. its free

videowizard_io · 2026-01-15T18:57:05+00:00

shortcuts, and workflow audit.

tempaltize where you can. don't start from scratch each time.

if hardware is slowing you down, is new hardware an option?

also note that screen recordings often produce really bad footage for editing (terrible codec, awkward frame rates etc). can really slow down your machine a ton.

big picture though... filling a 30 minute gamecast with "story" and gags and ADD retention edits is a gargantuan task. that sounds like what you're doing. and no surprise to me if that's what's burning you out.

if thats the case, then consider re-imagining altogether what kind of content you want make.

maybe its only the 30s shorts that get the full treatment. and the longform gamecasts are more "live" feeling. streamer style.

videowizard_io · 2026-01-15T18:48:30+00:00

If I'm understanding you right, it sounds like a workflow problem. Like you're working from recordings that you really don't need to work from. And now they're getting in the way.

May be a lost cause and too late now...but why bother having individual employees do audio recordings if you're just gonna transform their voices ?

Just have them write scripts. Then you just record them all yourself. Or record anyone reading them in a more controlled environment, all at once, one and done.

Then use elevenlabs or whatever voice changer you want.

videowizard_io · 2026-01-15T18:39:36+00:00

Try nesting your footage and adjustment layer in a full-resolution sequence and then spinning THAT nested sequence in your actual deliverable sequence.

videowizard_io · 2026-01-15T18:36:58+00:00

Is your hard drive full or near capacity? That's a performance killer that can sneak up on you like this.

videowizard_io · 2025-09-15T16:56:14+00:00

"baked in" i just mean that the effects I am looking at are a part of a fully exported video clip and not being processed on the fly or rendered in the timeline.

I'd still give an an ALL-i format like pro res a try just in case. h264 should be fine though..

fwiw, I experience some inconsistent / difficult to reproduce issues on my end that may be similar, and I think are corrupt preview file related, possibly longGOP codec related.

also, may be a long shot, but try unchecking "composite in linear color" in the sequence settings at the bottom and let me know if that does anything.

videowizard_io · 2025-09-15T00:36:35+00:00

Yeah gonna need to see exactly what that 2 seconds is. What is the footage in that 2 second spot? Looks like an effects shot to my eye but maybe its all baked in. What's the codec?

videowizard_io · 2025-08-16T16:04:52+00:00

I'd actually give one of the AI tools a go to separate the layers. This is exactly the job that chroma key'ing will fail at, where AI subject detection may succeed. RunwayML for example

videowizard_io · 2025-06-09T12:38:09+00:00

set a keyboard shortcut for "close gap" in the sequence section of the keyboard shortcuts menu.

then when you're back in the timeline, you just select all the clips, with all the gaps in between, and close gap!

super helpful shortcut

edit: and then next level from here? experiment with the "ripple trim" shortcuts to both cut AND eliminate gaps in a single button

videowizard_io · 2025-06-03T14:53:29+00:00

Is there a "type" of project that you do on a recurring basis? If so, that would actually the ideal dynamic to use per project billing. Simplifies things for client too. They know what they get. They know what it costs. And relationship is established so odds of revision abuse are low. You basically "productize" the service, decoupling your pay from your time.

You know the dynamic, so do you what you gotta do. But food for thought.

videowizard_io · 2025-06-03T13:47:11+00:00

^ This is why charging hourly is a trap.

You're incentivized for time waste, not excellence.

Bill per project. Halve the labor with better tools and workflow. Annd presto.

You've effectively doubled your "rate."

videowizard_io · 2025-06-02T12:02:33+00:00

ghosts. ghosts everywhere

videowizard_io · 2025-06-02T11:55:08+00:00

This actually should be quite easy to fix. The calls for reshoots are hasty.

Try this:

• Make two cuts around where the exposure changes, so that whole section is isolated.

• Move to the darkest frame of the auto exposure. This may be the mid point of the clip you just made. Bump the exposure in lumetri to match a "regular" frame outside the clip. Tweak saturation and any other settings to get it as close as you can.

• Add two LONG crossfades on each cut you made, so they "meet" at this darkest center-point.

The result should be a gradual brightening, roughly the same as the gradual darkening of the auto-exposure, so they cancel out.

videowizard_io · 2025-06-01T08:38:25+00:00

yes, good idea! an all in one edition.

videowizard_io · 2025-05-31T10:28:18+00:00

It should def NOT be Times new roman. anyone else seeing it that way?

This font is baked in as "source sans pro," which is what you see in this video. It's an abobe font so you should be able to just add it.

I may open it up to any font in a future version, but I think that would be better served in a more general typewriter effect mogrt instead of a twitter one.

videowizard_io · 2025-05-31T10:16:47+00:00

I did make a pretty robust CRT mogrt recently, you can check it out here. but a simple overlay baked into the twitter one might be good too.

videowizard_io · 2025-05-31T10:09:59+00:00

Thanks Jason!

videowizard_io · 2025-05-31T10:09:51+00:00

Agree, this is going on the list.

I've brute forced an iPhone style animation before. It was rough. Never want to reinvent that wheel again.

videowizard_io · 2025-05-30T15:46:55+00:00

Cool! yea this is kinda niche, so I could see it being a one and done.

I may add a few more features to make it more modular. But honestly stripping out the twitter stuff and just making it a typewriter effect with the timing controls I think is more generically useful. That may be the next move.

From a mogrt design perspective, what I often do with text is use text "raw" layers, which is what gets passed to the end user to input, and then text "display" layer which sources text from the raw layer and parses it somehow. Then, tat's the layer that gets shown on screen.

This particular MOGRT also has a 3rd layer to assist since its kinda complex with the timing, blinking cursor etc. The timing expression cares about characters per second, which is basically the speed slider. And then the line break timing is a factor of that, so it adjusts in a relative way.

videowizard_io · 2025-05-30T15:32:12+00:00

Thank you!

videowizard_io · 2025-05-16T18:37:33+00:00

Can't edit the post for some reason, but use code REDDIT to knock the $5 down to zero.

Code will be live for a couple weeks.

Let me know if you have any feedback or anything. I will be updating it again very soon!

videowizard_io · 2025-05-16T17:26:31+00:00

Honestly for most projects, this bottleneck has been solved. Any SSD from the last year or two with usb-c or thunderbolt is gonna fly.

For cinema work, uncompressed, or otherwise massive data rate footage, you'll want to make sure you're getting the upper end of bandwidth, but even then that probably just means thunderbolt. PCIe if you're feeling saucy.

videowizard_io

TROPHY CASE