Thats EASY. Read all the other posts. Happens every time there is a release. "Oh Thank you Sony" "I'm in love"!

John

Any scripts out there that could address this?

Yes!
The Rip Van Winkle script.
It puts you asleep for 100 years and when you wake up you find out the issue was fixed in Vegas 106.

John

Thats EASY. Read all the other posts. Happens every time there is a release. "Oh Thank you Sony" "I'm in love"!

That's unfair. I know I brought a series of criticisms -- the ripple issue among them -- into a post the same day Vegas 5 was released. I was not at all "in love" with that release and took some flak from the great BillyBoy for having the nerve to complain about the cost of the update.

Vegas 6 seems a much more enjoyable $200 spent, though as you say there are still issues that would be a welcome fix.

- jim

I can tell you because of this issue I will probably stay with V4, certainly I will not run out to buy V6.

On the plus side I have 5 copies of Vegas still on 4 so I have saved myself $2,000 if I don't actually buy V6.

This action is causing a serious budget problem over there at Sony. I calculate I personally have affected their budget by at least .000000000000000000000000000000000000000000000000000000000000001%

I am actually sorry that I have caused such a problem for Sony. It's not them, it's MADISON.

Stephen I agree it's shocking that this hasn't been fixed, but it's not worth shooting myself in the foot by not using all the other plusses that V5 and V6 contain.

Peter

LOL---did you ever think that maybe they CAN"T fix it?

rex has a point -- and even assuming they could, "fixing" it might break other Vegas functionality, or at least the effort needed might not be worth the resources.

Either way, it's a known Vegas "function," so why it's so much of a headache once you've identified it, I don't know. It's pretty easy to work around it, anticipate it. Especially now that V6 shows you cross-fade info.

- jim

Yes, but if it is "unfixable" a simple explanation that this is so would go a long way.

You're totally right.

A warning message, with an option to unlock the media, wouldn't break Vegas. Get real.

Rob Mack

I think that one of the problems that Sony has is that they aren't always forthcoming with information. This is a very basic problem that many have complained about. It would be nice if someone from Sony could explain why it can't be fixed, or why they haven't bothered to fix it.

To Rex-

Yes, they can fix it, Madison for whatever reason (they probably do not think it is important enough) chooses not to.

Right now you can perform a proper ripple on Vegas video versions 4-6. Just use your select tool, it is as simple as that. More of a pain and you need to do more work, but it can be done.

If Madison should happen to disagree (and I am pretty sure they won't) I have 3 numbers for them to call: Adobe, Avid and if they don't get it by then -- the Final Cut folks. Somehow, those companies have figured it out. I know it was a challenge, but they did solve it at least 3 to 5 years ago.......

Lets get real here this issue has been ignored. Probably because not enough people have demanded a resolution. Believe it or not - it may also be because Madison does not understand what the problem is. Remember that ripple did not even happen until V4. Truely amazing.

How else could a repeatable defined bug survive 3 generations and 3 or so years?

Steve, if you are right then its pretty stupid behavior and an explanation should be forthcoming--It just makes no sense.

I think that the idea of displaying a warning is very simple. It's not a fix but it would do the trick. Users should then be able to accept that ripple won't work if they've locked some of the events. Heck, that's what a lock is for, anyway.

Rob Mack

Not understanding the problem is pretty likely. I know a beta tester for another, better respected product who constantly complains about the programmers for that product not being able to see problems.

It's more likely than you'd want to believe.

But wait...sorry, I'm forgetting the real problem, that ripple is also shaking out transitions. Ugh! that's messy.

Rob Mack

Yes - there are two issues here - swarrine asked for the "disappearing fades" fix ages ago, and I think this is the one that's been suggested as possible "unfixable".

The locked events warning was my beef about six months ago. I only got caught with this once, but by the time I discovered the mess, I'd done too much later editing to consider using Undo. Because of that mess, I'm now very aware of it.

- and it would also help if locked events were outlined in RED rather than "slightly shaded" so they could be easily spotted at all zoom levels.

And the flash frame issue?
And the audio flatline issue?
And what about that credit roll. How many of use credit rolls at the end of our productions? The credit roll is a leftover joke from version 2 that is NEVER upgraded.
And the transitions? Implementing their duration and setting them in place especially across multiple tracks could be made lot easier than it has been. Isn't an improvement there warranted after this long.
That's why I have been complaining a lot lately. Sony has delivered exactly what I have predicted for over a month. A new set of bells and whistles and the same quirky editor that some people call "intuitive". Give me a break.

John

"Get real."

Get real? How 'bout you drop the attitude. If this were real life, I doubt you'd be talking that way to me or anyone else.

I didn't suggest a pop-up would break Vegas, I suggested re-working how Vegas "understands" where fades and transitions are placed within an event; how they relate to the event when it moves; how they relate to an event when other events surrounding it -- above and below -- are moved; etc. just might be a little more complex than a quick fix. This is why pre-renders are an issue -- it's not just one track in question, the entire timeline is affected by these moves.

As others have said, Sony declaring it unfixable would be "OK," at any rate much better than laving it alone altogether.

That said, lost fades and transitions should be about as surprising a hazard to anyone using Vegas by now as lung cancer should shock someone who smokes daily. It's a known issue, and for one reason or another the fix hasn't come in at least 3 upgrade cycles -- either Sony gives a straight answer, we all "deal" with it, or join the dev team and create all these easy solutions yourself.

- jim

* edit - sorry, should have described this one too - butt three events up to each other and apply fade downs/ups to each. Now move event 1 over any of the fade downs/ups and ripple - the fades are gone.

On a whim, I checked this and can't repro the problem. I just took one long clip and sliced-n-diced it up, added fades in and out to each event. Then, moved them all over the placed with auto-ripple set to "all tracks, markers, regions" and all my fades, cross-fades were preserved. I can take an event out of a group of three with auto-ripple off, then rejoin it, then auto-ripple on and move with no problems. I can even slide one event over a series of others, all with their fades set, and the fades all stay intact.

The only time I can get fades to disappear are if I drag the edge of one event to the edge of another, or drage an event over another, drop it, then pick it up again.

???

My apologies Jim. I was only refering to the problem with the locked events. that could be dealt with in the interface, with a pop-up warning.

The transition problem is different, of course. I haven't tried it yet but from the description it sounds like Vegas is removing the fade on the single event as soon as you overlap it (which I think is normal for vegas) and then failing to restore it when you ripple. Or, in other words it ripples after removing the fade, instead of before.

I have no idea if it's fixable but I would think it would be.

Rob Mack

I still can't get it to show up -- maybe I'm missing something...