"I still get a hickup when I go through a simple crossfade, which is really lame considering I'm editing on a 6 core CPU with 16 GB of RAM."

Then either you're doing something wrong or you're actually NOT dealing with avchd. I'm running a Q6600 quad, 6 gig ram, GTX285 vid card and avchd is now rock solid for me. No flinching what so ever on cross fades (video set on preview auto). I can even run a lot of the basic filters PLUS a cross fade with no flinching at all

But then I have always had this suspicion that there is something wrong with that machine of yours given the never ending list of problems you have with it.

First you ask a question that no one can really answer and then use the rest of your post to slam Vegas. Interesting.

But then I have always had this suspicion that there is something wrong with that machine of yours given the never ending list of problems you have with it.

Of course, Rob, it is my machine that is to blame for everything that is bad in the world, including wars, hunger, dictatorships, the BP spill and oh, even the miners trapped in Chile. Their rescue, by the way, had nothing to do with my computer.

First you ask a question that no one can really answer and then use the rest of your post to slam Vegas. Interesting.

Of course, John, my sole mission in life is to post questions that are impossible to answer and slam Vegas. That's why I keep buying version after version of me. Man, I must be quite an idiot!

"Man, I must be quite an idiot! "

Well I won't comment on that one.... but back to the issue at hand....

If I'm seeing completely solid playback and you're not then logically speaking there is something amiss with your workflow... or your machine. Either that or MY whacked workflow is some how freakishly causing Vegas to make a mistake and react properly.

Now which do you think is the more likely of the 2 scenarios?

Now..... are you actually asking for help on this issue.... or are you here to whine and complain as you usually do.

>If I'm seeing completely solid playback and you're not then logically speaking there is something amiss with your workflow

Or it could depend on what AVCHD you are editing. From Wikipedia:

"Panasonic AVCHD camcorders use AVC with High Profile @ Level 4.0 for all modes except 1080p50/1080p60, which are encoded with High Profile @ Level 4.2. Maximum data rate is limited to 24 Mbit/s for AVCCAM models, to 17 Mbit/s for most consumer models and to 28 Mbit/s for 1080p50/1080p60 recording modes."

I believe some of the consumer AVCHD is at an even lower bit rate. I assume the higher bit rate AVCHD is more difficult to edit.

/jerry

Now..... are you actually asking for help on this issue.... or are you here to whine and complain as you usually do.

Neither. You wouldn't ask that if you had properly read my post, especially the title. In case it wasn't obvious enough, I was asking if anybody had any information on whether Sony was working on bringing more CUDA features into Vegas, especially filters and transitions. Now if I have to dumb it down more than that, I really wouldn't know how to.

", I was asking if anybody had any information on whether Sony was working on bringing more CUDA features into Vegas, "

Since when has that information been available to the general public.... and for any of those who do know, they have all signed NDA's so they can't talk about it anyway. Now I suppose we can all stand back and take a wild stab-in-the-dark guess if you wish.... but then I would say that my crystal ball is about as good as yours is.

Any other (reasonably intelligent) questions?

"Or it could depend on what AVCHD you are editing."

Which is why I mentioned this in my above post:
"Then either you're doing something wrong or you're actually NOT dealing with avchd."

Many seem to think that the new pany 1o80p60 cams shoot avchd. They don't. What they shoot is not compliant to avchd.

A quote from Wiki:
"While this mode is not compliant with current AVCHD specification,...."

Any other (reasonably intelligent) questions?

Rob, I could answer to your lame attempts to pick a fight, but the truth is I'm tired of the idiots in this forum that constantly try to throw dirt in my face when I ask a simple question. Not to say that there are also some constructive and nice people in this forum, but obviously you're not one of them. So I'd rather not waste my time with you.

"I'm tired of the idiots in this forum that constantly try to throw dirt in my face when I ask a simple question."


Well first please allow me to point out that the term "idiot" is a personal attack on a person(s) which is not allowed in this forum.
Second;
Lame attempt to pick a fight??? How about lame question to begin with?

Rob, like I said, I'm not wasting my time with you.

Now, if anybody else has read or heard if Sony plans on implementing more CUDA features on Vegas, please feel free to comment. Of course beta testers can't break their NDAs, but maybe SCS announced something that I missed.

The Genarts Sapphire OFX plugins are compatible with Vegas 10 and are evidently capable of using an NVIDIA GPU. I didn't see the word "CUDA on the page I was looking at, though.

Sapphire is very, very expensive to buy but you can rent it by the month if you like.

Rob

[i]>Which is why I mentioned this in my above post:
"Then either you're doing something wrong or you're actually NOT dealing with avchd."

Many seem to think that the new pany 1o80p60 cams shoot avchd. They don't. What they shoot is not compliant to avchd.[/ii]

Rob, I believe there is plenty of room for render differences within the various quality levels of compliant AVCHD. For example, Panasonic compliant AVCHD ranges from 21 Mbps to 6 Mbps:

PH 21 Mbps (VBR)
HA 17 Mbps (VBR)
HF 13 Mbps (CBR)
HG 13 Mbps (VBR)
HN 9 Mbps (VBR)
HE 6 Mbps (VBR)

/jerry

"Rob, I believe there is plenty of room for render differences within the various quality levels of compliant AVCHD. For example, Panasonic compliant AVCHD ranges from 21 Mbps to 6 Mbps:"

That's correct. In fact avchd goes all the way to 24Mb/s.... which is what I use to test with.

Take out the insults and this is actually an interesting thread.

Boris BCC7 is extremely cool and makes use of graphics abilities only found in the current version of Vegas. Things like motion tracking were not available to developers until now. I expect that most of the candy will come from 3rd party developers, but the core ability that these developers will be exploiting is what we can thank Sony for.

The combination of this framework and Vegas's scripting capabilities is likely to mean that we are going to be able to get our hands on some pretty amazing tools in the near future.

Sebaz, I noted earlier in Post #63 that I contacted Sony Vegas tech support to inquire about the lack of GPU acceleration noted in my render tests and the lady seemed somewhat puzzled by it but acknowledged my issue and passed it on to the developers. She also mentioned that Sony engineers are dedicated to achieving proper GPU utilization and that we'll see more benefits over the upcoming updates/versions. Perhaps you might want to call them also.

I am seeing very little improvement in render times with Vegas Pro 10, 64 bit with my GTX260 video card when GPU acceleration is enabled, with GPU loads below 10%. I just did a test with Premiere Pro CS5 with AVCHD PIP (four scaled PIPs). With GPU it took 2min10secs to render out to AVCHD, with GPU disabled it took 7min40sec. GPU loads between 60-90%. It would be nice to see something like this in Vegas.

I must say, the last three posts are more the kind of conversation I was looking for when I started this thread rather than dumb and nonconstructive things like:

But then I have always had this suspicion that there is something wrong with that machine of yours given the never ending list of problems you have with it.

or

First you ask a question that no one can really answer and then use the rest of your post to slam Vegas. Interesting.

or

If I'm seeing completely solid playback and you're not then logically speaking there is something amiss with your workflow... or your machine. Either that or MY whacked workflow is some how freakishly causing Vegas to make a mistake and react properly.

or

Any other (reasonably intelligent) questions?

Some people here should read that Netiquette on this forum sticky.