Dylan Murphy
Forum Replies Created
-
I’m asking a technical question. You’re answering a philosophical one. I agree with everything you say in principle – but you assume there’s a professional crew to be interfered with on the other end of the line – there isn’t. It’s a weekly corporate web video and they want to be able to do it in house with their people. I shot the first three and they are paying me to talk them thru the next few. It’s just part of the gig.
-
I captured at 1344×840 and my target output rez was 1280×720 – I just copied the clips from one timeline and pasted them in another (with different sequence presets).
https://www.lafcpug.org/phorum/read.php?7,226728,226728#msg-226728
-
I solved the mystery and I’ll post it here (and at at the other forum I posted on) in case anyone else falls down this weird little rabbit hole.
It’s a screen capture project, w/ source footage 1344 x 840. I did the rough edit in a 1344×840 timeline – for timing and sync w/narration. I copied the sequence and converted it to 1280×720 to do the pans, zooms and final framing. From this timeline, I often sent stuff to motion for masks, mattes and graphics – and it worked 85% of the time…
But other stuff was going fuzzy. To fix it, I went back to the 1344×840 timeline – sent to motion from there and rebuilt the shot. Then brought that full rez motion file into 1280×720…
The match cuts between source footage and motion files are now invisible.
-
yes, triple checked
-
Thanks for the tip! I think it fixed the crashes I’ve been struggling with. Also speeds up render time.
-
The only way I could make it go away was to go to SYS PREFS>SECURITY>FIREWALL
and check ALLOW ALL INCOMING CONNECTIONS at the top of the pane
not the most secure solution – but nothing else worked