Thanks for the info.... the scripts work perfectly under Vegas 5.0d (build 194) though, so it must be something that happened after. I will check it into more details as soon as I have time though - maybe it helps if those who use Vegas 6 and use scripts including AdjustStartLength (to move clips forward and backward in the timeline) verify those still work with events that are not already adjusted to the start or end of the underlying video stream? I observe the problem with all my scripts (removeleft, sortevents, etc).

I will definitely try to add the "evnt.Start=evnt.Start-DeleteFrames" line in my script and report asap.

You're perfectly right... it seems AdjustStartLength works precisely as you described in pre-4.0d (sorry my prior posting. I misread "4.0d" as "5.0d" - I didn't expect Sony to fall back THAT far :-). This can be verified by the following short script that should adjust all events to the cursor position:

import System.Windows.Forms;

import Sony.Vegas;



try {

  for (var track in Vegas.Project.Tracks) {

    for (var evnt in track.Events) {

    	// evnt.Start=Vegas.Cursor;

      evnt.AdjustStartLength(Vegas.Cursor, evnt.Length, true);

    }

  }

} catch (e) {MessageBox.Show(e);}

This only works if you uncomment the commented line - otherwise the events are just moved above a fix video stream (so the offsets are then wrong). This is not as documented though, and definitely a bug. It means all scripts for Vegas 5 using AdjustStartLength no longer work. What should we do in our scripts now...? Can we expect this to be fixed soon, or do we need to add version checks for all out scripts? Any comments from Sony about this?

If you have a minute to spare, you ought to click on the Support button at the top of this page, and use the Email option to send this in as a bug report. I'd sure rather that they fix this to work like it did before, because I have quite a few scripts that will be broken if what you say is true.

Will that be corrected really?

This error blows up some important scripts, for me deleteUpToCursor and DeleteAfterCursor.

SONY, please be so kind and let us know!

I put a work-around in version 4.2 of Excalibur just because of this program. I know Sony is aware of the issue but cannot comment on when it might be resolved.

To work around the problem you simply need to adjust the Take Offset to the correct value.

Is this related to the fadeout problem I reported in the thread I started a few days ago? No one came up with any clue as to how to resolve that.

@ jetdv,

thank you for that hint - I have been able to modify the scripts, still based on a script of John.

Download for Vegas6b here:

scripts delete to/up cursor

It's really annoying having to fox such things at every version... don't forget to add an explicit version check for each AdjuststartLength, becaus eI assume it will be the other way around again in one of the next releases. I didn't include the "corrections" in my scripts yet because I don't feel like having zig versions of each script for each subversion of Vegas. I hoped the bug will be removed in 6.0b (I did report this problem to Sony several weeks ago, and they acked it) - obviously I was wrong with this hope which is pretty sad.

I agree fully - it is boring. I have also forewarded that "bug" or "change" to Sony - no answer yet. I would have liked to see this problem changed back to the old behaviour of AdjustStartLength, too.

However, I think there is no other way then to keep different versions ready. So, if the old version will work again with V6c, then we will use the old versions of the scripts again.

But Sony: this is not very professional, sorry to say so. And I love Vegas because it is a professional tool.

With the workaround I mentioned, it doesn't matter how the command works. One way it will be corrected. The other way, it will simply make no change.