[Wilfried Van]

Would be great to be able to buy it through our bank account instead of paypal .Don’t have a paypal and don’t want one .

[Wilfried Van]

Am using vegas pro since version 4 and confirm that from version 11 , maybe even 10 , vegas pro if FULLY utilising ALL CPU’s ( 32 threads ) at 100% whilst rendering and this on HP Z820 workstations with 2 x 8core HT XEON processors . People keep on spreading wrong information about this and I wonder why . The only disadvantage on the sony vegas versions is the lack of GPU assistance but instead one is able to use lots of RAM ( dynamic RAM preview ) which allows for instant fast preview when applied FX ‘s . The Magix vegas versions work better with GPU on but at the same time , one has to put the dynamic preview RAM to a few MEGAbyte in order for it not to display ” vegas has stopped working ” …

[Wilfried Van]

And this keeps on going in vegas pro 18. Project Properties at 32 bit full level and dynamic preview results in insane preview ( 3 frames , 2 frames , 1 frame , 16 frames , etc .. /sec ). 8 bit full level is OK . ( started since vegas pro 17 build 387 and ongoing ) . GPU=OFF ( when ON , this 18 is unstable as a wild horse , latest nvidia quadro drivers and this on both HP Z840 workstations )

[Wilfried Van]

BCC12 also not working anymore and preventing vegas pro 17 trial to start.
Well , anyway , let’s just see what happens in the next update , there is a lot of beta testers in the magix vegas forum 😉

[Wilfried Van]

It is here yes…. and doesn’t work with many plug-ins anymore such as boris continuum complete and others ….
Still on the latest SONY vegas pro 13 which is the most stable here , together with vegas pro 7 which NEVER has crashed on any system 🙂

[Wilfried Van]

Hi Francois ,

Thank you for your reply .
We are working with vegas pro since version 4 , so this program is not new to us .
We do know the differences between 8 bit and 32 bit in the meanwhile ????

The question we have is why >vegas pro build 307 all of a sudden can’t realtime play m2t files whilst all previous versions with same settings can ( with GPU=OFF , so the quadro M5000 is disabled in all these cases and is irrelevant here ) .
Anyway , we continue in meanwhile with the sony vegas pro 13 for this particular project and will wait what the next vegas pro 16 might ( or not ) do .
In parallel avid media composer will used since our hardware seems to fit that program better

[Wilfried Van]

Now the only thing which I can ( visually ) see is that later versions than build 307 have a ” Master Display ” setting added in project properties and I have absolutely no idea what those settings mean and do ( or don’t do ) .
Can’t find anything anywhere in this regards.

[Wilfried Van]

Hi George ,

32 bit full video because of better colors in preview which is near to final rendered project .

GPU=OFF because we have some projects with serious FX and bezier masking etc.. and need to run dynamic RAM preview regularly . When GPU=OFF , we can put dynamic RAM to about 32 GB ( out of 128 GB ) , which is still a small amount of the total RAM installed and allows for fast and easy dynamic RAM previews .
Chance of getting …stopped working …. is minor with GPU=OFF

In the vegas pro 16 later than build 307 , when GPU=ON , one has to put dynamic RAM to an incredible 200 MB or less !! . Otherwise the ….stopped working …pops up and that message we are very tired to see and does not allow for hours of editing . And even with that 200MB setting it randomly gives that message .

Swapping between GPU ON/OFF requires restart of vegas and altering dynamic RAM value and is everything but Obvious , so we do prefer the less possible chance of ….stopped working ….

The testing was just done to see whether there is improvements in real-time editing and previewing .
Will do some more investigations here

Thanks for your replies

[Wilfried Van]

Hi George ,

Thank you for your tests and answer .
We will try to find out why vegas pro 16 build 307 previews just fine ( full/best – 32 bit full range ) and uses all CPU cores and lots of RAM while doing so whilst the next builds does not and stutters at 5 frames/sec and does barely use CPU power .
GPU=OFF

the .m2t files are read by compoundplug and are 1440×1080 PAL from old HVR-V1E camera , captured by vegas and due to fact we had to insert some old shootings in a clip .
That’s where we noticed this .

Using the sony vegas pro 13 compoundplug in any later vegas pro 16 build 307 version ( temporarily ) , did not help .
Bizar .

At the same time we noticed with any later then 307 build , one has to limit the dynamic RAM size to 200MB when GPU=ON . Otherwise every few minutes ” vegas has stopped working ” . Previous builds , one could leave the dynamic RAM to , say , 32 GB or so , which has always been our standard setting when GPU=OFF in order to play very smooth and without stutter

Will try some more things . Ah , we are still on win 7 pro

[Wilfried Van]

Have been buying and upgrading all sony’s software each year ( since vegas pro 4 ) since I liked it and am still using latest vegas pro 13 of SONY . ( I did buy the magix vegas pro 14 upgrade and never installed it and never will )

I have said it before , Magix is really …. , I was hoping BorisFX …

So now I am in parallel learning and using the basics of AVID media composer since that is also the only software
being used here in Belgium by production houses
I started last year with AVID media composer FIRST , which is FREE and comes together with thousands of soundFX and other free stuff and got , after that year , a VERY good special introduction offer to step into the full AVID media composer .
My workstations ( HPZ820 and 840 ) are also fully compatible with their softwares and makes life easier .

A petty and I feel sorry too for Gerry since , as an electrical-electronics hard-and software engineer and manager , I do know what it is to develop things with a very small crew. VERY DIFFICULT , IF NOT TOO DIFFICULT