John Pale
Forum Replies Created
-
John Pale
January 9, 2018 at 3:39 am in reply to: Exporting in Premiere Pro Makes it Functionally UselessYou can export sequences to Media Encoder, which can run in the background. Depending on your system, it may result in sluggishness….however, if you select “Mercury Engine Software Only” that seems to help overtaxing the graphics card, allowing you to edit while it runs. Some operations will pause Media Encoder (FCPX does this when background rendering, similarly).
Rather than constantly rendering and rerendering AE comps, use Render and Replace. This function creates a single media file that replaces your AE comp in the timeline…similar to a video mix down, in Avid….except it remains linked to the AE comp, so you can revert back, if you need to make a change.
If you are more comfortable with FCPX, its a fine alternative.
-
I just tried some test files from ARRI cameras. The only ones that gave Premiere Pro trouble were MXF files from the ARRI Mini. I’m guessing they were from that camera.
I was able to convert them to ProRes (or pretty much any other format) using this.
https://www.arri.com/camera/alexa/tools/arriraw_converter/
-
John Pale
January 2, 2018 at 4:24 am in reply to: adding a new SMPTE timecode track to QT clips using Premier ProThank you. My apologies, I pasted the wrong link.
Same developer. I have both apps.J
-
John Pale
January 2, 2018 at 1:40 am in reply to: adding a new SMPTE timecode track to QT clips using Premier Pro -
I’ve had similar issues, but with using Project Manager to transcode/consolidate the sequence. The positioning gets all messed up on Essential Graphics.
Try exporting to an all iFrame codec like Apple Pro Res or GoPro Cineform.
If that works, take the resulting file and transcode that to MPEG2.
-
John Pale
December 18, 2017 at 5:17 pm in reply to: Timecode issue: Exported length not matching project length. Matches if I bring it back inIts the timecode thats messing you up.
The timecode is counting at 24 frames pers second. Your video is running slightly slower.
In NTSC, this discrepancy (timecode runs at 30 fps, but video is 29.97) is fixed by using drop frame timecode. Unfortunately, in the 23.976 realm, there is no drop frame timecode. So you have to live with the discrepancy between timecode and real time and plan accordingly.
-
John Pale
December 13, 2017 at 4:02 am in reply to: Possible project inherited was not properly ingested for onlineOften just AMA linking to the media into a new bin will allow you to relink your sequence to it (link to selected in open bins).
-
John Pale
December 2, 2017 at 11:01 pm in reply to: Essential Graphics not stretching to fill on outputThe text positioning gets all messed up if you use Project Manager to Consolidate the sequence, as well.
-
By default your Media Cache is stored on the internal hard drive. This is a different thing than your media files. Is the iMac building a new Media Cache? This might take awhile for over 20,000 files, but should only need to be done once.
-
John Pale
December 1, 2017 at 1:25 am in reply to: One system loading media in Premiere much slower than other systems.You might want to try emptying and rebuilding the Media Cache. This is stored on the local drive and not your shared storage. Each system has their own.