Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

WHY WON'T CS5.5 w/ NeatVideo Shots RENDER ??

George D.

George D.

Well-known member
Joined
Oct 22, 2008
Messages
980
Reaction score
0
Points
0
Location
N. California, USA
As I continue to use Adobe Premiere Pro CS5.5 in our Windows7 PC to edit our Red-One footage, I still obviously have a lot to learn, and I hope someone can help me.

Since some of you on this forum have suggested getting the NeatVideo plug-in for CS5.5, I have done exactly that, and I'm glad I did so. It is a very nice feature, and has helped me clean up several takes already that have needed noise removal or sharpening.

The problem I'm having now, is on a sample sequence I have been putting together. Several of the shots within the timeline have been sharpened via NeatVideo, and they look great. I did this because the lens we used to shoot those scenes was not quite as sharp as I wanted it to be, so I made them better. Also, some titles have been added, along with some dissolves and music.

After finishing the sequence, I went to Render it, but even after repeated attempts, the rendering would not go past about 2/3rds of the way. Then it stalled, froze, and would NOT finish. The ONLY way I could salvage it was to shut down the entire program, which, of course, lost all the rendering that DID take place. Then I'd have to start all over again, just to have the same thing happen yet again. I have tried rendering the whole sequence, or just the effects, and nothing works. It will NOT finish.

I "must" be able to render it, because it will NOT play smoothly through without it.

BTW - It's 4K HD.

What am I doing wrong here? Am I missing a step? Should I have rendered each and every NeatVideo-adjusted shot separately at the time I added it into the timeline? Is my computer not powerful enough?

If I have to start all over again, it will be a LOT of work, but if that's what it takes, then so be it.

*NOTE: The very first time I rendered the sequence it rendered just fine throughout with no problems. All the trouble started when I went back into the program and did some more NeatVideo sharpening on shots I had already sharpened once before. I just wanted to see how a "double sharpening" would look. Did I break some sacred rule or something?

Any help or advise or instructions would be most appreciated.

Thanks for your time.

.
 
Try rendering as an image sequence. That way you will not lose your rendering progress. It also may be more forgiving memorywise for the renderer. Compile the sequence into a movie file with audio afterwards. While I don't know why the renderer is crashing, this will also help isolate if there is a problem frame as it will be obvious on which frame it crashes.

Good Luck
 
The problem is related to neat video . I have had some problems in premiere and AE when applying multiple neat video filters on top of each other, Try removing your second instance of neat video and see if it renders fine. Or like Adam said, render to an image sequence...this way you'll know exactly where it crashed and you can pick up the render from there.
 
Maz Mawlawi said:
The problem is related to neat video . I have had some problems in premiere and AE when applying multiple neat video filters on top of each other, Try removing your second instance of neat video and see if it renders fine. Or like Adam said, render to an image sequence...this way you'll know exactly where it crashed and you can pick up the render from there.
Click to expand...

When you guys say, "image sequence", are you saying to put one shot at a time in the timeline and render it, then go onto the next one? Man, if I have to do it that way it's going to take me forever, but I'll do it if that's what's required.

"Movie file"? What's the difference between that and just a completed program in the timeline?

Please clarify.

Thanks.

.
 
An image sequence is a series of image files, dpx, tif, etc that is rendered from your timeline. If you render an image sequence and your render freezes, you have all of the frames allready saved prior to it freezing, you can start from the last frame and continue forward. You then bring those image files in as an image sequence that is basically a single video clip.
 
Stefan Scherperel said:
An image sequence is a series of image files, dpx, tif, etc that is rendered from your timeline. If you render an image sequence and your render freezes, you have all of the frames allready saved prior to it freezing, you can start from the last frame and continue forward. You then bring those image files in as an image sequence that is basically a single video clip.
Click to expand...

Man, have YOU lost me!

The files are R3D files from our Red-One, not some kind of time-lapse sequence comprised of still images.

Or, are you saying to break the R3D files into individual frames? If so, you've got to be kidding? At 30fps, for a long shot, that could take forever. There HAS to be a better way.

I'm sure it's something I don't understand. Which, is nothing new.

.
 
All motion pictures are just a series of still images strung together on a strip of Kodak film or in a video file such as R3D or avi. The suggestion is to render your existing timeline to a series of still frames, such as dpx, tiff or even jpeg. If the render crashes, you have all of the frames rendered to disk up to the crash point. You can then start the render to still frames again from the crash point. When all has been rendered, you can then assemble the final video file from the stills. It is a process I have used many times over the years when PremPro or Nuke decide to get indigestion.
 
I just encountered the same problem. All my Scarlet 4K renders have been working flawlesslu in AE, until I drop on Neat video for noise reduction. I did a simple test to make sure it was indeed neat video that was causing it.
Load 4K clip in AE, don't apply anything to it just render out to ProRes 4444. No problems, uses all 8 cores, renders fine.
Go back to same clip, now drop in neat video, apply the default noise reduction settings, now render to ProRes 4444. At first all 8 cores are maxed out and it appears to be rendering. It'll to go about 60-80 frames, then it halts and CPU usage is only at 1 CPU at 10%. Now I have to force quite AE, and even that takes several minutes to do as the systemed is getting hogged by something.

George, what others are saying about DPX render... It's just another output format. So instead of rendering to ProRes or h.264, you choose DPX. This will save each frame as a separate file. So when the render crashes, you'll know which frame it crashed on.

For me, this won't really tell me anything other than which frame it crashed on, as there is no other effects applied to the clip except the default settings for neat video. I'll have to debug further, to see if it's the Scarlet 4K+Neat Video+ProRess it's not liking and contact Neat Video developers... Hoping someone else can shed light on this.
 
Georg, have you tried to import the PPro sequence dynamically to AE, apply Neat Video in AE, and export the whole thing from AE?

If you export from PPro, have you checked the "Render at Maximum Depth" in the export video settings?
 
Out of curiosity, how much RAM do you have - and do you have any other apps open?

I have NeatVideo licenses for Fusion (OFX) on Win7 and FCP7 (and haven't seen any problems), and am waiting until my Scarlet arrives before buying it on either AE or Premiere or both in case a new version comes out in the mean time.

Be sure to report your issues on the NeatVideo forum and in an email to the developer.
 
Thanks to everyone for your help. I guess I just don't know the program well enough yet to understand what you are all talking about.

Michael: Thanks, but I "do" realize all film and video is a series of still frames. What I don't understand, is how I can "break up" R3D files into those still frames.

Zhibo: I haven't had the money to purchase AE yet. Hopefully in the near future. Yes, I think the problem IS with NeatVideo. I must be able to use that plug-in though, so I have to solve this. And, I don't even know what ProRes 4444 is.

Lauri: I have 12.0GB of RAM, and no apps open. What NeatVideo forum?


Sorry everyone, since I am so ignorant about all this. Having been in film for over 38 years, does not help me understand all this digital technology any better. Please be patient with me.

Thanks.

.
 
George, just set up PremPro to render to DPX. It will then save frames as individual files. Very simple after you do it once.
 
What they are suggesting is that you render out to an image sequence first.

Then, you'd import the image sequence into Premiere, and then render that out to your final output format.

This is pretty normal, especially in 3D Graphics where the renders sometimes fail, but also when using DaVinci Resolve where you just want to use another program to render to the final format (generally AE).

If it fails during the render to image sequence, you'd start the render where it failed, and hopefully be able to get a complete render.

The NeatVideo forum is located here:

http://www.neatvideo.com/nvforum/index.php

One other thing. Make sure you're using the latest version of NeatVideo. He keeps improving it in new releases, and does issue bug fix releases also.
 
Hi George,

If you haven't already - I would highly recommend that you work through the first two tutorials I created in this thread: http://www.reduser.net/forum/showthread.php?66182-Tutorials-for-Newcomers-to-Premiere-Pro

Also, one thing you mentioned was that you were doing this in order to be able to play back the footage smoothly. Could you pre-render the footage if you are simply wanting to see what the footage looks like in motion? (The way we did in your 5D timelapse thread from a while back)

As others have mentioned, exporting out to an image sequence format would be a good way of ensuring your render times are not wasted and may help you isolate which part of the timeline is causing freezes. Looks like you have got a handle on that now though :)
 
Michael Mayda said:
George, just set up PremPro to render to DPX. It will then save frames as individual files. Very simple after you do it once.
Click to expand...

DPX ????????

In about 5 more minutes, I'm going to give up. I'm beginning to think editing this stuff should be turned over to an expert. I'm a DP and a shooter, not a friggin' editor. :(

Oh well, I tried.

Thanks anyway.

.
 
Brad Allen said:
Hi George,

If you haven't already - I would highly recommend that you work through the first two tutorials I created in this thread: http://www.reduser.net/forum/showthread.php?66182-Tutorials-for-Newcomers-to-Premiere-Pro

Also, one thing you mentioned was that you were doing this in order to be able to play back the footage smoothly. Could you pre-render the footage if you are simply wanting to see what the footage looks like in motion? (The way we did in your 5D timelapse thread from a while back)

As others have mentioned, exporting out to an image sequence format would be a good way of ensuring your render times are not wasted and may help you isolate which part of the timeline is causing freezes. Looks like you have got a handle on that now though :)
Click to expand...

I'll try Brad, I'll try.

But, I'm beginning to think this stuff is WAAAAAAAAAAAAAAAAY over my head. There is so, so much to learn in just operating and understanding the camera, let alone trying to learn editing software. If this keeps up, I won't have any time for shooting the wildlife, which is my greatest love.

.

.
 
George-
In AE, you can choose how you want to output your sequence, and one of your options can be to render out an image sequence instead of a quicktime. AE then renders out individual frames from your timeline, numbered in order from 00000 to whatever. it is an easy way to see where the failure is without losing your work, as both AE and Premire both are able to easily import those frames back as an image sequence, which it identifies as one unbroken clip.
DPX is simply a type of image file, but you can just as easily render out to jpegs, tiffs, psd files or whatever makes sense for your test. the nice thing is that if the render fails, you have all the frames that DID render, and you can pick up again at the next frame after the crash.
-CK
 
Yes - just think of it as a 'save as' option.

You can save out a movie file (avi or QT) - but, if that fails you probably won't be able to play it.

But, if you set your output 'save as' option to be a sequence, as everyone is saying, you'll get a folder full of 'frames' so 24 per second. Then, when/if it bombs out on you, you can see what frame it failed at (00012 or 00400 etc). The advantage is, you can then load these sequential images back to a new timeline and you can see your results in motion.
 
Brad,

I can't thank you enough for the tutorial. I've only had time to go through 15 minutes of it today, and I've learned a great deal already. Guys like you are worth their weight in gold.

Thanks, and bless the Aussies.
 
You must log in or register to reply here.
Back
Top