Hmm, it looks like it is enabled. I guess from your comment that if it is on, then it must need to be off instead. Is that correct? Do I need to turn it off? But for the life of me, I'm not sure how I was supposed to know that. Is this behavior of MB documented somewhere?

And will turning it off automatically fix everything, or do I then need to go back and realign every clip?

To me as a first time user of MB, it would have been nice to have a popup telling me quantize is on and unusable results are going to happen. I can't believe anybody would WANT the result I got. Even if there's an explanation for why it does what it does, getting a little info from the plugin to avoid this would have been nice.

Thanks for the pointer.

quantize on means that all your cuts/movements are on a per-frame basis. that's good for video editing.

i've never encountered that "bug" before. sure there's not fades/overlapping at the start of the clips? that's what it's sounding like.

EDIT: How did you apply MB? On the event, media, track or project level?

Quantize to Frame should be enabled for video editing. I did not mean to confuse you.

Dave T2

In this case, I am applying MB at the clip level on all clips. I tried playing with it with quantize on and off. Quantize off actually made it worse.

I can guarantee there are no explicit fades on the clips. This was a completed project that I went back and retrofitted with MB to enhance the look. Simply adding the MB filter to the clips created this situation.

The key point is the failure ONLY occurs when "Clip = Media". In other words, the clip starts at frame 1 of the media. If I trim a frame off the front of the clip (i.e. clip starts now at frame 2 of the media or in a couple of cases, frame 3), then the problem goes away.

It definitely 'looks' like a fade. But I'm not doing it... Sometimes frame 1 is completely black. But in most cases frame 1 is a partial black-fade (you can see the picture, but it's almost black).

To me, this is definitely a bug (I'm a software architect/programmer for my day job). I guess it's probably not that prevalent since most people either apply MB at the track level and/or don't start many clips at frame 1 of the media. As I mentioned yesterday, the only reason this is so prevalent in this project is that it was a completed project, and I had trimmed all the media to equal the clips. Hence every clip starts at frame 1 of it's respective media file. Knowing this bug exists, I can work around it in the future. But it would be nice if it could get fixed.

Thx.

are you only using the 320x240 preview window for reference?

Why not just apply the MB FX to the track or project? Did you try rendering the whole project to a new track & applying to the new track media?

This is not a preview issue. I rendered the project to an AVI file and get black frames in the avi file. When I spread out the timeline to see every frame in the clip, the first frame is black. And when I single step frames left/right across the transition, I get a black preview window (and while sitting on a black frame, enabling/disabling the clip effect toggles the frame between black and 'correct'. I can't think of any possible way this is anything other than a bug in MB.

Every clip has a different MB style. Granted, I could put the MB at the track level and use HOLD keyframes to change the style on each clip. But that's a royal pain.

Basically, I've already found a workaround. But in either case, in my programming job, when a bug is found in my code, I fix it. I don't expect the customer to be satisfied simply because they figured out some convoluted painful workaround. This is a bug. It needs to be fixed.

Thx.