Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

4K (hard) workflow.

Sanjin Jukic

Well-known member
Joined
Dec 28, 2006
Messages
8,929
Reaction score
1
Points
36
Location
Vienna, Austria
Website
www.sanjinjukic.com
I shortly tested new Adobe Premier Pro 4.01 update with dropping QT (_F_) wrapped R3D files in timeline at 4096 x 2304 (16:9), did a small cut, then render all in Adobe Media Encoder at the full size 4096 x 2030 using AJA Kona 10 bit Log RGB Codec.

This file imported in AE at again full size 4096 x 2304, a bit color corrected, and again rendered in AJA Kona 10 bit Log RGB Codec.

Then again imported in Shake 4.1 and did additional CC and add a custom film stock grain look.

All in 4K, slow and heavy workflow but after that you can say that you have your movie ready to conform in 4K DPX and sent for print to film.

No any resizing and other compression or wavelet and workarounds involved.

All done in Mac Pro 8 core.
 
I shortly tested new Adobe Premier Pro 4.01 update with dropping QT (_F_) wrapped R3D files in timeline at 4096 x 2304 (16:9), did a small cut, then render all in Adobe Media Encoder at the full size 4096 x 2030 using AJA Kona 10 bit Log RGB Codec.

This file imported in AE at again full size 4096 x 2304, a bit color corrected, and again rendered in AJA Kona 10 bit Log RGB Codec.

Then again imported in Shake 4.1 and did additional CC and add a custom film stock grain look.

All in 4K, slow and heavy workflow but after that you can say that you have your movie ready to conform in 4K DPX and sent for print to film.

No any resizing and other compression or wavelet and workarounds involved.

All done in Mac Pro 8 core.

THIRD MAN -

I'm pretty confident your head is going to explode when you get the Adobe RED plug in ...:devil:

You won't have to roll that "heavy" ...
 
Mark,

hopefully.

After all that "make up" treatment in the software it really looks like a film.

Looking forward to work with that R3D Adobe plug in.

4K_crop_frame107.jpg

Mark, she is smiling at you from from one Vienna's party on this 4K "film look" documentary cropped example.
 
553_1227859793.jpg


Tell me again why I am so stupid skipping all of this hard, disk-chewing 4K stuff and just going to 1080p in Avid?

Although I agree, it'll be awesome to do effects and processing in Adobe. After my horrible experiences with REDCINE I will probably ditch REDCINE and use After Effects as a virtual telecine on my next project, unless RED wakes up and decides to un-cripple it...

Bruce Allen
www.boacinema.com
 
Bruce,

you are right and hopefully we'll get SOON "affordable" 4K solution from Adobe.
 
Bruce,

you are right and hopefully we'll get SOON "affordable" 4K solution from Adobe.

But you don't need 4K or lots of money! Get Avid for $2000 and a $500 PC and... and oh yeah, RedCine is crippled and sucks ass... RED / Assimilate are kinda letting down the side there.

So, maybe you're right ;)

Bruce Allen
www.boacinema.com
 
adobe workflow

adobe workflow

i definitely must try to cut in premiere qt wrappers.
but still, since cs4, i'm experiencing extra slow playpack in premiere and big memory issues in AE. with 16 gb of ram in my mac 8 core 3.2 ghz, i cannot ram preview more than 150 frames in 1080p.
in premiere, cutting with qt prores 1080p, which was an easy task with cs3, has become impossible.
am i missing something? i must go down with cs4 manuals and find out.
4.01 didn't improve much...
 
Me too!!!

Me too!!!

i definitely must try to cut in premiere qt wrappers.
but still, since cs4, i'm experiencing extra slow playpack in premiere and big memory issues in AE. with 16 gb of ram in my mac 8 core 3.2 ghz, i cannot ram preview more than 150 frames in 1080p.
in premiere, cutting with qt prores 1080p, which was an easy task with cs3, has become impossible.
am i missing something? i must go down with cs4 manuals and find out.
4.01 didn't improve much...


Man... I am having the same problems on my side... when I worked in CS3 it was good to go, but my playback in PrCS4 and ram preview in AECS4 is the same as yours... if you do figure this out, please post it.
 
quick question... after reading this ... I have to export about an hours worth of footage that is red 4k and export it on a dvd... what is the easiest way to do that??? i use final cut and have little knowledge of this red technology... It's already all on an external hd I just need to bring in all the files into final cut, but wondering what the best settings are and how to minimize the file size so that it could all fit in a dvd...
anyone have time to help a newbie out?!
 
the easiest way i think is cutting the _m proxies in fcp, the export the timeline as you would do for any other dvd by sending it to compressor with standard dvd settings.
 
i definitely must try to cut in premiere qt wrappers.
but still, since cs4, i'm experiencing extra slow playpack in premiere and big memory issues in AE. with 16 gb of ram in my mac 8 core 3.2 ghz, i cannot ram preview more than 150 frames in 1080p.
in premiere, cutting with qt prores 1080p, which was an easy task with cs3, has become impossible.
am i missing something? i must go down with cs4 manuals and find out.
4.01 didn't improve much...


You have to look on the fastest RAID to get things done and to look for any system with great performance staring from times of the first DV beginnings.

Adobe still didn't release an "official" R3D plug-in that we can improve or enjoy the best tings we could get with it.

Also be patient with it and it is coming approximately at the same as with FCP-Color 4K workflow before NAB 2009.

Hope this helps you and the developers too...
 
I'll do more tests between FCP, Color, Premiere Pro, AE and Shake... all QT based...
 
Back
Top