-
SVP 11 Crash, Crash, Crash!!!
-
Just deleted and reinstalled VP11, still crashing!
Now I don’t’ know what else to do.
Malcolm
Malcolm
http://www.malcolmproductions.com -
Has anyone used Sony’s tech support; $30 for one tech call?
I once had “support” from Dell, all they could recommend was to reinstall my operating system and all my software, that advice I don’t’ need to pay for!
M
Malcolm
http://www.malcolmproductions.com -
If it’s not too big for Dropbox, send the original media and the veg file and I’ll try it here. (Assuming I have the same third-party plugins you used.)
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I’m working with Jake Seagraves of Cineform right now, he did a remote access on my computer to see what was going on and I’ll update this post when everthing is straightened out, or not. If I cannot get VP11 to render I’ll take you up on your offer, thanks’ Steve.
Regards,
Malcolm
Malcolm
http://www.malcolmproductions.com -
Well, I finally figured out the source of my persistent render crashing. 32 bit floating point. I have been using this setting with VP11 and never had issued with it, but last week (something) happened and by adjusting my project settings to 8 bit, and the nested veg files as well, I was finally able to render out my project today without issue.
My thanks to Cineform’s Jake Seagraves for working with me on this issue, obviously not their fault, but he was willing to take the time to diagnose the problem.
Now I am wondering why did this start to occur as of last week? An update? Microsoft?, nivdia? I made 2 versions of my timeline, one using the cineform files and the other using my cameras h.264 files; both were crashing, and now they both work. So it’s something within VP11, and I just updated to build 683 “just in case” they fixed something.
I’ll have to do more tests with the project settings to see if I can use 32 bit for anything, from what I have read on the subject this seems like the preferred setting, but obviously not for my system!
I’m running an Intel i7 930 @2.8GHz Asus motherboard, 12 Gig ram Win 7 64bit Nvidia GTS 250 1Gig card with latest drivers. ESATA raid & separate render to drive.
If anyone has thoughts on the 8bit vs 32bit FP issue, I would like to hear about it.
Regards,
Malcolm
Malcolm
http://www.malcolmproductions.com -
I confirmed that I also have a problem with the 32 bit pixel format. See below for the results I got.
I just tried a render at 32 bit pixles with the MainConcept AVC Internet 720p and SVP 11 stopped (crashed). I tried again at but change back to 8 bit and it worked fine. I restarted SVP 11 again and tried at 32 bit once more and got the crash again.
I tried 32 bit again with Render -Customize template and setting the encoding to just CPU (NO GPU). Result was still a crash
Tried again same settings, but now turned off GPU in Tools-Options-Video and left it in 32 bit pixle and Render no GPU. The result was a good render.
This was with the SVP 11 Build 683 with NVidia 301.24 (beta)
-
This is very interesting.
For a long time I has been using the 32-bit floating point in SVP10, just because I was obsessing on what I thought would be the best possible quality. But, after learning many things about cameras in the past six months during my hair-ripping search for a cam, I came to realize that I can’t see any difference between 8-bit and floating point. Heck, I can barely see the difference between the 4:2:0 color space and the 4:2:2, in the Zacuto shoot-out tests (it is there, don’t get me wrong, but it is subtle for most of my purposes)
https://www.zacuto.com/the-great-camera-shootout-2011
8-bit projects render a lot faster …
Steve
Win7 Pro X64 on Dell T3400, MultiTB SATA, 8GB RAM, nVidia FX 570, Vegas 10e (and 11) x64 DVDA 5.2(build 133) Sony HDR-CX550V
Reply to this Discussion! Login or Sign Up