VEGAS Pro 15 build 177 General Discussion

Comments

Peter_P wrote on 8/28/2017, 7:26 AM

My computer is a 36core/72threads dual cpu, Quadro K5000 and 192GB ram inside and all ssd pro's from samsung so it's probabely not the pc that is not up to the task :-).

Did you adjust the 'Maximum number of rendering threads' in Options/Preferences to your 72 threads?

jurgen wrote on 8/28/2017, 7:31 AM

Yes I did. 48 is the maximum number of threads I can select

Peter_P wrote on 8/28/2017, 7:40 AM

Strange ....

Im running just a i7-6700k (@4.5 GHz) and UHDp50 files from a GH5 are played with full framerate in the internal 960x540 preview window with Best(Full). But still, setting the project to 1920x1080 makes the preview of UHD footage smoother.

Quitter wrote on 8/28/2017, 7:41 AM

If VP15 does not start:

http://www.semw-software.com/de/extensions/
SeMW ver. 1.0.9 works with VP 15

Last changed by Quitter on 8/28/2017, 9:52 AM, changed a total of 1 times.

Camcorder: Sony CX 520 VE
Hardware:   Acer NG-A717-72G-71YD, Win 10 Home 1903, i7-8750 H, 16GB, GTX 1060 6GB, 250GB SSD, 1TB HDD
NLE:  Sony Vegas Pro 13.0 Build 453
           Vegas Pro 14.0 Build 270

Kraznet_UK wrote on 8/28/2017, 7:43 AM

For some reason my GFX960 isn't showing up in the list in V15? Although it is showing in V14.

V15:

V14:


Are you running the latest drivers?


Yes I updated the Nvidia driver 385.28 just a couple of days ago. It's weird that it's showing up in version 14 though.

Asus Z97-A | Intel Haswell i7 4770K, 32GB DDR3 1866Mhz, Samsung 850 Pro 512 SSD System Drive, Crucial 960gb SSD A/V Drive, Crucial 960 SSD Samples Drive, Gigabyte GTX 960 2gb, RME Raydat, Windows 10 Home x64, Philips BDM4065UC 40" 3840x2160 VA 4K Display (scaling 125%), Windows 10 Home. Video Pro X, Samplitude Pro X3, Sequoia 14, Vegas 14.

 

marc-s wrote on 8/28/2017, 7:43 AM

Bummer... I was hoping for some good news with this release. I had a feeling when I saw them advertising a new exciting "freeze frame" feature that there were basically no new features. I mean... how hard is it right now to grab a still in Vegas? Answer: it's not!

Now if they can give me a rock solid stable version with no major steps backwards I may upgrade from Vegas 13 before migrating over to Davinci Resolve 14 once they gets the kinks worked out. I still like Vegas for certain types of editing so I can see it living in my toolbox even if they don't seem to have the ability or will to improve it. I've been a user since Ver. 3 so I remember the great strides they used to make with each release. Curious if there will actually be GPU improvements (or just marketing like in the past) and if I made a mistake switching from Nvidea to Radeon based on user recommendations.

Also I'll never understand the thinking that goes into the few new features that have been making it into the latest releases. How they could think we want a new picture in picture effect when we still don't have robust media management, native professional titler or multiple timelines is beyond me. If I had a plan master plan to destroy a great program over period of time this would be it. Add few new features to each release, ignore the ones that most people probably want and watch the competition leave you in the dust.

Norbert wrote on 8/28/2017, 8:00 AM

Expected something special, improvements and new features but nope, it's just the same old VEGAS with a thin coat of fresh paint. What a letdown. No intuitive composite sequences, output encoders are still the same. I guess MAGIX doesn't want VEGAS to compete with their true flagship NLE, VIDEO PRO X. All they need to do is take the good bits of each and make a monster app, it doesn't make sense why they have to keep both and yet VEGAS is way better but needs some features that are already in VIDEO PRO X.

What features exactly?

Glovercover created this UI concept that appeals to what I am talking about.

Composite Sequences. All I need is a tab to create another sequence and have all my sequences appear in a smart bin. I can double click on the composite sequence if I need to make changes to it and it opens on the timeline. At the moment, I have to drag a .VEG file into the timeline, which is really not the best workflow.

I agree with that. The new dark UI ugly af next to this made by a user here. We got nothing of the features Vegas users wanted. R.I.P. Vegas Pro, I loved u but it's time to switch to Premiere since Magix doesn't care about Vegas users.

Paul-Fierlinger wrote on 8/28/2017, 8:03 AM

I can't figure out the first basic thing for setting up a custom GUI: How do I move the windows around? When I go to help it says: To undock a window click the and drag it. Darn it! The key word is missing!! Not a good start. Holding CTRL does nothing.

Robert W wrote on 8/28/2017, 8:12 AM
 

I agree with that. The new dark UI ugly af next to this made by a user here. We got nothing of the features Vegas users wanted. R.I.P. Vegas Pro, I loved u but it's time to switch to Premiere since Magix doesn't care about Vegas users.

I hope Magix are reading this and realising they need to radically change how they are operating. This is a userbase that have been taken for granted for at least 10 years. Reading the new feature list I do not think what has been released constitutes a major new release. It looks like we may well be continuing the trend we saw with the previous owners of being fobbed off on annoying and often critical bugs and being encouraged to buy new releases in the vain hope that the old problems may be fixed.

Can anybody second the early report of the Dolby Pro AC3 codec still being missing? If it is the case that this is true then Magix, you have not got a clue. I am not going to put out a DVD or Bluray release using the basic AC3 codec. It lacks critical configuration options. They give the impression that they want us to be using Vegas for cinema productions by including a very good option in ACES 1.0 support. But then why remove a codec we had for at least the last 9 years that means you can not encode AC3 with theatrical or music programme flags set? If they would at least come out and explain what has happened, rather than promising for it to be added to Vegas 14 and then it not even be in 15, at least then we would know why. Instead it is a clear piece of fobbing us off.

Kraznet_UK wrote on 8/28/2017, 8:16 AM

V15:

V14:

 

The above looks like GFX960 didn't work in V14 but it's now working in V15.

Sorry I mislabelled it. The top pic should be V14 and the bottom pic V15. I've corrected it in my original post.

Asus Z97-A | Intel Haswell i7 4770K, 32GB DDR3 1866Mhz, Samsung 850 Pro 512 SSD System Drive, Crucial 960gb SSD A/V Drive, Crucial 960 SSD Samples Drive, Gigabyte GTX 960 2gb, RME Raydat, Windows 10 Home x64, Philips BDM4065UC 40" 3840x2160 VA 4K Display (scaling 125%), Windows 10 Home. Video Pro X, Samplitude Pro X3, Sequoia 14, Vegas 14.

 

Alexey_P wrote on 8/28/2017, 8:27 AM

VP15 does not start ((. Does anyone know what the problem is?

set wrote on 8/28/2017, 8:31 AM

VP15 does not start ((. Does anyone know what the problem is?

If you are using SeMW extensions, please update it to latest version!

https://www.vegascreativesoftware.info/us/forum/semw-extensions-for-vegas-pro-15--108311/

Alexey_P wrote on 8/28/2017, 8:37 AM

VP15 does not start ((. Does anyone know what the problem is?

If you are using SeMW extensions, please update it to latest version!

https://www.vegascreativesoftware.info/us/forum/semw-extensions-for-vegas-pro-15--108311/

WOW! ))Thank you so much. It helped!

Norbert wrote on 8/28/2017, 8:56 AM
 

I agree with that. The new dark UI ugly af next to this made by a user here. We got nothing of the features Vegas users wanted. R.I.P. Vegas Pro, I loved u but it's time to switch to Premiere since Magix doesn't care about Vegas users.

I hope Magix are reading this and realising they need to radically change how they are operating. This is a userbase that have been taken for granted for at least 10 years. Reading the new feature list I do not think what has been released constitutes a major new release. It looks like we may well be continuing the trend we saw with the previous owners of being fobbed off on annoying and often critical bugs and being encouraged to buy new releases in the vain hope that the old problems may be fixed.

Can anybody second the early report of the Dolby Pro AC3 codec still being missing? If it is the case that this is true then Magix, you have not got a clue. I am not going to put out a DVD or Bluray release using the basic AC3 codec. It lacks critical configuration options. They give the impression that they want us to be using Vegas for cinema productions by including a very good option in ACES 1.0 support. But then why remove a codec we had for at least the last 9 years that means you can not encode AC3 with theatrical or music programme flags set? If they would at least come out and explain what has happened, rather than promising for it to be added to Vegas 14 and then it not even be in 15, at least then we would know why. Instead it is a clear piece of fobbing us off.

Yes, people won't be motivated to upgrade if even old bugs aren't fixed. Now as I can see we've got some new... bugs, too. I loved Vegas because of things I still can't do in Premiere such as changing the order of the video tracks but since Vegas keeps crashing for nothing I have to change my workflow. I don't have time to deal with bugs and crashes, there are some crappy bugs that are there since Vegas Pro 8. If Magix cared they would focus on fixing ALL the old - known - bugs instead of creating features - with new bugs of course. It makes no sense to build new features on an unstable program. There are no sane specialist who would recommend that.

Only when there are no more known old-new bugs they should take a closer look at what users really want. What the majority of users use Vegas Pro for. They will lose lots of consumers if they won't listen to what they really need. They should start with hiring a new designer since even Glovercover - a simple user here - could create a way better looking UI. People who upgrade for money must be naive since the new release is filled with old and newly created fresh bugs.

Robert W wrote on 8/28/2017, 9:16 AM

I think a feature freeze is probably not tenable at this point, with Vegas lagging so far behind the rivals in so many key areas. I think the ACES 1.0 and LUT support were essential and had to be in this release if they wanted to be taken seriously. A fully integrated native motion tracking option available in all releases would have been useful. Proper GPU support was also essential (and the jury still seems to be out on whether we have got this). I can see that is seems that the team are working towards righting some old wrongs. It sounds like the maximum threads configuration has finally been moved from the hidden menu to the main menu (unless this happened in Vegas 14?) But if that Dolby Pro AC3 support is still missing, that is unforgivable in my opinion, especially in the context that we were advised it would be restored to Vegas 14.

The simple fact is that there were a lot of releases in the 14 series and the bugs should have all been removed before they moved to 15. But then I think we saw in the previous owner's era, the developers at times appeared to think they were working of a revision of a release, and then late in the day it became a major new release. They are dealing with the legacy of years of developing features over resolving bugs. I suspect it may be a very big task to clean up the mess in the codebase that has been left with the production schedules in the last owner's era. For all we know, they may have made huge strides in cleaning up the code, and there may be efficiencies that are not apparent until we use the application extensively. However, I think this optimizations should have been done largely in the 14 series, and users should not be expected to pay for what amounts to an incremental or at best another transitional major release in Vegas 15. That is unless the production is in severe financial difficulties and needs the release to pay everybody's wages for the next year. At some point though I think there is going to need to be a rebuild from the ground up. The VfW framework is a major hindrance, and I suspect possibly one of the biggest barriers to taking proper advantage of GPU hardware.

Magix can not take for granted the loyalty of the long term userbase. Cantankerous busy bodies such as myself have reluctantly using Vegas for years in spite of its shortcomings because of the basic design and workflow. But it is palpable that the irritation is getting to the point where people are ready to learn new application to get away from the frustration and the shortsightedness of Vegas. We can not be expected to wait year after year for the grail of Vegas releases.

David Johns wrote on 8/28/2017, 9:16 AM

Just chipping in with my general impressions. I'm still on v13 because I couldn't see anything in 14 that I really wanted, certainly not for the price being asked - and by and large I feel the same about v15, sadly.

I was really looking forward to this, given the year+ of development time the team have had and because I'm a massive Vegas fan. Unfortunately it seems to be a smattering of cosmetic tweaks and a couple of plugins. Granted some people will be delighted with LUT support and selective attribute pasting is nice but was cropping or PIP really so difficult before as to warrant time spent on dedicated plugins?!

More frustratingly for me, there's still no support for multiple sequences in the same project (.veg nesting is not as efficient or useable in this regard) or for collapsing selected events into a single compound entity which would be massively useful. No update / improvements on the legacy FX. No motion tracking (thank goodness I have Boris BCC10 and can Match Move things with that). No support for individual masks applied to FX or FX chains (again, Boris largely comes to the rescue)

I dislike most of the new icons and the track banners are a total showstopper - on my laptop's HD screen, most of my vertical timeline space is now taken up with blocks of solid colour instead of useful track thumbnails.

This feels more like v14.5 than a full new release and it's not worth $200 for the update (Vegas Edit only) for me. The retail prices shown for new licences are absurd!

Incidentally, Magix, if you're going to bundle specific Boris effects, may I commend Title Studio to you instead of that New Blue thing? It's a terrific piece of software.

Having used Vegas since 2000, I shall carry on with v13 and when I need to upgrade will either have to learn Resolve or - heaven forbid - buy a Mac and get FCP X I suspect.

Dammit :-(

David

jozef-pavlik wrote on 8/28/2017, 9:34 AM

Vegas Pro 15

"As an owner of older versions of Sony VEGAS Pro and Movie Studio, you can upgrade to the latest version any time, at a special price."

Is Vegas Pro 15 free for Magix Vegas 14 owners ?

Best,

Ole

no they want $ 249 for upgrade from V14 and has same problem like V14

HeavyMetal wrote on 8/28/2017, 9:37 AM

Does the new version support current RED color?

Gabriel_Isa wrote on 8/28/2017, 9:43 AM

Expected something special, improvements and new features but nope, it's just the same old VEGAS with a thin coat of fresh paint. What a letdown. No intuitive composite sequences, output encoders are still the same. I guess MAGIX doesn't want VEGAS to compete with their true flagship NLE, VIDEO PRO X. All they need to do is take the good bits of each and make a monster app, it doesn't make sense why they have to keep both and yet VEGAS is way better but needs some features that are already in VIDEO PRO X.

What features exactly?

Glovercover created this UI concept that appeals to what I am talking about.

Composite Sequences. All I need is a tab to create another sequence and have all my sequences appear in a smart bin. I can double click on the composite sequence if I need to make changes to it and it opens on the timeline. At the moment, I have to drag a .VEG file into the timeline, which is really not the best workflow.

Unfortunately that VP15 still have no the feature !WTF !

Nick Hope wrote on 8/28/2017, 9:46 AM

Three VP15 improvements that don't appear in the official release notes:

  • Panasonic GH5 10-bit 422 footage now opens correctly
  • The video stream of JVC YUV 4:2:2 footage now decodes correctly
  • iPhone/iPad footage now opens correctly (without requiring Quicktime)
     
marc-s wrote on 8/28/2017, 9:47 AM

"Incidentally, Magix, if you're going to bundle specific Boris effects, may I commend Title Studio to you instead of that New Blue thing? It's a terrific piece of software."

I did notice when I logged in to see the upgrade cost it listed "Boris Boris Continuum 3D Objects Unit" as included with all upgrade options. When I went to the Boris site it seems to say that "Title Studio" is part of the above plugin. If so this makes the upgrade a little more appealing if it works well with Vegas.

wilri001 wrote on 8/28/2017, 9:56 AM

VEGAS Pro 15 build 177 has been released.

Find it at http://www.vegascreativesoftware.com/us/vegas-pro/

General discussion in here please. Please make a new post or comment on an existing one for specific issues.

This thread will be updated when the official announcement has been made in the NEWS forum.

Nvidia Sony CODEC render support is great. Any CUDA support for GPU transitions? It would be nice to see them smoother while editing with Nvidia card.

John Lewis wrote on 8/28/2017, 10:04 AM

I am not so lucky

In the last 7 hours i have asked for my Magix password to be reset so i can try the trial

Each time it says i will receive an email but never get one

bipwave wrote on 8/28/2017, 10:13 AM

Three VP15 improvements that don't appear in the official release notes:

  • Panasonic GH5 10-bit 422 footage now opens correctly
  • The video stream of JVC YUV 4:2:2 footage now decodes correctly
  • iPhone/iPad footage now opens correctly (without requiring Quicktime)
     

Panasonic GH5 10-bit 422 footage now opens correctly.

Thanks need this! :)