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

Comments

bitman wrote on 10/28/2018, 10:28 AM

 

Yes this is an 'old' bug. You will also notice, that the FX windows/interface can still not be used wirh 150% nor 175% scaling in High DPI mode.

Confirmed, I was not aware of that. 125% it will remain then. At least I will have more real-estate, but my old eyes start to suffer 😵

Last changed by bitman on 10/28/2018, 10:29 AM, changed a total of 1 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)

 

richardbushell wrote on 10/28/2018, 10:42 AM

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.

Peter_P wrote on 10/28/2018, 10:55 AM

At least I will have more real-estate, but my old eyes start to suffer 😵

@bitman

I really can not work with 125%. The text becomes too smal for my older eyes. But 149% seems to work concering the FX interface as well but I had stability problem with that scaling. Does that occur with 125% on your system as well ?

Nick Hope wrote on 10/28/2018, 11:07 AM

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.

@richardbushell Have you been thoroughly through this troubleshooting post?

bitman wrote on 10/28/2018, 11:27 AM

@bitman @Peter_P What is your display resolution?

3840x1600 (ultra wide, updated in signature)

Last changed by bitman on 10/28/2018, 11:31 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)

 

Peter_P wrote on 10/28/2018, 11:37 AM

@bitman @Peter_P What is your display resolution?@

@Nick Hope

Mine is UHD : 3840 x 2160.
Even I could very hardly read the text, I switched to 125% scaling and in this mode I did not get the mentioned freezes, but with some minor editing of XAVC-S footage (So4 TRUE) in the TL Vp16 B307 just terminated with an error to be send.

bitman wrote on 10/28/2018, 11:40 AM

At least I will have more real-estate, but my old eyes start to suffer 😵

@bitman

I really can not work with 125%. The text becomes too smal for my older eyes. But 149% seems to work concering the FX interface as well but I had stability problem with that scaling. Does that occur with 125% on your system as well ?

I have not used anything other than 125%, I am a bit cautious about using a non-default scaling (like a custom scaling le.g.149%) as Microsoft warns that such custom scaling is not recommended (as opposed to default scaling 100/125/150 etc...) it is even hidden in the advanced properties which is further sign of "better not mess with it".

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)

 

bitman wrote on 10/28/2018, 11:47 AM

@bitman @Peter_P What is your display resolution?@

@Nick Hope

Mine is UHD : 3840 x 2160.
Even I could very hardly read the text, I switched to 125% scaling and in this mode I did not get the mentioned freezes, but with some minor editing of XAVC-S footage (So4 TRUE) in the TL Vp16 B307 just terminated with an error to be send.

I understand now that you need more scaling than 125% to read text with your 4K monitor. This is one of the reasons I did not purchase a 4K monitor, but an ultra wide curved, which requires less scaling and has great horizontal space for timeline editing (and is a great gaming monitor for immersion as well).

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)

 

Peter_P wrote on 10/28/2018, 11:48 AM

I have not used anything other than 125%, I am a bit cautious about using a non-default scaling (like a custom scaling le.g.149%) as Microsoft warns that such custom scaling is not recommended (as opposed to default scaling 100/125/150 etc...) it is even hidden in the advanced properties which is further sign of "better not mess with it".

I only tried the 149%, because it was recommended in the High DPI thread. Normal/System-text  is also not as clear as with the regular scaliling. For my system MS is recommending 150%, but this results in too small text for me and does not help Vegas to display the FX interfaces properly. So I stay with 175% and hope that some days I can use Vegas with clear text, icon and pictures in High DPI mode.

Peter_P wrote on 10/28/2018, 11:59 AM

I understand now that you need more scaling than 125% to read text with your 4K monitor. This is one of the reasons I did not purchase a 4K monitor, but an ultra wide curved, which requires less scaling and has great horizontal space for timeline editing (and is a great gaming monitor for immersion as well).

OT

I’m not interested in gaming but want to have a 1:1 mapping of my UHD footage on the display on full preview.

/OT

Coriaman wrote on 10/28/2018, 8:56 PM

being used interchangeably between Japanese and English.

When used in English, Japanese is mixed up.

Nick Hope wrote on 10/28/2018, 9:50 PM

being used interchangeably between Japanese and English.

When used in English, Japanese is mixed up.

@Coriaman Please report that issue by submitting a support request at https://support2.magix.com/customer/en/vegas/form

set wrote on 10/29/2018, 8:02 AM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-update-2-build-307--113473/
Official announcement

Martin L wrote on 10/29/2018, 2:33 PM

I installed build 307 this morning and it opened! Although the first attempt Vegas didn't manage to open the project I had started three days before, but on second attempt it worked. Then I was able to work with it the rest of the day with only one crash. What that was about I don't know but the error message from the PC said the GPU driver stopped working and had to be reset. That crashed Vegas. But after that no problems.

Build 307 is quicker and smoother too. I like it and hope it continues to work.

jrb101 wrote on 10/30/2018, 4:43 AM

So far with Vegas 16 (365 ed), since update 261 and also 307 I've been enjoying buttery smooth timeline playback (using so4compound and GPU acceleration on!) and no crashes that weren't the fault of a 3rd-party plugin.

I'm actually really impressed with Vegas Pro now, and after toying with going back and forth between Vegas and Davinci Resolve 15, I think I might settle on using Vegas for the vast majority of my projects. Well done Vegas Pro developers - you're doing a great job pushing forward on the product and trying to squash any bugs that get reported!

Lots of people seem to hate on Vegas for being buggy or crashing a lot, but I've found it to be just as stable as other NLEs when set correctly - just look at the forums for Premiere Pro, or Resolve and see how many issues they have too - the main issue is that it's not always obvious what the "right" settings are for anyone's particular setup (e.g. so4compoundplug seems to cause a lot of issues in however it's decoding AVC for a lot of people) 

I don't know if there is a "Suggestions"/"Feature Requests" post that I could add to, but if there is I'd like to add a couple of requests as there are a couple of features in Resolve that I do miss in Vegas (but not enough to push me away from it):

1) Native optical flow retiming/resampling - it's not perfect and can lead to odd artefacts, but it is a really useful method in other NLEs

2) A version of "Morph Cut" (PPro), "Flow" (FCPX) or "Smooth Cut" (DVR) transition, which is reliant on optical flow to create new frames (and face-tracking in the case of PPro's Morph Cut) - it's a reasonably specialised requirement, but I say "errr" and "ummm" lots in my videos and using this kind of transition means I can cut all of these out and have a nice smooth talking-face/vlog video without a million jump cuts!

3) Planar tracking, corner pinning and "track backwards/track forwards" for the tracking module (unless I'm missing the options) - the new tracker is great and I hope it continues to get developed further.

Overall I'm really impressed with how far Vegas has come in the last couple of years and where it seems to be going.     

Jon Baker - Experienced in the audio game, newbie at the video game 😉

(YouTube - "A Beginner Guitarist's View")

PC and camera: AMD Ryzen 3 2200G Desktop w/16GB DDR4(2666 o/c @3200MHz) , ~5TB of storage across various HDDs, Focusrite Scarlett 6i6 audio interface (runs a condenser mic and dynamic mic for audio capture), Mackie CR5BT studio monitors, 24" 1080p monitor (not anything special!) and Olympus PEN E-PL6 camera with external mic input adaptor and Olympus ME51S electret lavalier and Takstar SGC-598 shotgun mic.

MagixPascal wrote on 10/30/2018, 7:40 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.

set wrote on 10/30/2018, 8:35 AM



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.

Add my experiences (in case you haven't use subclip technique) : I guess it depends on your source or 'shake-level', but, since they required to be put as MediaFX, so it is applied to whole clip including unused part. I usually do cutting first, define the trim range of the clip used, then create subclip based on the range of the clip used. Make stabilization process based on this subclip can make a differences than applying it to whole clip.

fr0sty wrote on 10/30/2018, 9:45 AM

Yeah, requiring that the effect be applied at the media level is very inefficient. Maybe I don't want to stabilize an hour long clip that will take hours to stabilize, maybe I only need the few minutes of it that is going to end up in my final edit... Not only does it waste time, but as pointed out above, it can make the correction more aggressive than needed.

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

That's why creating a subclip is a solution for me... especially when you need few minutes of an hour long clip source. Creating subclip will limit only the analyzing process for that selected range only.

Martin L wrote on 10/30/2018, 10:11 AM

So, how how do you create a subclip? What does it mean?

jrb101 wrote on 10/30/2018, 10:16 AM

So, how how do you create a subclip? What does it mean?


Just had to look this up myself in the manual - page 142!

You can create a subclip by either viewing the media clip in the trimmer window and selecting in and out points, then click on the "Create Subclip" button in the trimmer window and give it a name in the subclip dialog box

OR

You cut the video on the timeline, then right-click on the portion you've cut to your needs and select "Create Subclip" from the context menu.

I never knew about this before and it looks like it could be a real time-saver with the stabilizer!

Jon Baker - Experienced in the audio game, newbie at the video game 😉

(YouTube - "A Beginner Guitarist's View")

PC and camera: AMD Ryzen 3 2200G Desktop w/16GB DDR4(2666 o/c @3200MHz) , ~5TB of storage across various HDDs, Focusrite Scarlett 6i6 audio interface (runs a condenser mic and dynamic mic for audio capture), Mackie CR5BT studio monitors, 24" 1080p monitor (not anything special!) and Olympus PEN E-PL6 camera with external mic input adaptor and Olympus ME51S electret lavalier and Takstar SGC-598 shotgun mic.

j-v wrote on 10/30/2018, 10:20 AM

So, how how do you create a subclip? What does it mean?


met vriendelijke groet
Jan

Camera : Pan X900,GoPro Hero7 Hero Black
Desktop :AsRock Z270 Pro4, W10 , i7 7700K 4.2Ghz,16 DDR4 GB RAM, Gef. GTX 1050 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362, CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).
Both Nvidia GPU's have driver version 430.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!