Thanks for posting. Could I ask you to please file a bug report on this one? That way our engineering team will get the report and be able to act on it. Go here: http://www.adobe.com/go/wish
After Effects & Premiere Pro use the identical codec to import R3D files.
Hi Kevin, I will do the bug report.
Hi Steve, that probably is true. The NeatVideo plug-in in AE and PPro is also the same - at least the technician in NeatVideo claims that. So, then it must be PremierePro itself reading or interpreting the .R3D files incorrectly.
Remembering that NV plug-in asks the host application for adjacent frames, I made also an experiment (in PPro) with how much is cut from the beginning of the clip with the following results:
- as told before, if the clip is not shortened from the beginning, NV gives good results
- if I shorten the clip only one or two frames, the result is not much worse
- if I shorten the clip ten frames, the results are getting worse
- if I shorten the clip couple of seconds, the results are getting even worse
- the more I shorten the clip from the beginning, the worse results I get...
The clip I've tried has steady movement (the camera moves steadily in one direction). Therefore, I guess PPro gives different time references for the frame played and the adjacent frames NeatVideo plug-in is asking for. If the clip has been shortened on the timeline only a bit, then they still work quite well as references for NV to be used. And the more the clip has been shortened on the timeline, the less the "asked frames" work as a good comparison. It seems as if NV plug-in asks frames based on the length of the original clip, and PPro gives frames counted from the beginning of the edited clip on the timeline. Hence the bad quality.
I made the bug report. Let's hope there will be a solution soon.
I was told that the bug (PPro not able to read or interpret properly .R3D files) is not limited to only .R3D files. Also other codecs have similar problems, although I have not experimented that myself.
So, it would be nice to hear experiences form other NeatVideo users in PremierePro.
I was also told a "solution" to this problem:
"Since the cause of the problem is known, a possible solution for now is also clear: do not cut the clips that use Neat Video (or any other filter that uses temporal API of Premiere. It is okay to use the beginning section of the cut clip, but not the section after the cut."
Well, what's the point of using PremierePro (or any editing software) if you can't make edits on the timeline!!!!