[Jim Lino]

Thanks a lot!

[Jim Lino]

Also… figured out how to combat the giant roto box… in case anyone else has this issue…

Use the negative tool brush, start from the top of the frame, off-screen, and make a single line straight down. That’s it… the roto will disappear.

[Jim Lino]

That’s right, same shot, Blaise. Dave suggested I use rotoscoping with AE rather than masks with Premiere. And it’s true, I’m a novice… but most videos just aren’t thorough or communicable enough. (any suggestions?) The real knowledge is only given out in pieces. So I am watching them, for sure, Adobe stuff all day… but there’s only so much you can do until you have to just dive in and do it yourself.

And for that extra little stuff, you gotta come to a place like this, right?

However, you’re right. I was finally able to complete the shot with a little more patience. But not sure if it was a little due to my pc… although I got a i7700 cpu, 1070 gpu… seems like AE was a little sluggish at times.

I had to let the renderer catch up, basically…. there was a point where the roto tool was temporarily freezing AE…. I’d make a slight adjustment….. the window would go black…. I’d wait about 2 min… and the picture would come back and the roto brush would be live again.

After about an hour of this….. the system eventually caught up to me at a 1:1 speed. It then took no time at all to finish the roto…. what took me days of trying…. I did it in 12 minutes once the program “woke up” and let me do it.

Thanks for the help.

[Jim Lino]

Deleted my work, started over from scratch…. and I’m still getting this issue. It does about 10 frames of the rotoscope, then on the following frame, the entire frame fills up as a single roto….

Like in this photo, everything is ok:

However, in the very next frame, I get this… notice the purple roto line fills the entire frame:

Am I just not moving it forward correctly?

thx for any help!

[Jim Lino]

Ok thanks for that confirmation. Sometimes I expect these programs to perform flawlessly and just assume it’s my error somehow (of course, most of the time it is).

I’ve got AE and while I’m not as comfortable with it, I’ve gotta suck it up and get on it it cuz I know it’s a valuable tool.

Thanks again for the help.

[Jim Lino]

Dave, you sure there isn’t an easier way with Premiere?

I know I said the word “rotoscoping” but it’s just masks that I’m messing with here.

How does a mask set in stone on Keyframe 1…. then distort itself…. after work on Keyframe 25 is completed….?

It doesn’t matter if that mask is a square or a custom line…. it shouldn’t change/erase the work.

If you needed to blur out the McDonald’s logo in your video… you’d create a mask, dial up the blur, and move the box along each frame (I know you can auto) in line with McD logo. What is the difference here? I don’t think you’d take that example into After Effects to do…?

[Jim Lino]

Ok thanks, Dave! I’ll try that.

Kinda reminds me of that old Seinfeld episode about how the car rental company knows how to “take” the reservation, they just don’t know how to “hold” the reservation.

Premiere knows how to let me make the mask, just doesn’t know how to hold the mask in place once I click over to the next frame.

[Jim Lino]

Ok thanks a lot. Those tips reaffirm things.

However, I think this is a hardware issue now. I’m having these problems at the work pc…. I took my project home and am not getting the frame tearing, after I redo the sequences.

I had really always just been doing it a basic way — 60fps and applying speed effects or regular time remapping.

After reading your advice, Modifying>Interpreting the clips individually that I wanted to slow down did make a smoother difference instantly…. and it did look nicer with the Warp Stabby. I’ll also try that longer method of exporting the stabilized clips, too.

Now, my IT guy is trying to figure out what could be wrong with the work computer.

It’s almost identical to my home pc…. they’re both intel core i7700k, 16 ddr4 ram and a nice gtx 1070.

On occasion, the work pc has shown a GREEN SCREEN in the top-left source viewer window…… it’s shown single RED FRAMES when scrubbing thru raw footage….. and some other weird issues.

Thanks for helping me with my workflow situation…. don’t really wanna bother you guys with these troubles. I’m sure he’ll figure it out…. maybe the previous video guy before me was mining some bitcoin on the side with the gpu or something and wore it out…?

[Jim Lino]

Right, that’s what I shoot at…. 1/125th @ 60fps.

Now, here’s one of the reasons for my confusion….

When starting a new project and before even importing the raw footage, if the sequence settings are set to 29fps or 25 or whatever (the default for DSLR Editing Mode)….. as soon as I go to make my first edit on the timeline… a message will pop with Premiere suggesting I change the sequence settings to match the footage.

I can choose “no, keep current settings”…. but in the past, I’ve typically chosen to go with its suggestion and match the footage. And if that footage is 60fps… the timebase becomes 60fps. So where am I going wrong there?

But ok, interpret footage, I’ll make use of that now. Workflow-wise, you use “interpret footage” really on a clip by clip basis, then, correct? You’re using interpret footage primarily for slow-motion purposes and just modifying that clip when the time comes?

Thx again!!

[Jim Lino]

Well, I’ve been experimenting with all different settings to try to figure it out. The 60fps timebase was just my current setup this time.

Creating a new project, changing to a 25 or 30fps timebase did not solve this issue. I got just as many frame tears as before. ☹

Thanks for the reply, Blaise.

Could this be a hardware issue? Needing more than 16gb ram??