Matt Cohn
Forum Replies Created
-
i found this helped work round the problems we are experiencing:
-new project
-browse to a clip thats in the folder where most of yr clips for the project you want to open are
-import that clip so its on the timeline
-NOW try and open the project you want.I think 64bit windows /vegas gets easily confused over paths. This seems to kick it onto the right path
Pathetic but it works for me
@JR, yes Vista is death! gonna upgrade asap.
-
its on the same machine that vegas is on. can you play a 60gig YUV file in WMP? thats how big a typical render is (about 17 mins section)
-
thank you John
-
QT photojpeg.
btw, it rendered ok on the pther machine as YUV avi. Also, periodically projects at this size will render fine, as either qt or avi, but often they dont . its a wierd one!
-
yes, checked, I am on the latest QT too!
on the other machine, an i7 with 8 gig ram, I couldnt render to avi pegasus codec. Next I will try a YUV avi render on that machine. So far, I would still love an answer to my orginal question of a batch conveter that can convert YUV avis to QT.
thanks
Matt -
hi John. Thanks for your response. Yes, I’d love to render to QT directly!
I posted a fuller description of my prob on the sony forums that gives the info you request:a year ago, I was working on vegas 9 and being unable to render projects. the problem was never resolved despite frequent mails to tech suppoprt.. Now, a year later, I am trying to do version 2 of this same project, and receiving the same error message:
‘vegas was unable to render xxx project’ with no further info is little help, tho it seemed last year as if some sort of memory problem could be occuring. The only work around I found was to render thr project in regions.I find it unbelievable that in this time Sony has not solved the problem. It is a well known problem that is discussed in the community…I saw one user write that he hoped that the 9.0d build would solve these problems. Apparently, it hasnt. I am rendering at 1648×768. With about 20 video tracks, but of these only 2-4 are concurrent. I use no effects other than the standard vegas ones. My machine is a macpro quadcore with 8g ram running vista64 bit via bootcamp. My other main machine, an i7 processor also with 8gig ram and vista64bit, falls over with the same non-informative error. We are attempting to render to Quicktime photojpeg max quality.
There was a response today:
Reply by: Yoyodyne
Date: 4/28/2010 10:25:27 PMWhen I’ve been in this situation the most pain free method has been to render the timeline to something like Cineform or MXF and drop that rendered file into a new Vegas project and render to my “delivery” format form their.
-
Theo!
thank you so much for your prompt and clear response. That has resolved the issue.
Great stuff, you are a star and the power of community is a wonderful thingBest,
Matt -
Man, have they still not fixed those memory rendering errors? Can’t believe it, so rubbish. A year ago they were killing me and lots of other people. ( have a topend system with loads of Ram and i6 so there shouldnt really be a resource issue). Sony, wake up or we’re forced to FCP.
-
Thanks to another post, I think ‘lock envelopes to events ‘ explains this!
-
sorry no one replied to you till now. i had a look and found this to change these settings; i set page file max and min to 6000mb on a different drive to my system. maybe it will help!
https://support.microsoft.com/kb/308417
To manually change the size of virtual memory, follow these steps:
Click Start, click Run, type sysdm.cpl in the Open box, and then press ENTER.
Click the Advanced tab, and then under Performance click Settings.
Click the Advanced tab, and then under Virtual memory click Change.
Under Drive [Volume Label], click the drive that contains the paging file that you want to change.
Under Paging file size for selected drive, click Custom size, type a new paging file size in megabytes (MB) in the Initial size (MB) or Maximum size (MB) box, and then click Set.
Click OK to close the dialog box and apply changes.x
m