VEGAS Pro 16 Update 4 (build 361) - General Discussion

Comments

joost-berk wrote on 1/22/2019, 10:11 AM

Hello, I too have a problem, when we can take mxf videos on Vegas? Because I try to carry this type of video file, but his refuses. It will be nice at the next update, that Vegas can take away MXF

Thank you

Vegas does take MXF files for many years already. If it comes to files that where produced with Sony camera's MXF should work as expected.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

joost-berk wrote on 1/22/2019, 10:35 AM

Great work is going on for Vegas. Good job guys!

Still I want to mention a strange bug that i'm experiencing. When I push the "Render as..."-button after editing for a while, Vegas does crash. Crash-manager let me send an error-report (what I always do). The only way to prevent this crash is to first restart Vegas and then initiate a render with an (almost) empty project. For example with only a default checkerboard from the Media Generator tab. Then I reload the project I'm working on and then I can render the project.

So Vegas crashes by initiating the render-dialog (which shows the render-templates) after editing.

Wel, I did a lot of testing on this bug and it seems that it is not only a hardware related bug, but also a combination of software drivers and plugins. I tested this bug by unplugging all external devices (such as MIDI-controller, USB-soundcard, SDI-card, multiple displays and GPU) but the crash remains. Even when I only use Vegas internal plugins.

I do not have this issue on other PC's. Not even on my MacBook pro with bootcamp and external hardware plugged in running Vegas.

Does other people have this issue? It's driving me crazy!

Cheers!

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Fiola wrote on 1/22/2019, 1:48 PM

Great work is going on for Vegas. Good job guys!

Still I want to mention a strange bug that i'm experiencing. When I push the "Render as..."-button after editing for a while, Vegas does crash. Crash-manager let me send an error-report (what I always do). The only way to prevent this crash is to first restart Vegas and then initiate a render with an (almost) empty project. For example with only a default checkerboard from the Media Generator tab. Then I reload the project I'm working on and then I can render the project.

So Vegas crashes by initiating the render-dialog (which shows the render-templates) after editing.

Wel, I did a lot of testing on this bug and it seems that it is not only a hardware related bug, but also a combination of software drivers and plugins. I tested this bug by unplugging all external devices (such as MIDI-controller, USB-soundcard, SDI-card, multiple displays and GPU) but the crash remains. Even when I only use Vegas internal plugins.

I do not have this issue on other PC's. Not even on my MacBook pro with bootcamp and external hardware plugged in running Vegas.

Does other people have this issue? It's driving me crazy!

Cheers!

Howdy partner, yup, same problems here too on several PC's ... although newest version is most stable for me yet since VEGAS 15 got released.

GerY wrote on 1/22/2019, 11:35 PM

Problems in Dual Fish Eye Stitching 360 Plug in, this plug in , dont save custom presets. show the new preset name saved, but with default settigs.

Is Fundamental for workflow with other 360 cameras , that are not in the presets..

Thanks!

 

Same here.

 

VEGASPascal wrote on 1/23/2019, 7:45 AM

Problems in Dual Fish Eye Stitching 360 Plug in, this plug in , dont save custom presets. show the new preset name saved, but with default settigs.

Is Fundamental for workflow with other 360 cameras , that are not in the presets..

Thanks!

 

Same here.

 

Will be fixed in one of the next updates.

erkan-s wrote on 1/23/2019, 9:44 AM

Vegas pro 16 works perfect
To do 8K rendering vegas pro 17 or next update to the next
thanks

Len Kaufman wrote on 1/24/2019, 12:51 AM

One positive improvement that I appreciate is that now, when I wish to drag a clip onto the timeline, it is much easier to grab the clip. With the last build, it seemed to be quite finicky.

fer754523 wrote on 1/24/2019, 9:01 PM

for when the mkv support also AC3 does not open vegas aver if they improve guys I pay the program very expensive

joost-berk wrote on 1/27/2019, 4:22 AM

 

Howdy partner, yup, same problems here too on several PC's ... although newest version is most stable for me yet since VEGAS 15 got released.

Hey,

A few days ago I started with a clean instal of VP16, I deinstalled Vegas, threw away everything containing Vegas, Magix and Sony. And removed everything in the regedit. I did a clean Vegas install. Right now I am testing for the bug (crash by Render As.. initiation) and so far. so good. First I stess-tested Vegas with all internal and external hardware. It seems to stay stable.

Right now I am adding third-party plugins. Neatvideo, Izotope and NewBlue FX all seem to work well! There is a suspicion that somehow Waves and/or Red Giant Magic Bullet is causing the trouble.

Maybe you can confirm this behavour?

Cheers!

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

joost-berk wrote on 1/28/2019, 8:07 AM

Now here's an interesting post: https://www.vegascreativesoftware.info/us/forum/vegas-16-freeze-after-hitting-render-button--112952/#ca709261 This is what I am facing everyday. Let's start testing with QSV turned off! Maybe this is the solution.

**UPDATE**

No! Turning QSV is not the solution. Vegas still keeps crashing...

Last changed by joost-berk on 1/28/2019, 8:31 AM, changed a total of 1 times.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

EdgyPotato wrote on 1/28/2019, 10:06 AM

this version of vegas pro freeze a lot when I press ctrl + z

Ustik wrote on 1/29/2019, 8:37 AM

this version of vegas pro freeze a lot when I press ctrl + z

I noticed the same. Almost every time I press CTRL+Z Vegas freeze...

 

Fiola wrote on 1/29/2019, 10:18 AM

CTRL+Z Freeze, the "Render As" Freeze, the random Freeze while playback ... all of these bugs were reported back to first version of VEGAS 15 ... they never mentioned them in the feedback / reports / or known issues ... even though many people address that.

I am now after random 10 crashes in one project without any effects ... just trying to play what I edited yesterday. Without any chance... freezing every 10 seconds in playback... And that's the last version of vegas. It seems that it's stable until you actually want to really work with the software. During small tests is all good. On actual projects it's really really really big pain.

j-v wrote on 1/29/2019, 10:21 AM

When do you press Ctrl-Z and what is your intention with that command?
Clearing the track from its events as it is intended for by default.

Last changed by j-v on 1/29/2019, 10:55 AM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

joost-berk wrote on 1/29/2019, 11:02 AM

This morning I opened an Support Ticket at Magix for the "Render As..." bug. Vegas is pretty much unusuable like this. The most anoying part is that my systems task manager shows only a faction of load on CPU/GPU/RAM/SSD during editing and rendering. So there are enough resources left in the machine.

I discovered that when I run Vegas in Compatability Mode (Windows 7), the "Render As..." bug doesn't appear (yet). But still I have to test this furter to see how long it will last.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Andrew B wrote on 1/30/2019, 3:50 PM

Hi Everyone,

I found a temporary solution to my serious editing/playback issue with V16 build 361.

I am creating a 30 minute video. At about the 10 minute point, it started having serious playback issues where it would look like it is trying desperately to render the next frame (growing line of dots next to the frame number in the preview window) and then it would lock up.

Everything was fine up to this point and I am mostly using generated text on a static background in a 1080/30p project. A very, very simple project. I figured the last few lines of text I added to the project media maxed something out and started crashing things.

I tried all sorts of playback settings, all the way down to draft/quarter, but the same thing would happen.

SOLUTION: I set dynamic RAM ram to ZERO and turned off my GPU.

Preview works fine for now (just like in previous version of Vegas). I am not sure if this has just bought me some time until I max something out again or if it is just an issue with the latest NVIDIA drivers.... who knows. At least I get to meet my deadline for this video.

I really don't think the Dynamic RAM preview was the issue. I think there is an issue with my Nvidia 1080 driver and Vegas working together.

Hope this helps someone!

 

Andrew

My system: Dual Xeon E5-2667 v4 processors, 128GB Ram, raid 0 SSD, Nvidia 1080, Win10 Pro.

JesusSheep-1965 wrote on 1/31/2019, 8:57 AM

In The Color Correctors Add Support For Quick Adjustment . Add Video Color Checker Patterns from X-Rite,DataColor Also Input Values For Sorce Gama,Target Gama,Color Temp Where Track can be Color Corected.

ernie-tamminga wrote on 2/1/2019, 3:11 PM

For me, the build 361 update launches an infinite loop of failures.

I'm running Vegas 16 Pro, build 52 in the latest version of Windows 10. Every time I start Vegas it says there's an update. I click "Perform update now" and it downloads the update and asks me if I want to install immediately or after the program is closed. If I choose immediately, it tells me it can't install the update while the program is running. If I choose after the program is closed, and then I close the program, nothing happens --- no update. And then the next time I start Vegas, the whole loop starts all over again. Also, according to Task Manager, there is no Vegas process running in the background. I restarted my computer anyway, but that made no difference at all. I'm back in the infinitely-failing loop. Looks like the update isn't gonna work.

j-v wrote on 2/1/2019, 3:35 PM

Did you also look in your "my documents\MAGIX Downloads\Instalation manager" if you see there the file for instalation?
You can also go to your Magix account to download the latest build 361

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

ernie-tamminga wrote on 2/1/2019, 7:12 PM

Thank you. The downloadable file on the Magix website is just called vp16_dlm.exe -- no build number specified.. Do you know if that is actually build 361? The filename is the same as the file that I installed when I first got Vegas 16.

Marco. wrote on 2/2/2019, 4:03 AM

"vp16_dlm.exe" is the download manager, not Vegas Pro. If you've installed and run the the download manager you see which build of Vegas Pro is offered for download and installation. And if you don't need, don't install "Magix Connect".

IntelManagementEngine wrote on 2/5/2019, 8:08 PM

I am to scared to install it. Things are running well.

Norbert wrote on 2/6/2019, 8:05 AM

When GPU acceleration is on after a while during editing the external fullscreen monitor starts blinking when I hit play. As if it was mixing the frames not knowing the order. I have X AVC S and X AVC L files on my timeline, I use 2 screens, one is in full screen, my GPU on this PC is MSI GTX 1080 with newest nVidia driver, I have 16 GB RAM and a Ryzen 1700x. The program runs but I have to restart it to get rid of the problem. When GPU acceleration is off it doesn't happen. Also, "Allow legacy GPU rendering" is turned on/off when GPU is enabled won't make a difference.