VEGAS Pro 15 Update 8 (build 416)

MathiasH wrote on 11/21/2018, 7:41 AM

Dear Community,

We have now updated VEGAS Pro 15 to ensure a more stable version. Please be aware that updating an older version will not be a regular practice.

Regardless, we hope our VEGAS Pro 15 users appreciate the bug fixes we have implemented.

You can download the build 416 now at: http://rdir.magix.net/?page=7K7DXLMSUQYB

New Features

  • Custom frame rates can now be set when encoding using AMD and VCE render templates in the MAGIX AVC/HEVC formats
  • An update notification feature has been added in order to keep in better touch with users when new product updates and fixes are available    
  • Time Stretch/Pitch Shift capabilities have been added to Scripting API for Audio Events

Bug Fixes

  • Pasting event attributes from one generated media event to another with different properties now works properly
  • Renaming certain files in the Explorer window no longer causes a crash
  • Audio recorded using Quicktime on a Macbook Air no longer get corrupted by so4compoundplug
  • The ExpandTrackGroup method in the TrackGroup class for scripting no longer collapses an already-expanded track group
  • Overwriting files when rendering with AMD VCE templates now properly reports file size
  • The Internet HD 720p 29.97 fps (AMD VCE) template now yields the proper framerate
  • Audio recorded using Quicktime on a Macbook Air no longer get corrupted by so4compoundplug
  • The Neat Video (and other temporal effects) now works properly when placed before Pan/Crop in an event FX chain
  • Paste Event Attributes no longer incorrectly adjusts Pan/Crop settings
  • Stand-alone preview and capture DeckLink cards, such as DeckLink Mini Monitor or Mini Recorder, are now properly supported
  • Overwriting files when rendering with AMD VCE templates now properly reports file size
  • Internet HD 720p 29.97 fps (AMD VCE) template now render with the proper frame rate
  • The render destination folder is now used for temporary file creation during the render process to avoid inadvertently filling up the user's C: drive
  • Event Pan/Crop animation now works properly on events that hold still images
  • All files now retain Markers & Regions in Trimmer
  • Right Alt+z and Shift+Right Alt+z now properly give users of the Polish localized version ż and Ż
  • Color Curve channel behavior has been improved so that changing the channel on one changes only that one and no others, and new curves are always added with the default settings instead of the settings from the previous curve worked with

Best regards,
Mathias

Comments

vkmast wrote on 11/21/2018, 8:13 AM

Vegas Pro 15 users, please note.

fr0sty wrote on 11/21/2018, 11:43 AM

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.

juan_rios wrote on 11/21/2018, 11:50 AM

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

MagixDerek wrote on 11/21/2018, 12:53 PM

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.

Cliff Etzel wrote on 11/21/2018, 1:21 PM

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

fr0sty wrote on 11/21/2018, 6:01 PM

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.

Wuster wrote on 11/21/2018, 6:50 PM

@MathiasH, 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.

walter-i. wrote on 11/22/2018, 1:56 AM

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

Last changed by walter-i. on 11/22/2018, 1:58 AM, changed a total of 1 times.

Camcorder: Pana HDC SD909, Sony FDR-AX53
Hardware: P8Z77-V LE Plus Vers.0910, Core i7-2600K 3,4 GHz, 16 GB Ram, Radeon HD 6870, SSD 250 GB, W7 HP 64
NLE: Vegas Pro11-15, Heroglyph4, RespeedR

Renton-Maclachlan wrote on 11/24/2018, 11:14 PM

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

fifonik wrote on 11/25/2018, 9:01 PM

Thank you, thank you, thank you!

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

EricLNZ wrote on 11/25/2018, 9:44 PM

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.

zdogg wrote on 11/27/2018, 2:43 AM

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?

OldSmoke wrote on 11/27/2018, 7:21 AM

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?

RogerS wrote on 11/27/2018, 8:05 PM

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.

RogerS wrote on 11/27/2018, 8:27 PM

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.

EricLNZ wrote on 11/27/2018, 9:37 PM

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.

mark-b8783 wrote on 12/8/2018, 9:20 PM

Is this update applicable to Move Studio 14 Paltinum?

I am currently using Version 15.0 (Build 157)

Cheers

vkmast wrote on 12/8/2018, 9:42 PM

No, it is a Vegas Pro 15 update.

matthias-krutz wrote on 12/10/2018, 5:41 AM

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.