I also just completed a project using .mxf (converted using Clipbrowser) and it worked great until I started adding effects. I initially started the project in the last version of Vegas8, but rendering was slow and I knew that V9 had better compatability with the XDCAM EX format. I downloaded the trial, knowing that I would have to complete the entire DVD project in V9 (since the files are not backwards compatible).
Long story short, I discovered that V9c would give me a low memory error trying to render once it hit a time-stretched clip. Everything else was OK, but that particular clip caused the low memory error.
I also noticed that V9 creates multiple instances of itself in the task manager. I quit Vegas, but it remains an active process. If I start the program up again, it creates another instance.

My system is a 3Ghz quad-core running 32bit XP Pro XP3 with 4GB DDR2 800 memory and a 1TB raid 0 work drive (only 300GB on it currently).

I also noticed that Magic Bullet HD plug in (the one that comes with Vegas) only uses a single processor while rendering.

Not to hijack the thread, but would my rendering issues continue if I jumped to 64bit? I am tryingto render out a 2.5 hour show to widescreen DVD NTSC format, and I had to split it into 32 sections to get it to work. I then reassemble those clips into one long clip and re-render again - this is super quick as no re-compression is required. It is just a PAIN to get the 5.1 surround mix to line up and basically took WAY too long to make it work.

Andrew, I'd love to try and help find out what causes these memory issues.

I'm using quite a bit slower machine than you, (2.66 Ghz Core2Duo with 2 Gig RAM, XP Pro SP2), and although I occasionally get low memory messages while EDITING - and closing and reopening V9.0c (32bit) solves this - I never get problems while RENDERING.

I'm also using XDCam EX MXF files, often with projects 2 hours or so long, and with occasional time stretched clips.

I haven't dabbled with 5.1 surround, but I doubt this is the cause.

I just hope the common factor for those with rendering problems emerges soon ...

I also wonder if my issues stems from the fact that I started the project in V8c and then began editing in V9c. We just delivered the DVD, so I have not really had the time to try to troubleshoot things like I would like. I hope to have more info on exactly WHEN this happens in a few days...

One thing is certain, I thought I had bad memory at first, because switching from Vegas to another program in memory (like Photoshop) used to be instant, but now can take up to 5 minutes! V8 still switches pretty quick, but V9 is horrible.

So, the few answers I received before being 'Jacked' say "MXF for NLE" seems to work best.

I've been seeing people talk about the loss of quality with MXF but I'm looking for a Less Taxing editing experience... so I guess I'll try MXF and see what it looks/feels like.

"I've been seeing people talk about the loss of quality with MXF but I'm looking for a Less Taxing editing experience... so I guess I'll try MXF and see what it looks/feels like."

I've read this thread three times. I cannot for the life of me figure out what the issue is. I've been shooting with an EX3 and editing with MXF files for over a year and not had one second's problem.

And what is this about "loss of quality"? What have you been reading, anyway?

BTW, what version of Vegas are you using?

"I've been seeing people talk about the loss of quality with MXF"

You're confusing two different things.
The camera record mpeg-2 inside a mp4 wrapper. The Clipbrowser gives you the option to rewrap it into MXF for NLE. No re-encoding is done so there can be no loss of image quality period.

Transcoding anything to a lossy codec will always involve some loss. This does not happen during a rewrap as explained above. Converting say AVCHD to MXF is a different discussion not to be confused with this one.

Bob.

As I read through this thread then looked again to see where I saw "MXF = Loss of Quality"... it was a totally different discussion as farss stated.

I'm running the latest version of Vegas Pro 32bit... but I also run Premiere Pro, FCP, & Avid, so I always shoot for a workflow that will work across the board.

I have been unable to kick out an MXF... then I did more research and found out that the Clip Browser does NOT support XP 64bit. It just freezes when I tell it to Export MXF.
- So I guess that means I'll have to wait to put this new flow into effect for comparison.... aaargh!

As far as I can tell there's no difference between putting the mp4 files straight from the camera on the timeline and rewrapping them via the Clipbrowser to MXF. Changing the wrapper is unlikely to make any difference in how well Vegas handles the footage as the vvideo stream itself is unchanged.
My only reason for exporting to MXF is to handle the split file joining problem and also so my footage is compatible with both V8 and V9.

Bob.

In Vegas 9.0, you can use the Device Explorer and pull the video files directly from the cards onto the timeline without having to use ClipBrowser to rewrap.

You're not going to find one file-type that works in all those NLEs across the board without some juggling. If that's what you want, you might try Avid's codec.

Spot recommends MXF 4.2.2 50 Mb for useability accross all NLE's.
There is a tutorial on the VASST site about this.
It will require conversion from the MXF obtained from Clip Browser which is 4.2.0 35 Mb but should have neglidible impact on quality and run smoothly on most NLE's.
FCP users need to install free plug-in to use MXF.
Lars, I think it was, did extensive testing on this format and compared it to Cineform for transparency.
Malcolm

"Spot recommends MXF 4.2.2 50 Mb for useability accross all NLE's."

That would require re-rendering all the footage! In many cases that could/would be unacceptable.

I think the OP was looking for a solution closer to the ingesting stage of the work flow.

Agreed but more to the point in this case you're transcoding 4:2:0 mpeg-2 at 35Mbps to 4:2:2 mpeg-2 at 50Mbps. Quality will take a small hit as you're recompressing into a lossy codec and playability will decrease due to the higher datarate. Both are using the same codec with the same GOP. It's a loose/loose idea.
As for interopatibility I'd hazard a pretty safe bet that any system that can play XDCAM 422 will also play XDCAM EX. The reverse may not hold true.

Bob.

transcoding 4:2:0 mpeg-2 at 35Mbps to 4:2:2 mpeg-2 at 50Mbps

This sounds like it's going the opposite direction than I'd like to go.
Although I do some 'Cuts Only' pieces, my projects are usually lots of Compositing of Graphics & Layers, Transitions, & Effects. Because of this, I sometimes edit 'Blindly' with the video layers OFF and rely on the Audio for my cues. I then go back over it bit by bit to scoot things a few frames to get them where they should be. Just wish I could edit WYSIWYG without the Stutters & Dropped Frames.

I loved DV because I could stack layer upon layer upon layer... but now with our need for HD and having an EX1, the editing experience is nowhere near as smooth as I'd like for it to be.

Maybe I'll just have to invest in a Super Computer... that will be over priced and obsolete shortly.