John Pale
Forum Replies Created
-
What frame rate are the cameras shooting at?
-
“Load Filler” in the source monitor. Insert Edit between two clips.
-
It’s an easy firmware install to make a 4,1 into a 5,1. Takes 2 minutes. Yes, it’s a hack, but the computers are basically identical, so the 5,1 firmware works fine.
My Mac Pro is a 2009 (4,1) that was a 2.23 GHZ 8 core which is now a 2010 2.93 GHZ 12 core (5,1).
The actual processor upgrade is challenging, but no need to do that if your goal is merely to run macOS Sierra. -
John Pale
May 27, 2016 at 1:20 am in reply to: Poor playback with mix of rendered and unrendered clipsWhat are your renders set to? Is it the default iframe MPEG or something else?
Maybe try Pro Res for your render codec/ -
John Pale
May 25, 2016 at 3:52 am in reply to: Avid Media not relinking despite MXF media being in the folder“Then I shouldn’t be able to place the individual mxf files in the folder in the first place correct?”
Not talking about Read Only in Finder. Read Only by Avid.
The folders that live inside the MXF folder have to be named in a very specific way. In a standalone system, the only folder Avid will write to is simply named “1”. When the maximum number of files are reached folder “1” is automatically renamed “2” and a new “1” is created. In a networked system (Unity/Isis), there are folders for each computer name on the network with a “.1” appended (then computername.2, etc.)
If the folders are named any other way, they become Read Only to Avid. You can use this rigidity to your advantage for media management purposes, if you know what’s going on.
-
John Pale
May 24, 2016 at 10:30 pm in reply to: Avid Media not relinking despite MXF media being in the folderWere the folders enclosed within the MXF folder named by Avid or manually named?
If they were manually named, they would probably be read only, so that would explain why no new media database was written when you deleted them.
(Do not worry about the media databases you deleted. They are easily rebuilt once you get to the bottom of what’s going on here.)
-
I don’t know if its still true in CC 2015, but it has been that Premiere Pro only made use of two GPUs during rendering and output to file.
-
Make sure nothing is slightly overlapping your source and/or record monitors before doing anything drastic,. Also make sure your composer window is not positioned slightly off screen
-
It’s in Media Composer Help.
T stands for Temporal. It means a motion adapter has been applied because the clip does not match the project frame rate or field order.
-
You can set all your renders to your anticipated export codec in your Media Creation settings, if it’s supported, but honestly I have not tested to see if it makes any appreciable difference in export time.
You can do a same as source export if you transcode your finished sequence to Pro Res or Avid DNX HD/HR. Or you can do a Video Mixdown, as suggested.
Probably not the answer you wanted to hear.