[Wilfried Van]

SONY made a huge mistake by selling it to the present owner .
That’s all I can conclude , unfortunately .

[Wilfried Van]

Maybe I am not clear enough ☺

Start vegas , do not load anything , just set the properties and set the ” apply these for all new projects ” and press apply.
Now exit vegas .
Restart vegas and verify the project properties -> all are correct but view transform ( ACES instead of OFF ).

When saving a veg file with the properties , it reloads fine with all the project properties correct but each time vegas is started again and nothing yet loaded ( no veg file , vegas just opens ) the properties are again view transform to ACES instead of OFF .

Bizar

[Wilfried Van]

Hi Graham ,

Open vegas ( without a project ) for first time and set project properties properly , save and of course “Start all new projects with these settings” . ( am using vegas since version 4 and this basics I do know in meanwhile ☺ ) .
Now close vegas .
Re-open Vegas and everything BUT ” view transform ” is correct in project properties ( ie the OFF changed into ACES ).

Wilfried

[Wilfried Van]

Here using HP Z820 workstations with dual xeons ( 2 x 12 cores ) and 64 GB of RAM ( and some quadro’s and SSD’s , of course ) .
GPU Always OFF but RAM preview forced to 48 GB .
Pretty nice comfortable previewing in this case. Since vegas pro 12 , vegas also uses the RAM , which was not the case with all previous versions.

The fact that sony vegas pro is still thinking 32 GB RAM and 16 threads being the ultimate hardware being used for sony vegas , is not much pro nowadays. ( since some more years )

When , in internal prefs , I do increase those maximums to present available workstation levels ( 48 GB RAM , 40 threads ) , there is a boost of previewing capabilities ( GPU remains off ).
Unfortunately those settings have to be reset each time after restart and that’s a pain .

So instead of adding useless features in new versions , I would rather like to see this basics to be attacked properly .

And you don’t need mac when having worked on a hp z820 ( now even 840 ):-).

[Wilfried Van]

Thanks for the confirmation
Really ashame such important basic function having a serious bug and not being resolved . Instead of adding fancy things most of us do not need nor use , they better concentrate on having the basics working and as steady as versions 4,5,6 and 7.
I would pay for that , not for the fancy things anymore …..

[Wilfried Van]

Thanks Theo , same full identical crash with 5.4

[Wilfried Van]

Hi Jon ,

The system at studio is HPZ820 and dellT7500 , both win7x64.

Moved the sapphire AE effects ( since they are there anyway ) manually into the boris red plugin folder ( as before with the genarts sapphire 6 , which worked ).

Boris red crashes fully as soon as you simply try to add one of the
genarts fx . ( both in standalone red as when red being used as plug-in of , for example vegas pro 11 or 12 )
Total boris crash , no messsage.

Just wanted to point this out since that worked with genarts sapphire 6 version .

[Wilfried Van]

RED whatever 5 version still playing PAL clip much too fast when RED being used as plug-in of vegas . ( as described here below or above )

Gave up on this BORIS RED( how long is version 5 now released ?? ) and bought the adobe production premium CS6 suite instead at a good price .

[Wilfried Van]

Thanks for your answer Steve , but it got already answered by the engineers of genarts within 2 hours after reporting to their offical support site. ( being a vegas issue )

Of course , latest version is installed but would not matter much since it is a vegas issue ( also officially reported to Sony ).

Dell T7500 , dual Xeon W5580 , dual nvidia quadro 4000 , 48 GB RAM , 4 HDD , win7x64 , pure and only video editing station and solely installed vegas pro , DVDarch , soundforge and after effects.

[Wilfried Van]

Hi Peter ,

Were your labs able to look into this and if so , could you reproduce it and if so , is there to be expected a remedy ?

Best regards