I saw it only once (V7.0b) but never was able to reproduce it.

In 7.0c release notes, there is this info:
Fixed a rounding issue that affected crossfade, composite level, and composite-level envelopes.

Maybe bug is fixed ?

Okay, I finally got fed up with this and updated to 7.0c (thought I would take my chances with the other issues that have been posted here). After upgrading and opening the project I have been working on, the same issue is still there.

Anybody else getting this in 7.0c?

j razz

I wanted to fade out one clip to black and fade up on the next clip. The moment the two clips had no gap (snapped together) the fades disappeared and the moment I seperated the two clips they reappeared.

I'm sittin' here scratching my head trying to figure out what's going on here and if I hit some weird button and changed the format or something.... But I was unable to do what I wanted no matter what I tried and had to settle for a crossfade, I was too lazy to put envelopes on for just one transistion....
I've had numerous V7c problems and reinstalls and am still trying to get stuff to work right and stop crashing. Meanwhile, it sounds like I've experienced the same bug?
Also, last night could not get my automatic crossfades to happen when adding media to my timeline. Had the icon depressed (chosen) had it set in properties, no go....
Had to manually set all my crossfades too...

Look forward to getting all this fixed, someday....(two reinstalls still haven't fixed problems, to be continued....)

Teaktart

Yeah, I get the same thing, but I can always drag the fade arc back out on the right side event but it is no where to be found on the left side event.

Make sure you submit a support ticket.

j razz

Hey jrazz,
You just reminded me that I had the exact same thing where the right hand clip would stay faded and it was always the one on the left that had the disappearing fade syndrome....when they were snapped together.
Sounds like a consistant issue.

Eileen

I have seen the fade bug on rare occasions in the past. It happened when I had "quantize to frames" and "snapping" enabled, and the end of the clip did NOT fall on the frame boundary. I would simply move the end so it snapped or cut the clip and deleted part of it, then set it to the correct length. I have not seen it in 7c and have never tried specifically to reproduce the error.

Tech Driver is correct. I've noticed this issue since Version 3 and, in my experience, it always indicates that an event does not properly end on a frame boundary. There can be many reasons for this:
"Quantize to Frames" has been turned off while adjusting the length of an event.
Or, as happened to me in my last project, adding PAL footage to an NTSC project.
The solution is to adjust the length of the offending event so that it lands on a frame boundary.
I really don't think this a bug as you shouldn't have an event that does not end on a complete frame.

-Dan

Here is the thing though- I have one event butted up against the other event. The one on the right side I can adjust the fade arc. The one on the left I cannot. So, if one ends on something other than a complete frame that means the other has to start on an uncomplete frame. Why then can I adjust the arc on the right side event but not the left. It would seem that I should be able to adjust the arc on either event regardless of whether the event ends on a full frame or not.

j razz

If you zoom far into where the 2 events are butted together I think you'll find a minute gap between them. If "Quantize to Frames" is on then you cannot move an event to a partial frame and the two events will never be joined. In any case, you really don't want the gap to exist so the events should be adjusted to end on a complete frame.
I guess you can argue that Vegas should allow the fades to occur and I can't say you're wrong. However, I am grateful that the program gives me some indication that I have a problem with my events not ending on a proper frame.

-Dan

On the project I am currently working on, I just want it to fade to black and then fade into the next event. The extra half of a frame that it is still black does not really matter to me and yes, I can pull the event back some more- I just find it odd that I would have to do this; it seems like more of a bug than a feature. Why not just make the end of the event have a red line appear (like the blue or the yellow that 7 incorporates now) showing that it does not end on a whole frame? That would be better than relying on a fade arc that you may or may not use when you butt the events up together- if you are using straight cuts, you would never know that it ends on a partial frame.

j razz

Yes, I would rather Vegas give me a consistent visual clue that an event has an improper length. I don't think the Vegas programmers consciously decided to make the fade arc an indicator of an improper event length. It's neither a bug nor a feature rather it's an anomoly that I have found to be useful at times.

-Dan

I have seen all of these symptoms in 6. What puzzles me is how an event can start/end on a "partial" frame. Can anyone explain that? I would think Vegas would always chop an event on a frame boundary.

"What puzzles me is how an event can start/end on a "partial" frame. Can anyone explain that? I would think Vegas would always chop an event on a frame boundary."

Don't forget, Vegas is also an audio application and audio isn't constrained by frame boundaries.

-Dan

I think I recall zooming all the way in when I had the problem and there was no gap, they were together but as mentioned the left hand clip is the one that kept "losing'' the fade when the two clips were snapped together, and I believe I had the "quantize to frame" enabled...

Does that sound like your scenario?

And have you ever actually seen a half frame on the timeline? I've never seen that.....would / could there be any difference if it were a SD clip vs a CFDI (HDV) clip with the GOP?

Teaktart

That does sound like my scenario.

I am using HDV M2T files and experience the problem.

I am also using a HDV timeline with pictures and experiencing the same problem.

j razz

I got a response back from Sony today that told me to update at the provided link. I followed the link only to be directed to the 7.0c update- which I have already installed and am using as stated above.

I wrote back emphasizing that I have already installed 7.0c and asked for another look at the issue. I will post what I find out.

j razz

Okay, they responded again (quick mind you) and stated that I need to uninstall every Sony program I have on my computer, then wipe the registry clean of all Sony entries and then reinstall all my sony software and if I want to save my presets and effects and transitions, then I need to save them via the preset manager- all other customizing will be lost....

Why do I have a feeling this is not the answer to my problem? Sounds like a lot of work for something that seems to be a generic response that may or may not work.

I wish the response would have went something like this: Hello Jeremy, we reviewed your situation and the others on the threads that you sent us. We see that this is an issue with a few on the forum and we have had others write tickets on this same issue. Currently we are looking into a way to fix this issue and so far have found it to be related to the the snap of events and the whether or not quantize to frames is checked. We understand this is an inconvienance and we are assuredly working hard to resolve it by the next letter update. In the meantime, here is a small patch that should allow the usage of the arc regardless of what the cause is as it is a script with a gui that allows you to type in the time you want the fade to cover. Hope this helps in the interim. Have a good day and let us know if you have any problems with the script.

That would have been customer service and I would have nothing but great things to say about Sony's support.

j razz

j razz:

HOLD ON A MOMENT ....

I've been one of the most persistant complainers of problems with my software lately, i.e. ConnectHD, Vegas7c, and Cinescore1b.
I did reinstall each one and some of my problems were solved but none of the problems with using Cinescore and CFDIs alone or in Vegas7c...

I put in a support ticket and after a few back and forths got the same response. I didn't want to spend forever reinstalling my other Sony software like Acid6, SoundForge7 ,etc as they did not have problems.
One more question about this and I got the reply to just un and reinstall Vegas7c and Cinescore1b and go and dig out and delete anything at all related to those two offenders. (I even left my Vegas 6d installed). I got instructions for removing any remnants in the registry and any left over folders in C:

OK, did all that, downloaded V7c and CS1b again from Sony website (thankfully it wasn't painfully slow the night I downloaded) and reinstalled.
Afterwards...
I had one wretched evening editing pre-reinstalled(ConnectHD) CFDIs, saved my work incessantly and had about 20 crashes that night. What a slow painful drag that was....
BUT, once I rendered the edited project to Vegas intermediates (1080i) I finally got footage that would work correctly in Vegas and I could finally get Cinescore to work as it should.

Summary:
>You many not need to uninstall all the other Sony software
>I did not uninstall "shared" folders i.e. Acid Loops, Cinescore Themes
>But all my extra scripts did disappear and I had to reinstall Ult S and Excaliber

>I think getting the remnants out of the registry and doing the super clean reinstall may have solved 90+% of my problems.
>I followed that with total "housecleaning" and defragged every drive

I also now believe that the clips that were giving me and Vegas such a horrible time were somehow corrupted when I first captured with ConnectHD ( before I reinstalled that software even though the clips looked fine on the timeline they would only play for a few seconds and Vegas would crash consistantly)
After reinstalling ConnectHD I only had a couple of minor snags capturing and newly captured footage no longer has caused all the incessant crashing in Vegas and Cinescore.
I finally got to edit, create music, and render the past couple of sessions and the only remaining weirdness was that after rendering my last project Vegas just up and closed and when I reopened I had the "autosaved" version pop up and that should not have happened....

So, I hope you read this before you undo all your stuff and can limit the amount of stuff you have to reinstall....and can save yourself a lot of 'down time'....

Teaktart

p.s. the last session I even tried the fade down and up again and it actually worked as it should, hope it stays that way!