Ripple shortcomings still - BUT SOME GOOD NEWS

Comments

swarrine wrote on 4/19/2005, 2:42 PM
My theory on why ripple does not work is this:

If you use the slect tool to highlight a selection then move everything as a block it works fine BECAUSE everything moves as a block.

If you use ripple, the event you click moves then everything else snaps to it.
When you cover one clip with another the fade to blacks are removed.
Since ripple works on a snap to basis, many times you are forced to move one clip over another and thus the loss of work occurs.

The logical answer is to reprogram ripple to make it move as a block instead of a snap to.

It is possible there is a reason they can't do that as a quick fix, but, ripple one way or another we know is possible and should be fixed.

rmack350 wrote on 4/19/2005, 3:47 PM
It seems that the sequence of events is something like
--move event
--remove fades
--trigger ripple

I'm sure there's more to it but in general they either need to capture the state of the events before removing the fades or else delay removing the fades until after capturing the state of the events. Almost the same thing but not quite.

Rob Mack
PeterWright wrote on 4/19/2005, 6:38 PM
Ok - just discovered some good news in V6.

If you have auto-ripple enabled, which I never do, but if you do, then the disappearing fades problem is solved!!! Rather than overlapping, then rippling, everything to the right of the moved Event moves with it, so it's similar to using the select tool to move a whole block.

So, swarrine - it's solved!, unless, as I said, you use Post Ripple, in which case the fades still disappear if covered by the moved event - but now that there's an alternative, there's no need to ever get caught.

So that's one for Sony.
Cheers chaps!
Nat wrote on 4/19/2005, 6:47 PM
Would still be nice if it gost fixed... I never use auto ripple too dangerous imo.
craftech wrote on 4/19/2005, 7:19 PM
Most of us I think gave up on autoripple a long time ago.
Look, all of us who have bought several versions of Vegas (in my case 2, 3, and 4) have found "workarounds" for the problems. BUT, don't ask me for one to keep buying new versions every year when I STILL have to use the same old workarounds on the same old problems. Statements like "maybe they can't fix it" shouldn't be acceptable statements for version after version. There is no way I will believe that reworking the editor from the gorund up wouldn't make basic editing easier and more reliable in Vegas 7. Please!

John
PeterWright wrote on 4/19/2005, 7:53 PM
As I said, I never use auto ripple either, but if I knew I was going to drag an event over the top of a fade I didn't want to lose, I would click auto ripple on, make the move and click it off again - hardly a workaround.

Remember, no-ones asking you to buy anything. If the new features would help your work, go for it, otherwise no problem.
craftech wrote on 4/19/2005, 7:58 PM
I think you are still missing the point Peter.

Regards,
John
filmy wrote on 4/19/2005, 8:08 PM
I agree with craftech on this. Issues with ripple, flash frame, black frame and so on have been around. No one is forcing anyone to buy these "upgrades" or newer versions but if Vegas were a car there would have been some agency forcing Sony to issue some sort of 'recal' on it to fix these issues. (And I am not saying that Vegas 6 has all of the same issues but it seems like it does have at least some of them...until people start posting about finding black frames or flash frames with version 6 anyway)
craftech wrote on 4/19/2005, 8:18 PM
Exactly.
How do we get Sony to improve the way the basic editor works? Or do we jump ship if we don't like it? What kind of logic are we dealing with here? That is why I am saying that some of you are missing the point. We like Vegas, but we WANT Sony to change some of the basic common editing functions and even rework the editor from the ground up if necessary to truly improve it.
It's hysterical listening to people Ohh and Ahh about HT support, nested timelines, and system wide media management while not caring about the most amateurish credit roll function in video editing that NEVER CHANGES from version to version.

John
jlafferty wrote on 4/19/2005, 8:35 PM
Maybe that's because -- being "the most amateurish" credit roll function -- we never use it. I, for one, have used a credit roll... uhm, never. It's a shame it's not perfect, but it's far from a deal breaker, or any of the other things people seem to be blowing it up to.

Now, repeatable flash frames, blank frames, and other problems like this are an altogether different issue.

- jim
craftech wrote on 4/19/2005, 8:45 PM
Jim,
If you never use it then why knock it's importance. I produce videos of musicals and plays and dance productions. I have to use a credit roll. This one requires drop shadows and other enhancements to make it look good. There is a ridiculous procedure one must go through to make the credit roll slow down. There are only three color choices to set up columns, etc with so you have to have all the main titles the same color and font, all the subtitles the same color and font. If you make a mistake you have to post here to find out if anyone knows how to insert a blank space in it (I recently told someone how to do it that has been using Vegas for a long time and never knew). He just started over as many others have who didn't know. To my knowledge neither Sonic Foundry nor Sony ever put the procedure in one of the manuals. I found out how to do it a long time ago from some of the great people on this forum.
I could go on.

John
PeterWright wrote on 4/19/2005, 8:56 PM
I would never defend the built-in Credit Roll, but on the rare occasions when I need one, I always use the standard Title generator and Placement Tab to do the same thing - much quicker, more customisable, unlimited fonts, outline and shadow without using Track Motion.
jlafferty wrote on 4/19/2005, 9:14 PM
I produce videos of musicals and plays and dance productions. I have to use a credit roll.

I don't understand why a credit roll is your only option.

I've never used one because I just don't like the way it looks/feels -- I'd much rather fade in/out pages of names. Still, isn't there a way to use keyframes and track motion or pan/crop to build a better roll than Vegas's default tool?
craftech wrote on 4/20/2005, 6:58 AM
isn't there a way to use keyframes and track motion or pan/crop to build a better roll than Vegas's default tool?
===========
This is what I don't get. You are suggesting a "workaround". I am tired of workarounds. I should and DO expect that Sony improve the BASIC editing tools videographers and filmmakers use. And credit rolls are one of them. That IS NOT unreasonable to ask them to do after this many years.

John
swarrine wrote on 4/20/2005, 7:15 AM
Hi Peter-

WOW! I don't believe it. Really? They fixed it? That is excellent news. I am going to download V6 today and try it out.

Oh boy....
BillyBoy wrote on 4/20/2005, 7:41 AM
This thread and similar ones point to the growing unhappyness with unresolved issues first brought to light in some cases several versions ago. New features are fine, but ignoring bugs or not addressing some long known klutzy "features' like the mickey mouse credit roll isn't very smart because they have a cumulative effect on both work flow and creativity.

It seems the way to get Sony's attention is scream and rant. That worked for the small but highly vocal gang that wanted "better" media management. You now have something, if or not its better is debatable.

Now Sony, how about fixing long standing bugs and mickey mouse featues. Doing so would be the "professional" thing to do.
jlafferty wrote on 4/20/2005, 7:57 AM
John,

We have a disagreement on what qualifies as a bell/whistle, and what qualifies as a basic editing need. I'm of the opinion that a credit roll -- titling in general -- is a bell/whistle; whereas better media management and nested projects seem like basic editing needs. This is why we've got opposite feelings about the update.

Sorry to read you're frustrated, but I think there's bigger fish to fry (e.g. the flash frame, blank frame, audio problems you've previously mentioned).

- jim
BillyBoy wrote on 4/20/2005, 8:06 AM
Just curious... have you EVER seen a movie or documentary even, without a credit roll at the end?

I agree some things will be viewed differently depending on what you use Vegas for, so one guy's idea of "must have" features will vary from the next guy's ideas of what's more important. I think we can all agree that right now as things stand there are simply too many annoying and well documented "bugs" that haven't been addressed. I'm not referring to new things just cropping up in version 6, rather things some are reporting are STILL in version 6 or 5 if you haven't upgraded and were knows for years already. Why haven't these been fixed?
rmack350 wrote on 4/20/2005, 8:22 AM
I hope you're being tongue in cheek!

They fixed automatic ripple but not post-edit ripple. Play with it a bit. Kind of interesting and I think it gives a clue as to the nature of the problem.

Esentially, what they did was make auto ripple move all events before the overlapping could ever happen. This circumvents the automatic removal of fades.

Problem is that it's a quarter-measure. It doesn't have any bearing on manual ripple, which I suspect people may use more than auto ripple.

Many things in this new release are evidence that Sony really is listening to a lot of demands. But it seems like either the beta testers or QA aren't getting into the process early enough. We're looking at a beta version of Vegas 6

Rob Mack