PremierePro CS6 does not interpret .R3D files properly

hi,

 

i have problem using neatvideo plugin premierepro cs6. plug-in produces unacceptable results when processing "temporal filter radius" other 0 - means nv plug-in compares adjacent frames. phenomenon happens if clip on ppro timeline has been edited shorter beginning. if clip unedited on timeline, plug-in produces results.

 

i have same plug-in in aftereffects cs6, , works perfectly. (i work macpro osx 10.7.5)

 

so, spoke neatvideo technician, , said happens because ppro interprets .r3d wrong way. said instance following: "ae , pr read original file (.r3d) using different codecs , in cases produce different results (meaning provide different versions of same original frame input file host application/plug-in) or produce no results @ all. example, if plug-in asks host application provide adjacent frame (not current 1 see in preview, preceding or next frame) conduct temporal processing , host application not return proper frame because of buggy codec (some codecs buggy, saw before) nv bad adjacent frame or not @ and

so not able correctly process current frame, result in lower quality output."

 

so, made experiments, , attached 2 examples (small details of neatvideo processed frame). first (better one) processed frame (the clip not cut or shortened on timeline), , same quality in aftereffects.

 

 

and next 1 shows bad quality result of same frame (when clip has been edited shorter on timeline).

 

 

so, conclusion premierepro misinterprets clip, looses time reference when edited shorter beginning of clip, , not able point right adjacent frame(s) neatvideo plug-in, , therefore plug-in produces bad results.

 

so, adobe, please make proper codec interpret red files (.r3d) in premierepro.

 

thanks!

thanks posting. ask please file bug report on one? way our engineering team report , able act on it. go here: http://www.adobe.com/go/wish

 

thanks again!

More discussions in Premiere Pro CC

adobe