set VEGAS MPG2 as PROCODER 2

M

MOJE

Member
Hi,

I us a PROCODER. Procoder is BETER as VEGAS MPG2. Do You set VEGAS MPG2 as PROCODER 2 ???

VEGAS MPG2 is BETER in COLOUR and PROCODER is BETER in VBR as VEGAS VBR.

ANY KEY FRAME .....


THANKS
 
I'm not sure if I quite understand either, but if you're wanting to render your MPEG-2 videos using Procoder, then you would simply need to render your Vegas project to an AVI file (DV or uncompressed depending on the source material and post-processing you've done) and use procoder to encode the video.

You can also use Satish's Frameserver to send video from a Vegas project and open it in Procoder and encode it.

If you're asking how to use procoder to encode your Vegas projects from WITHIN Vegas, then that is not possible as Procoder is essentially a separate program, whereas Vegas needs codecs to encode video/audio.
 
Well, if you're rendering for DVD and using DVD Architect, all of this is moot. You should render from Vegas with a DVD Architect MPEG-2 template.

If you don't -- if you drop a Procoder MPEG-2 into DVD Architect -- DVD Architect is going to re-render the video into DVD Architect-compliance anyway, so you will have wasted your time.
 
David Jimerson said:
if you drop a Procoder MPEG-2 into DVD Architect -- DVD Architect is going to re-render the video into DVD Architect-compliance anyway, so you will have wasted your time.
Click to expand...

Is that true? My jaw is on floor. Surely DVDA is source agnostic as long as the file is MPEG-2 and it fits the available space?

I recently completed a very large project completely rendered in Procoder 2 (way better than the on-board Mainconcept) and DVDA3 did not re-encode a second of it.
 
While DVDA doesn't take just any MPEG-2 file, it definitely accepts files rendered with other encoders without the need for recompression.

Based on the source file guidelines in DVDA's help file (filed under Using DVD Architect Software -> Before You Get Started: Preparing Your Files), your source files need to be encoded with certain characteristics to keep DVDA from recompressing them (Frame size, Max bitrate, etc.). On top of that, the source files must match the DVDA Project properties.

My own rendering tests have confirmed this. You can definitely encode to MPEG-2 without needing to use Mainconcept's DVD Architect MPEG-2 templates from within Vegas. These templates are there mostly to help users render a DVDA compliant MPEG-2 without any hassles.
 
You can encode from Procoder and MAKE it compliant with DVD Architect; I guess I was a little clumsy. Bottom line is, the further you get away from the specs, the more likely it is it'll have to rerender, and if MOJE is talking about bitrates, etc., he's probably going to be falling in that danger zone.
 
Whilst I'm pretty confused by Moje's post too...it's quite easy to frameserve from Vegas to Procoder, thus saving a render step for Procoder. There is a tutorial on Frameserving from Vegas on the VASST site. Substitute Nero for Procoder, and you're done. I've done this on several occasions. I disagree that Procoder is better, but hey...whatever ya wants to do. Cinemacraft is better, for certain, and there are a few others, but Vegas placed very, very high in an encoding shootout over on vcdhelp.com
 
David Jimerson said:
You can encode from Procoder and MAKE it compliant with DVD Architect; I guess I was a little clumsy. Bottom line is, the further you get away from the specs, the more likely it is it'll have to rerender, and if MOJE is talking about bitrates, etc., he's probably going to be falling in that danger zone.
Click to expand...

Hi David. I use Procoder files in DVD Architect all the time and they never have to be re-rendered at all. Procoder has DVD compliant presets so I doubt if there is any compatibility issue. Do you have any specific examples where DVDA has to MAKE a Procoder file compliant?

Richard Hunter
 
Hi David. Well, I don't quite understand what you mean when you say that DVDA will make the Procoder file DVD compliant. I thought that a file it is either compliant or non-compliant, and that a non-compliant file would simply get re-rendered. Can you clarify what "make compliant" means?

Also, you seem to be implying that Procoder files are "further away from the spec". In what way do they not meet the DVD spec? I've been using Procoder for years in the belief that the output files were DVD compliant, so I'm very interested in this. Thanks.

Richard
 
A DVD-compliant file is a DVD compliant file, but not all MPEG-2 files are DVD-compliant. The further away you get, when encoding an MPEG-2 file, from the DVD Architect template, the more chance there is DVDA will have to re-encode it.
 
Hi David. Yes, this part I understand, but first you mentioned that Procoder files had to be re-rendered, (which on my system they don't), and then you said that DVDA could MAKE Procoder files compliant. I'm just not sure exactly what you mean by that.

Of course it is possible to set up Procoder to produce an MPEG2 file that is not DVD compliant, but my experience using Procoder DVD presets (and elementary streams) is that no video rerendering in DVDA is necessary at all.

Richard
 
I can't speak for what David intended to say, but I interpreted what he said as meaning that Procoder could be used to create MPEG-2 files that are compliant with DVDA (as opposed to using DVDA to make Procoder-created files compliant somehow).

The only way DVDA will make a non-compliant MPEG-2 file compliant is by re-rendering it.

Bottom line IMHO is, if there's ever a question on whether an encoder can create a MPEG-2 file that will work in DVDA without re-encoding, just consult DVDA's help file, because it has all the specs needed for making a file compliant with DVDA.
 
That's right; you can use Procoder to do it. Like I said; I was clumsy. I was just trying to minimize the fallout from the obvious language barrier and give MOJE the simplest advice I could, which meant that in attempting to answer a question I wasn't sure I understood, I would be as non-specific as possible and give general advice that would work. (I, of course, didn't take into account that other people would be reading, too -- my bad.)

I don't think any of us are entirely sure what the original question was here, but it seemed to me that MOJE likes Procoder's MPEG-2 rendering better than Vegas's. He did not say DVD-compliant MPEG-2s, just MPEG-2s, singling out bitrate. This is an area where it's pretty easy to make a non-compliant MPEG-2. I only meant to say that getting away from the render template in Vegas runs the risk of having DVDA re-render, in which case, it's a waste of time. In other words, Vegas already has a DVD-A template; MOJE wants to use a different template with uncertain changes; there's a good chance it won't be compliant.
 
Haha, yeah! I still don't know what the question was!

It made sense to provide the simplest solution to his "question".

Just remember...we ARE listening (reading) :evil:
 
You must log in or register to reply here.
Back
Top