vegas 4 is killing me
- bum
- 17747114553
- Joined: Sat Nov 08, 2003 9:56 pm
vegas 4 is killing me
well, its not killing me but it is killing my time. it seems to take absolutely forever to export a video, no mater what format and/or setings i use. as in, its exporting at between 2-4 frames a second. in otehr words, if i want to preview a amv im making (because when ya preview it in vegas in it lags and skips a bit) then i might as well go out and rent a movie or 2 while its exporting, and if i wana combine an avi and an ac3 then i should go to space and travel at neer the speed of light so i would only have to wait a few minutes (thats physics by the way). seriosly though, it cant have anything to do with my hardware because im runing an athlon2600xp, 512ddr333, on a 64meg gf4 (which im upgrading to a fx next week). can anyone please tell me what the hell is wrong and what im supose to do to make vegas export at a half decent rate ?
-
- Joined: Wed May 16, 2001 11:20 pm
For comparison, I just rendered most of my current (Vegas 4) project. It's a simple romance vid, so it's mostly long clips with slow crossfades, some speed adjustment, and some panning. There's an 11 second dream sequence with b&w and light ray effects...this takes almost half the total rendering time.
So, for three minutes of timeline, it took about 11 minutes to render, or approx. 8-9 frames per second. This is typical in my experience. With many layered effects, less than 5 fps rendering would not surprise me. I'm using a 2.53 GHz P4, by the way.
Are you sure that Premiere is that much faster, or does it just seem that way due to the pre-rendering that is done during editing? (I'm guessing here; I have some, but very little experience with Premiere).
So, for three minutes of timeline, it took about 11 minutes to render, or approx. 8-9 frames per second. This is typical in my experience. With many layered effects, less than 5 fps rendering would not surprise me. I'm using a 2.53 GHz P4, by the way.
Are you sure that Premiere is that much faster, or does it just seem that way due to the pre-rendering that is done during editing? (I'm guessing here; I have some, but very little experience with Premiere).
- bum
- 17747114553
- Joined: Sat Nov 08, 2003 9:56 pm
-
- Village Idiot
- Joined: Fri May 03, 2002 12:17 am
- Location: Denver, CO Banned: Several times!
- Contact:
-
- Joined: Wed May 16, 2001 11:20 pm
I repeated the render that I described above as a "28.8 Kbps" WMV8 file. It took two minutes for the whole stretch...about 45 rendered frames per second. The result looked and sounded like junk.
I did it again as a "256 Kbps" WMV8: took 6.5 minutes, or 14 rendered frames per second. This file actually looks nice, but still not quite as good as DV.
I'm not sure what else I can tell you. Looks like you have enough RAM. What about spare hard disk space? (And de-fragged?)
I did it again as a "256 Kbps" WMV8: took 6.5 minutes, or 14 rendered frames per second. This file actually looks nice, but still not quite as good as DV.
I'm not sure what else I can tell you. Looks like you have enough RAM. What about spare hard disk space? (And de-fragged?)
- King_Cold
- Joined: Tue Dec 10, 2002 9:43 pm
Sorry about the other time. I kinda misunderstand stuff at 3 am.
Well, when I wanna preview my work I render it with PICVideo Lossless JPEG Codec at quality draft, and my audio pcm uncomporessed or mpeg-layer3. For example, it took me ~24 minutes to render a 6min AMV with those settings. You do need more hd space for this. With this example the file size of my rendered file was 1.72gig.
I found that this was the fastest way.
And I also found that any effects wish uses transparency slows down the rendering drastically.
Well, when I wanna preview my work I render it with PICVideo Lossless JPEG Codec at quality draft, and my audio pcm uncomporessed or mpeg-layer3. For example, it took me ~24 minutes to render a 6min AMV with those settings. You do need more hd space for this. With this example the file size of my rendered file was 1.72gig.
I found that this was the fastest way.
And I also found that any effects wish uses transparency slows down the rendering drastically.
If you think about what you tought you knew then you know what you think you thought you knew but you think you don't and If you think about what you thought you knew, then you think you don't know what you thought you knew but you do.
Think about it! If you can't understand my sig, don't you say nothing about my spelling!
Think about it! If you can't understand my sig, don't you say nothing about my spelling!
- King_Cold
- Joined: Tue Dec 10, 2002 9:43 pm
Sorry about the other time. I kinda misunderstand stuff at 3 am.
Well, when I wanna preview my work I render it with PICVideo Lossless JPEG Codec at quality draft, and my audio pcm uncomporessed or mpeg-layer3. For example, it took me ~24 minutes to render a 6min AMV with those settings. You do need more hd space for this. With this example the file size of my rendered file was 1.72gig.
I found that this was the fastest way.
And I also found that any effects wish uses transparency slows down the rendering drastically.
Well, when I wanna preview my work I render it with PICVideo Lossless JPEG Codec at quality draft, and my audio pcm uncomporessed or mpeg-layer3. For example, it took me ~24 minutes to render a 6min AMV with those settings. You do need more hd space for this. With this example the file size of my rendered file was 1.72gig.
I found that this was the fastest way.
And I also found that any effects wish uses transparency slows down the rendering drastically.
If you think about what you tought you knew then you know what you think you thought you knew but you think you don't and If you think about what you thought you knew, then you think you don't know what you thought you knew but you do.
Think about it! If you can't understand my sig, don't you say nothing about my spelling!
Think about it! If you can't understand my sig, don't you say nothing about my spelling!
- aznfs
- Joined: Fri Aug 23, 2002 11:22 pm