VEGAS Pro 18 Update 2 (Build 373) - General Discussion

Comments

Robert-Higgins wrote on 11/10/2020, 10:05 PM

If you click on the Info's off the error reports< you can read and provide here by the upload link that info.
Further: reïnstalling does not help you much, you have to do a full reset following this Link exactly and not change some in the settings of Vegas 18 after you did that: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

 

Robert-Higgins wrote on 11/10/2020, 10:06 PM

It appears that helped a lot. Sorry for all the bad mouthing on my part. I never knew about full reset, wished I would have known about that from the start. Anyway thanks for the help.

j-v wrote on 11/11/2020, 3:29 AM

Glad for you it did help.👍

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 21H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti, Intel HD graphics 630
Laptop  :Asus EVO37T, W11 home version 21H2, CPU i7-10875H, 16 GB RAM, Intel UHD Graphics + NVIDIA GeForce RTX 2070. VP 19, 20 and VMS PL 17 are installed, all latest builds, Nvidia GPU driver version 517.40 Studiodriver and Intel GPU
driver 31.0.101.2111
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR !!!

Older Dutch tutorials of 3POINT and me: https://vimeo.com/vegasvideoforum

Len Kaufman wrote on 11/12/2020, 10:29 AM

This is an issue that probably only affects a small percentage of users, but I thought I'd present it here. If you go into the lens correction feature, the correction for my Lumix 12-60 3.5-5.6 is much worse than without the correction. Please take a look at this screen shot of with and without. I'm editing on 2 screens, so it's a very wide screen shot, but I included both screens so that you can see in which the lens correction is checked. With correction (horizon very distorted) Without correction (horizon straight)

EricLNZ wrote on 11/12/2020, 4:00 PM

@Len Kaufman If the horizon is straight to start with I would assume there is no distortion so why correct it? "Correcting' then adds distortion? Or maybe I'm misunderstanding.

Len Kaufman wrote on 11/12/2020, 4:10 PM

Hi @EricLNZ. Thank you for your response. There are other corrections besides horizon. For example vignetting, etc. When I apply the Vegas correction, it makes some other corrections, though that horizon distortion is unacceptable.

dirk-g wrote on 11/12/2020, 6:00 PM

@Magix the download process within Vegas Pro is horrible. Spend an hour downloading, select one of the two options (as not sure which is better) and close program. Nothing happens. Open program, no change, other than notification of update available to download. Magix needs to fix this or make the specify proper steps as to not have any installer after all that ... full waste of time! Very frustrating. How about just point users to the download link if you can't make this process work?

That's my issue. Prompts me to do the update, but when I do, it says it can't update while Vegas is running. But Vegas *isn't* running when I attempt to do the set-up.

I'll just leave it be for now.

RogerS wrote on 11/12/2020, 7:41 PM

This is an issue that probably only affects a small percentage of users, but I thought I'd present it here. If you go into the lens correction feature, the correction for my Lumix 12-60 3.5-5.6 is much worse than without the correction. Please take a look at this screen shot of with and without. I'm editing on 2 screens, so it's a very wide screen shot, but I included both screens so that you can see in which the lens correction is checked. With correction (horizon very distorted) Without correction (horizon straight)

I asked a while ago how to deal with zoom lenses as I don't see a place to enter the focal length. Your lens probably has barrel distortion on the wide end but not the other end and if you apply the barrel distortion fix for 12mm to other focal lengths it will dramatically overcorrect.

So I think this feature is useful for primes but not for zoom lenses at this point.

When you hover over the sliders it says "parameter of a PT Lens model", so I assume it's using that lens database. I actually use PT Lens for photos and it has values for Make/Model/Lens and then focal length. Without that last one I don't think it's useful.

Len Kaufman wrote on 11/12/2020, 11:00 PM

@RogerS

Thank you. I think that's the answer. I can't imagine the amount of work to test all of those lenses. And then at multiple focal lengths for the zooms? Whew!

 

mark2929 wrote on 11/21/2020, 2:00 PM

Any news about prores RAW?

lenard wrote on 11/21/2020, 7:48 PM

Any news about prores RAW?

I don't believe you'll ever see it on Vegas Pro. Vegas apologists usually say 'small team' and 'corona' as any defence for bugs or lack of updates/features and for something like a proprietary codec they'll say licencing is too expensive for a small company like Magix, but edius got prores raw support while having a small team in this time of corona. Also cost is not an issue with Blackmagic RAW ,The codec is open and free, supported via the free SDK and and there are no hidden licenses or ongoing fees. Edius also support BRAW, but it's not available in vegaspro.

 

cyvideo wrote on 11/21/2020, 8:36 PM

Hi All.

Just running into a problem in build 373 which is stopping me using it as the video levels it is displaying are incorrect. Totally not usable for broadcast levels. Shooting XAVC on Sony FS7 and in Vegas 16 the correct black levels are displayed when the 16/235 box is checked. In Vegas 18 build 273 through the black levels are totally incorrect when set for 16/235. They are a full 50mV under '0' black level. I think this is a bug unless I've missed something. Anyone else experience this level mismatch? Thanks in advance.

EDIT: Just realized if you drop the Vegas "Levels" plugin onto the head of the track selecting the preset "Computer RGB to Studio RGB" it then restores the blacks back to the correct levels. Trouble is it also reduces the rest of the video levels too much so not even a work-around. To me it's looking like a WFM bug... unless I've missed something obvious?

Chris - CYV Productions

EricLNZ wrote on 11/21/2020, 9:25 PM

@cyvideo Presumably you've looked at this thread https://www.vegascreativesoftware.info/us/forum/vp18-notes-on-the-8-bit-full-level-option--122749/

RogerS wrote on 11/21/2020, 10:23 PM

Any news about prores RAW?

I don't believe you'll ever see it on Vegas Pro. Vegas apologists usually say 'small team' and 'corona' as any defence for bugs or lack of updates/features and for something like a proprietary codec they'll say licencing is too expensive for a small company like Magix, but edius got prores raw support while having a small team in this time of corona. Also cost is not an issue with Blackmagic RAW ,The codec is open and free, supported via the free SDK and and there are no hidden licenses or ongoing fees. Edius also support BRAW, but it's not available in vegaspro

No news about ProRes raw. Magix last said they are still awaiting Apple approval. Nobody is saying anything about licensing or small team or pandemic in this context.

RogerS wrote on 11/21/2020, 10:27 PM

Hi All.

Just running into a problem in build 373 which is stopping me using it as the video levels it is displaying are incorrect. Totally not usable for broadcast levels. Shooting XAVC on Sony FS7 and in Vegas 16 the correct black levels are displayed when the 16/235 box is checked. In Vegas 18 build 273 through the black levels are totally incorrect when set for 16/235. They are a full 50mV under '0' black level. I think this is a bug unless I've missed something. Anyone else experience this level mismatch? Thanks in advance.

EDIT: Just realized if you drop the Vegas "Levels" plugin onto the head of the track selecting the preset "Computer RGB to Studio RGB" it then restores the blacks back to the correct levels. Trouble is it also reduces the rest of the video levels too much so not even a work-around. To me it's looking like a WFM bug... unless I've missed something obvious?

Chris - CYV Productions

@cyvideo As Eric pointed out, Vegas now handles levels conversion automatically in VP 18. If you want to keep the legacy levels functionality change product to 8-bit video (legacy). In 8-bit full, you no longer need to use computer to studio presets on output or to conform full range footage- Vegas takes all studio range footage and expands to full range for editing and then outputs studio range when you export. Uncheck studio range in scopes.

RogerS wrote on 11/21/2020, 10:33 PM

@RogerS

Thank you. I think that's the answer. I can't imagine the amount of work to test all of those lenses. And then at multiple focal lengths for the zooms? Whew!

 

Len, I found the database that has the rest of focal lengths for these lenses. https://github.com/lensfun/lensfun/tree/master/data/db
You can enter the values manually if needed.
If you're using Panasonic lenses on Panasonic bodies you should be able to do distortion correction internally, which saves doing it in Vegas.

If your lens isn't characterized, here is how to do it manually: https://www.vegascreativesoftware.info/us/forum/how-to-determine-distortion-parameter-for-vegas-lens-correction-plugin--125289/

It looks like this lens database was actually crowdsourced!

lenard wrote on 11/21/2020, 11:40 PM

 

No news about ProRes raw. Magix last said they are still awaiting Apple approval. Nobody is saying anything about licensing or small team or pandemic in this context.

I know that was said, but it could be corporate speak, which is why I bundled BRAW into the reply which has no licencing limitations, but isn't on Vegas either, if Braw codec was supported I'd be more inclined to believe the only reason apple prores raw is not available is due to Apple

RogerS wrote on 11/22/2020, 12:18 AM

 

No news about ProRes raw. Magix last said they are still awaiting Apple approval. Nobody is saying anything about licensing or small team or pandemic in this context.

I know that was said, but it could be corporate speak, which is why I bundled BRAW into the reply which has no licencing limitations, but isn't on Vegas either, if Braw codec was supported I'd be more inclined to believe the only reason apple prores raw is not available is due to Apple

I think we have to take what we are told at face value. The alternative is to effectively accuse others of lying to us and I don't think that's healthy for this forum.

On BRAW, this is what I read before and have no reason to believe it isn't true now as well. Magix is clearly focusing on fixing GPU support based on changes we've seen from VP 17 to 18 (like adding AMD decoding last year), and the contents of the VP 18 updates:

VEGASDerek wrote on 9/28/2019, 2:50 AM link

We have a very long backlog of format support requests which we would love to get to you and that include BRAW). The focus for our File I/O team over the last several released is to improve reading and rendering performance, which you all know. The reality of the matter is that without the current performance and GPU support work which we have been doing, many of these requested formats would been virtually unusable in VEGAS. We hope to get to work on new format support again in the not too distant future, but at the same time, we have a tremendous amount of code restructuring we still would like to do to improve general performance of VEGAS Pro.

With all that said, I do not want to discourage anyone from making a request for format support, even if it duplicates what others have requested. This will help us know which formats are in most demand at the moment and direct our efforts toward them."

If I could suggest priorities it would be to fix dynamic ram preview, improve support for variable frame rate footage, increase GPU utilization/performance, add recent HEVC file variants (like what the a7sIII puts out) and then implement new raw formats.

walter-i. wrote on 11/22/2020, 2:29 AM

I think we have to take what we are told at face value. The alternative is to effectively accuse others of lying to us and I don't think that's healthy for this forum.

+1
I think there are enough forums out there dealing with theories that are legitimately based on assumptions - it is enough if we stick to the technical and factual level here.

If I could suggest priorities it would be to fix dynamic ram preview, improve support for variable frame rate footage, increase GPU utilization/performance, add recent HEVC file variants (like what the a7sIII puts out) and then implement new raw formats.

+10

lenard wrote on 11/22/2020, 4:25 AM

 

I think we have to take what we are told at face value. The alternative is to effectively accuse others of lying to us and I don't think that's healthy for this forum.

On BRAW, this is what I read before and have no reason to believe it isn't true now as well. Magix is clearly focusing on fixing GPU support based on changes we've seen from VP 17 to 18 (like adding AMD decoding last year), and the contents of the VP 18 updates:

Corporate speak is not lying, you tell a truth to mislead.The truth being Apple have not given them the rights to decode their codec. Only magix know if that's unusual given what they provided in their application. The real truth as you believe it, is that GPU decoding performance is not good enough for either Prores raw or BM raw so if they had the rights it still wouldn't exist in vegas pro due to a lack of gpu performance

 

If I could suggest priorities it would be to fix dynamic ram preview, improve support for variable frame rate footage, increase GPU utilization/performance, add recent HEVC file variants (like what the a7sIII puts out) and then implement new raw formats.

If a company couldn't fix something (within financial constraints) the worst thing they could do is tell the public that, so if that ever is the answer for these various bugs that have been around for the longest time we'll never know . Modern Vegas is so dependant on the bolt-on so4 reader for GPU support and decoding modern formats of video yet that increases the instability of software by a large amount. Maybe they find in future the secret to stability and gpu performance is doing away with so4 reader forever and finding a replacement. At this VP18 timeline point it's core is sony vegas and bound by certain limitations, don't see that ever changing anymore.

Achille-Porzi wrote on 11/22/2020, 4:32 AM

Hallo to you. After Vegas Pro 16 and 17 and having tried ver. 18, 2 days ago buyied it at discounted price, with SF14, hoping to find a good program as prior versions. But in two days of light use found lot of problems, like no Media generator Tab, AI plugins not working and some crashes. Now i'll ask back my money and probably nevermore buy such problematic program.

Sorry for my English

vkmast wrote on 11/22/2020, 5:22 AM

This forum is a user forum and not able to give you back your money. Please see the advice here.

@Achille-Porzi

Achille-Porzi wrote on 11/22/2020, 9:02 AM

I know. Thanks. It was only to let you know the problem. I found that AI plugins don't work. This version of Vegas has many problems, hasn't it? Bye

wideseen wrote on 11/22/2020, 11:47 AM

I start Vegas Pro 18, acknowledge updating, it downloads and I opt for immediate install.
The app is automatically closed and then a pop-up says "unable to update ... while it is running".
I did a restart, closed every app and checked for Vegas related processes.
I update from build 284.

Please help.