@Dexcon DirectX 11 is not only for games, it can also be used for rendering contend in general as well as in GUI generation.

Hopefully the video engine is moving towards such modern graphical APIs.

The memory leak problem when using the 'LUT Filter' FX with nVIdia GPU acceleration enabled is still there in Build 194 - only workaround I've found is to use (much slower to render) 3rd party LUT loaders or disable GPU acceleration.

See this post in the Build 122 thread for more info - https://www.vegascreativesoftware.info/us/forum/vegas-pro-22-build-122-general-discussion--147185/?page=6#ca927352

When I right-click and drag multiple media items from the project media onto the timeline and select "Add Across Tracks," the events are arranged in a staircase format.

They used to be arranged vertically, right? Is this a bug?

The screenshot is from the Japanese version of the interface.

@eleven https://www.vegascreativesoftware.info/us/forum/problem-of-importing-files-across-tracks-by-right-drag-in-vp22-b194--147703/

thanks @jetdv

Does this mean the specifications have changed? It's inconvenient, so I would like it to be reverted to the original specifications.

I finally took the bullet and installed VEGAS Pro 22 after so many crashes, freezes and hangs of VEGAS Pro 20, and the result was literally night and day. To be honest, I almost ditched VEGAS Pro in its entirety (I am a 10+ year user of the VEGAS Pro series even since the Sony versions) due to the instability of VEGAS Pro 20 (and its predecessors) but am now a happy camper😄

Since the upgrade to VEGAS Pro 22, surprisingly, I haven't had a single freeze during multicam editing phase. Even five tracks of 4K (UHD) footage can stably be edited (and rendered). There might be issues on other functions I have yet touched; however, the stability of such a primary editing function was exactly the area I was expecting to see improvements over the past decade. Cangrats to the developers team and keep up the good work!

 

Does this mean the specifications have changed? It's inconvenient, so I would like it to be reverted to the original specifications.

@eleven It's not supposed to be like this. I hope it will be fixed soon.

I noticed that sometimes Vegas pro 22 presented a bug on the last frames of my videos (whether go pro or osmo pocket), which shows a dark green screen. By restarting the software, it disappears and may then appear on other videos. Are others affected by this bug?

I noticed that sometimes Vegas pro 22 presented a bug on the last frames of my videos (whether go pro or osmo pocket), which shows a dark green screen. By restarting the software, it disappears and may then appear on other videos. Are others affected by this bug?

Are you using an NVIDIA GPU? Which model exactly? Is it H264 (AVC) or H265 (HEVC) footage?

I've installed the AI Assistant, redeemed the voucher and restarted the trail version of Vegas but under the tools menu I do not see the AI Assistant option. Anyone had this and had success in make the AI Assistant show up?

I noticed that sometimes Vegas pro 22 presented a bug on the last frames of my videos (whether go pro or osmo pocket), which shows a dark green screen. By restarting the software, it disappears and may then appear on other videos. Are others affected by this bug?

Are you using an NVIDIA GPU? Which model exactly? Is it H264 (AVC) or H265 (HEVC) footage?

Yes an NVIDIA GEFORCE RTX 3080TI 12Go gDDR6X 1xDVI / 3xDP / 1xHDMI PCI Express 4.0 16x and I checked for the footage, this H264 (AVC)

my graphics card is updated regularly and I didn't have this bug before and it doesn't happen all the time, thank you

I noticed that sometimes Vegas pro 22 presented a bug on the last frames of my videos (whether go pro or osmo pocket), which shows a dark green screen. By restarting the software, it disappears and may then appear on other videos. Are others affected by this bug?

Are you using an NVIDIA GPU? Which model exactly? Is it H264 (AVC) or H265 (HEVC) footage?

Yes an NVIDIA GEFORCE RTX 3080TI 12Go gDDR6X 1xDVI / 3xDP / 1xHDMI PCI Express 4.0 16x and I checked for the footage, this H264 (AVC)

my graphics card is updated regularly and I didn't have this bug before and it doesn't happen all the time, thank you

@davewire35 Thanks Dave. I also have NVIDIA GPUs and would love to see if I have the same issue- could you upload a couple of files from both cameras to a site like Google Drive for testing? If a few of us can confirm the issue it will be easier for the developers to fix.

I noticed that sometimes Vegas pro 22 presented a bug on the last frames of my videos (whether go pro or osmo pocket), which shows a dark green screen. By restarting the software, it disappears and may then appear on other videos. Are others affected by this bug?

Are you using an NVIDIA GPU? Which model exactly? Is it H264 (AVC) or H265 (HEVC) footage?

Yes an NVIDIA GEFORCE RTX 3080TI 12Go gDDR6X 1xDVI / 3xDP / 1xHDMI PCI Express 4.0 16x and I checked for the footage, this H264 (AVC)

my graphics card is updated regularly and I didn't have this bug before and it doesn't happen all the time, thank you

@davewire35 Thanks Dave. I also have NVIDIA GPUs and would love to see if I have the same issue- could you upload a couple of files from both cameras to a site like Google Drive for testing? If a few of us can confirm the issue it will be easier for the developers to fix.

yes of course I can try to do that but the problem is that sometimes it appears on footage and then nothing more, I'll see what I can do and show you a screen. Have you ever heard of this bug? I read yesterday on another post but I don't remember where, a guy mentioned the same thing

finally I found : https://www.vegascreativesoftware.info/us/forum/green-screen-for-a-few-seconds--147016/#ca923903 (last build I got the same bug, so still in that new build)

I don't need to see a screenshot- I've reported and seen plenty of green frames with VP 21.300 through 22.194, though it's getting much better now with many more types of footage.

Your original footage would be helpful so we can try to replicate it in different ways (I find overlaps and transitions can more easily make the green appear).

Hi.

“Auto-Ducking Controller Build 194”
Here I'm running into a wall. I have a music track and a commentary track with some comments. There are pauses between the individual comments. This is where my problem lies. The ducking, as it is from B194 onwards, lowers the music volume at the first comment and returns to the normal volume after the last comment. Roughly speaking, just a common reduction for all comments. Is this intended or am I missing something?

Sample.
Hold: After the attack phase is complete, the hold parameter controls how long this initial attenuation is maintained before the release phase is reached.
Release: Sets how quickly or gradually the sidechain detector stops applying dynamics when a signal falls below the threshold again.

Vegas looks to be reading source duration metadata when it should be reading duration, padding the video out to make it longer and causing audio desync.

Format profile                           : Main 10@L5.2@Main
HDR format                               : Dolby Vision, Version 1.0, Profile 8.4, dvhe.08.10, BL+RPU, no metadata compression, HLG compatible
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 12 min 13 s
Source duration                          : 12 min 17 s
Bit rate                                 : 54.3 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 2.35:1
Frame rate mode                          : Variable
Frame rate                               : 49.881 FPS
Minimum frame rate                       : 16.667 FPS
Maximum frame rate                       : 333.333 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.131
Stream size                              : 4.63 GiB (99%)
Source stream size                       : 4.66 GiB (99%)
Title                                    : Core Media Video
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : HLG
Matrix coefficients                      : BT.2020 non-constant
Codec configuration box                  : hvcC+dvvC

Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 12 min 13 s
Source duration                          : 12 min 13 s
Bit rate mode                            : Variable
Bit rate                                 : 300 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 26.2 MiB (0%)
Source stream size                       : 26.3 MiB (0%)
Title                                    : Core Media Audio

Hi.

“Auto-Ducking Controller Build 194”
Here I'm running into a wall. I have a music track and a commentary track with some comments. There are pauses between the individual comments. This is where my problem lies. The ducking, as it is from B194 onwards, lowers the music volume at the first comment and returns to the normal volume after the last comment. Roughly speaking, just a common reduction for all comments. Is this intended or am I missing something?

Sample.
Hold: After the attack phase is complete, the hold parameter controls how long this initial attenuation is maintained before the release phase is reached.
Release: Sets how quickly or gradually the sidechain detector stops applying dynamics when a signal falls below the threshold again.

Addition.

Red line shows ducking as done by Vegas B194. Blue line shows how it is done correctly.

Hi.

“Auto-Ducking Controller Build 194”
Here I'm running into a wall. I have a music track and a commentary track with some comments. There are pauses between the individual comments. This is where my problem lies. The ducking, as it is from B194 onwards, lowers the music volume at the first comment and returns to the normal volume after the last comment. Roughly speaking, just a common reduction for all comments. Is this intended or am I missing something?

Sample.
Hold: After the attack phase is complete, the hold parameter controls how long this initial attenuation is maintained before the release phase is reached.
Release: Sets how quickly or gradually the sidechain detector stops applying dynamics when a signal falls below the threshold again.

Addition.

Red line shows ducking as done by Vegas B194. Blue line shows how it is done correctly.

Hi.

“Auto-Ducking Controller Build 194” The solution. My current status: Vegas ducks my music track as a whole. From the first comment and ends with the last comment. That couldn’t be it. Otter can do it, Vegas can’t (not yet). Vegas can do it! There was an error with the music track for me. How did I find the solution? I set up additional listening tracks below the current track and deleted the old one. Immediately afterwards, the ducking line was displayed in the most beautiful up and down and I inserted my music file into one of them. Done. Everything perfect. See also screenshot. Everything perfect. See also screenshot. I am satisfied.

The question remains, why didn’t work the first audio track?

Added:
But I almost forgot one highlight. Once these parameters for send and listen are set, I can add as many comments as I want in the send track. The listen track reacts immediately and turns the music down. I can move my comment back and forth on its track, the ducking moves as it moves. Really well done.

Almost my ideal. Because - if I delete a comment, the ducking in the listen track remains and has to be corrected manually.

Could it be that the tracks Automation Setting was set to Off? Right click on the track and then to More to find Automation.

@Hajowo

Hi.
Thanks for the tip. Hm, that could have been it. But I checked there. What I suspect in retrospect is that this track was previously used by Otter's ducker. It is possible that residual settings were left behind by this tool. After deleting the problem track and only using the newly created ones, I am happy.

I get temporary distorted audio doing the following, do others?

https://we.tl/t-zL8QS44d4b