Comments

xberk wrote on 12/23/2009, 10:03 PM
I'm using 9.0b 64bit and 8.0c .. Here's why. 9.0c cannot handle jpgs or pngs without problems... 9.0b 64bit does fine for me on SD but not so well on AVCHD. So I'm using 8.0c when using AVCHD and 9.0b 64bit when using SD. If you are not using still images and 9.0c 64bit is very good for AVCHD or SD. My two cents.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

PeterWright wrote on 12/23/2009, 10:39 PM
I think the decision may be based on what format video you work with.

I've been using 9.0c (OS 32bit XP) since the day it came out without problems.
I work with MXF files from EX1 cam.
farss wrote on 12/23/2009, 10:58 PM
I thought I was doing just fine too with V9.0c under XP 32 but now I've found I can reliably lock it up badly.

XDCAM footage on track 1.
HDV on track 2
Enable external monitor.
Use event pan/crop to H flip a short clip on track 1.
All good so far.
Now add a Bezier mask to clip.
It gets increasingly tardy as I add more keyframes and then goes over an event horizon. Preview render (the "....." thing) runs for a while then it stops, GUI fails to respond. Eventually have to drive a stake through it's heart to kill it.
Highly repeatable.
Anyways I'll just scrap my little creative notion and keep on cutting away.


Bob.
Grazie wrote on 12/23/2009, 11:03 PM
Bob? What do you have set aside for Build Ram Preview setup?

Grazie
farss wrote on 12/23/2009, 11:59 PM
512MB.
I checked because I usually have 1024MB.

Aside from this one issue I'm nearly two hours along the T/L without a problem, that's with external preview on all the time.

Bob.
Grazie wrote on 12/24/2009, 12:05 AM
Knock it back to 16mb. Remember my experience with ExtMon and BRPs? - I now have it set to 16mb and no more issues.

Grazie
farss wrote on 12/24/2009, 12:13 AM
Well I've made the issue go away by not adding a mask with lots of keyframes. Screwy thing was after I restored the project complete with all the keyframes I'd added it played out fine. It was the process of adjusting keyframes / nodes that caused the grief.
One thing that is interesting. Vegas of old would abort trying to render the current frame if you moved the cursor, now it doesn't. Maybe it's possible a queue is overflowing or some such and that's what brings it unstuck.

Bob.
Grazie wrote on 12/24/2009, 12:23 AM
> "Maybe it's possible a queue is overflowing . .

Reduce to 16mbs and just see.

- g
farss wrote on 12/24/2009, 1:30 AM
Didn't push it hard enough to make it crash but the problem in the command processing queue is still there. I can outrun Vegas updating the preview by many seconds.
I jog forward a few frames and the cursor doesn't move, tool selection does nothing and then blatt, the cursor has moved and the tool under the cursor has changed. This happens immediately I start adding keyframes to change the mask. Even if it didn't crash it's unusable, one would go bongers trying to live with a GUI that works like this. Even when things settle and Vegas has caught up with me the response time to changes to a node's handles is way too slow. It feels like I'm dragging a block of concrete through treacle.

I've done this same kind of thing with XDCAM footage in V8. V9.0c is a new world of pain. For this job I'll just keep it simple and get it out the door.

Bob.
othersteve wrote on 12/26/2009, 6:56 PM
Thanks for all the input thus far guys. As of now I have decided to give 9.0c 64-bit a shot. I will be attending CES in a couple of weeks and I hope it serves my needs well for some HD H.264 editing (9.0a did just fine last year at E3).

-Steve