RED IPP2 In Premier 12.1

[Anthony Berenato Jr]

Looks like Adobe finally pushed IPP2 in Premiere, and I'm surprised at how well the settings copy over from color work I've done in REDCINE-X. Even the LUT managed to make it into the panel as well!

I'm not sure what sort of magic Phil pulled leading the Adobe team in the right direction, but I'm super happy that this seems to be an extremely easy transition between an IPP2 first-pass color in RCX and import into Premiere. I was expecting to have to have to at least pull over my LUTs by hand. Excited to finally be fully moving to the new pipeline for all of my projects in the future.

Link to update additions:
https://helpx.adobe.com/premiere-pro/using/whats-new.html

Link to IPP2 Panel in Premiere:
https://imgur.com/a/VNteO

Looking forward to more things popping up for NAB.

 

[Phil Holland]

Just behind the scenes testing things out and poking where I can.

Here are examples of the two ways you can edit your RED IPP2 settings when working natively in REDCODE RAW with your .R3Ds:

Also, depending on your hardware setup, you might notice some decent speed improvements when working natively.

It works great and you still have Lumetri to utilize when you need to go further.

Those last two bits on the file browsers for Creative Cube and CDL will be coming very, very soon.

 

[Anthony Berenato Jr]

I have to say that that so far the release has been a tad bittersweet. On one hand, new projects that I've created with IPP2 footage have performed pretty well on my system and have me rather excited for a full IPP2 workflow. However, I'm seeing about half the performance I did previously with old Legacy projects that I'm bringing back into Premiere. A lot of stuttering footage at debayer ratios that I haven't had issues with even yesterday.

Unsure if this is just Mac related, I'm running on the 18-core iMac Pro. Switching the decoding modes didn't help. Downgrading back fixed the issues with projects that had Legacy footage. (One old project kept giving me an "Adobe Player" low-level error and wouldn't even load my footage.)

Wondering if it has something to do with either the OpenCL / OpenGL errors that RED corrected for Macs recently - not sure if this fix needed to be included in the new SDK. Also wondering if this might have something to do with Premiere's SDK implementation needing more time to decide how to display R3D files (if it realizes the look requires Legacy mode) as they're played. Or - it could just be general corruption of an old Premiere file. I haven't tried Legacy files in a brand new project just yet.

Seems like I might be waiting around until the next bug fix, sadly.

 

[Thai Christen]

I have to say that that so far the release has been a tad bittersweet. On one hand, new projects that I've created with IPP2 footage have preformed pretty well on my system and have me rather excited for a full IPP2 workflow. However, I'm seeing about half the performance I did previously with old Legacy projects that I'm bringing back into Premiere. A lot of stuttering footage at debayer ratios that I haven't had issues with even yesterday.

Unsure if this is just Mac related, I'm running on the 18-core iMac Pro. Switching the decoding modes didn't help. Downgrading back fixed the issues with projects that had Legacy footage. (One old project kept giving me an "Adobe Player" low-level error and wouldn't even load my footage.)

Wondering if it has something to do with either the OpenCL / OpenGL errors that RED corrected for Macs recently - not sure if this fix needed to be included in the new SDK. Also wondering if this might have something to do with Premiere's SDK implementation needing more time to decide how to display R3D files (if it realizes the look requires Legacy mode) as they're played. Or - it could just be general corruption of an old Premiere file. I haven't tried Legacy files in a brand new project just yet.

Seems like I might be waiting around until the next bug fix, sadly.

So it looks like they haven't fixed this problem.
That was the reason why I downgraded back to Premiere 2017 from 2018. I am on a fast PC Workstation.
I think I will wait too :-(

 

[Kenneth C Merrill]

Just behind the scenes testing things out and poking where I can.

Here are examples of the two ways you can edit your RED IPP2 settings when working natively in REDCODE RAW with your .R3Ds:

Also, depending on your hardware setup, you might notice some decent speed improvements when working natively.

It works great and you still have Lumetri to utilize when you need to go further.

Those last two bits on the file browsers for Creative Cube and CDL will be coming very, very soon.

If you utilize Lumetri, do those Lumetri adjustments apply "after" the IPP2 output mapping?

 

[Anthony Berenato Jr]

So it looks like they haven't fixed this problem.
That was the reason why I downgraded back to Premiere 2017 from 2018. I am on a fast PC Workstation.
I think I will wait too :-(

Should have saw my excitement drop when I loaded up a current project to see if it performed better. (Still waiting for full CPU usage at different debayer ratios. Surprised 1/8 uses 9% of my CPU, 1/4 uses 50% and still manages to stutter, 1/2 uses 80% and isn't very stable. Not sure why 1/4 can't use my full CPU and be smooth as butter.) Smile tanked when I was viewing in both 1/4 and 1/8 with what felt like a playback of 8 FPS.

I'm going to try a clean install later tonight and see if it all works a little better. For now, finishing up these last few projects on 12.0.1. One of these days !

 

[Evan Falbaum]

Anybody experiencing super slow h.264 export times when using IPP2 color in premiere versus legacy? I have a 4 mintue video taking 5 hours to export with just manual IPP2 color applied in Red source settings (no LUTS, no Lumetri) and no other effects. New projected created since the update. Generally, I would expect this export to be under 30 minutes on my system.

EDIT: Nevermind. Seems like it was a fluke. Tried it again and it's exporting at an hour with maximum bit depth and render quality checked. Did it in 7 minutes with those unchecked. Don't know why the 5 hour one happened. Seems to be a premiere issue and not IPP2 related - just happened to be my first IPP2 export.

 

[Anthony Berenato Jr]

Seems like I'm getting some really nasty performance out of the new v12.1 update for Premiere. So many dropped frames that I can't keep up, despite the resolution setting. Anyone else with this issue?

I've added my bug report to the User Voice forum, and I'd like to encourage any Premiere users also running into IPP2 trouble to vote for it / also comment with their own issues:

https://adobe-video.uservoice.com/f...d-ipp2-implementation-april-2018-major-droppe

Tried my hand at v12.1 again yesterday and still couldn't manage to get the same R3D performance out of Premiere as I could previously. Any other users having any problems? Is there something I can do to really wipe / clean any preferences that might be causing issue? It seems like Premiere magically installs all my presets again when I reinstall every time.

 

[Carlo De Agostini]

Is it possible to set the IPP2 image pipeline by default when importing an R3D in Premiere? I hate that I have to change the pipeline in the Master evey file I import in my project.