VEGAS Pro 14 Update 4 (build 211)

Comments

wsd wrote on 1/15/2017, 7:31 PM

By the way, is an update with improved compatibility even in the pipeline, or at least in the backorder list of fixes?

 

(And if test files in any codec these cams can create are needed, I can obviously provide them)

gary-rebholz wrote on 1/16/2017, 10:33 AM

Thanks wsd. Panasonic support (or more accurately, the lack of it) is a legacy of the former owner for somewhat obvious reasons. For equally obvious reasons, we are taking Panasonic support much more seriously now. Thanks for keeping me up to date on what you need.

wsd wrote on 1/16/2017, 11:15 AM

Thanks wsd. Panasonic support (or more accurately, the lack of it) is a legacy of the former owner for somewhat obvious reasons. For equally obvious reasons, we are taking Panasonic support much more seriously now. Thanks for keeping me up to date on what you need.


I am painfully aware what the historic reason is. Yet, P2 support started under Previous ownership, but never worked flawlessly. Magix must indeed drive the dagger home now, so to speak. And -at once- become a viable option in Pro NLE systems.

I am merely happy to hear that Panasonic is on the shortlist for updating support (whatever that will mean in reality). If I can be helpful in any way, please just ask. As you might have read, we have made the latest official sizzle real for a Panasonic camera (entry to medium level professional market) that is about to hit the market on Vegas Pro, it is nice to know that in the future Vegas Pro would support al pro cameras from the brand.

peter-ilyk wrote on 1/20/2017, 6:23 PM

Thanks wsd. Panasonic support (or more accurately, the lack of it) is a legacy of the former owner for somewhat obvious reasons. For equally obvious reasons, we are taking Panasonic support much more seriously now. Thanks for keeping me up to date on what you need.

Hi Gary Thanks very much for all your work with Vegas over the years and the great tutorial you used to provide with Sony Vegas. Will you be presenting similar tutorials with Magix Vegas? Also I wasn't aware that there was an upgrade to build 211 - I only came across this by chance. In the old days, whenever there was an upgrade you would get a message when you opened the program, but that does not seem to happen with Magic Vegas - at least not in my case. This would be useful to have in order to keep up to date with the latest builds.

gary-rebholz wrote on 1/23/2017, 8:44 AM

Thanks for the kind words peter-ilyk. We'll keep doing our best here. We have certainly discussed the issue of tutorials around here, but creating those was a full-time job for me back in those days, and with new my responsibilities, it's tough to figure out where to find the time to do them. As for the old "net notify" system, that unfortunately can't be supported through MAGIX systems. However, we are working on something similar and hope to have that implemented in a not-too-distant update. In the meantime, keep your eye on the News section here as all updates are announced here as soon as they're ready.

craig-meeks wrote on 1/23/2017, 3:45 PM

Installed the new patch! I've been using Vegas Pro for many many years simply because of it's speed of use. I'm all about quick turnaround times. For most jobs, I just haven't found another software that let's you get things done this fast. Keep up the great work Gary and the rest of the Magix team.

jwood wrote on 1/23/2017, 9:22 PM

Howdy - Is there a fix for loading in a ProRes file and not having audio? Vegas 13 works fine - but the same file has nothing for Vegas 14. Just wondering if I've missed something. I currently have build 211...Any assistance would be most appreciated! Jeremy

NickHope wrote on 1/24/2017, 1:17 AM

Howdy - Is there a fix for loading in a ProRes file and not having audio? Vegas 13 works fine - but the same file has nothing for Vegas 14. Just wondering if I've missed something. I currently have build 211...Any assistance would be most appreciated! Jeremy

No support yet for ProRes with multiple audio channels. I hope it's coming soon! One workaround is to rename C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\mxhevcplug to something else to disable the mxhevcplug.dll decoder and force Quicktime for Windows (qt7plug.dll) to decode the file. Bear in mind that your video will have more contrast if Quicktime decodes it.

jwood wrote on 1/24/2017, 10:18 AM

Thank you, Nick - changed the name to mxhevcplug2.dll - and it worked like a charm! I appreciate it. Take care.

set wrote on 1/24/2017, 2:42 PM

As Nick Hope states, the video will be more contrast if qt7plug.dll is used.

So, I think you can use qt7plug.dll to export the audio channels to separate WAV. Then get back to use mxhevcplug during editing (working with separate WAV audio and different video file).

Last changed by set on 1/24/2017, 2:43 PM, changed a total of 1 times.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

NickHope wrote on 1/24/2017, 11:23 PM

But also bear in mind, if you allow mxhevcplug.dll to decode the video, that the first frame of a 23.976/29.97/59.94fps ProRes file is repeated in VP14 build 211. I'm not sure if a frame is skipped between the 2nd and 3rd frames (haven't tested that) but it's safest to trim 2 frames off the beginning of every file on the timeline, either manually or by using this script.

JesusSheep wrote on 1/28/2017, 12:40 PM

Are you Going to Support 360 Editing and VST3 ?

gary-rebholz wrote on 1/30/2017, 10:11 AM

Are you Going to Support 360 Editing and VST3 ?

Both are certainly on our list, along with so many other things. So, as usual, it's a matter of difficult prioritization choices, and we'll have to decide where they fall in the list. Thanks for the nudge.

damian-c wrote on 1/30/2017, 11:44 AM

Hey gary rebholz, why don't you make vegas pro also support midi ?

Vegas pro already has great audio features, but the midi is still missing.

And when I say midi, I mean virtual studio instruments (VSTi) .

gary-rebholz wrote on 1/30/2017, 11:56 AM

And when I say midi, I mean virtual studio instruments (VSTi) .

Also on the list...

damian-c wrote on 1/30/2017, 12:11 PM

hey that's great news gary rebholz !

i am looking forward to using midi (vsti) in vegas pro.

gary-rebholz wrote on 1/30/2017, 12:19 PM

Well so do I, but let me be clear..."it's on the list" means that it is one of the things in our backlog that needs to fight for priority. There's no way I can promise any specific feature at this point. I wish I could give you everything right now, but it's a process and we have to decide what we can reasonably accomplish and when.

damian-c wrote on 1/30/2017, 12:21 PM

Ok

gary-rebholz wrote on 1/30/2017, 1:26 PM

I'm curious about what VSTi implementation in VEGAS Pro would look like. You started out by saying "MIDI," so are you envisioning a full MIDI sequencer? Or, would it be support for VSTi that turns the MIDI information from the instrument into audio on the VEGAS Pro timeline (without the ability to adjust or sequence MIDI further)?

JesusSheep wrote on 1/30/2017, 2:36 PM

How About Adding 7.1 even up to 9.1 channel support in Vegas And 32 and 64 bit audio support.

JesusSheep wrote on 1/30/2017, 2:42 PM

Add option in Samplitude Pro X3 to open Video in Vegas and and other Video editors and Sound forge for Audio Editing. Vegas not need edit the file the file but read and iimport it. ProDAD is working Software forf 360 Video Editing.

Rainer wrote on 2/3/2017, 3:37 PM

I'm curious about what VSTi implementation in VEGAS Pro would look like. You started out by saying "MIDI," so are you envisioning a full MIDI sequencer? Or, would it be support for VSTi that turns the MIDI information from the instrument into audio on the VEGAS Pro timeline (without the ability to adjust or sequence MIDI further)?


Gary, hope you don't mind if someone random chips in - you'd pretty obviously need a sequencer. I don't think it would be insurmountably difficult to add - how it would look would be to add a third type of track (so you'd have video, audio, midi) allocate the instrument and open the sequencer from the midi track. My view, don't do it, multi-function always means compromise and complications, use the right tool for the job . People who use midi for sound design already have a DAW which can display video.

Former user wrote on 2/4/2017, 3:43 PM

Does build 211 contain ALL previous builds? If installing ALL the builds will make VP 14 more stable (locked up my system at inconsistent intervals) I will gladly install them. I will need a list though. Just found out MS 13 doesn't import .mov files. I agree, how rude.

 

Regards,

VidGuy069

vkmast wrote on 2/4/2017, 4:36 PM

Does build 211 contain ALL previous builds?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-14-update-4-build-211--104988/#ca648998

https://www.vegascreativesoftware.info/us/forum/vegas-pro-14-s-update-history-so-far--104998/