[Josh Meredith]

Are they AVI DIVX files? I can play DIVX files on my computer, but when I tried to open one in Vegas, I got the same result you described in your first post.

[Josh Meredith]

Happens to me all the time! I swear my eyes are oblivious to mistakes during editing, but then I watch the freshly rendered file, and notice tons of abrupt edits and misspelled text. Then there are always newly discovered problems when I watch the first burned DVD.

I don’t think there is a shortcut built in to Vegas to help. But you can just fix the problem, render the fixed secion, and then create a new Vegas session, insert the original flawed render, and patch your fixed section into it. Then when you re-render that, it should go pretty fast because it is just one long file with very few edits and no plug-ins.

This works best when you’re rendering an uncompressed file like an AVI, but in a pinch, I’ve done it with MPG2’s, and the final product looked fine.

[Josh Meredith]

The nice thing is Vegas should run like a champ on nearly any modern system. I just got a mid-level laptop off the shelf at Staples, installed Vegas 6 just to see if it would work at all, and I haven’t been back to my main editor (fairly powerful desktop system) for anything other than rendering since. I would have been satisfied if I could only edit audio with the laptop, but I’ve been able to edit enormous video projects with lots of of plugs-ins and transitions on this thing.

Now I edit on my laptop, using an external drive. Then I take the HD to my main system, fire up Vegas, and let it render. I can’t imagine locking myself in my office to edit like I used to.

My only point being that as long as your new computer can run XP, you’ll probably have no problem with Vegas. And since your new system will probably far exceed minimum specs, you’re going to be just fine.

[Josh Meredith]

I can’t explain why your burned DVD is behaving so strangely. However, I have had several problems in which a project tests fine on DVDA before I prepare the project for burning, but when I play the burned DVD in my set-top player, it behaves completely differently.

I’ve discovered that this only (and always) happens when I’m making a DVD that consists of several video files. My solution is to render a single video (MPG2) for DVDA with appropriately placed index marks, rather than to render each chapter as a seperate file. That should solve your problem, too.

[Josh Meredith]

So I can go to the command prompt, enter “CONVERT H: /FS:NTFS”, and convert my entire H drive (not just a partition) to NTFS without losing any files?

Thanks.

-Josh

[Josh Meredith]

The free script worked! Thanks again.

[Josh Meredith]

I am using the >>| and |<< buttons on every remote for every DVD player I have. In every case, on every DVD I burn in this fashion (compilations of several mpg-2's) with DVD-A, the << and >> button’s work, but not the >>| buttons. And in each case, I’ve told DVD-A to enable every possible remote function.

For a quick fix, I’m just going to render a single mpg2 containing every chapter of my project, and insert chapter markers on every segment. Then I’ll burn that as a “single move” in DVD-A

[Josh Meredith]

I’m using 6.0d

When you say “markers” do you mean chapter markers? Because what I did was import a bunch of vegs into the timeline, and then I inserted chapter points at the beginning of each veg. None of the individual vegs had chapter markers, though.

Thanks for the reply. I’ll check to see how many threads I have enabled, but I’m pretty sure I set it up for 2 when I installed 6.0