Phil Peacock
Forum Replies Created
-
For sure John. Very keen.
Not going to get all sloppy, but it’s great knowing that you, and several others who are regular contributors and solvers in this forum, are constantly here, with your assistance.
I am an almost daily reader of peoples input on this forum and it almost feels like family, although one that I don’t need to feed and that doesn’t (usually) answer back.
Now get to bed!
-
Soooo glad you’re still up John. Thanks again, it WORKED! This was so frustrating. Still don’t know why this should work like this though. Will have to puzzle that through myself.
But thanks again!! -
Thanks for your prompt reply Graham.
What you suggest is what I think I have already tried. Alas, no prize.
And using the various other options of in/out/both I get these results, each of which is a bit weird really. Not working how I would have thought it should. Maybe my copy of computer/video card/Vegas is playing up somehow?;-
-
Maybe this can help you. I was having issues with SVP11 too on a very new and reasonably spec’d Win7 computer.
Tom Pauncz and Mike Kujbida very helpfully posted a possible solution which has seen my set up go from totally frustrating to pretty much rock solid.
Try it and see how you go.
-
Thank you, thank you! Once again Mike. I can now go to bed!!!
-
Thanks Al. Fair bit of investigation going on there and a very comprehensive posting. I take onboard all you’ve said. Likewise, I have had to avoid, as much as I can, too many VFX and, like you, it wasn’t only NB fx that caused the crashes.
Mike’s suggestion however DOES seem to have worked. Certainly in the short amount of time and the little work I have done since making the alteration. I was already running Win7 but simply setting it to run in compatability mode with Win7 (weird eh?) appears to have stabilised everything.
Good luck with your endeavours though.
-
Mike!!
You have saved my sanity a couple of times now and this seems to be one of them. Been throwing a few things at Vegas after this little tweak and seems as though nothing fazes it now!
My amazement can be summed up in three words – “Well I never”, ha ha.
Really, thanks. I am still holding my breath though.
-
Hi Al
I am running on an Asus P8H67 mobo, 8 gig of Corsair DDR3 with an Asus GTX550Ti video card. And yup, I have two 24″ monitors hooked up to the card. I use Win7 64b and am running the latest build of Vegas 11 Pro.It HAS to be the video card incompatibility doesn’t it? I keep testing, even with single events on the timeline. Last night for instance; one clip, copied to another track with a mask and then a Gaussian blur added to that top track with the mask. Crash!
And again. And again. The clip I used was some stock footage from the internet which was 720×480, 30fps progressive footage. My project settings were 720×576 25fps interlaced.
Sorry for all the details, just trying to be comprehensive for you. Good luck with your theory though! Let me know if there is anything else I can provide you. Maybe others here can detail their tests, using a minimum of events and effects, in order to try and isolate wherein the issues lie. As a said in my initial post I think, when mine crashes it more often than not does so without the option of posting the issues to Sony.
-
Sorry guys. What was I thinking?! Still getting plenty of seemingly RANDOM crashes. Probably can disregard my previous post. If only it had been that simple!
-
Thanks Edward. I was wondering if that was the culprit.
A couple of times I had uninstalled NB Titler Pro and then installed the updated version (1.1)as indicated in the úpdate’drop down. Couldn’t work out why it was not recognising the updated version and was still indicating that a newer version was available even though I had tried to install it a few times. It was only when I read the fine print that came with the update that I found the advice for Vegas Pro users to stick to the 1.0 version.
Anyway, all good now so thanks for your directions. Very much obliged.
