Comments

JohnnyRoy wrote on 4/9/2003, 8:29 AM
This has been discussed before. The problem is that its difficult to determine when you’re reaching the 9GB limit because an uncompressed AVI file will reach it much faster that one that uses a codec like DV, and a compressed DV AVI file will reach the 9GB limit faster than an MPEG render would. So there is no way in the script to tell when you will reach 9GB to determine how big a section should be to render.

What you might be able to do is write a script that renders a certain amount of time for a particular output type. So if you know that 40 minutes of DV AVI is approximately a 9GB render, then you could write a script that rendered 40-minute chunks when using DV AVI.

I don’t know if such a script exists. I was thinking of trying to set up a rendering grid and so I would have to write a script that splits a project into sections to parse out to several rendering machines on the grid. This would be very similar. Unfortunately, I don’t have time this week to write it as I’m rehearsing for a gig this weekend (I’m a musician) for a Japanese TV pilot and I’ve got a lot of songs to learn between now and then. I could try to write something like this time renderer next week when I have more time. (sorry)

~jr
jetdv wrote on 4/9/2003, 11:02 AM
Try this script and adjust it for whatever length of time you want:

Render Segments
cobalt wrote on 4/9/2003, 3:54 PM
May I suggest you go back and modify the documentation for this script?

// here are some default variables for the GUI.
var defaultBasePath = "d:\\renders\\";

what are the double slashes for? is this a variable thing in the script? Can i change it to:
var defaultBasePath = "v:\hale\";
or does it need to be?
var defaultBasePath = "v:\hale";
does the directory need to exist already?

I am very glad that there is scripting available, but PLEASE remember that it's editors that are using these scripts, not programmers.

var renderLength = new Timecode(4000 * 60); // 4 minutes???

These numbers mean absolutely nothing to me.
4000 whats? multiplied by 60 whats? divided by 4 minutes ? are those 4 minute chunks?

Thanks for providing scripts in the first place. I'm not complaining just saying that all these scripts if they are to be modified internally should be well documented.

have a nice day!
jetdv wrote on 4/9/2003, 4:12 PM
When specifying a subdirectory path, (like c:\mydir\) you have to use double slashes such as variable = "c:\\mydir\\"

Yes, the directory must exist.

1000 ms = 1 second so 4000 ms = 4 seconds so 4000 * 60 = 4 minutes.

(or 1000 * 60 = 1 minute * 4 = 4 minutes)

Does this help?
cobalt wrote on 4/11/2003, 1:27 AM
Yea, thats perfect, but maybe you could put that into the script itself?

Every programmer making scripts should take those 4 lines as an example of what to include with thier scripts as built in help.

The reason I hate scripts in general is the lack of documentation within the script for editors. Keep in mind I downloaded this script, having never seen a Vegas Script before and then having to go all over the place to figure out what double slashes mean. This script isn't crucial for me so I just waited a day or two til the reply came in, but if it was crucial I would've been spending valuable time deciphering scripts.

If you want scripting to really take off you must take that last step of creating good documentation and a sample, otherwise most editors will just keep chugging along with what they know works.

Thanks for the response!
jetdv wrote on 4/11/2003, 2:02 PM
Since it was my script, I have made those changes. It can be downloaded from the same location as before.

BTW, 00:04:00:00 could also be used to indicate 4 minutes (timecode)
cobalt wrote on 4/13/2003, 8:32 AM
Thats perfect.

I hope that all scripts created for vegas will have proper documentation, especially for variables that need / can be changed by editors.
roger_74 wrote on 4/13/2003, 12:33 PM
There seems to be a problem with this script. You will loose at least one frame on each cut.
jetdv wrote on 4/13/2003, 4:15 PM
Roger, I thought the same thing but the 1 frame difference was added by SonicPJM.
roger_74 wrote on 4/13/2003, 6:16 PM
This is tricky business. I was thinking of making a general splitter to be included in a script I'm making, but all the different formats make it complicated.

I tried rendering a ten second clip and used your script to make four segments (renderLength = 3000 ms). Add the rendered segments to the timeline and the difference is obvious.

However, if I remove renderStart++ and instead add 3ms and renderLength - 1 frame, then the sync is perfect.

I guess this is due to the nature of video and different framerates. You need to split at intervals that are suitable to the framerate you're using.
jetdv wrote on 4/13/2003, 8:48 PM
renderStart++ has been commented out.