HELP HELP HELP RENDERING !

julie.koro wrote on 9/10/2009, 1:41 AM
I am desperated.

I have serious problems while rendering my projects in Vegas 8.0 c Build 260.
It freezes and it doesnt' complete the rendering process... never at the same % and no matter wich kind of template i use.

I work the same type of projects since many months ago, small videoclips, with the Properties : HD 1080-50i (1920x1080; 25,000 ips)

In the timeline i use transitions and effects such as color corrector or contrast.

I have already done many many small clips this way, mpeg2, size 640 x 480, (for web sites). As well as DVD PAL with DVD Architect studio with NO problems.

I don't know when or how it started to change... as i keep doing the same thing. I work with the same camera (JVC EVERIO model no. GZ6HD7E) which gives .TOD files (after i create MPG files with Cyberlink Power Director DE 6.5.2209 and then i work them in Vegas.

I have even changed of computer, i changed windows vista for windows xp pro, I have now 2 procesors Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, Physical memory: 2 097,1 MB, Paging memory available: 4 194,3 MB, Virtual memory possible: 2 097,0 MB

I contacted the technical support (in France) and the only answer they gave me after 1 month... it's that the problem are my files mpg and so i should test my project in Vegas 9...

Actually, the technical support doesnt even know if it will work or not, and my company has bought vegas pro 8.0 -because it should work and it used to work perfectly- and they are not agree about paying the upgrade in the case that the render finally works...

Can anybody help me???
Thanks

Comments

ushere wrote on 9/10/2009, 1:51 AM
if it worked in the past then:

a. you've added some program since then?

b. can you render anything - media gen file to what you want to?

c. vegas has got somehow corrupted?

d. and mpg on the timeline is asking for trouble afaic...

and if i may ask, if your end product is for web / dvd, why are you stressing your pc with 1920X1080? you'd be better off working 1440x1080 (native hdv) and if you want to keep as close to your original, try using .mxf, or cineform.....
julie.koro wrote on 9/10/2009, 2:27 AM
Thanks for answering!!!
a. you've added some program since then?

yes, software of 2 cameras (photo), but in the new computer i have just installed vegas and dvd architect.

b. can you render anything - media gen file to what you want to?
no... vegas freezes and it doesnt complete the 100 % of rendering

c. vegas has got somehow corrupted?
i have thought about it but i don'know how... since i'm the only one that uses this computer and it started to fail just one day... like that...

I work with 1920x 1080 because in the first contacts i had with the sony technical support they told me to adjust the properties of the project with my media files. The mpg are full hd.
I have to render the same project for the web; dvd and now also in blue ray.
I will try the mxf
julie.koro wrote on 9/10/2009, 2:47 AM
It freezes also at 11% of the mxf...
farss wrote on 9/10/2009, 2:52 AM
MXF is a container, that generally contains...mpeg-2!

Are you by any chance using 32bit float processing?

Almost every project I do is 1920x1080, it should work.

Bob.
julie.koro wrote on 9/10/2009, 2:59 AM
mfx... i dont know exactly how to work with it :s

No, i dont use the 32 bit... Im at 8 bit
Christian de Godzinsky wrote on 9/10/2009, 3:36 AM
Try to set the number of rendering threads to ONE (1) !!! (in the Vegas preferences).

This has helped me in similar cases.

You can also disable the other core(s) in your bios but that is more cumbersome. Worth trying if the first trick does not do the job.

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

julie.koro wrote on 9/10/2009, 3:48 AM
Thanks Christian !

Rendering threads is 1, also the previs. ram is 32.
I also use the option quantisize. on the video layers.

The videos for the web, i have done it! i am so happy because it finally worked.

I am still trying to render a flux DVD architect but... that one doesnt work at all...

I changed the properties, instead of setting PAL system, i used NTSC and it worked...

the problem is that we are in france so i need a PAL for the dvd and the blue ray...
farss wrote on 9/10/2009, 4:40 AM
"I changed the properties, instead of setting PAL system, i used NTSC and it worked... "

Now that is scary. I assume you mean the project properties, in which case it shouldn't make any difference.

Bob.
julie.koro wrote on 9/10/2009, 4:46 AM
yes Bob, the project properties.... anyway it rendered ok... but i still cant render the flux video dvd
Grazie wrote on 9/10/2009, 4:53 AM
"Adjust source media to better match project or render settings" - Is one of the new options in VP9 Project Properties. Could this have a bearing - Bob?

Grazie
farss wrote on 9/10/2009, 5:23 AM
I don't see how. Odd that he had the project properties matching and to some extent fixed the problem by having it not match, figure that one out. Of course it could be that it had no real correlation at all.

Switching to only 1 core seems to be a common fix for these kinds of problems. I read and hear a lot of suggestions that you need 2GB per core and that's on PCs and Macs. If that's true then reducing the number of cores reduces the amount of RAM needed. Wierd huh.

The one and only way I've struck any real success when these problems become intractible is to convert all the source material to a non long GOP codec. If you've a lot of hard disk space then uncompressed is the go. The Sony YUV codec will use less disk space and coming from mpeg-2 you'll oose next to nothing in image quality.
To do this you render all source material to alternate codec. If you've got a lot of source files then a batch render tool like the Veggie Toolkit or US would be well worth the money. The process is easy enough.
Render to another folder, keep the file names the same, obviously the extension may change. Then rename the folders. When you reload the project Vegas will complain about all the missing media as the file extensions have changed. However as the file namesare the same it should only take a few minutes to get this all sorted.


Why the above seems to work I cannot say for certain. I suspect it's because Vegas buffers all the frames in the GOP in RAM and given enough tracks and enough else going on it simply runs out of RAM.

Bob.
julie.koro wrote on 9/10/2009, 5:43 AM
I keep trying... My clip of 2 minutes has the effect color corrector (i am not sure of the right english translation ) but there are the color corrector and the secondary one. I use both and if i erase them from the video layer then the render works (multimedia only).
farss wrote on 9/10/2009, 6:18 AM
Your English is good.

I'm running out of ideas. I understand that you've tried the same project with the same media on two different computers and have the same problems. If that is correct it excludes many possible problems such as hardware or a corruption of Vegas itself.

As the clip is only 2 minutes long all I can suggest you try is this:

1) Open Vegas and set project to 1920x01080 50i. Add the clip. Render to AVI, select Uncompressed.

2) Open original project. Goto Project Media, Right Click the 2 minute clip and select Replace. Select the Uncompressed AVI you created in 1)

Now see if your project will render OK.

If you still have a problem I think I'm out of ideas, sorry.

Bob.

julie.koro wrote on 9/10/2009, 6:38 AM
Thank you very much for your help Bob.
It didnt work :s :(
I keep trying...
Byron K wrote on 9/10/2009, 10:32 AM
I've had a similar thing happen to me before I started using Vegas.

Maybe you can render half the video at a time and stitch them together in another project.

If one half renders and the other half doesn't then maybe there's a corrupt file. Split the bad portion in half and see what half renders and which half doesn't. (called divide an conquer)
Eddy Bee wrote on 9/10/2009, 11:12 AM
I had a similar problem, also using 8.0c. Vegas would partially render one of my projects and then stop dead. All my other projects always rendered fine.

After some trial and error, I was able to remedy the problem by removing one of the video effects plugins I had inserted on the video bus (Video Output Effects). In my case, the offending plugin was the NewBlue Noise Reducer from the Video Essentials II pack, which came as a big disappointment, but at least I was able to render the video.

Hope that helps.
Rosebud wrote on 9/10/2009, 11:20 AM
Julie,

J’ai eu un problème similaire que j’ai résolu en reconstruisant le projet :
Tu ouvres deux instances de Vegas et tu fais un copier/coller de tous les events d’une instance à l’autre.
S’il y a des mouvements de piste (ou des effets), il faut le faire manuellement car il n’est pas possible de les coller.

En espérant que cela pourra t’aider ;)

Gilles
LReavis wrote on 9/10/2009, 12:15 PM
I regularly have had this problem with long-form (an hour or two) projects that include lots of effects. I always have been able to render by putting markers at 2-min. segments then using a batch rendering program (Veggie Toolkit) to render each 2-min. segment using Cineform intermediate. Then I put all the segments on a new project timeline and render that using whatever codec of choice.

Once in awhile I encounter a really stubborn segment that still won't render even though only 2 min. long. In that case, I select it and copy it into a new instance of Vegas, save it to a new .VEG, and close the original project. After a reboot, the new tiny 2-min. project will render (although I believe that sometimes I've had to cut even the 2-min. segment into smaller pieces).

I've also read that some have found that each crash nevertheless yielded a good partial render, even though not complete. They simply put the incomplete rendered file on a new top track, then selected the remaining portion of the timeline and rendered again, this time with the "Render loop region only" box checkmarked. Each time Vegas crashes, they repeat this process until they have the entire top track complete. Then they render out the entire project using their codec of choice.

Other hints: Turn off memory eating options, such as Waveforms and Frames (uncheck the box in the View menu). And, yes, I render using only one thread instead of 4 on my quad-core machine. Rendering on my old P4 on an Intel motherboard is of course just one thread/core, and it does indeed render a little farther into my projects before the crash occurs.

Some have claimed that turning off the antivirus also helps, but I haven't found that to be true. I've also read that setting Dynamic Ram Preview to 0 helps (Options>Preferences>Video tab), but I haven't personally tested that.
julie.koro wrote on 9/11/2009, 1:04 AM
Yes Eddy, i noticed that by removing the video output effects it worked better
julie.koro wrote on 9/11/2009, 1:11 AM
Merci Gilles;
Je l'ai fait aussi; et oui ça marche... mais ça me le fait à nouveau dans le projet que j'ai refaite. J'ai crée 2 projets avec copier_coller et ça ne marche pas. Par contre si j'enlève les effets comme correcteur de couleur dans la sortie vidéo ça m'a rendu mon morceau super. Mais bon; le souci ce que je dois rendre le clip avec les effets...