[Ryan Holmes]

What format are you trying to import? What does RAW mean? CR2 files? DNG files? Canon XF? H.264? I’m assuming you don’t mean Canon RAW from a C500 because you wouldn’t be using CS 5 to edit.

If you shot CR2 still files you’ll need to bring them into Photoshop or Lightroom and convert them to a format PPro can read – PSD, JPEG, tif, png, etc. PPro CS5 can’t take CR2 files.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

What Marc said.

You may try downloading Adobe Creative Cloud and try out Adobe Media Encoder. That’s what I transcode footage through and it’s the fastest encoder/transcoder I’ve seen (though Telestream Episode gives it a good run for it’s money).

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

It depends on what you’re shooting – stills vs. video, RAW vs JPEG, Magic Lantern vs. Stock Firmware, etc.

I use Sandisk Extreme and Extreme Pro CF cards for all my shooting. They are pricey compared to the generic brands, but they’ve never once failed in a shooting environment. And when I’m on set, that’s most important to me! We also run Magic Lantern firmware on our 5D3 which requires the SD card slot to be used to circumvent the standard Canon boot process.

Others can correct me, but I believe the CF slot allows for faster data transfer than the SD slot. So if you plan on shooting high frame rate RAW stills (like for sports) the CF card slot is the way to go. If you’re just shooting head shoots then the SD slot is plenty sufficient. If you plan on running ML firmware than you’ll be using both slots (CF card does the video recording though). If you’re shooting video using the standard Canon firmware, then I think either the SD or CF card slot will serve your purpose provided you buy a fast enough card (CF minimum UDMA 6 with write speed of at least 50MB/s, SD minimum Class 10 with a write speed of at least 50MB/s).

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Preferred: Same frame rate, different resolutions.

NLE solution: setup your timeline as either 1080 or 720 and conform the footage to it. So you’ll either be scaling up the 720 footage to 1080 or downsampling the 1080 footage to 720. Either way is fine. It just depends on your footage, how you plan on delivering, etc.

Keeping the fps the same though will save you headaches in the end of having to transcode footage to match frame rates.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

You’ll want to convert that footage to an edit friendly format, especially if using CS5. An edit friendly codec is something like DNxHD, MXF, etc. Since you’re using CS5 it probably can’t play some file types natively (like MOV’s from a 5D). That was the first year Adobe introduced the Mercury Playback Engine, which is now the backbone of everything they build.

So you’re 2 options are:
(1) Convert Canon 5D footage to a more edit friendly codec (creating larger file sizes and possibly needing faster hard drives for smooth playback)
(2) Upgrade your software to Adobe CC for the latest benefits. From CS6 forward editing h.264 MOV’s from a Canon 5D wasn’t as big a problem (CS5.5 could kinda sorta do it, but not smooth). Just keep in mind that MPEG formats are intended as delivery codecs. So that’s DVD spec, Blu-Ray spec, h.264 spec, etc. Manufactures have adapted the codec to be a shooting format (see any DSLR or GoPro), and NLE’s have tried to allow editors to use the format, but it’s a very complex codec to decode on the fly smoothly.

Additionally, CS5 worked better with Nvidia graphics cards. AMD wasn’t supported well back then. Adobe has made great stride with AMD support in the last 2 years, but it still isn’t as robust as a Nvidia GPU.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

You can read the rumor sites, but that’s about it. Canon is fairly tight lipped when it comes to release timelines.

https://www.canonrumors.com

Given the history of the TXi line, I would assume you’ll see a T6i announcement this year. Product availability later this year or early next year. I would also expect it to have very modest spec increases over the T5i.

https://en.wikipedia.org/wiki/Template:Canon_EOS_digital_cameras

However, I expect a 7D replacement as the primary announcement for Canon this year. Since the TXi line doesn’t get as much fanfare, I could imagine them announcing the 7D Mark II and a T6i at the same event.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Yes. You “can” shoot slow-mo at 1/2000 but it may not be the desired look you want (see above links for more info). As you change your shutter speed you’re going to have more or less motion blur. Too little blur looks very strange to us and can negate your story by taking the viewer out of the experience.

I would run some test to see if it accomplishes what you want. If you’re trying to control light then I’d recommend picking up some ND filters or a variable ND filter so that you’re not dependent on the shutter speed to control exposure levels.

P.S. – Twixtor is a way of generating slow-motion footage from source material that was shot normal speed (i.e. 29.97 or 59.94). It will create in-between frames to “slow down” the footage. Depending on what you shoot it can do an amazing job, but processing times can be quite long.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

PNG image sequences aren’t a multi-threaded format. So it’ll only use 1 core of 1 processor. When you jump into other formats like ProRes, DNxHD, h.264 you’ll see multiple cores being utilized.

So you’re also running the same hard drive for both source media and final output? Not usually recommended, but since you’re doing an image sequence your slow point will be the individual processing of each frame.

Keep in mind your also doing a 4K frame. And your image sequence is spitting out frame-by-frame results (so 30 stills a second). That’s a lot of processing for a single core process.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

In AME what’s your renderer? The drop down menu should say Mercury Playback Engine GPU Acceleration (CUDA) since you’re running an Nvidia GPU.

Other things that contribute to render times:
(1) Format/codec of source media
(2) Format/codec of output
(3) Disk speed and connection type of where you source media is located
(4) Disk speed and connection type of where your output media is going

AME CC moved further into utilizing more cores and more of the CUDA technology. CS6 made good strides over CS5.5, but CC did turn up the juice a bit. Something else to consider….

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Have you tried exporting out of Premiere directly? So don’t Queue the timeline, just export straight from Premiere. See if that works.

What computer are you running? OS version? Plugins? What FX do you have on your timeline clips? Any filters applied? Any 3rd party filters applied (Boris, Red Giant, etc.)?

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost