I am running Vegas 17 and tried to install the update, but only got "Update cannot be installed with Vegas 17 running." I tried the "update when the program closes option with the same result.

As it is, it is still working. I just get nervous skipping updates.

please fix dual monitor

When I click on preview on external monitor Vegas 18 crashes. I've never have had this problem when using 17 or earlier versions. Also when I searched Google for this issue, I found that there were many others having the same issue. Please if anybody has any information on this I would appreciate some help if not Magix/Vegas please provide a fix.

527 is crashing more often than normal and now all my videos freeze. Audio plays fine but the video goes black. My main computer is pretty much useless. Is there any way to reinstall the previous build until this is patched out?

@Elijah-Black  ... the previous VP18 build 482 (the full program, not just the installer) can be downloaded from https://www.vegascreativesoftware.info/us/forum/vegas-pro-vegas-post-release-history--104998/?page=2

Of course, you will need to uninstall b527 before re-installing b482.

@Elijah-Black  ... the previous VP18 build 482 (the full program, not just the installer) can be downloaded from https://www.vegascreativesoftware.info/us/forum/vegas-pro-vegas-post-release-history--104998/?page=2

Of course, you will need to uninstall b527 before re-installing b482.

Incredibly thankful for this!

Hi everybody,

file i/o of build 527 does not work on my computer, I get corrupted video display as long as I do not switch back to legacy AVC decoding. There was no such problem with the previous release (that crashed rather often which was the reason why I updated immediately when 527 came out). I did not change anything on my computer besides update to build 527.

@OPUS please start a New Post with your issue and include a screenshot there. Thank you.

To those having issues, be sure to use the driver update utility in the vegas help menu to ensure you have the correct drivers.

Well, then. I tried logging into the Hub Explorer today and it let me in! Transferred a few files from my Android phone and Vegas Pro synced them fine. Everything seems to be working well.

Well, then. I tried logging into the Hub Explorer today and it let me in! Transferred a few files from my Android phone and Vegas Pro synced them fine. Everything seems to be working well.

How did u do that it says restricted for me idk y

Posting as before: support does not seem concerned that Build 527 will not start on my system (see attached) but whatever. Build 482 still works fine.

Here are my system details again:

Win 10 64-bit build 10.0.19042 on AMD MSI 7B79 Ryzen 7 3700x Graphics: AMD Radeon R9 360

NB: ALL Latest drivers installed

So... I did find the link to the last known good version of build 482 which runs fine on the above system. So why does build 482 run fine and build 527 does not?  According to the data, the issue appears to be a dll problem and not a driver issue.  Please advise. Thank you.

It looks that your gpu driver is not the right one.
Install the online version available at Help/Check for Driver Updates in VPro 18

Just a follow up on my 1st. post in this thread. I now also tested CLOG3, (is also hevc 10 bit 422, IPB and ALL-I) previously only CLOG. Loads and plays fine. There is an issue though if I select a pixel format of 32 bit "Full range". The Red channel gets raised and so the picture takes on an orange/red hue. This doesn't happen if I select 32 bit "Legacy range" or 8bit pixel format. This issue is there also with just Clog, though less pronounced.

I'm not that familiar with anything using a pixel format of 32 bit, but this seems odd.

While testing this VP crashed, no big deal since i'm doing all this on my laptop, But when I checked all of the boxes to send the crash report, at the end there was a link to click on and get more info. about this issue. So I clicked on the link. This link downloaded VP17 build 452 ??

Below are the RGB Parade 32 bit Legacy and Full screenshots, the Red was a little higher anyway to start with, but it clearly moves more with the "Full" setting.

32 bit Legacy range ............ 32 bit Full range

For 32-bit full range it reads file metadata (see what color space Vegas thinks it is and correct if needed). If view transform is set to a value other than off it will make further changes. I don't really understand what's going on behind the scenes either and prefer 32-bit video levels for that reason.

@Enea-Boscolo
If you want help, you should open a thread of your own and post detailed info there - something like this: Start at B: and C:
https://www.vegascreativesoftware.info/de/forum/important-information-required-to-help-you--110457/

For 32-bit full range it reads file metadata (see what color space Vegas thinks it is and correct if needed). If view transform is set to a value other than off it will make further changes. I don't really understand what's going on behind the scenes either and prefer 32-bit video levels for that reason.

@RogerS In media properties I had the Media's Colour space already set to default, I now changed to Canon Clog-3 to match the actual media. The garish orange image is even brighter! Using this Clog-3 Colour space setting in properties, but setting the Project Properties back to 32 bit video levels brings everything back to the usual washed out colour. So I guess then adding a Clog-3 lut would fix things up.

I'm not wishing to post this here as an issue for myself, that would require starting my own thread, I thought that it's odd and maybe Magix needs to see if there is something up with this 32 bit full range effect.

Ok. I noticed that when I was in (Project Properties) 32 bit Video levels that several items, 5, are greyed out. When I switched to "full" they become available, but the "Compositing Gamma" which was 2.22 (greyed out) in "Video levels" changed to 1.0 (Linear) in "Full range". Simply changing that value back to 2.22 fixed the colour shift. The other 4 greyed out items retained their same values when changing between Video levels and Full range.

older build version in case needed: https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-4-build-482--127859/

how do you uninstaill the newer version?

older build version in case needed: https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-4-build-482--127859/

how do you uninstaill the newer version?

Windows, Add or Remove Program

@Enea-Boscolo Just use Windows Add/Remove. In settings search Remove, Select Add or Remove Programs, click on the app and an uninstall option appears.

Hi,

@vkmast: Thanks for your reply.

This is what I see when I import an MP4 file (that looked fine in the prvious build) into build 527 using the default file i/o settings (some parts of the screenshot have been blurred by me):

All system and graphics drivers on up-to-date on my computer, though Vegas does not recognize the fact, that it is a AMD Ryzen system (Ryzen 9 4900HS, Nvidia GPU, 24GB Ram):

Maybe I should switch back to the previous build? Using legacy AVC decoding seem slower in build 527 than in the previous version, I have the impression that Vegas is not more stable than before (just sent a crash report), so far nothing won but something lost.

Yesterday Vegas let me know the update was available so I clicked on it and the download started after a minute or so but was very slow.

I had a client coming so canceled the download. I just opened VP18 to go ahead and update and didn't get the pop up so I went to Help/check for software updates and it states "no updates available."

I went to about and it shows the older version...how can I get the update?

how can I get the update?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-5-build-527--129047/