[Kurt Zaiser]

Sigh.

Got the latest MBSuite trial (version 11) and same thing happens – as soon as I check “Dust” or “Splotches”, individually or in combination with other MisFire sub-effects, the render fails after a few dozen frames.

Even updated to the current ATI drivers a few weeks ago when I upgraded to Vista Ultimate to use all 20GB.

Oh, well. 11 out of 13 ain’t bad. If anyone has any ideas (maybe it’s my graphics card?), please let me know.

Thanks.

[Kurt Zaiser]

Just tried rendering an uncompressed AVI with only Misfire applied. Checked the heavy/noisy sub-effects and get the same result – render fails after a few seconds.

Also dusted off CS3 – MisFire renders fine with seeing only 4GB of RAM. So, seems like MB 1.4 and CS5 don’t play nice together. Must be an x64 vs x86 thing. Not surprising, I suppose, given the time between their release dates.

I guess I’ll have to try the latest MB trial version and see if that helps. I stopped updating after AE 10.0.1 because everything was just the way I wanted it (until I tried using MisFire recently).

Back to the trenches…

[Kurt Zaiser]

Thanks Dave.

Sorry I didn’t mention the version (it’s listed in my profile). I’m using CS5x64. I am using MB suite but it’s 1.4 – maybe that’s the trouble. Perhaps I should trial the latest version. Should have thought of that before posting. I’ll also try a lossless version of the input video and see if that helps – thanks for the idea.

Regarding OpenGL, I have read plenty of posts from Todd so I always have OpenGL off.

[Kurt Zaiser]

John, thank you for trying to help. I’ve been reading this forum for four years and you’re always jumping in to help others.

On my prior, 32-bit PC, I was using 8.0c (that’s what I was basing my recollection upon). I only installed 8.0a on my 64-bit machine in order to update to 8.1. Therefore, I can say with certainty that 8.0a and 8.0c behave the same in this regard.

Okay then, if I have masking or careful cropping/animating to do, it’s back to 8.0. Maybe I can still render the .veg using 8.1 hoping for the 64-bit rendering speed improvements, if any. I’m hesitant to upgrade to V9 only to discover the same issue exists there. I”ll ping SCS and see if they can offer any advice.

Thanks.

-Kurt

[Kurt Zaiser]

Well, this is getting more and more…um..interesting.

Just to verify my sanity, I fired up 8.0a and everything works perfectly. I started a new project, set the Project Settings by choosing some source footage from that camera [note, I DID have to set the PAR from 0.9091 to 1.212 but the field order was correct], dragged the source to the t/l and the footage appeared aspect-correct in both the Preview and Pan/Crop windows. I did NOT have to right click the footage and change any properties. Glad to know I wasn’t dreaming 😉

Repeated in 8.1 and everything ‘seems inverted’. By that I mean, I set the Project Settings from source footage selected same as with 8.0 [changing both PAR and field order from what Vegas gave me as default from examination of the footage file], dragged the footage to the t/l and it was pillar-barred (4:3, squished) in the Preview window BUT IT WAS 16:9 IN THE Pan/Crop Window! Next, I right-clicked the footage to change its Properties to PAR 1.212 and the window views switched: the Preview window now shows 16:9 (normal looking footage) and the Pan/Crop window shows squished, pillar-barred footage.

Is this a bug, operator error or bad carma?

-Kurt

[Kurt Zaiser]

John, the Everio model is GZ-MS100RUS – a small, flash-only unit. When I get home tonight, I’ll try a new project and follow your advice before dropping footage. I DID try to ‘adjust aspect ratio to source’ as well as ‘…to output’ and that had no effect on the footage but did change the dashed outline of the Pan/Crop window ever so slightly.

If I do not set the PAR of the footage (by right-clicking Properties), the footage is quite clearly squished-n-pillar-barred in the Preview Window. The footage, if played directly on WMP or VLC, is widescreen. Hence, my need to change the PAR to 1.212 from 0.909.

I’m pretty sure I didn’t have this problem when I was using Vegas Pro 8.0b but that could just be my flakey memory. I’ve always had to adjust the PAR but I’m quite certain I’ve not had a subsequent Pan/Crop viewing problem after doing so.

Thanks for helping. I’ll post tonight…

-Kurt

[Kurt Zaiser]

Kevin, that worked! Thank you so very much. MPEG-2 -> AVI via Vegas Pro and back into AE.

-Kurt

[Kurt Zaiser]

Try renaming your MPEG2 file extension to ‘.vob’ and then drag ’em in. I had the same problem with my JVC .mod files.

-Kurt

[Kurt Zaiser]

Thanks Steve.

Just after I posted, I searched Sony’s Vegas forum and found a thread that mentioned the .vob trick. I’ve been using the trial version and almost punted on the product. In all other aspects, I like the software and will probably purchase the real deal… Let’s see how my first rendering job turns out.

Thanks again for the fast reply, Steve.

-Kurt

[Kurt Zaiser]

Hi folks.

I just began using V8 and find myself in the same predicament – my camcorder MPEG-2 files play fine on the PC via Windows Media Player and in Roxio’s MyDVD NLE but V8 drops the associated audio. Have you been able to drag in other files successfully or do you have to first open them in V7 (which I do not have)? I’ll re-read the instructional tomb again and see if anything jumps out at me but it seems that if V7 did this without issue, then V8 has a bug.

Note:
When I look at the properties, the file is a MainConcepts MPEG-2 and this does not seem to support an associated audio track. When I try to render projects as MC MPEG-2, the audio I add to any tracks is dropped from the output.

Thanks.

-Kurt