Mark Barton
Forum Replies Created
-
Check to see if you have any other software running while SVP 11 is loaded that might have exclusive access to the audio card. SVP should not crash, but maybe it did not know how to handle the response from the audio driver. Usually they say to disable Windows system sounds, since you don’t want those to wind up in your audio mix. Check for things like Skype that may be running in the background. Are you running ASIO drivers or the generic Microsoft drivers? I checked the release notes for the 595 build but did not notice anything specifically that caught my eye that would cause a problem. It could be they are initializing the card differently to change the settings, but it is not generic enough of an error to cause problems on my system. I am running the Microsoft drivers as the ASIO4All driver was not working well with my hardware. It worked for a while but then I would have problems when I switched out of SVP 11 to run other programs.
-
I cannot reproduce this either with build 595. It applies the audio property changes without crashing. Are you sure the audio driver did not change recently. I guess you will know when you revert back to the older SVP 11 build and it is still broken.
-
I was able to reproduce this if I used 1080p video and project properties set to 1920×1080 and then used the Tools menu to burn a DVD. When I changed the project properties to be DVD Widescreen and then went back to the Pan/Crop tool on the jpg and selected match output aspect ratio, the crop changed size slightly and the extra pixels did not show up on the DVD when playing on the computer.
-
I just rendered a 2 hour source media clip shot at 1920x1080x60p AVCHD into the Blu-Ray 1920x1080x60i template and it completed successfully in about 3 hrs. My project settings were set to match my source media.
Maybe it is the Power supply or memory as someone else suggested. I’m running a gold standard 800W PS and 12GB of Corsair RAM. All “12” CPUs were running 90%+ on my i7 hexcore.
-
It looks like your card is a lower GPU than the HD 57xx series. From what I could see from browsing around the AMD site is that your card supports OpenCL 1.0, but the HD 57xx or higher supports OpenCL 1.1. It would be nice if that were the case, that SVP 11 would detect that and not attempt using it.
From the Sony site:
https://www.sonycreativesoftware.com/vegaspro/gpuacceleration
AMD/ATIRequires an OpenCL-enabled GPU and Catalyst driver 11.7 or later with a Radeon HD 57xx or higher GPU. If using a FirePro GPU, FirePro unified driver 8.85 or later is required.
-
Was your project settings for DVD Widescreen or were they set to match the 1080i source?
-
%USERPROFILE%{backslash}appdata{backslash}local{backslash}sony{backslash}vegas pro{backslash}11.0″
Not sure why all the backslashes were removed from the post; replace “{backslash}” with an actual backslash
-
I have successfully done similar, where I used 60p footage and rendered to 60i with the GPU turned on. As a test right now I took a 2min 23s video project I am working on that was shot at 1080p x 60p and chose Render As for Blu-Ray 1920×1080-50i. It completed successfully in about 4 min.
-
I meant what video source are you editing? AVCHD 1080p, MiniDV, etc. What format are you trying to render to in other words what are you selecting in the Render As dialog.
My renders complete with the GPU turned on, but that could be that we are not using the same plugins.
-
Do a {Win Key} R to get a run dialog and paste the following in
%USERPROFILE%appdatalocalsonyvegaspro11.0
See if there are any errors in these files that may give us a clue to what is happening. Did you have something for me to render so we can see if it is Sony Vegas Pro or something specific to you computer that is causing the problem?