Frameserve project
- Thread starter buhce
- Start date
I would tackle the render problem before I looked at frameserving to another program.
What kind of project is it? What kind of footage is it? What are you trying to render to?
Need as much detail as possible.
What kind of project is it? What kind of footage is it? What are you trying to render to?
Need as much detail as possible.
It doesn't seem to matter what footage it is. I've tried lots of different footage- mainly Sony Ex1 footage(tried both .mxf and original .mp4). I'll get the 'out of memory' error when rendering 8-bit (sometimes it just freezes at variety of percentages)and it'll just crash with an unknown problem when rendering in 32-bit. (or with an error like that in the quote)
I am mainly rendering to .wmv 1080p but have tried 720p. Also tried other codecs mainconceptand the Sony .mp4 and they were working for a couple of renders, then it just began again. Occasionaly with 32-bit I'll get some error code. I know I'm not out of memory 'cause I have 12Gb and the application doesn't even come close to using it all before it crashes. In the past I've had to start rendering smaller clips and reseeding them back into a new project - shouldn't have to do this. Plus sometimes even that crashes.
That's what I got the last time I used 32-bit project at either 1080p or 720p.
Oh yeah I use Magic Bullet Looks also. It's not my setup 'cause I have tried it on my other computers and the same thing happens at various points in the render. It's not the footage either - this happens with every project. I'm at a loose end. Tried adjusting render threads and Dynamic preview. Tried going through each option in the preferences and switching them off, tried getting Sony to fix the problem, tried getting Red Giant to fix the problem.No dice.
I am mainly rendering to .wmv 1080p but have tried 720p. Also tried other codecs mainconceptand the Sony .mp4 and they were working for a couple of renders, then it just began again. Occasionaly with 32-bit I'll get some error code. I know I'm not out of memory 'cause I have 12Gb and the application doesn't even come close to using it all before it crashes. In the past I've had to start rendering smaller clips and reseeding them back into a new project - shouldn't have to do this. Plus sometimes even that crashes.
That's what I got the last time I used 32-bit project at either 1080p or 720p.
Oh yeah I use Magic Bullet Looks also. It's not my setup 'cause I have tried it on my other computers and the same thing happens at various points in the render. It's not the footage either - this happens with every project. I'm at a loose end. Tried adjusting render threads and Dynamic preview. Tried going through each option in the preferences and switching them off, tried getting Sony to fix the problem, tried getting Red Giant to fix the problem.No dice.
Last edited:
You're saying that any project with any kind of footage will not render, and that's true on multiple computers running Vegas? That doesn't seem right at all.
Try removing the MB stuff and see if it works.
Try removing the MB stuff and see if it works.
Any HD footage when using Magic Bullet mainly.
Just happened again:
it happens on my 32bit systems too.
I've had it crash on me before without the MBL.At the moment ( on this project) it seems to be crashing on a fade out where there is no footage or it's faded to black. I might try some black video.
I was hoping 9 would fix this.
Just happened again:
it happens on my 32bit systems too.
I've had it crash on me before without the MBL.At the moment ( on this project) it seems to be crashing on a fade out where there is no footage or it's faded to black. I might try some black video.
I was hoping 9 would fix this.
Last edited:
Hi Buhce,
Couple of months ago, I tried to frameserve vegas 8.0C to use external encoder such CCE SP2 or Procoder 3, I got no reply from this thread. After researching some information , now I know how to do it.
1. Installed Debugmode frameserver ( download from website, google it )
2. go to Vegas and render as Debugmode frameserver.AVI in drop down menu, let it run, but do not stop, just minimize it ( very important do not stop it )
3. then run external encoder ( CCE Sp2 or any encoder ) it will be linked to vegas files and render out as any format or Mpeg2 ready to burn for DVD.
Hope it will help you
Billy
Couple of months ago, I tried to frameserve vegas 8.0C to use external encoder such CCE SP2 or Procoder 3, I got no reply from this thread. After researching some information , now I know how to do it.
1. Installed Debugmode frameserver ( download from website, google it )
2. go to Vegas and render as Debugmode frameserver.AVI in drop down menu, let it run, but do not stop, just minimize it ( very important do not stop it )
3. then run external encoder ( CCE Sp2 or any encoder ) it will be linked to vegas files and render out as any format or Mpeg2 ready to burn for DVD.
Hope it will help you
Billy
buhce:
Did you specify Stereo or Surround 5.1 sound? I encounter the same kinds of errors when I render Full HD (any format) with Surround sound, but I can render ok when I specify stereo sound.
NOt that I am using Vegas Movie Studio, not Pro, but I'm gessing the rendering components are the same.
I'm beginning to suspect the problem lies with the Microsoft Visual C++ runtime library, and not Vegas itself. There are several versions of the VC++ runtime out there and I'm guessing Vegas is dependent on a particular version, which is now obsolete. It's posible that Windows Update replaced some parts of this and that, in turn, is what's causing Vegas to crash.
All this is just supposition so far, but after I installed Vegas MS on a fairly clean laptop that had no VC++ at all it rendered fine. This is very reminiscent of the old "DLL Hell" problems in earlier versions of Windows, and, unfortunately, is very difficult to resolve -- if I am correct.
Did you specify Stereo or Surround 5.1 sound? I encounter the same kinds of errors when I render Full HD (any format) with Surround sound, but I can render ok when I specify stereo sound.
NOt that I am using Vegas Movie Studio, not Pro, but I'm gessing the rendering components are the same.
I'm beginning to suspect the problem lies with the Microsoft Visual C++ runtime library, and not Vegas itself. There are several versions of the VC++ runtime out there and I'm guessing Vegas is dependent on a particular version, which is now obsolete. It's posible that Windows Update replaced some parts of this and that, in turn, is what's causing Vegas to crash.
All this is just supposition so far, but after I installed Vegas MS on a fairly clean laptop that had no VC++ at all it rendered fine. This is very reminiscent of the old "DLL Hell" problems in earlier versions of Windows, and, unfortunately, is very difficult to resolve -- if I am correct.
I've thought that it's perhaps a windows problem also. Does your Vegas MS still render fine and what version of windows were you using?
Regarding audio. I checked it and I'm rendering stereo.
Problem Solved!!
I reset the memory flags using CFF explorer of the following:
vegas80.exe
wmfplug4
(and other codec .dll files)
open the program
goto file\open
then find the file... in this case it would be Vegas.exe
On the left side you'll see "NT HEADER".... "DOS HEADER"... etc
Highlight "FILE HEADER" under "NT HEADER"
On the right side you'll see a chart and in the bottom right corner you will see "CLICK HERE"
Click on that and a check box menu system will open.
Scroll down the menu list until you see "app can handle > than 2gig address space" and check that.
Save the file and close
remember to run the program as admin
I've not had a crash since
I reset the memory flags using CFF explorer of the following:
vegas80.exe
wmfplug4
(and other codec .dll files)
open the program
goto file\open
then find the file... in this case it would be Vegas.exe
On the left side you'll see "NT HEADER".... "DOS HEADER"... etc
Highlight "FILE HEADER" under "NT HEADER"
On the right side you'll see a chart and in the bottom right corner you will see "CLICK HERE"
Click on that and a check box menu system will open.
Scroll down the menu list until you see "app can handle > than 2gig address space" and check that.
Save the file and close
remember to run the program as admin
I've not had a crash since
Last edited: