Comments

Steve_Rhoden wrote on 9/15/2022, 4:35 PM

@m3lquixd The preview window can be docked anywhere you like, the interface layout is 100% adjustable.

 

m3lquixd wrote on 9/15/2022, 6:07 PM

@m3lquixd The preview window can be docked anywhere you like, the interface layout is 100% adjustable.

 

This video did not help me. As far as I know vegas does not allow to set the preview in the right corner of the screen next to the timeline as I showed in the image. What I did was an improvisation, which is how I am currently having to use it.

About me:
Hi! Melqui Calheiros Here. I've been using Vegas as my only video editor for over 10 years. I edit professionally for various influencers, public bodies and small businesses. My goal is to squeeze Vegas to the fullest! And end the prejudice that software has here in Brazil.

⬇️ Some of my jobs. ⬇️
https://www.vegascreativesoftware.info/us/forum/post-your-vegas-creations--109464/?page=37#ca872169

PC Specs:
Operating System:
    Windows 11 Pro 64-bit
CPU:
    AMD Ryzen 3 3200G 3.60 GHz
RAM:
    16,0GB Dual-Channel DDR4 2666MHz
Motherboard:
    Gigabyte Technology Co. Ltd. A320M-S2H-CF (AM4)
Graphics:
    4095MB NVIDIA GeForce GTX 1650 (ZOTAC International)
Storage:
    465GB Seagate ST500DM002-1BD142 (SATA )
    238GB Lexar 256GB SSD (SATA (SSD))

DoctorOfMusic wrote on 9/18/2022, 4:21 AM

Yeah, the usual rude comments and disrespect towards the Vegas developers !

 

If you NEED your software to work "well", and you get a myriad of problems, like CHUGGING previews, frequent time line crashes and artifacts...it gets a little frustrating.

I have three copies of Vegas 19. Crashes have dropped to very, very few. But the CHUGGING on three different computers with three different versions of hardware at standard 1080p...is just not gonna cut it against Davinci Resolve.

I have not decided if I am going to make the move. I've tried everything for a stable, consistent Vegas experience. I dunno. Perhaps the final straw is the fact after buying three Vegas 19 licenses I find out I have to buy a Vegas 360 license to get the text to speech...thats almost sealed my move to DaVinci.

I am absolutely not going to be rude — I understand that the Vegas development team is small & doubtless under a lot of pressure. And I've seen the argument that their limited time is better spent adding new features than dealing with 'core' issues. I also appreciate that some progress has been made in some areas, which is good.

But I'd like to offer an alternative view. I think time spent dealing with the fundamental issues of sluggish playback performance, crashing (mostly when editing on the timeline) and better handling of 4K & 8K video would be time well spent, because people *would be prepared to pay for it*.

I was inspired to write this post by comments others have made on the forum — "same old choppy playback" — "still crashing on 4K media" — "would love to stay but am learning DaVinci Resolve"... etc.etc. And I think a lot of the people making comments like this *really would* prefer to stay with Vegas Pro, but are finding these absolutely fundamental issues so frustrating, they are planning to move elsewhere.

AFAIK DaVinci Resolve, Premier Pro, Final Cut Pro, Avid do not suffer from these problems.

My situation is that I bought VP15, having seen how much better NVidia graphics cards were supported. It was a revelation at the time. But the legacy Sony sluggishness & instability was still there, so I thought I'd wait and see if that improved. I try the demos of every new Vegas Pro release, and although I can see many improvements (not least, I love the way it looks now) but those fundamental problems **are still there**. So I muddle through with VPro 15 (usually still adequate) and am looking seriously at learning Resolve.

But bring me Vegas Pro 21 with a completely rewritten Core Video Handling Engine (or whatever is required) and my credit card will be on the table in an instant, to purchase the latest version. I would be prepared to pay for a ground-up rewrite which fixed the sluggishness/stability issues **with no new added features at all** — and I would pay willingly. Because once these problems had been fixed, then Vegas could carry on from strength to strength.

I suspect quite a number of people who post here, or possibly just read this forum, would feel the same way?

Komaryt wrote on 9/19/2022, 6:28 AM

3. Occasionally I have black screens in rendered footage. Sometimes it is at start of movie, sometimes it is in middle of movie. In 60-90minutes movies it is hard to see it and I need to render it again. On timeline everything is alright but it happened after rendering.

@Komaryt
There are a few threads on black frames - have you used the forum search?

yes I did. Nothing works.

Is there any idea how to turn off adding rendered clips on timeline after rendering?

flyerstl wrote on 9/19/2022, 9:34 AM

I searched but did not find anything on this: Quantize to Frames. I see that "turn off for audio only edits" has moved to the Prefs/Editing, but when this box is checked, altho on the timeline I can now to audio edits less than 1 frames, in the trimmer window, it's still quantized to frames, so I often can't find the beginning of a sound, for instance, precisely. Thx.

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

flyerstl wrote on 9/19/2022, 11:35 AM

This one still bugs me: I can't figure out how to get this to work properly:

Enable Automatic FX Window Resizing (last click box under General Prefs). No matter which way I check this, the FX windows still resize automatically, and since I run audio plugins in series, I often have 4-5 plugins in a row, so making the window large and staying that way is easier for me to make adjustments, rather than clicking the LEFT-RIGHT arrow keys to get from one plugin to another. Any thoughts on this?

And whilst we're here, here's a couple more quirks and they may just be with my system, i dunno.

--Sometimes when refreshing the EXPLORER folder, it becomes inactive and I have to close that tab, and then open it back up, and it takes up to 30 seconds before I can do anything again.

--In ProTools there's a way to have more than one audio plugin window active. You use CTL or ALT-click to do it. I often like to keep a VU meter on my master fader, but still want to be able to adjust EQ and things on other tracks without having to open/close/resize, etc. Is this possible?

Loving V20 otherwise.

jmm in ST Louis

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

MyChain wrote on 9/19/2022, 11:43 PM

Close Caption should be improved and developed to be modern and easy to use.

Thanks

@MyChain it is something that they are interesting in implementing (CEA 708 CC natively), as soon as they can, but it is unclear when that will be.

I hope Magix will develop and improve Closed Caption to make it easier to use. and supports multiple languages.

Robert Johnston wrote on 9/20/2022, 1:14 AM

In Color Grading on the new Utilities tab, using the White Balance picker for neutral seems to give wrong results. For example testing the picker on Gray Solid Color (RGB:128,128,128) dragged from the Media Generator to the timeline turns the solid color to RGB:131,125,131. Having a hard time getting things neutral in other images.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro

Martin L wrote on 9/20/2022, 4:23 AM

Copying audio event and pasting attributes to another doesn't work, neither does selectively pasting. As for now you have to add effects to each audio event separately.

flyerstl wrote on 9/21/2022, 1:13 PM

Here's a new one: in earlier versions, double clicking on a folder name in Explorer window would open up that folder. now when you dbl click the name, it highlights the folder name, as if in Windows you were going to rename it, but then Vegas becomes unresponsive for several seconds, "Vegas is not responding". Eventually, you get control back and in some cases the window does actually open up. It's almost like it's indexing or something. The workaround is to double click ONLY on the yellow file folder icon (but it's much smaller and harder to hit for us old timers). See attached photo. jmm


 

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

MarkAnthony121 wrote on 9/21/2022, 5:46 PM

Yeah, the usual rude comments and disrespect towards the Vegas developers !

 

If you NEED your software to work "well", and you get a myriad of problems, like CHUGGING previews, frequent time line crashes and artifacts...it gets a little frustrating.

I have three copies of Vegas 19. Crashes have dropped to very, very few. But the CHUGGING on three different computers with three different versions of hardware at standard 1080p...is just not gonna cut it against Davinci Resolve.

I have not decided if I am going to make the move. I've tried everything for a stable, consistent Vegas experience. I dunno. Perhaps the final straw is the fact after buying three Vegas 19 licenses I find out I have to buy a Vegas 360 license to get the text to speech...thats almost sealed my move to DaVinci.

I am absolutely not going to be rude — I understand that the Vegas development team is small & doubtless under a lot of pressure. And I've seen the argument that their limited time is better spent adding new features than dealing with 'core' issues. I also appreciate that some progress has been made in some areas, which is good.

But I'd like to offer an alternative view. I think time spent dealing with the fundamental issues of sluggish playback performance, crashing (mostly when editing on the timeline) and better handling of 4K & 8K video would be time well spent, because people *would be prepared to pay for it*.

I was inspired to write this post by comments others have made on the forum — "same old choppy playback" — "still crashing on 4K media" — "would love to stay but am learning DaVinci Resolve"... etc.etc. And I think a lot of the people making comments like this *really would* prefer to stay with Vegas Pro, but are finding these absolutely fundamental issues so frustrating, they are planning to move elsewhere.

AFAIK DaVinci Resolve, Premier Pro, Final Cut Pro, Avid do not suffer from these problems.

My situation is that I bought VP15, having seen how much better NVidia graphics cards were supported. It was a revelation at the time. But the legacy Sony sluggishness & instability was still there, so I thought I'd wait and see if that improved. I try the demos of every new Vegas Pro release, and although I can see many improvements (not least, I love the way it looks now) but those fundamental problems **are still there**. So I muddle through with VPro 15 (usually still adequate) and am looking seriously at learning Resolve.

But bring me Vegas Pro 21 with a completely rewritten Core Video Handling Engine (or whatever is required) and my credit card will be on the table in an instant, to purchase the latest version. I would be prepared to pay for a ground-up rewrite which fixed the sluggishness/stability issues **with no new added features at all** — and I would pay willingly. Because once these problems had been fixed, then Vegas could carry on from strength to strength.

I suspect quite a number of people who post here, or possibly just read this forum, would feel the same way?

As a wedding filmmaker I would GLADLY dish out $800+ for Vegas that works as you mention above. I was just editing today and it breaks my heart when I get 5 crashes per day, and the micro input lag especially when hitting "s" to cut and it not registering makes me want to pull my hair out. I'd love to pay for a version of Vegas on which I could edit 4K Canon R5 CLOG3 footage without proxies. I'm totally with you. My situation is literally like yours. I've stuck with Vegas through so much ridicule from colleagues since 15. So for me 21 would be my last attempt to stick it through before moving on to learn something new.

Ronald-Henderson wrote on 9/21/2022, 6:36 PM

I like the features of being able to import project files from othere NLE's, and it would be really nice to be able to import other VEG project files into the timeline, but not as nested files.

GloriaGloria wrote on 9/27/2022, 11:59 AM

I have been block from downloading the trial version of Vegas Pro 20 I stopped Chrome by setting off safe browsing and started to download and then again was blocked and I do not know what to do! Any one can help me please... I also se of the Controlled folder access and even though do not let me download

vkmast wrote on 9/27/2022, 12:02 PM

Have you tried to use a different browser?

@GloriaGloria

GloriaGloria wrote on 9/27/2022, 12:20 PM

I just right now happened to downloaded but I do not know how to open!!!!

GloriaGloria wrote on 9/27/2022, 12:25 PM

Just by being kind to me and answer me I just managed to do everything and open the program... many thanks for your kindness!!!! May God bless you...and your family!

GloriaGloria wrote on 9/27/2022, 12:29 PM

But I must add that I thought I was going to be able to open an mp4 file, because in my Vegas Pro 19 does not open them... does not show the video just the sound... well exactly the same in Vegas Pro 20, they did not fix the problem!!!

RogerS wrote on 9/27/2022, 12:32 PM

@GloriaGloria VP does open MP4 files. This particular file may not be supported in Vegas though. What's in the file? Use MediaInfo to answer:

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

If it's HEVC, you could try disabling the legacy HEVC decoder in preferences/ file io and see if that helps.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with 31.0.101.4091 driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (driver 31.0.101.2115), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.648
Vegas 20.270

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

kinetik wrote on 9/27/2022, 1:52 PM

when vegas will be version 30 we will be still crying about the program not being able to preview smoth footage 😆 and no proxies is not the solution...all development should be targeted to this PROBLEM-- we dont need new features..we cannot edit this way its crazy

j-v wrote on 9/27/2022, 2:05 PM

@kinetik
Sadly I do not belong to your "we".

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 22H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
537.42 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2125
Laptop  :Asus ROG Str G712L, W11 home version 22H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 537.42 and Intel UHD Graphics 630 with driver 31.0.101.2125
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)
 

GloriaGloria wrote on 9/27/2022, 2:16 PM

@GloriaGloria VP does open MP4 files. This particular file may not be supported in Vegas though. What's in the file? Use MediaInfo to answer:

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

If it's HEVC, you could try disabling the legacy HEVC decoder in preferences/ file io and see if that helps.

No... you are not going to believe me. I got a file direct from my Sony NXCAM and when I finished doing things on it on Vegas Pro 19 I render it mp4 and save it. I went out of the program and later went to open it and did not show the video just the sound!!! Even though was done the mp4 trough the very Vegas Pro 19.... To tell you the truth it is very annoying because a had a Vegas Pro 13 and I was able to work with the mp4s I paid 150US for the upgrade and since then I can not use it!!!!!

j-v wrote on 9/27/2022, 2:20 PM

Vegas Pro 19 I render it mp4 and save it.

Can you give a screenshot of the exact rendertemplate you used?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 22H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
537.42 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2125
Laptop  :Asus ROG Str G712L, W11 home version 22H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 537.42 and Intel UHD Graphics 630 with driver 31.0.101.2125
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)
 

Timur wrote on 9/28/2022, 5:31 AM

The search bar doesn't work Preferences:Internal

Greg-Kintz wrote on 9/28/2022, 10:17 PM

3. Occasionally I have black screens in rendered footage. Sometimes it is at start of movie, sometimes it is in middle of movie. In 60-90minutes movies it is hard to see it and I need to render it again. On timeline everything is alright but it happened after rendering.

@Komaryt
There are a few threads on black frames - have you used the forum search?

yes I did. Nothing works.

Is there any idea how to turn off adding rendered clips on timeline after rendering?

I occasionally had the same issue. For me, it was disabling the graphics card for rendering that fixed it.