ProresRAW dead in Premiere Pro

[stiipe]

Hi Guys,

i had to shoot a imagefilm. I did it with my NINJA V - SONY FX3 - PRORES RAW.

Cutting was easy, but thats it. 

My Playback and Render is crap. 

my timline looks like this:

 the nested clips are all with effects and needed. (speed ramp and warp)
underneath the nested clips are statments of the interviewer and while playback - there are always glitching frames/overlay issues, don't know how to describe. While scrolling, suddenly the clip underneath appears or blinks strangly. That is while playback and Render as well. 

I've already tried all render settings, preview settings, resetting all premiere, delete cache. 

did anyone else experience such things?

My PC:
Windows 10

i9 12900K

64GB RAM

RTX3080

BR Stipe

[stiipe]

Hello Guys,

still issues there. so my proresRAW files in premiere PRO WINDOWS don't work. after rendering they are choppy and full of glitches. i don't know what do to. 

[Richard M Knight]

When you say render do you mean export? they are different things. You could try rendering the whole timeline to see if that helps.

[stiipe]

yeah i mean export. i tried already, prerender, everything nothing helped. the only way to render it - if i put the project on a mac, but i have just a slow macbook pro - so my sony files are to heavy for the mac but prores RAW, the mac exports without any problems.

[R Neil Haugen]

Understand ... I'm a practical guy. I don't really at all care about anyone's feelings, my own or others,  nor any " But I wanna ..." ... I just care about what works, now.

You've got Warp and speed ramps on clips ... well, that's a problem just waiting to happen. Why?

Warp is the freaking HEAVIEST effect possible ... period. Even more so than Neat video noise remover. Then you throw speed ramps in, which also  requires a ton of computational work on the fly. Oh ... my. 

Warp works by analyzing every frame ... and for every frame!!!!!! ... storing the entire pixel by pixel data to the sequence file (and therefore the Project file) for all factors, including all image re-creation stuff. Note that after you apply Warp to several effects, your project file on disc expands ... massively?

Ok, now think this through. To get playback with Warp clips, your computer is not playing back video frames. It is computing video frames pixels from a combination of original pixel data and the analyzed data.

I do hope you can see, you're putting one Hades of a load on the machine with Warp applied to a clip. Applying any other effect simply exacerbates the problem. Especially time changes and other heavy things like Lumetri.

So my practical advice, is simply apply Warp until you get a good result. Then ... immediately ... do a full render & replace to a new file, maybe ProRes 422 for most things, a higher one if you really need high Q final export.

You can always "restore unrendered" if you need to modify that clip section.

The above practice keeps 1) your project size manageable 2) the timeline playing back nicely and 3) exports within reasonable time periods.

NOW ... apply any other effects, you have normal timeline operation. 

[stiipe]

i will try this with full render and replace.
i made a workaround for that: i exported it on a very slow macbook pro. i7 - 16GB RAM - result - FINE. a slow macbook pro handles the proresraw easy. my WINDOWS machine (much more better specs) cannot handle it. Therefore my macbook pro cannot handle my sony clips.
So i've got a macbook pro which can handle my proresraw files with ease, but not my Sony files.

and a WIN machine with the specs above, which can handle my sony files with ease, but not my proresraw files.

In my NEW Project, i do have clips without any warp or speedramps. and same issue frames are skipping or choppy, just like in the previous Project.

With my Sony clips only there are no issues at all. Only if i put proresraw files from my ninja v.

[R Neil Haugen]

This kind of thing drives ya nuts ... how differently different rigs and at times OSs do with different formats. Very annoying.