Velocity envelope bug ?!?

MikeCrash wrote on 2/12/2004, 11:28 PM
Project bottom field first, insert DV clip with bottom field first setting, set velocity envelope to -100% and you get jerky video - the field order when setting velocity env. to negative values need to be reversed. Can be done with setting upper field first on media, but this cannot be done when combining positive and negative values

Comments

Grazie wrote on 2/12/2004, 11:59 PM
MC - Read your post 3 times now, and I still can't get the meaning, could be me . .maybe others will . . could you put it another way, please?

Regards,

Grazie
MikeCrash wrote on 2/13/2004, 6:01 AM
OK, once again

1. Imagine you have typical project with field order - bottom field first
2. Insert DV clip with field order - bottom field first
3. Insert Velicoty envelope to this clip and set it to -100%, so it will play backwards at the same speed
4. Render the clip to MPEG-2 in DVD format and burn it to DVD

Now imagine the original video has fields ABCDEFGH....
The resulted video in DVD format has fields ....GHEFCDAB
But it should be ....HGFEDCBA

... so the two fileds from one frame are reversed and the video will play jerky
The field order must be reversed on negative velocity envelope values to play smooth
jetdv wrote on 2/13/2004, 6:50 AM
I believe Vegas automatically reverses the field order when using negative velocities. So, you should be getting HGFEDCBA.
Wolfgang S. wrote on 2/15/2004, 10:38 AM
Unfortunately, this bug ist well-known, and has been explored some time on www.vegasvideo.de/forum.

True, the field order must be reversed, when you go to a negative velocity. The best way to do so is to render the event to a new track, with an reversed field order uff; import this event again, correct the field order back to bff (for DV-avi), and apply now the velocity envelope with -100%.

Important: make sure that "blend" is activated in the project properties.

Comment: that has been tested with DV-PAL-avi videos.

Kr
Wolfgang

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

johnmeyer wrote on 2/15/2004, 9:24 PM
By odd coincidence, I happened to need to reverse some video today. I remembered that the last time I did it, I didn't like the results, so I searched the forum today, and found this current message.

Based on the input in this thread, I did some tests and confirmed that the Vegas 4.0d velocity envelopes definitely have a nasty field reversal bug.

Note: This bug, as the original poster noted, makes the velocity envelopes totally useless anytime you need to go between forward motion and reverse motion during the same event. If you only need reverse motion, then you can reverse the event fields and get a good render.

Here are the tests I performed.

I took some video that included a left/right pan and applied a -100% velocity envelope. I then rendered this video and previewed it on an NTSC monitor.

It looked horrible.

The fields were obviously reversed. I tried another render with Force Resample. No improvement.

I tried another render, and reversed the fields using the Custom button in the render dialog. No improvement.

I then clicked on the event, and reversed the fields there (i.e., I changed from "Lower Field First" to "Upper Field First." The video rendered correctly.

I also tried applying Supersampling of 2 to the unmodified event and was able to get pretty good quality. This may be the workaround for those that need to go forwards and backwards in the same event.

Sony, please put this on your list of things that need to be fixed in the next release.
Wolfgang S. wrote on 2/17/2004, 11:25 PM
John,

the solution has been posted two messages earlier - it is necessary to render the event with reversed field order to a new track; and then apply the velocity envelope with -x%. Then it works fine - but only if you have either "blend" or "interpolate" in the project properties activated.

Took us a while to figure that out in the German vegas-forum, especially that "blend"/"interpolate" is important here.
:-))

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

johnmeyer wrote on 2/18/2004, 12:22 AM
the solution has been posted two messages earlier - it is necessary to render the event with reversed field order to a new track; and then apply the velocity envelope with -x%. Then it works fine - but only if you have either "blend" or "interpolate" in the project properties activated

My "solution" was a little different: I simply reversed the field in the event, rather than in the render. That seemed to do the trick.
Wolfgang S. wrote on 2/18/2004, 9:41 PM
I think we tried to reverse the fieldorder too without prior rendering to a new file too, John. But as far as I remember it did not work - but I am not sure here. Will try it again...

****** John said:
I also tried applying Supersampling of 2 to the unmodified event and was able to get pretty good quality. This may be the workaround for those that need to go forwards and backwards in the same event.
******

Did you really use the same event, based on the same file on the harddisk? Only reversed the fieldorder and both directions worked within one event after going to UFF, without any errors? Or have you splitted the event in two events at the point where you changed the direction?

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

johnmeyer wrote on 2/19/2004, 9:14 AM
Did you really use the same event, based on the same file on the harddisk? Only reversed the fieldorder and both directions worked within one event after going to UFF, without any errors? Or have you splitted the event in two events at the point where you changed the direction?

I used one NTSC event, and did not reverse the event field order. I then applied a velocity envelope and added points that were both positive and negative (i.e., both forward and reverse motion). I then turned on the video bus and inserted supersampling and set it to 2. The result looked reasonably good. It certainly did not have the "jitter" that you get when the fields are reversed and the the camera pans side-to-side.
Wolfgang S. wrote on 2/21/2004, 10:24 AM
Yes, this works also with PAL in the same way. Supersampling is a workaround for this bug - also if you set it to 1 only. As John said, it works fine if you have both forward and reverse motion.

For reverse motion only - it works also find to set the velocity envelope to -100% and the event properties to UFF, and render it to LFF. However, that cannot be used if you reverse the motion direction within the event - even not, if a forward part is not included in the area of the event that is rendered.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems