I can confirm that I don't see any NB VE 4 plugins, whereas I see all NB VE 6 plugins in the screenshot.
peterh337:
Now it is asking to restart Pro, but doing so doesn't do anything; it just brings up the same form as above...
Did you tried it after deinstalling MSPPS?
on your picture is the same as i get, and it works!
jetdv:
The VE6 Package bundled with Vegas Pro 13 is currently getting a watermark in Vegas Pro 14. This should be resolved in a future update.
No need, it works fine in VP14, without a watermark
As for the bundled NB VE 6, are these comments still valid?
https://www.vegascreativesoftware.info/us/forum/video-essential-vi-problem--98772/#ca603383
Yes, i have installed the NewBlueVideoEssentials6ForWindowsSetup30-140723 (it is the update from the bundle that you get when installing it)
OK... I downloaded that new file from NB and, with Vegas *not* started, the installer pops up this
http://peter-ftp.co.uk/screenshots/2016-10-24_081214.jpg
The "settings" icon has no useful options, as you can see.
So I closed that. Now, starting Pro 13, when I go to the Lens Correction plug-in and click on About, as before, I get this
http://peter-ftp.co.uk/screenshots/2016-10-24_081629.jpg
which is as before. Clicking on the options does the same thing as before. The no-GPU setting doesn't work.
Yes I uninstalled MSPPS some days ago.
"I can confirm that I don't see any NB VE 4 plugins, whereas I see all NB VE 6 plugins in the screenshot"
Please ignore my Sony URL pointing to VE 4. I thought "IV" was 4 :)
So it looks like I have the expected plug-ins, doesn't it?
Clicking on the options does the same thing as before. The no-GPU setting doesn't work.
You must select and restart, as it told you, otherwise nothing will happen!
If you restart and check it again the options should be still selected
Please ignore my Sony URL pointing to VE 4. I thought "IV" was 4 :)
IV is 4, VI is 6!?
Nothing is changed since you posted this: http://peter-ftp.co.uk/screenshots/2016-10-22_095551.jpg
I restarted Pro 13. Are you saying, Quitter, I need to reboot the PC also? (rendering a long video right now)
BTW I did reboot the PC before installing the NBFX .exe - due to the warning about locked files. NB also asked for the PC to be rebooted.
For change the NBFX GPU settings, you only need to restart Vegas
1. popup
2. select
After restart
is it possible that you have never restarted before?
Quitter - my checkboxes never acquire the check marks, as shown in your screenshot
http://peter-ftp.co.uk/screenshots/2016-10-24_110213.jpg
I click in them and I just get the warnings to restart Pro. But no checkmark appears.
Weird.
I have restarted the PC many times. After a long render it is advisable.
maybe you use a Color Scheme that you don't see it?
I never changed the colour scheme in the app, or in the OS.
I see absolutely nothing appearing in any of the 3 checkboxes.
Ok, so you have a problem 😉
You should tell this (checkmark-problem) to NewBlue, maybe they have a solution
Whether it is displayed or not, does it make a difference while rendering?
Good Q. I could never tell on short renders. The last render started to break up after about 3 days, on a PC which was not touched at all.
Also I don't know for sure at all whether NB is the cause of that render corruption problem. "We" think it might be responsible for it because Pro 13 crashes very fast if GPU is globally enabled (under Preferences), and this NBFX Lens Correction plug-in is the last place in which GPU has not been disabled.
Is there any way to tell in Vegas whether the GPU is being used, in any context? I think it always uses it for the preview window - well obviously because the video card is doing that!
Edit: just doing a render of a 7 min movie, same FX as usual (contrast, colour correction, lens correction), and it estimates 2hrs+ render time. That is about 1/20 of real time and about 1/2 the speed of previous, so it could well be that something has changed.
I have just rendered this quick and dirty video
and it took 2.5 hours which is 2x longer than normal. So maybe the GPU option in NBFX was being used and isn't anymore. But I cannot tell otherwise.
The other thing is that I repeatedly accessed the computer over remote desktop (RDP) and that didn't corrupt the render. It did however cause Pro 13 to crash at the end, leaving the finished .mp4.tmp file there, which I just renamed to .mp4 and uploaded to vimeo.
2,5 h for 7:33?
just for info: your PC configuration, your video source, your render setting?
i7-970, 3GHz, 24GB, 2TB 6mbit SATA, GTX750 Kalm 2GB.
Source is a Sony FDR-1000V 1080P 50fps 25mbits/sec, AVC.
Render to: http://peter-ftp.co.uk/screenshots/2016-10-24_171744.jpg
Program layout: http://peter-ftp.co.uk/screenshots/2016-10-24_171700.jpg
FX chain: http://peter-ftp.co.uk/screenshots/2016-10-24_171957.jpg
VLC media info: http://peter-ftp.co.uk/screenshots/2016-10-24_171850.jpg
http://peter-ftp.co.uk/screenshots/2016-10-24_171923.jpg
Rendering it again: 2hrs 20 mins.
Output file 677MB.
1080P 50fps 25 Mb/s MP4 AVC
Have you tried another template?
with lower constant Bitrate?
Your output is
Bit rate mode : variabel
Bit rate : 12,1 Mb/s
Maximum bit rate : 40,0 Mb/s
Sure; a lower bitrate speeds it up correspondingly.
However, the camera produces 25 mbits/sec (most likely fixed bitrate) and I don't want to lose too much of that. If I was doing stuff only for vimeo and then chucking it away, I would render at 5mbits/sec, or maybe 10 because Vimeo does its own downsampling regardless of what you upload, to about 5.
If those stoopid checkboxes could be checked or unchecked, I could test this with and without, but right know I cannot tell if the NBFX lens correction is using the GPU or not.
peter, can you go to your Lens Correction Video Event FX dialog/window and click "About"?
My lens correction is from the Starter Pack and gives this
peter, i am amazed at these colors...
Your OS is?