Premiere Pro sequence 3840x2160

[David Kudell]

Trying to prepare some footage for RedRay and my Premiere sequence won't play when set to 3840 x 2160 (16:9 UHD). But it does play when set to 4096x2304 - this is also 16:9 and is one of the preset options when you create a sequence in Premiere. Does Premiere not support 3840x2160 playback? I'd prefer to cut at the resolution I'm exporting. Sure I can cut at 4096x2304 and then export at 3840x2160, but that will introduce an extra scaling process that could reduce image quality. I already have to scale the clip once when I import the 5K R3D into Premiere.

 

[Burke Doeren]

Which version of Premiere Pro are you using? CS6 or CC?

Also, have you considered cutting on a 5K timeline then exporting to 3840 x 2160 UHD? That would result in one scaling operation on export, and may be faster for you anyway. Plus you can always reduce playback / paused resolution to 1/8th and you should be able to cut away on most systems.

 

[CK Olsen]

have you tried "Scale to frame size" on your 3840 timeline clips? its clean as a whistle on export, and often gives you better playback while editing. 'Course this defeats any scaling/cropping YOU might have done purposely, so tread carefully...
-CK

 

[Wes Howell]

Trying to prepare some footage for RedRay and my Premiere sequence won't play when set to 3840 x 2160 (16:9 UHD). But it does play when set to 4096x2304 - this is also 16:9 and is one of the preset options when you create a sequence in Premiere. Does Premiere not support 3840x2160 playback? I'd prefer to cut at the resolution I'm exporting. Sure I can cut at 4096x2304 and then export at 3840x2160, but that will introduce an extra scaling process that could reduce image quality. I already have to scale the clip once when I import the 5K R3D into Premiere.

David, There is a known issue with 16:9 playback when using a REDRocket in Pr. Are you using a rocket? If so, you may be able to cut in a non-16:9 sequence and just copy and paste the project into the 3840 timeline for final export. (this could be a temp workaround til the bug is fixed) I do this a lot anyway in my own workflow (say 1080p deliverable) as I like to cut native 5k then paste into a "delivery" sequence so I can specify my own scale settings. This gives me good pan and scan options and direct control over crop. Make sense? -Wes

 

[Kennan Ward]

Thank you I was just having the same problem and decided to export from PR CS6 to FCProX, instead!

Maybe I could try your suggestions!

Thank you,

Kennan & Karen Ward

David, There is a known issue with 16:9 playback when using a REDRocket in Pr. Are you using a rocket? If so, you may be able to cut in a non-16:9 sequence and just copy and paste the project into the 3840 timeline for final export. (this could be a temp workaround til the bug is fixed) I do this a lot anyway in my own workflow (say 1080p deliverable) as I like to cut native 5k then paste into a "delivery" sequence so I can specify my own scale settings. This gives me good pan and scan options and direct control over crop. Make sense? -Wes

 

[David Kudell]

David, There is a known issue with 16:9 playback when using a REDRocket in Pr. Are you using a rocket? If so, you may be able to cut in a non-16:9 sequence and just copy and paste the project into the 3840 timeline for final export. (this could be a temp workaround til the bug is fixed) I do this a lot anyway in my own workflow (say 1080p deliverable) as I like to cut native 5k then paste into a "delivery" sequence so I can specify my own scale settings. This gives me good pan and scan options and direct control over crop. Make sense? -Wes

Yes, I do have a Rocket, but I was able to get it working by changing my audio hardware settings in Premiere from Blackmagic to internal Line Out. Something about audio hardware in Premiere Pro causes a lot of glitches. I have no problems playing back once I switch to internal line out.

The only downside to cutting in a non-16:9 sequence is we shoot 5K full frame, and I like the ability to pan & scan and move the frame around to reframe if needed in the 3840x2160 sequence, and I would lose that control over individual clips if I nested an entire sequence (unless I were to cut that sequence up).

 

[Wes Howell]

Yes, I do have a Rocket, but I was able to get it working by changing my audio hardware settings in Premiere from Blackmagic to internal Line Out. Something about audio hardware in Premiere Pro causes a lot of glitches. I have no problems playing back once I switch to internal line out.

The only downside to cutting in a non-16:9 sequence is we shoot 5K full frame, and I like the ability to pan & scan and move the frame around to reframe if needed in the 3840x2160 sequence, and I would lose that control over individual clips if I nested an entire sequence (unless I were to cut that sequence up).

Hi David,

Thanks for the update. I will continue to verfiy that we are working solid in Premiere.

Re: Nesting. In my workflow, I don't nest. I just copy and paste to a 1080p sequence when I'm nearing finishing stages. Next you can scale to frame, or specify motion settings (size) for your clips. Sometimes, I do a quick scale to frame on 4k/5k clips right before editing (it's a little faster when using scale to frame on 5k clips in a 1080p timeline) then I go back and either pan and scan or set manual size (so I can crop exactly where I want it to to the new 16:9 Aspect Ration) If you have, for example, lots of 5k you can position where you want and copy and paste your scale settings (or even pan and scan) to other clips. This is VERY useful for those workflows when you are mixing with 1080 content. If you don't have any 1080p content - then staying 4k might be the best thing for your workflow / content.


With the workflow i described above you can keep your old 5k sequence for future use and have a 1080p for final deliverables.... (and of course you could take the finished 1080p and copy paste back to a 4k/5k down the road as well) Hope that makes sense.


Works well for me.

Best,
Wes