I have updated within a few days since VideoFactory 2.0. Jeez, never a problem. XP Pro, AMD, yadda, yadda, yadda. Goin' to Vista shortly. Darryl

No problems with the latest version on my end. One of the machines I run it on is a dual quad core, so that may help settle down some of the forum users who are concerned about Vegas balking on that type of machine.

hey mooney, do me a favour, can u run the latest rendertest?
Would love to see results and your spec

A Dual QUAD? Is that 8 operating cores?

Well, I downloaded and installed the 8.0b update last night. Then I tried capturing some HDV footage from my Canon XH-A1. I found that every clip ended up with somewhere between 3 and 6 bad frames at the end of the clip. Typically there would be a couple of frames that looked the first frame of the next clip, along with a frame or 2 that would be sort of messed up looking - like part of one frame overlaid on top of another frame.

I am able to trim the bad frames off the end of each captured clip, and outside of that, everything else seems to be working fine, so far. So it's not a complete disaster.

Has anyone else experienced this problem?

Rick

http://www.Hogans-Systems.com

> Has anyone else experienced this problem?

Yes, this is a known problem that didn't get addressed in the 8.0b version. Hopefully it will some time in the future, but the stability of 8.0b is great and I'll take stability over function any day. As a workaround, you can turn off scene detection and just split the scenes yourself as you edit.

~jr

"A Dual QUAD? Is that 8 operating cores?"

Yes sir. I guess the new Penryn chips. Within a few percent of double the speed of a single quad on tasks that use all the cores, like the DivX encoder benchmark.

Bob.

What motherboard? I am looking to upgrade my PC this spring, and 8 cores sounds cool.

Without a doubt, Vegas has a problem reading m2t files. Clips from my JVC HD110 import into Vegas with red frames on the timeline and black frames on the preview window. The dropped frames occur at clip boundaries, aka scene changes, that Vegas fails to detect in the m2t files.

Apparently, some camera manufacturers don't write the same EOF marker at the end of a clip that Sony cameras do. And vegas engineers are burying their heads in the sand over this issue. Whether intentional or not, I'll leave to conspiracy theorists to sort out.

Fortunately, third party converters like Cineform conversion correctly detects the scene changes and creates a seperate clip when it builds the intermediate file. CFHD has saved my bacon more than once.

hey Bill have u tried HDV split then importing to Vegas?

Im yet to ditch MPG editing in V7.. in fact its the only format i edit in at this time.. buts the V7...

I think ill wait til 8e... LOL

DJ..

haven't tried HDV split 'cuz HDLINK is working fine for me. I prefer working with CF Intermediates, anyway.