Forum Replies Created
-
You can see the codecs by trying to export a file in Media Encoder and checking what options are listed under QuickTime.
This update might help: Adobe Media Encoder CS6.0.1 for Mac
Also compare the QuickTime version numbers between your two installations. CS6 officially supports QuickTime 7.6.6 (link). If you are using a later version try installing 7.6.6 instead.
You could also check what applications are different between the two hard drives. Did you load any non-standard codec packs (x264, other)? Try uninstalling any video players other than QuickTime (e.g. VLC, etc).
How was the 40GB MOV file created? Try to make a MOV/H.264 copy rather than MOV/MP4. Also, if the file will be edited it is better to use I-frame only (key frames every 1 frame). Alternatively, try a different codec.
-
Ivan Myles
January 26, 2013 at 8:15 am in reply to: RED 4k to 1080 proxy CPU fan running while editingIt will be a challenge to edit 4k footage on a laptop. Proxy files are a good place to start. You could also add an external video card or RAID array via Thunderbolt.
https://www.youtube.com/watch?feature=player_embedded&v=jKx-cr4bi74
-
– What is the codec?
– Did the files previously work in Premiere, and on the same computer?
– Are the errors occurring only in Premiere, or in QuickTime, also?
– Did you try uninstalling and re-installing QT? -
Ivan Myles
January 26, 2013 at 7:24 am in reply to: RED 4k to 1080 proxy CPU fan running while editingIf I understand your post correctly, the processing load is high because Premiere is still using the same 4k source files. Proxy files are lower quality copies that are used instead of the source footage during the editing process.
From a file management perspective the idea is to substitute small copies for the larger source files. In general, the steps are as follows:
– create the proxy files by transcoding your 4k source footage into lower resolution, lower bitrate files
– import the proxy files into Premiere
– create a sequence as required for your desired final output
– drag the proxy files onto the timeline and edit/add effects
– before exporting the final output, replace the proxy files with the original source footageThere are some great web videos that can walk you through the process in more detail.
-
Ivan Myles
January 24, 2013 at 4:51 am in reply to: I want to do my encode using Handbrake. what is a good mezzanine export from Premiere?As per thread [1], Premiere Pro will export ProRes422 on a Mac with FCP installed. On a PC, try “DnXHD, Blackmagic, Uncompressed, DVCProHD, etc.” [2]
I use Blackmagic 10-bit 4:4:4 (AVI) as an intermediate format. You could also try the H.264 codec in Premiere Pro for direct export without transcoding.
[1] https://forums.creativecow.net/thread/3/907697
[2] https://forums.creativecow.net/thread/3/922859 -
Have you tried exporting directly from Premiere Pro instead of sending the job to the queue?
-
Ivan Myles
January 22, 2013 at 4:43 am in reply to: Film transfer shake/ jitter removal in PPro (or AE)I am getting good results removing handheld jitter using the Stabilize Motion function in AE, and then importing the AE composition to Premiere Pro.
Ways to reduce softening and artifacts are to i) minimize scaling (and avoid double-scaling), ii) increase composition bit depth, iii) import the AE composition to Premiere Pro instead of creating an intermediate file, and iv) if using intermediate files, select a codec with low/no compression.
If your workflow allows, another option is to edit the unaltered footage in Premiere and then stabilize in AE prior to exporting the final output file.
-
It will look choppy if the source file is being captured at 4.92 frames per second. Exporting at 25 fps just repeats each frame five times. Try to recapture at a higher frame rate.
-
That worked. Thanks!
-
The gamma issue seems to be significantly worse on PCs with both QuickTime and Adobe Creative Suite. The same videos that look pretty bad on one computer look great on another machine that doesn’t have the Adobe apps loaded. YMMV