Cool of you all to show 15 some more love even though you're probably well on your way to making 17 a reality by now. I'm sure those who haven't jumped ship to 16 yet are very appreciative. That said, I see you added BM mini-monitor support and it isn't even in 16 yet... PLZ add it soon! That = 10 bit output for me without having to buy an expensive pro-level GPU, since I already bought a mini-monitor for Resolve.

It is worthy to consider this fair play from Magix. Thanks.

That said, I see you added BM mini-monitor support and it isn't even in 16 yet... PLZ add it soon!

Update 2 of VP 16 should have this support in it. For some reason it was missed in the release notes.

Nice to see those of us still on Vegas Pro 15 haven't been left behind.

That said, I see you added BM mini-monitor support and it isn't even in 16 yet... PLZ add it soon!

Update 2 of VP 16 should have this support in it. For some reason it was missed in the release notes.

It only shows one decklink device in my preferences menu. I have both the decklink studio 4k as well as the mini-monitor 4k. It has always seen the studio, but I can't use it for monitoring due to it only having SDI outputs, so I only use it for capture. The mini-monitor doesn't do anything if I plug it in and select blackmagic decklink from the output device menu, even if the studio 4k is disabled in device manager.

@VEGAS_CommunityManager, thanks for your support of the users in releasing build 416! However, I seem to have come across a memory leak bug in V15b416.

I have 32GB RAM and 64GB swap, and it takes about 5-10mins for the Memory Commit to keep growing and exhaust the total virtual memory available and then it crashes my machine to a black screen that needs a hard reboot. Needless to say, I lose my work 😕

https://www.icloud.com/photos/#0-kDIYweM0zAPOFQZ-8Q5DMNw

If you will reach out to me, I would be happy to assist in troubleshooting and resolution.

Many thanks to the Magix-Vegas-Team! Very, very fair!!!!!!!!

Any chance of getting the policy of not allowing old versions to be sold on changed?

Thank you, thank you, thank you!

Looking forward to download and install it today as my last "show stopper" is fixed in this update!

Any chance of getting the policy of not allowing old versions to be sold on changed?

I wasn't aware that you couldn't. Anyway Item 7 of the EULA refers and my reading of it is that yes you can provided you follow what it says. If I'm wrong then hopefully someone will correct me.

That said, I see you added BM mini-monitor support and it isn't even in 16 yet... PLZ add it soon!

Update 2 of VP 16 should have this support in it. For some reason it was missed in the release notes.

It only shows one decklink device in my preferences menu. I have both the decklink studio 4k as well as the mini-monitor 4k. It has always seen the studio, but I can't use it for monitoring due to it only having SDI outputs, so I only use it for capture. The mini-monitor doesn't do anything if I plug it in and select blackmagic decklink from the output device menu, even if the studio 4k is disabled in device manager.

I have Intensity Pro (PCIe) and Decklink Mini Monitor, and the Intensity has always sort of worked with Vegas, but not the Decklink Mini Monitor, though it works with Davinci and Adobe, so it is Vegas, and I downloaded this even though I have both 15 and 16 installed, but to NO AVAIL...same as you, just shows ONE INSTANCE of BM card.. Why does Vegas put out false announcements, or tell me what I need to know here... @MathiasH .somebody, anybody?

I just updated to the latest build of VP15 and may have stumbled across a bug.

I tried to selectively prerender an event using Magix AVC with VCE and that didn’t work. The project is a 4K project with XAVC-S files from my a6300. I can see the prerender is running but when finished I don’t get the bar across the selected section indicating the prerender and the playback is slow which means Vegas doesn’t read the prerendered file. It does however work with other codecs like XDCAM and even MagicYUV. Can somelese with an AMD card and VCE confirm my findings?

Thank you for these bugfixes. I held off on 16 as 15 never became stable enough for me to use reliably (various GPU issues) and didn't want to get burned again.

This commitment to stability makes me think more positively of Magix.

Any chance of getting the policy of not allowing old versions to be sold on changed?

I wasn't aware that you couldn't. Anyway Item 7 of the EULA refers and my reading of it is that yes you can provided you follow what it says. If I'm wrong then hopefully someone will correct me.

The poster might mean not Magix not selling old software versions to consumers rather than transfers of used software.

The poster said "sold on" so I assumed it was the latter. But you may be correct. Renton-Maclachlan needs to clarify if he still has the problem.

Is this update applicable to Move Studio 14 Paltinum?

I am currently using Version 15.0 (Build 157)

Cheers

No, it is a Vegas Pro 15 update.

I tried to selectively prerender an event using Magix AVC with VCE and that didn’t work. The project is a 4K project with XAVC-S files from my a6300. I can see the prerender is running but when finished I don’t get the bar across the selected section indicating the prerender and the playback is slow which means Vegas doesn’t read the prerendered file. It does however work with other codecs like XDCAM and even MagicYUV. Can somelese with an AMD card and VCE confirm my findings?

@OldSmoke: I can confirm this issue. I've tested it with VP15 and VP16. I used the Red Car HD project for that. When rendering with VCE, no pre-rendered file is created. Rendering in a new track does not cause problems with VCE.

I have to tell something here. Almost all my issues with VP15 stability has gone even before this update after I upgraded my memory from 16 to 32 GB RAM. Now I can work flawlessly as I can with VP14. Good to see some other bug fixes. Now I would like to try VP16 again, but my trial has expired.

hi, just wondering if anyone could direct me with helping to eliminate the blue sky color distortion I see when viewing or rendering either video or photos on my Vegas Pro 15 editing package. See the two attached photos. The same photo was displayed with a photo or media program and the bright blue sky was captured. As soon as I brought the same image into the Vegas Pro 15 and displayed it on the same monitor (or even the preview monitor), the sky turned the dark grey and all color was lost.

I suspect I've have a setup problem, but cannot figure out what to change.

thanks for any help, vic borgogno

Do you have the Chroma Key FX applied by accident?

Marco, I did check a lot of items thinking it might be something like the Chroma Key effect, but couldn't find the culprit. However, I did accidentally discover the "Split Screen View" (4th item over from the left jut above the preview window) had an item called "Select All"; after clicking on that the blue sky came back. In trying to go back to the grey sky, I couldn't get back to the original problem by clicking on any of the items under "Split Screen View".

So, I'm off and running once again, or so I thought! Then the Vegas Pro 15 version 416 crashed once again and upon bringing the program up, it had the entire video in grey scale. Once again I went to the "Split Screen View" and tried the "Select All", no change with any of the options. Then I remembered another Post that mentioned "Overlays" and some of the grey-scale selections at the bottom of that drop down; sure enough the "Green as Grey-scale" had been checked by the Vegas Pro 15 version 416 crash.

A side note: have you purchased Vegas Pro 16? I have been quite frustrated and frankly discouraged by the crashes, but more so by the notification of SW updates, or the lack of notification. I have been having crashes on just about every version of SW from Vegas Pro 14 onward, so I don't expect Vegas Pro 16 to be any different. One can always hope that someone has some good words concerning the Vegas Pro 16 crashing or lack thereof.

I am back running again, so thanks for your concern

vic