Suggestions For Ways VEGAS Can Improve

fr0sty wrote on 9/13/2022, 4:14 PM

What are the top 3 things you want to see the development team focus on improving first? Keep in mind this is different than new feature requests, this is discussing improvements to what is already there.

Comments

MikeS wrote on 9/13/2022, 5:04 PM

Preview Window: support zoom in and out

Preview Window: support OFX control overlays/overlay widget interactors

You can argue that these are new feature request, but to me they are improvements to the Preview Window functionality.

Last changed by MikeS on 9/13/2022, 5:06 PM, changed a total of 1 times.

Vegas Post 19 Build 458 
Boris FX Continuum 2022 Build 15.0.1.676 
Boris FX Mocha Pro Plug-in 2022 v9.0.2 Build 197
Windows 10 Pro - 64-Bit
ASUS PRIME Z890-P motherboard
Intel Core i7-97000K @ 3.6GHz
RAM 32GB (2x 16GB) 2666MHz DDR4
GeForce RTX 2070 SUPER

lan-mLMC wrote on 9/13/2022, 6:21 PM

Keyframe improvement : Bezier keyframe for Pan/Crop/Mask and Track motion ;

Performance improvement : Smoother realtime (not cache/pre-render) playback for complex projects ;

Decoder improvement: Wider format/codec support like PotPlayer.

pierre-k wrote on 9/14/2022, 5:17 AM

Do you have a vacation to come up with topics like this? What we want is clear. Guys can choose here or start from the top.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-feature-requests--134374/

Anything from this list will please us.

pierre-k wrote on 9/14/2022, 5:30 AM

But ok. 3 things I need the most...

1. Smoother playback of everything with support for saving to some memory.

2. Zooming in on the playback window with the mouse wheel and double-clicking to return the zoom to its original size would be a great thing.

3. Increase the upper limit for event acceleration from 400% to infinity. Or at least 1000%

Dexcon wrote on 9/14/2022, 5:47 AM

Increase the upper limit for event acceleration from 400% to infinity. Or at least 1000%

1000% (i.e. 10 x) - It's already there, in VP19 anyway. After adding a velocity envelope to a video event, R click the node and select the maximum velocity option - you'll find that it is 1000%. Or use the Set To field to 1000%.

Cameras: Sony FDR-AX100E; GoPro Hero 8 Black

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2022.5.1, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX9 Advanced

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

pierre-k wrote on 9/14/2022, 6:10 AM

Increase the upper limit for event acceleration from 400% to infinity. Or at least 1000%

1000% (i.e. 10 x) - It's already there, in VP19 anyway. After adding a velocity envelope to a video event, R click the node and select the maximum velocity option - you'll find that it is 1000%. Or use the Set To field to 1000%.

I mean the TimeStretch method using the Ctrl key.

bitman wrote on 9/14/2022, 6:19 AM

- Proper next generation Intel processor support (Alder Lake), see my recent post; Vegas should be using P-cores by preference and stay away from E-cores as much as possible... This maybe a tough one, P-cores can have 2 virtual cores halving the resources, E-cores not, P-cores can handle AVX512 instructions (banned now by Intel, even fused away in HW rev.2), E-cores cannot, ring bus speed reduced if E cores are used etc... The windows 11 thread schedular (advised by Intel's Thread Director) chooses the cores to run the threads, and does it best, but it is not perfect...

- Release more frequent new builds (with consequently smaller number of fixes and new features), or have public beta's

Last changed by bitman on 9/21/2022, 6:01 AM, changed a total of 5 times.

APPS: VIDEO: VP 365 (20), VP 19 post (latest build -643), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 15 HDpro XXL, Boris Continuum 2022.5, Davinci Resolve Studio 18, SOUND: RX 9 advanced Audio Editor, Sound Forge Audio Clean Lab 3, Sound Forge Audio Studio 16, Sound Forge Pro 14, Spectral Layers Pro 8, Audacity, FOTO: Zoner, DXO, Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 21H2
  • CPU: i12900K with Cooler: 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
  • PS: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

pierre-k wrote on 9/14/2022, 6:34 AM

Proper next generation Intel processor support (Alder Lake), see my recent post; Vegas should be using P-cores by preference and stay away from E-cores as much as possible...

I am quite afraid of this hybrid way of processors. If Vegas will primarily use p-cores, the 16 core processor will become an 8 + 1/2 core processor. I think Intel's strategy in this case is unfortunate.

fr0sty wrote on 9/14/2022, 12:09 PM

I can't say which, but one improvement requested here is already in testing. They are listening.

Keep them coming!

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)

Steve_Rhoden wrote on 9/14/2022, 1:14 PM

@fr0sty Yep, that upcoming improvement gonna have a lot of users eyes popping right out of their heads lol 😄

pierre-k wrote on 9/14/2022, 1:29 PM

I can't say which, but one improvement requested here is already in testing. They are listening.

Keep them coming!

You are as mysterious as a castle in the Carpathians. 😂

If they listen well, it's this......

Smoother playback of everything with support for saving to some memory.

Because this is the most important point of all. Everything else is irrelevant for the moment.

DMT3 wrote on 9/14/2022, 2:29 PM

+1 pierre-k. Stability and smooth playback.

fr0sty wrote on 9/14/2022, 2:37 PM

You can trust that I, and everyone else involved directly with the team, have made that fact LOUD and clear to them. I've heard from the team that they are prioritizing the work on performance and stability now, and they also just added some new devs to the team, and are in the process of hiring more. I can confirm beyond any shadow of a doubt that stability and performance improvements are at the very top of their list of things to do. I cannot confirm when you'll see that work in an update, I imagine part of making the performance gains super stable will require a lengthy testing phase, so please be patient.

- Release more frequent new builds (with consequently smaller number of fixes and new features), or have public beta's

This one is tricky... release them too frequently, you haven't allowed enough time for testing, so lots of bugs remain. Public betas are very difficult for a small team to maintain, but they did take a big step in that direction by growing the beta team to larger than it has ever been before (under Magix) for VEGAS 20, and also completely changing the way the beta team communicates with the developers, both of which have already resulted in big stability gains in recent versions/builds.

Last changed by fr0sty on 9/14/2022, 2:44 PM, changed a total of 2 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)

pierre-k wrote on 9/14/2022, 11:12 PM

Are the new developers from Davinci's team? Joke.🤭

relaxvideo wrote on 9/15/2022, 1:00 AM

1. Stability

2. Smooth playback.

3. Really: smooth playback. Without any fx a simple cut is not perfect with h264 or h265 files. I always see dropped frames at cutpoints. Why not think in advance? Decode the next events on timeline in parallel. I used to edit this way in early 2000's (of course with dv avi or mpeg2 files) with Edius or other apps. But with Vegas i still cannot do in 2022 :(

Elynde wrote on 9/15/2022, 1:22 AM

Smoother playback in the preview window please. I have tried every "fix" I can find on the matter, and it is still guesswork on how a project will look because the preview window is so lagged.

alifftudm95 wrote on 9/15/2022, 1:34 AM

Update existing OFX with mirror padding functions.

PC DEKSTOP

CPU: Ryzen 9 5900x

GPU: RTX2060 6GB

RAM: 64GB 3200MHZ

Storage:

C DRIVE NVME M.2 1TB SSD GEN 4

D DRIVE NVME M.2 2TB SSD GEN 4

E DRIVE SATA SSD 2TB

F DRIVE SATA SSD 2TB

G DRIVE HDD 1TB

Monitor: BenQ PD2700U 4K HDR

 

 

 

Gid wrote on 9/15/2022, 4:30 AM

Ways VEGAS Can Improve - Video FX search finds presets not just the main categories.

Magix Movie Studio Platinum 2023 - from 2004-ish - Latest version,
Vegas Pro 20
Vegas Pro/Post 19 (Latest build), HitFilm Pro,  
Boris Continuum, Sapphire, Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, Optics,
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans

I'm 53, I've been a UK joiner for 37yrs, apprentice trained & time served, I make videos about my work & post them on Youtube so that i can share what I've learnt over the yrs,
https://www.youtube.com/c/Gidjoiner

At the moment my filming is done with a Samsung Galaxy S21 Ultra 5G

Kinvermark wrote on 9/16/2022, 1:08 PM

My "top 3" (non-feature request) Improvements:

1) Performance: Not just HEVC hardware support, but also implement the tools needed to make difficult high bit-rate camera formats playable. This implies a modernized proxy system and intelligent "selective pre-render" that works as a proper cache (i.e. doesn't reset when I sneeze)

2) "Professionalize" the codec support: this means supporting SOURCE TIMECODE!!!!! (which implies .MOV containers rather than just .avi or mp4) and 10 bit grassvalley, AVID DNX, and maybe Cineform (legacy). Prores is great, but still no source timecode support, and we are on MS-Windows after all, not Mac OS.

3) Better project interchange with other programs. Vegas is too small to be its own island. XML interchange partly works, but needs to be upgraded/updated. I need mixed frame rate timelines to work, as well as end fades, etc. Native timeline support for exporting a Davinci .drt file format would be the best for me - if possible.

BONUS SUGGESTION: (as is is related to above) - No more creating .sfk etc. FILE SPLATTER! These kinds of files need to be coralled into a subfolder at minimum; a user specified location at best.

Thanks for reading!

 

Howard-Vigorita wrote on 9/18/2022, 9:34 PM

My 3 pie-in-the sky requests would be for: 1) better scripting, 2) decoder plugin support, and 3) better encoders

Better scripting would include save and restore of all preferences and settings including internal. As well as startup and exit scripts.

Decoder plugin support would allow plugins to replace all current decoders and video level mapping schemes.

Better encoders would include adding lossless compression encoding formats like ffv1, hevc, and av1 and the ability to use them as intermediates.

And double precision compute and internal storage for audio and video data... my 4 pie-in-the sky requests would be for....

jetdv wrote on 9/19/2022, 9:20 AM

As well as startup and exit scripts.

@Howard-Vigorita This can already be done. You can tell VEGAS to run a script upon startup. You just start VEGAS from a batch file something like:

"c:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe" -SCRIPT:"d:\StartupScript.cs"

Plus, Custom Commands can monitor for "AppInitialized" which would occur on the startup of VEGAS and also monitor for "AppWindowClosing" and "AppWindowClosed" which might be useful for an exiting script. I'd have to do some testing to verify exactly how these event handlers work.

What are the types of things you're wanting to do on startup and exit?

DrinkyBird wrote on 9/19/2022, 9:44 AM
  1. Performance. Yes it's already been mentioned, but it's still important. Compared to other products VP's playback performance can be quite poor. Evidently it's not awful - it's good enough that when combined with its overall workflow and functionality, VP still wins over all others - but it could be so much better.
  2. Formats. Finish the existing experimental Matroska reader, with full GPU acceleration and the like - AVC in MP4 and AVC in MKV should be functionally identical. Add support for decoding and rendering VP8, VP9, AV1 video and Opus audio; in Matroska, WebM, and Ogg formats (as applicable), with GPU acceleration when available.
  3. A more minor thing... the stream labels feature I requested some time ago would also be nice.

Last changed by DrinkyBird on 9/19/2022, 9:45 AM, changed a total of 1 times.

OS: Windows 10 20H2
CPU: Ryzen 7 2700X
RAM: 32GB DDR4-3000
GPU: NVIDIA GeForce RTX 3060 Ti Founders Edition 8GB
Storage: Samsung 970 EVO Plus 1TB, Samsung SSD 870 QVO 2TB, Seagate FireCuda 2TB, Seagate BarraCuda 4TB
Sound: Creative Sound Blaster Z SE

Reyfox wrote on 9/19/2022, 9:53 AM

All the above for sure. Vegas has made tremendous strides in adding necessary new features to keep the software current.

But... the title editor needs a ton of help.

No sense in repeating what was written above. BUT what about Vegas Post?

Greg-Kintz wrote on 9/19/2022, 4:42 PM

Three suggestions:

1) Stability: Starting with Vegas 18 and more so with Vegas 19, I've had more cases of crashes. Sometimes while working, sometimes while going to render. I don't have it as bad as some of the others here have had it, but let's put it this way- I've learned to continually hit save all the time, as the auto recover doesn't always do its job. Sometimes if I don't need the latest features or certain codecs, I'll use my older Vegas 12 or 13 as those older versions respond quicker and are far less likely to crash. I am currently on Vegas 19 build 550. Was going to go download the latest version of 19 but when so many were scrambling to uninstall the latest version and go back to 550, I held off. And this was close to this summer, so Vegas began focusing on version 20. No more updates for V19. I've been updating versions sense V12 but it seems now is a good time at least for me to pause as the improvements for the money are quite negligible. And stability again is a bit like a roulette wheel.

2) HDR support for professional codecs. Vegas has had HDR output support for H265 which in the pro world is strictly a final delivery codec. If you make something in HDR and want to save to an intermediate codec, lossless or render to a well established pro standard like DPX or ProRes with HDR, Vegas currently cannot deliver. Now Magix has make good progress in slowly getting ProRes certification, which is great as ProRes is one of the defacto standards in the industry. But it also needs ProRes with full HDR metadata support. Likewise for DPX.

3) Lossless multichannel audio and multiple stream muxing for ProRes encodings. If you deliver a ProRes file to a major network, cable provider, streaming service, or authoring facility, they will often ask for a lossless version of your 5.1 audio, a stereo downmix, alternate language tracks, and/or descriptive serves track. All muxed in one prores stream. Vegas can currently do all of these functions, but not muxed together in a ProRes encoding. ProRes in Vegas is currently 2.0 stereo audio only, locked in at 16bit/48k.

 

Show me a giant improvement in #1, or.. even adding #2 and/or #3 and I'm back in.