again on Vegas Pro lag...
again on Vegas Pro lag...
Sorry if this is beating a dead horse, but I'm under a tremendous time pression (please see http://www.sonycreativesoftware.com/for ... &Replies=3), and I need a definitive answer to the following questions (my goal being absolutely no lag in my already synchronized music project):
1. With the previous version of NV (2.0), which will give better results:
- setting radius to a non -zero value, and checking the no-lag mode
- setting radius to zero
2. Does the newest NV version deal better with this lag problem in Vegas Pro?
Thanks Vlad,
Piotr
1. With the previous version of NV (2.0), which will give better results:
- setting radius to a non -zero value, and checking the no-lag mode
- setting radius to zero
2. Does the newest NV version deal better with this lag problem in Vegas Pro?
Thanks Vlad,
Piotr
Vlad,
I have rendered the very same clip using the very same codec and settings, in 2 versions - one with, the other without the NV plugin. Unfortunately, while the non-NV version is exactly the same length as the original, and aligns with it perfectly on Vegas T/L one under another - the same cannot be said about the clip, rendered with the NV filter... Even though I even went as far as turn the temporal filtration off completely.
Piotr
I have rendered the very same clip using the very same codec and settings, in 2 versions - one with, the other without the NV plugin. Unfortunately, while the non-NV version is exactly the same length as the original, and aligns with it perfectly on Vegas T/L one under another - the same cannot be said about the clip, rendered with the NV filter... Even though I even went as far as turn the temporal filtration off completely.
Piotr
Sorry Vlad - I did try the same clip with a couple of other FXes (Sony's own Curves, or the AAV Colorlab's White Balance) - and when I render the same clip to another track, the original and the output align perfectly...
Add NV 2.6 - and even with temporal filtration off, the rendered clip is slightly "longer" on the T/L, and I can't find even a single moment in time when it's in perfect sync with the original!
Piotr
PS: One last question: I notice that with temporal filtering radius set to 0, the "No lag" option is still "alive" (i.e. not greyed out like the rest of them) - should it make a difference whether it's checked or not?
Add NV 2.6 - and even with temporal filtration off, the rendered clip is slightly "longer" on the T/L, and I can't find even a single moment in time when it's in perfect sync with the original!
Piotr
PS: One last question: I notice that with temporal filtering radius set to 0, the "No lag" option is still "alive" (i.e. not greyed out like the rest of them) - should it make a difference whether it's checked or not?
Sorry Piotr, cannot reproduce the problem on our side so far. Something must be different in your project/video clips.
The radius=0 disables the temporal filter in NV, so the N-frame lag (N = radius) normally introduced by the temporal filter (when no-lag option is not used) is not introduced (0-frame lag is the absence of lag). In other words: with radius=0, NV itself does not introduce any lags, irrespective of other settings.
The no-lag option allows to avoid that N-frame lag even when radius>0.
So, if you enable the no-lag option, then NV itself will not introduce any lag in the video stream it processes (with any radius). It will receive each input frame, process it and output it without a delay of N or any other number of frames, that is without lags.
Please try to enable/disable that option and see how the lag changes. It should change by N frames (N = temporal filter radius you use).
There are no other sources of lag in NV in Vegas. If you see any other lag or myssync then it must be Vegas (or some of its components, like codecs) itself. Perhaps something related to that 29.97 vs 30.00 fps issue.
Vlad
The radius=0 disables the temporal filter in NV, so the N-frame lag (N = radius) normally introduced by the temporal filter (when no-lag option is not used) is not introduced (0-frame lag is the absence of lag). In other words: with radius=0, NV itself does not introduce any lags, irrespective of other settings.
The no-lag option allows to avoid that N-frame lag even when radius>0.
So, if you enable the no-lag option, then NV itself will not introduce any lag in the video stream it processes (with any radius). It will receive each input frame, process it and output it without a delay of N or any other number of frames, that is without lags.
Please try to enable/disable that option and see how the lag changes. It should change by N frames (N = temporal filter radius you use).
There are no other sources of lag in NV in Vegas. If you see any other lag or myssync then it must be Vegas (or some of its components, like codecs) itself. Perhaps something related to that 29.97 vs 30.00 fps issue.
Vlad
Piotr,
Could you try to reproduce the problem in a small fresh new test project with a small clip instead? It would be easier to send (to support [at] neatvideo.com) and it would be the whole project, ready to render and reproduce the problem.
Regarding CUDA and Vegas 11, v3 itself will most likely work the same fast as in any other version of Vegas, unless Vegas uses a lot of CUDA resources, which may slow down the other CUDA user - NV. Generally, the fact Vegas uses CUDA does not in itself help NV itself in any way, but of course may help to speed up the overall rendering in Vegas.
Vlad
Could you try to reproduce the problem in a small fresh new test project with a small clip instead? It would be easier to send (to support [at] neatvideo.com) and it would be the whole project, ready to render and reproduce the problem.
Regarding CUDA and Vegas 11, v3 itself will most likely work the same fast as in any other version of Vegas, unless Vegas uses a lot of CUDA resources, which may slow down the other CUDA user - NV. Generally, the fact Vegas uses CUDA does not in itself help NV itself in any way, but of course may help to speed up the overall rendering in Vegas.
Vlad
OK, here is the link to one of them:
http://www.4shared.com/file/n5pXVBdV/NV ... clips.html
Please inspect how the rendered clip gets longer than the original; also - even though the original 29,97 fps was rendered to 25 fps (in a 25 fps project), this doesn't make any difference as rendering to 29,97 in a 29,97 fps project produces an even longer file!
Please comment
Piotr
http://www.4shared.com/file/n5pXVBdV/NV ... clips.html
Please inspect how the rendered clip gets longer than the original; also - even though the original 29,97 fps was rendered to 25 fps (in a 25 fps project), this doesn't make any difference as rendering to 29,97 in a 29,97 fps project produces an even longer file!
Please comment
Piotr