[Tyson Onaga]

sorry, kelly … brain cramp … it is Alt-6 (View->Edit Details) …

[Tyson Onaga]

I have never seen Vegas “lose” an event like this. Something must be modifying the underlying file that the .veg file is referencing. For an exhaustive list:

1. open your “good” .veg
2. press alt-F6
3. from drop list, pick Show Events
4. click the top left corner (select all)
5. ctrl-c
6. open excel
7. ctrl-v
8. in excel, Format->Column->Auto Fit Selection

You can repeat the process for the “bad” .veg file but put the data into a different worksheet.

For those bad events, find the event by searching in good worksheet based on Track (col A), Active Take Name (col F), Take Start (col G). Take note of the File Path (col J).

Now find the exact same event in the “bad” worksheet.

If the File Paths are the same, then something is happening to that file(s) between your Vegas File Close and File (re)Open.

[Tyson Onaga]

Foo comes from Foobar (fubar) … is the project name. E.g., Project_v#

which would be used:
Project_v1.veg: A X(1)
Project_v2.veg: B X(2)
Project_v3.veg: C X(3)
Project_v4.veg: D X(4)

1. Create X(base).veg

for each Project_v#.veg:
2. Copy X(base).veg to X(?).veg [or whatever naming schema you’d like)

3. Edit X(?).veg

4. Create Project_v#.veg [or copy it from prior version]

5. Edit Project_v#.veg

6. Nest (insert) X(?).veg into Project_v#.veg

If all X(?).veg are the same length [or more accurately, swappable…] then
7. Add successive X(?).veg into Project_v#.veg as Takes
Drag it to the Media Pool, select it, R-Click and drag it on top of the desired
media, select Add as Takes from the popup menu.

To switch between Takes:
a. R-Click to select the media
b. from the popup menu choose Take
c. and then the Take you want

—–

You’ll have a Project_V#.veg files for each major variation (A, B, C, D, …)
Each Project_v#.veg file will have 1 (or more) variations of the ending X(?).veg nested within.

[Tyson Onaga]

Sounds like you want .veg files like this:

Foo1.veg: A X(1)
Foo2.veg: B X(2)
Foo3.veg: C X(3)
Foo4.veg: D X(4)
…

where A, B, C, D are different and X(n) are variations of X. I’d start with X and save it (your “base” version). For each Foo?.veg, make a copy of X and name it accordingly [X(?).veg]. Make your changes and nest that version into Foo?.veg.

You could probably “Add as Takes” various X(?).veg into each Foo?.veg to see how the variations would play out.

[Tyson Onaga]

That “polished” sound is probably done with stuff like this:
https://www.tcelectronic.com/powercore.asp

or stuff like it … which is why it is probably a great idea to follow Mike’s advice.

[Tyson Onaga]

720 x 486 = 1.48
640 x 480 = 1.33

Have you tried creating a 640 x 480 project, nesting the 720 project inside of it, and putting a 1.48 pan/crop event at the beginning, and then render?

[Tyson Onaga]

Found the issue. Apparently, if you start with a blank unsaved workspace, you can’t Render As without getting that error. I was trying to do a quick audio edit and dropped a wav file into a blank project. Render As always gives the error. If I open a “blank” saved project and do the audio edit there (don’t save it) the error doesn’t happen.

[Tyson Onaga]

It doesn’t matter what the file name is. I tried everything from long file names to foobar. Even Untitled doesn’t work. And this happens sporadically and I have no idea why. I can’t find a pattern that reproduces it either. Shutting down and restarting Vegas mostly works.

It is just !@)!*(_*( bloody annoying.

[Tyson Onaga]

How many tracks to you have? You could try:

a. render Track 1 to QuickTime Animation
b. render Track 2 to QuickTime Animation
c. create new project with matching properties
d. insert renderA to Track 1; turn on Alpha channel
e. insert renderB to Track 2; turn on Alpha channel
f. render to your desired target

Expand process for additional tracks.

g. delete those pesky little .mov files when you’re done

[Tyson Onaga]

Thanks John. I had tried Color Balance but couldn’t get the colors to match exactly. Color Balance uses values -0.500 to 0.500 so I was using Excel to convert RGB 0…255 values but they didn’t match up. Sepia on the other hand, seems to work nicely.