V22 - Wrong Clipping Issue and Audio Wave Display Bug (Wave Moving)

Thomas97 wrote on 11/29/2024, 10:07 AM

Hello to all Editors,

I am a 10+ years Vegas editor and 2 weeks ago I upgraded from v20 to v22.
The amount of issues and bugs I've found with v22 is embarrassing, so I'm just asking if anyone has ever encountered these issues.

Bad Snap (video)
Every time I try to snap a new event by dragging it to the timeline, Vegas highlights the correct snap position, but once the mouse button is released, the actual snap is different.

Wrong Waveform when stretching audio (video)
When trying to stretch the audio to the left, the whole wave moves. As you can hear, it is just a visual bug.
Moreover, zooming in-out from the timeline moves also the audio wave a little bit, always as a visual bug.

Solutions tested:

Importing preferences from v20

Quantize to Frame options

Timeline measurement (time and frames)

Different files

Different computers

Maybe there's something new I don't know, or maybe I never had this issue before and there's a setting I still need to learn. Vegas 20 has none of these problems and works perfectly.

Does anyone know how to possibly fix this issue? Thanks in advance.

Comments

zzzzzz9125 wrote on 11/29/2024, 10:51 AM

I can reproduce the second one and have reported it to Magix. Hope it can be solved in the next release.

For events, I always disable loops: uncheck Preferences -> Edit -> Enable event loops by default. You can also disable loops by Right-clicking -> Properties -> Loop. When you extend the event to the left, it creates a new loop, which causes problems with audio peak. When the loop is disabled, it no longer allows you to do it. This issue only occurs on MP3, not WAV, FLAC, or OGG.

For the first issue, I can't reproduce it. Someone else needs to test it further.

Robert Johnston wrote on 11/29/2024, 11:37 AM

@Thomas97 In version 22, I can reproduce the bad snap. If I zoom in far enough on the timeline, I will get a correct snap. Version 21 does not have this issue.

Thomas97 wrote on 11/29/2024, 11:59 AM

@zzzzzz9125 and @Robert Johnston
Thank you so so much for the more or less positive feedback. At least it is something happening to more users and not only to me.
The question now is: with the 1-time purchase license, will I get the updated version with these bugs fixed? And what's the best way for users to report to Vegas these issues? Support so far acted like it was my problem.

RogerS wrote on 11/29/2024, 5:37 PM

Any updates to 22 are free for you. Whenever the next version of VEGAS comes out that's a paid upgrade

mark-y wrote on 11/29/2024, 8:10 PM

Every time I try to snap a new event by dragging it to the timeline, Vegas highlights the correct snap position, but once the mouse button is released, the actual snap is different.

That may be entirely because your "Quantize to Frames" switch is set (correctly) to "ON."

In the real world of video editing, the smallest discrete quantified unit of measure is One Frame, not 1 millisecond, as your timeline cursor is capable of showing. IOW, it jumps to the nearest frame boundary, absolutely correctly and as necessary for glitch-free editing. There is no such thing as an interframe sample point in video production.

Quantize to Frame options

A huge note to you going forward. Quantize to Frames does not do anything after the fact. Turning it On does not reposition the events already on your timeline. You must instead start with a fresh project, and introduce your Media Events one-at-a-time with the Quantize switch already turned on. That is the only way it works, unless there is a script somewhere to to the dirty work for you. ;?)

Welcome to the discussions.

EricLNZ wrote on 11/29/2024, 9:24 PM

@Thomas97 Further to mark-y's comments, as you are probably aware you can easily check for unquantized frames by switching on Options/Quantize to Frames/ Show Unquantized Event Edges. They show up as red lines on your timeline.

john_dennis wrote on 11/30/2024, 12:49 AM

It's unlikely that Quantize to Frames is the root of the problem since, in my case, the displacement is more than one frame.

GPU On

Legacy Decoder

It's likely a program defect.

3POINT wrote on 11/30/2024, 7:43 AM

IMO indeed this is a bug, I was also wondering the last times I edit, that I got a lot of blank frames between events. I can confirm that while snapping to events is enabled, as soon as event to snap at is detected and releasing mouse button, the new event is jumping 3-4 frames and leaving a blank space between the previous event. This ONLY happens while dragging an event from the media folder to the timeline. For events that are already on the timeline, snapping to other events works correctly.

Thomas97 wrote on 11/30/2024, 8:51 AM

Hello @mark-c and @EricLNZ

As already written in my original question, I checked if having enabled or disabled QF helps fix the issue, and it doesn't.

QF could potentially affect max 1 frame or half a frame.

Also how @john_dennis shows and how it's clearly visible on the videos I shared via Drive, sometimes it affects more than two frames, even up to 7.

I would like to share another video: click here (or check below)

As you can notice, the snap issue will move the new event placed to the right when the mouse is more 'pushing' to the right, and the same goes to the left, when the mouse is more towards the left of the snap trigger field.

Additionally, the snap issue happens only when an event is first placed, not when an existing timeline event is being repositioned. (as @3POINT noted)
To be more precise, it happens also when you drag and drop a file from (in my case) a Windows folder, not only from Media Explorer (which means clips, title and text, colors, ...)

Again, this is only affecting the latest v22 build and it's a quite serious bug, at least for me. I edit videos that are 2+ hours long with render regions active, which means my timeline is zoomed out most of the time and indeed this issue is way more noticeable.

I would like to kindly ask @VEGAS_CommunityManager to take a look into this and notify the DEV team about these 2 bugs if not aware yet.

Thank you, everyone, for the time spent testing to verify these issues reporting, I appreciate it.

FayFen wrote on 11/30/2024, 12:19 PM

I just upgraded to VP22 , still have the trial here and indeed the bad snap issue is very bad.

I think it should jump high for the next build.

Very strange it wasn't reported before.

3POINT wrote on 11/30/2024, 1:58 PM

Very strange it wasn't reported before.

Indeed, most issues reported are issues with mporting screen captures of game plays. No issues reported that where it is all about, namely video editing...!