NeatVideo: Pro install over Demo?

Kimberly wrote on 10/1/2013, 12:20 PM

Does the Pro version install seamlessly over the demo version? I presume it does, but you know what they say about when you presume. (Or is that when you assume?)

Thanks to everyone who contributed on this thread:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=861903

I was searching for info on something else, which I never did find, and got onto NeatVideo instead.

Regards,

Kimberly

Comments

mudsmith wrote on 10/1/2013, 12:34 PM

As a recent purchaser of Neat Video (mostly to deal with noise in HDV clips shot in low light or extreme contrast), I can tell you: a)It sure does work well, and b)why not just de-install the demo?....hardly seems worth the worry once you have made the decision to purchase.

Another small, but important, detail I picked up in my initial use: Rendering times from my timeline were massively shorter when I chose the GPU option inside the Neat Video software menus. I would stress this is separate from the GPU acceleration menus inside Vegas......basically a one button click that will save you hours. In my case, I was rendering to Cineform and the Neat software was making this very, very slow....until I had Neat use GPU acceleration. (My listed system no. 2 with the GTX570 card). The Neat Video software is very hungry for processor power.

ECB wrote on 10/1/2013, 1:10 PM

You can install the Pro "over the top" of the Demo. http://www.neatvideo.com/qna.html

Ed B

Kimberly wrote on 10/1/2013, 1:34 PM

[I] Q Should I uninstall the older version of Neat Video prior to installing a newer one?

A This is not necessary. You can install a newer version of Neat Video over the older one.[/I]

Duh! I should have ready further . . . thanks for the link : )

Bliss Video Productions wrote on 10/1/2013, 2:14 PM

"Another small, but important, detail I picked up in my initial use: Rendering times from my timeline were massively shorter when I chose the GPU option inside the Neat Video software menus. "

Where in the Neat menus do you find this option? I'm not seeing it.

Mark_e wrote on 10/1/2013, 11:40 PM

Add neat video it to a clip then go to where you create the profile there are drop downs on the top that have options/settings it's in there

Best bet is to select the auto profile option I think then it runs through a test cycle to find the optimum balance between CPU and gpu (something sony and others could learn from, what a good idea!)

On my system 11 cores no gpu is the optimum configuration will vary depending on your setup.

Kimberly wrote on 10/5/2013, 2:42 PM

I found it in by adding NeatVideo to a clip and choosing Configure to open the interface. From there I selected Tools/Preferences/Performance in the menu.

Grazie wrote on 10/6/2013, 3:54 PM

Just installed the V3.4. That Performance engine, to determine by TRUE analysis of my PC, was worth the UG by itself. Maybe SCS uses something similar?

Grazie

set wrote on 10/6/2013, 7:08 PM

First install 2011, just updated today too... It has been so long... :)

The Optimize performance feature for CPU-GPU combination is nice...

I got the following results (40% allowance for GPU memory usage* by NeatVideo) :
----------------------------------------------------------------------------------------------
Frame: 1920x1080 interlaced, Radius: 1 frame
Running the test data set on up to 8 CPU cores and on up to 1 GPU

CPU only (1 core): 1.3 frames/sec
CPU only (2 cores): 2.54 frames/sec
CPU only (3 cores): 3.51 frames/sec
CPU only (4 cores): 4.1 frames/sec
CPU only (5 cores): 4.13 frames/sec
CPU only (6 cores): 4.03 frames/sec
CPU only (7 cores): 3.89 frames/sec
CPU only (8 cores): 3.76 frames/sec
GPU only (ATI Radeon HD 5700 Series): 3.31 frames/sec
CPU (1 core) and GPU (ATI Radeon HD 5700 Series): 3.03 frames/sec
CPU (2 cores) and GPU (ATI Radeon HD 5700 Series): 3.7 frames/sec
CPU (3 cores) and GPU (ATI Radeon HD 5700 Series): 4.67 frames/sec
CPU (4 cores) and GPU (ATI Radeon HD 5700 Series): 5.56 frames/sec
CPU (5 cores) and GPU (ATI Radeon HD 5700 Series): 5.65 frames/sec
CPU (6 cores) and GPU (ATI Radeon HD 5700 Series): 5.52 frames/sec
CPU (7 cores) and GPU (ATI Radeon HD 5700 Series): 5.52 frames/sec
CPU (8 cores) and GPU (ATI Radeon HD 5700 Series): 4.59 frames/sec

Best combination: CPU (5 cores) and GPU (ATI Radeon HD 5700 Series)
----------------------------------------------------------------------------------------------

CPU Only 5 cores is the fastest, and after that, it slows down?

*Is it okay to Full 100% allowance GPU memory use by NeatVideo ?

Set

Mark_e wrote on 10/7/2013, 3:21 AM

For NeatVideo I usually do any tidy up first so I usually do rough edit with plenty of overun add neat video (with adaptive and overun fix checked and 3 frame temporal, I like the neat sharp just in the luminance channel so do that if needed basic colour correction and levels if needed then have neat at 100% gpu (I've just changed to a 570 gtx and gpu/cpu combo better than my previous post where just cpu was better) turn off vegas gpu else there might be contention for resource at 100% and neat is where the work is happening, change project to 32bit float render out to new track ciniform high (the latest build of vegas and the latest go pro studio make that work out of the box again upto 1080p for free) then use that going forward. Change back to gpu accelerated and 8 bit to finish editing when done.

ritsmer wrote on 10/7/2013, 8:17 AM

@set: interesting numbers.

I also tried to run the built-in benchmark.
CPU is a 4930 hex-core at standard clocks 3.4/3.9:

CPU only (1 core ): 7.8 frames/sec
CPU only (3 cores): 22.2 frames/sec
CPU only (6 cores): 34.5 frames/sec (Optimum, better than 5 or 7)
CPU only (9 cores): 33.3 frames/sec
GPU only (GeForce GTX 650 with 1.8 GB): 7.7 frames/sec
CPU (1 core ) and GPU: 7.8 frames/sec
CPU (3 cores) and GPU: 12.0 frames/sec
CPU (6 cores) and GPU: 12.2 frames/sec
CPU (9 cores) and GPU: 11.5 frames/sec

So I stick to CPU only when Neat'ing - as I also always render using CPU "only".

ECB wrote on 10/7/2013, 9:24 AM

Run the Optimization test several times in a row and see if you get the same results with each successive run.

Ed