VEGAS Pro 16 Update 2 (build 307) - General Discussion

Comments

Soundivad wrote on 10/30/2018, 10:37 AM

The Video Stabilisation autozoom is still to agressive.

Thanks for your feedback and the hint for the checkbox.

I do not understand the word too "agressive". The "Auto Zoom" checkbox is adjusting the minimum borders for you. If you change the zoom slider manually, than you will see black borders.

It's like any other video stabilizer (Mercalli, Boris, etc.)... The zoom is the result of the length of your smoothing and the camera movement. If you increase the smoothing length, the zoom in effect is also increased.

With too agressive i mean, the autozoom is zooming in too much, in the clips i tested it with, it zoomed in all the way, but moving the slider manually to ca. half was enough to avoid black borders.

set wrote on 10/30/2018, 10:48 AM

I just tried it again and I agree with Soundivad, the autozoom zooming is too much. Need to manually adjust it zoom out.

>> For those who work in rush... this can be disadvantage because you will need to zoom out manually and check the whole sequence to make sure no black bar appear.

Kinvermark wrote on 10/30/2018, 12:55 PM

My trial ran out and Magix won't give me another.... :(

So, can anyone comment on whether or not the storyboards (and thumbnails) are working correctly?

(ie maintaining correct order, in/out points, no crashes on thumbnail resize, etc.)

zdogg wrote on 10/30/2018, 1:28 PM

Nope, 307 still crashes upon startup for me. I've uninstalled all plugins installed from previous Vegas versions, and I have simply have not been able to use Vegas 16 since purchasing it, it has never started up yet. Despite reporting the startup bug several times officially, there has been no resolution to this issue. I am nearing the point where I need to demand a refund, as I simply cannot use the product.

Richard, do you have a MIDI device or audio device that Vegas wants to access, but cannot. Hardware controller....those types of occurrences will cause a crash sometimes. The other "usual suspect" is a not cooperating AVI or MOV file (the underlying file format, as these are wrappers) there is a fix for AVI plug, are you loading a totally black project file?

Norbert wrote on 10/30/2018, 2:09 PM

X AVC L playback is worse than ever. Even Vegas Pro 14 plays back everything in realtime, Vegas 16 gives me 3fps... files created by Sony PXW X70 and PXW Z150

tom-sylvester wrote on 10/30/2018, 4:25 PM

Thank you for your great work in continually improving a great product. I'm a convert from Adobe Premiere and am here to stay.

Julius_ wrote on 10/30/2018, 8:59 PM

"You can now create subtitles by importing SRT files with the Insert Subtitles from files feature"

I love you Magix !!! THANK YOU ! 👍👍👍

Can you tell me how this works exactly? Thanks.

ram17 wrote on 10/30/2018, 9:30 PM

The new stabilization fx still a hit or miss, sticking with the old one for now. And a few hours of staying in the project media & setting in-out points plus a few instances of resizing thumbnails gets Vegas freeze & wait 2-3 minutes to respond again or restart app. It's 2 or 3 times in a while but that's tolerable, it just happened when you are halfway with hundreds of (Canon DSLR 1080p) clips involved, hope they make it more stable though. Anyways good job for making it solid (that's for me).

PS:

Just a request to Magix, can you please kindly include in the keyboard map these few features in Vegas so that we can assign shortcuts to it. Thanks.

Add missing stream, Close gaps, Selectively paste event attributes.

raWer-Studio wrote on 10/31/2018, 3:38 AM

Footage from Fuji XT-3 still playback laging. In Davinci Studio 2160x50p 10bit x.265 playback is smooth :-( Please Magix work on it.

bbgunn wrote on 10/31/2018, 4:53 AM

With 307 I can no longer import or drag and drop any media of any type, including jpegs. The fix for this previously was to make sure that C:\Program Files\VEGAS\VEGAS Pro 16.0\Vegas160.exe wasn't running as an admin, but now that no longer works. I did reboot the computer, no luck. Alienware Aurora R7 Windows 10 version 1803, NVIDIA GeForce GTX 1070, 16 gig RAM. It was working with the previous version 251.

bbgunn wrote on 10/31/2018, 8:16 AM

With 307 I can no longer import or drag and drop any media of any type, including jpegs. The fix for this previously was to make sure that C:\Program Files\VEGAS\VEGAS Pro 16.0\Vegas160.exe wasn't running as an admin, but now that no longer works. I did reboot the computer, no luck. Alienware Aurora R7 Windows 10 version 1803, NVIDIA GeForce GTX 1070, 16 gig RAM. It was working with the previous version 251.


Tried uninstalling 307 using the control panel, and reinstall 261. Now Vegas won't start. Then reinstalled 307 and it starts but I have the same problem where I can't import any video or graphics. Both times I installed 307 I initially received a .NET error the first time. Both times I used the task manager to kill it and then it started the second time. At this time I'm dead in the water.

james-ollick wrote on 10/31/2018, 10:55 AM

 

@bbgunn Try using VP16's Explorer and right click on the file you want and select add to Project Media. That works for me. I do miss dragging and dropping to the timeline.

Last changed by james-ollick on 10/31/2018, 1:35 PM, changed a total of 1 times.

Home built PC - Corsair case, ASUS ROG Maximus XI Code motherboard, i9 9900k, 32 gigs Corsair Vengeance RGB 32GB DDR4 DRAM 3200MHz,  Sapphire Nitro+ Radeon RX 580 graphics card, Corsair 1000 watt power supply.

Kinvermark wrote on 10/31/2018, 12:35 PM

@bbgunn

Sounds like a lingering install (registry?) problem. You may want to do a clean install and/or contact Magix support.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-faqs-and-troubleshooting-guides--104787/

 

jimbo20 wrote on 10/31/2018, 4:52 PM

After install it is still build 261, not 307. How can I get 307?

alan-f wrote on 10/31/2018, 6:21 PM

Just want to confirm that this will only overwrite my Vegas Pro 16 installations, and that it will leave my Vegas Pro 12 installations (which I still use for older projects with specific plugins) alone. My first installation of 15 broke the Boris effects I had installed in 12 - don't want that to happen again. TIA.

bitman wrote on 11/1/2018, 9:43 AM

My trial ran out and Magix won't give me another.... :(

So, can anyone comment on whether or not the storyboards (and thumbnails) are working correctly?

(ie maintaining correct order, in/out points, no crashes on thumbnail resize, etc.)

@Kinvermark

I do not know if this will work if your trial has run out, try this for a quick temporary check if the patch solves your issue, download the patch, next disconnect yourself from the internet, change your PC date manually to e.g. a week less than your expire trial date, install the patch and try stuff out. If you are done checking things out, put your date back to normal (or let it update automatically) once on line back again. If you are satisfied, buy the upgrade.

Last changed by bitman on 11/1/2018, 9:46 AM, changed a total of 2 times.

Current system: VP16 (suite) build 424, VP15 (suite) build 416, Magix Video Pro X (VPX11), Corel VS ultimate 2019, a lot of NEWBLUE plugins, Titler Pro 6, Mercalli 4.0, Respeedr, Vasco Da Gamma 12, VASST stuff, Production Assistent pro3, Boris Continuum 2019,...

  • OS: Windows 10 Pro 64, version 1903
  • CPU: der8auer i7-8700K (advanced edition), default speed (no overclock), Cooler: Noctua NH-D15s
  • RAM: G.Skill Trident Z 3200C14 DDR4 64GB, XMP set to profile 1 in BIOS
  • Videocard: NVIDEA RTX 2080Ti (Founders edition), NVIDEA studio drivers
  • Monitor: LG 38 inch ultra-wide (21x9) - yes upgraded from 34 to 38, I can see more tracks now! Resolution: 3840x1600
  • C-drive: Samsung NVMe SSD 2TB 960 pro
  • Data storage: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z370 Aorus Gaming 7
  • PS: Corsair HX1200i, Case: Silverstone fortress 2, shuttlePROv2, Keyboard and mouse: Logitech G910 and G700s (and now Evoluent Vertical Mouse)

Before November 2018: NVIDEA Gibabyte GTX 1080ti

Before November 2017: windows 10 Pro 64, i7-4790k, mem: DDR3 16GB GTX TITAN X (Maxwell)

 

Nick Hope wrote on 11/1/2018, 10:52 AM

After install it is still build 261, not 307. How can I get 307?

@jimbo20 Where did you get the file that you installed from?

Just want to confirm that this will only overwrite my Vegas Pro 16 installations, and that it will leave my Vegas Pro 12 installations (which I still use for older projects with specific plugins) alone. My first installation of 15 broke the Boris effects I had installed in 12 - don't want that to happen again. TIA.

@alan-f (sorry, you're untaggable) In theory yes. I personally have never had a Vegas installation interfere with a previous one or its plugins, and I have 10, 12, 13, 14, 15, & 16 on this computer.

jimbo20 wrote on 11/1/2018, 11:08 AM

@nick I used the download link in your original post. It's the initial released build.

Nick Hope wrote on 11/1/2018, 12:13 PM

@nick I used the download link in your original post. It's the initial released build.

@jimbo20 That's strange. It shouldn't be. I checked the links again and they both have "307" in the title, and nobody else reported this problem. You could try using an official "download manager" installer from here. Or try uninstalling your existing version first.

Marcin wrote on 11/1/2018, 1:40 PM

I'm happy with the update 2, thank you for fixing the mistake "Right Alt+z and Shift+Right Alt+z now properly give users of the Polish localized version ż and Ż".

jimbo20 wrote on 11/1/2018, 2:32 PM

@nick I used the download link in your original post. It's the initial released build.

@jimbo20 That's strange. It shouldn't be. I checked the links again and they both have "307" in the title, and nobody else reported this problem. You could try using an official "download manager" installer from here. Or try uninstalling your existing version first.

Yes, the download I got from that link has "307" in the executable, but it seems to install "261". The download manager did in fact install the "307" version, asked me to register the product, and the splash screen and About box does indeed now show "317". Thanks.

MikeyDH wrote on 11/1/2018, 7:39 PM

Well, I bit the bullet, downloaded and installed Vegas Pro 16 Edit. So far 3 attempts to edit some simple AVCHD footage with a split and a clock wipe and 3 crashes. The disappointment is real.....Something like this has never happened with any version of Vegas until today

Marcin wrote on 11/2/2018, 12:50 AM

Try to disable Enable QSV Encoding and Decoding

JesusSheep-1965 wrote on 11/2/2018, 9:40 AM

Great How About Some Plugins For HDR :)