VEGAS Pro 22 Build 93

Comments

pavel.lu wrote on 8/24/2024, 8:13 AM

Hi, please is it possible to convince the trimmer to use proxy video?

nancyrry wrote on 8/25/2024, 3:39 AM

Hi,

Congratulations on the release of VEGAS Pro 22. I am excited to see what new features and improvements have been added. I will check out the News forum post for more details. Looking forward to hearing feedback from other users on their experience with the update.

Thanks

daniel-rimon wrote on 8/25/2024, 11:58 AM

I have some issues with speech to text, he uploads the subtitles to the timeline but in dizolobs and not at the right timing. I'm currently using the previous version to create an accurate timing. This is a bug that needs to be addressed because at the moment I can't even use this option in the new version.

Secondly, I have raised this issue before, the directionality of the text, in the editing pane of the text, that you will be able to choose the direction from right to left. All the punctuation is messed up there. Also choosing mixed colors and not just a single color. I sought to diversify the possibilities of using animation as well as letter animation. In right-to-left spelling, you can't write a paragraph without all the text disappearing. 
In general, in my opinion, all the work on the text in Vegas needs to be changed and updated because it's really old and hasn't been significantly updated in over 5 years. 

Also significantly update Credit Roller, really not updated since version 4 or 5. 

fr0sty wrote on 8/25/2024, 5:30 PM

The bug you mention is being worked on. No idea when a fox will come, but they're on it.

Last changed by fr0sty on 8/25/2024, 5:31 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Len Kaufman wrote on 8/28/2024, 4:58 PM

I'm having an issue with one aspect of v22, that I didn't experience with v21 or any prior versions. I'm working on a project with a LOT of clips in the injested files folders, though not very many actually on the timeline. Whenever I switch out of Vegas to use another program, or if I switch to another computer (I have my monitors and keyboard and mouse on an A/B switch), when I come back to use Vegas, it takes forever to regain use of Vegas. The little blue circle goes around and around, taking almost as long to "ingest" as when I first brought those files into Vegas.

A lot of the projects I work on involve a lot of files. I do travel video, and sometimes, a trip might be 2 weeks long and generate a bunch of clips. I don't recall changing anything from v21 to v22. Can anyone suggest a way to speed up the process?

Thank you.

Len Kaufman

EricLNZ wrote on 8/28/2024, 6:45 PM

Probably this as I understand the default changed with VP22. Untick the option

@Len Kaufman

Ross-Wild wrote on 8/28/2024, 11:47 PM

Hello everyone how come I can't download, (VEGAS Effects) I've been using that software to color grade my videos. Anyone knows what happened??

RogerS wrote on 8/29/2024, 5:38 AM

What do you mean download? It's not still installed?

Reyfox wrote on 8/29/2024, 7:19 AM

@Ross-Wild and what version of Vegas Pro do you own?

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Howard-Vigorita wrote on 8/29/2024, 3:49 PM

Hello everyone how come I can't download, (VEGAS Effects) I've been using that software to color grade my videos. Anyone knows what happened??

@Ross-Wild Here's a thread about Vegas Effects and vp22...

https://www.vegascreativesoftware.info/us/forum/if-i-upgrade-to-vegas-pro-22-can-i-still-use-vegas-effects--146666/

If your only issue is downloading it, the version for vp21 direct download link is under the #3 Read Me First link:

https://www.vegascreativesoftware.info/us/forum/more-important-posts-please-read-this-first--134404/

morke-m wrote on 8/30/2024, 5:13 AM

The audios in version 22 have a rain sound interference in the background, mainly the mp3s
Have you noticed this? Do you know how to fix it?

here media info

 

Formato                                  : MPEG Audio
Tamaño de archivo                        : 320 MiB
Duración                                 : 2 h 19 min
Modo de tasa de bits                     : Constante
Tasa de bits general                     : 320 kb/s
Librería de codificación                 : LAMEºe7-£ / @3B-…Ã*
major_brand                              : mp41
minor_version                            : 1
compatible_brands                        : mp41isom

Audio
Formato                                  : MPEG Audio
Formato de la versión                    : Version 1
Formato del perfil                       : Layer 3
Ajustes del formato                      : Joint stereo
Duración                                 : 2 h 19 min
Tipo de tasa de bits                     : Constante
Tasa de bits                             : 320 kb/s
Canal(es)                                : 2 canales
Velocidad de muestreo                    : 48,0 kHz
Velocidad de fotogramas                  : 41,667 FPS (1152 SPF)
Modo de compresión                       : Con pérdida
Tamaño de pista                          : 320 MiB (100%)
Librería de codificación                 : LAMEºe7-£ / @3B-…Ã*

 

bitman wrote on 8/31/2024, 3:27 AM

@Len Kaufman the suggestion of @EricLNZ may help (I left it ticked however), but I suspect the issue maybe different, perhaps it is just a matter of hard drives being parked while you are using other applications (after a certain time as being set in the windows power options), then they need time to spin up when refocusing Vegas.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Zorac wrote on 8/31/2024, 10:24 AM

I just upgraded from v19 and had two issues. Both issues happen when loading in projects from v19 (I haven't tried with a new native v22 project). The first is when I have something masked using the crop/pan function; it doesn't preview correctly unless I have the preview window set to full (the coordinates for where it places the mask don't seem to update/scale when using a preview less than full). I noticed a similar issue with the chroma fx; the preview doesn't display correctly unless the preview window is set to full. Second, the offsets on files are off when using my rx6650xt for acceleration (where the source is trimmed changes/wrong when I load a project with the 6650 enabled, but everything is correct when it is disabled). When I switch to CPU (12700k) or to the iGPU it is okay. I can't use the 6650 to render either (in v19 or v22), as the output files have glitches.

As for a wish list, I would love to see a medium setting on the smart mask (a middle ground for the current low and high options) and a way to edit frame by frame to clean up the odd glitch or two. Fixing the AMD GPU bugginess would be nice, too, but that may be an AMD issue, not a Magix issue.

I've been a user since the Sonic days; it is great to see Magix continue to put resources into the software and continue to improve and develop Vegas! I've strayed to other options but keep returning to Vegas as my preferred video editor.

Len Kaufman wrote on 8/31/2024, 12:29 PM

@bitman Thank you for your comment. The solution offered by @EricLNZ above solved my problem. I wasted a LOT of time with that issue, but the Forum (here) with @EricLNZ came through. I would think that when Magix publishes a new version of their software, they might make a list of defaults that were changed (unless I missed it).

Reyfox wrote on 9/2/2024, 4:07 PM

'Fixing the AMD GPU bugginess would be nice, too, but that may be an AMD issue, not a Magix issue.'

What issues specifically..... what card and what drivers..... I use AMD. See Signature below...

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Zorac wrote on 9/2/2024, 4:40 PM

What issues specifically..... what card and what drivers..... I use AMD. See Signature below...

I'm close to a solution. I'm running a rx6650xt (currently on 24.7.1) and a 12700k. Under the 'file i/o' tab to use the 6650 for hardware acceleration, as well under the 'video' tab setting GPU video acceleration to the 6650, plus enabling legacy AVC (file i/o tab), seems to be a working combination. I haven't used the AMD rendering yet (still using CPU) to see if the final products have glitches. Using legacy AVC seems to be the key.

I can open a file with my current settings, and it is perfect, everything works as it should. I turn off legacy AVC and all the file offsets/cuts will be wrong and the timeline is just a mess. Everything is stable, which was my challenge with v18/v19. Oddly enough, I tried to reproduce the timeline offset issue in v19 by toggling on and off the legacy AVC option, and in both scenarios (with AMD GPU selected on both tabs), it was fine.

RogerS wrote on 9/2/2024, 6:17 PM

Sounds like a decoding issue with your specific media and MxCompound.

Zorac wrote on 9/2/2024, 9:11 PM

Sounds like a decoding issue with your specific media and MxCompound.

Good though, so because of your direction I stopped looking/changing settings in Vegas and I started looking at which clips were the issue (all created with OBS as mkv, then stream copied into mp4 containers using avidemux), then brought them into a new project to try and recreate the issue. I can't get the issue to reproduce in a new v22 project, but I have two old projects doing it. Both projects were started in v19, so I'm wondering if the issue is that the projects were created in v19, then brought into v22 (needed to use v22 specific features, specifically smart mask). All my v19 projects are closed off now, so I'll turn off 'legacy AVC' and see if it happens going forward.

As an aside, I discovered footage from my Sony camera is non-compliant mp4 files as it uses PCM audio; it doesn't seem to cause an issue, though and Vegas seems to be OK with it.

Pedro-C wrote on 9/3/2024, 1:38 AM

I bought Vegas Pro 22 yesterday to edit my videos but right away it started framing every second and i tried to fix it but nothing worked, then later when i tried putting effects on it, the video would go black then everything would just glitch out and crash my pc. I don't know how to fix this problem if it's just me or the software glitching out itself.

VEGAS Pro 365

I'm using a AMD Ryzen 7 3700X 8-Core Processor

Nvidia GeForce RTX 3060

RogerS wrote on 9/3/2024, 4:08 AM

Good though, so because of your direction I stopped looking/changing settings in Vegas and I started looking at which clips were the issue (all created with OBS as mkv, then stream copied into mp4 containers using avidemux), then brought them into a new project to try and recreate the issue. I can't get the issue to reproduce in a new v22 project, but I have two old projects doing it. Both projects were started in v19, so I'm wondering if the issue is that the projects were created in v19, then brought into v22 (needed to use v22 specific features, specifically smart mask). All my v19 projects are closed off now, so I'll turn off 'legacy AVC' and see if it happens going forward.

As an aside, I discovered footage from my Sony camera is non-compliant mp4 files as it uses PCM audio; it doesn't seem to cause an issue, though and Vegas seems to be OK with it.

If you'd like others to test any problem footage feel free to report back. Legacy AVC in VP22 is the standard decoder VP19 used, Fyi. Legacy AVC in 19 is an even older decoder that doesn't use the GPU.

If it's Sony XAVC S with PCM in a MP4 container I think that's a legal combination and what all my footage from the past 6 years is so should work well in VEGAS.

Len Kaufman wrote on 9/4/2024, 11:08 PM

Probably this as I understand the default changed with VP22. Untick the option

@Len Kaufman

@EricLNZ Your suggestion (above) certainly worked. But strangely, 3 times now, Vegas has reverted back to the "checked" box. And I had NOT been back into the preferences for any other reason, other than to fix, as per your suggestion. And yes, I hit apply. Fortunately, this time I knew exactly how to fix it, thanks to your suggestion. But is there a way to keep Vegas from arbitrarily changing to default?

EricLNZ wrote on 9/5/2024, 3:51 AM

@Len Kaufman Strange. Try hitting Apply, then OK, then shutdown VP. Then reopen to get back to work.

My understanding is that changes only get permanently recorded when Vegas shuts down. So if it shuts down abnormally changes are lost.

fr0sty wrote on 9/5/2024, 10:21 PM

Fixes coming soon with the next patch. Hopefully your issue is in this list.

Fixes and Improvements (for build 122):

Fixed a bug that could cause the Explorer window to not properly update after redocking 

Pan and Crop adjustments no longer lead to distorted preview 

Fixed crash which could occur when opening ProRes 422 HQ files through the Open dialog 

All BlackMagic RAW files now display with the proper aspect ratio 

Missing renderers are now available again in the Render to New Track feature 

The Render As dialog now shows QSV templates only when appropriate hardware is available 

Optimized GPU-based readers to ensure that fallback to CPU readers occurs only after GPU resources are exhausted 

Fixed a memory leak which would occur when using some OpenGL-based functions 

Subtitle generation is now properly aligned when using the Speech-to-Text generate function 

Fixed a crash that occurred upon clicking the Clear mask with selection button in the Smart Mask plug-in 

Fixed a crash that occurred when importing some projects via the Import | Media menu option 

Fixed a crash that could occur when the persisted state is corrupted in the Explorer window 

Fixed a crash which could occur when the application regains focus 

The Welcome dialog now properly closes after opening a project 

The Frame Center section in the Auto Reframe plugin now properly refreshes when using the Preview Window interacts 

The Reframe function now properly resets the location box position in the Auto Reframe plugin 

Fixed location of persisted data for the Explorer window 

Fixed a crash which could occur when attempting to open a .txt file in the Explorer window 

Fixed a crash which could occur after changing/replacing hardware in machine 

Prevent a potential crash which could occur when the QuickTime plugin is activated 

Follow Object button in Auto Reframe plugin now appropriately opens the keyframe window 

Add to Timeline function in the Explorer window now properly creates an Undo event 

Fixed an issue with improper parameters being available for the MP3 encoder, which resulted in a rendering error 

Ignite FX now works properly 

AI Upscale no longer turns the Preview window purple when the window setting is set to Preview mode 

AI Upscale no longer causes memory leak 

Fixed a crash which could occur with some Canon-based files