Stephen Mann
Forum Replies Created
-
So far, I’ve done 4K-30P and 2.7K-60P. Just drop them on the timeline. I have to admit that I am hooked on using proxy files for the rough cuts, but the Hero4 makes them for me – I just have to rename them for Vegas (.sfvp0 suffix) and I have my instant low-res (really low-res) proxies.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
“You would think that Sony would make sure that Vegas Pro can ingest GoPro 4 Black footage without any problems but it cannot.”
I must be a Bumblebee because I just drag the mp4 files from my GoPro Hero 4 to the Vegas timeline. I didn’t know I was supposed to be having problems.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I am glad that you fixed it and that you let us know of the resolution.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Did you watch the GDI count while rendering? But, GDI overrun and Pagefile crashes are the only things I know will cause a BSOD.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
look at the GDI’s while rendering anyway. I haven’t seen it happen but another user had an errant driver or codec, I don’t recall which, that was not releasing GDI’s properly. He reported that he could watch the GDI useage climb during the render, and as soon as it got really high, he got the BSOD. If I recall, it was a New Blue F/X plug-in. If you are using any NB FX, try a render without it.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I would suspect that it’s time to re install everything. BSOD is pretty rare in Win7 but PageFile errors are one place that you can still get them. The NTOSKRNL is pretty much the heart of the OS. Windows 7 is built on the Windows NT Kernel, which was built on top of DOS, so all this means is that the kernel was trying to do an operation when it crashed. Your Pagefile is managed by the kernel which is why that is the first thing to check. But switching it back to your boot drive and letting Windows manage it was a good test. You probably know this, but Pagefile settings don’t change until you reboot.
You can also get BSOD if you use up your allotment of GDI resources. Every graphics object, the ones you see like icons and windows, plus those held in RAM is a GDI object. I haven’t ever seen it happen, but if you have thousands of still images on a video project, every one of those images consume a GDI.
Here’s an article from Microsoft that may help, at least to use Task Manager to see if you are anywhere near using all the allocated GDI objects.Steve Mann
MannMade Digital Video
http://www.mmdv.com -
-
When you select any transition, it becomes the default for all transitions that follow. If you want to change it, just select another transition.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
-
If I recall, you have a slightly underpowered PC for video editing. The difference in render times may be because your PC resources have changed. Before you start a long render – reboot. Many programs that you may run on your PC eat resources that Vegas would like to have. For example, if you run any Microsoft Office program, the program loads part of Office into RAM and it stays there until you reboot. They do this to give the appearance of fast loading. Browsers are also huge memory hogs that don’t completely remove themselves from RAM until you reboot.
Steve Mann
MannMade Digital Video
http://www.mmdv.com