although you will miss out of the marketing "bang" of a new version announcement.
This also presents its own issues, such as features that have been ready for months being put on the shelf until a new version drops, to help add to that "bang", vs. just releasing them as soon as they are done... or users buying an old version just before the new one drops and feeling left out.
...unless the idea is to be able to offer "one year free updates" from ANY point during the year at which a customer purchases a Vegas license/update?
That's exactly what the Update Service is. For example: You buy the license on 31. March 2022 and you will get Updates until 30. March 2023. If you don't buy a new year you will stand on the last version. I think that's a great thing and better than this shit with a subscription and if you cancel it you lost the complete software.
For example that's the point why I NEVER! will use Software from Adobe. Instead I use other products from other companies.
VEGAS makes the sub worth it IMO, by also including stuff like online collab/cloud storage and the stock video and music library with millions of clips to use... but yes, having the option is a huge benefit for VEGAS, and I don't see that changing anytime soon.
I would also like to see VEGAS adopt an update model similar to Resolume, where it works like this:
"From now on all Resolume micro releases (major.minor.micro) are backdated to the previous major or minor release. So if your license was eligible for version 7.13.0 you're also eligible for version 7.13.2 even if your license has expired before version 7.13.2 is released. We think this is only fair and it keeps everyone on the most stable version as possible. Normally micro releases contain only a few bug fixes, but to celebrate this license change we did sneak in a tiny little new feature in Arena and one in Wire. If you're the first to find it then post a screenshot on social media with hashtag #resolume you'll win a grand prize! "
Not sure how this could work with how VEGAS is engineered... what say ye, Derek?
After using several weeks Vegas 20 build 139.. stability of program is pretty good (1080p, 4k, mp4 stuff). Some hiccups with GoPro clips. Those can be solved transcoding them first.
Minor playback lag observed when pressing play button on some cases.
"From now on all Resolume micro releases (major.minor.micro) are backdated to the previous major or minor release. So if your license was eligible for version 7.13.0 you're also eligible for version 7.13.2 even if your license has expired before version 7.13.2 is released. We think this is only fair and it keeps everyone on the most stable version as possible.
Hmmm, that's only useful if there will be minor updates for a long time. If Version 7.14 is released and there will be no more updates for 7.13. x than it's useless. Also the developers have to support more than one version. That's more work and more frustration for the users, because they get no new features.
I think the Update Service from Magix is the best way for now. The only thing is, that it's extremely frustrating if your license has expired a day before an update / upgrade was released.
I think a combination would be great. 1 Year free Updates and Upgrades, but at least a minimum number of Updates. (without fixes for wrong going updates like Vegas 19, 361 and Vegas 19, 381)
What do others think about it?
Edit: I use the Web-Developer-Software Codelobster. They have a similar model like Magix. You buy the Software and get one Year Updates and Upgrades but you can buy additional years and than the next year(s) are very cheaper. (I buyed it with 3 additional years)
The only thing is, that it's extremely frustrating if your license has expired a day before an update / upgrade was released.
Very true. But the same thing currently applies to many products from BorisFX, formerly to FXHome products prior to Artlist's take-over, and to NewBlueFX products under their new licensing arrangement. Even if there were a 'grace period' of whatever time, there would still be those who miss out by one day.
After using several weeks Vegas 20 build 139.. stability of program is pretty good (1080p, 4k, mp4 stuff). Some hiccups with GoPro clips. Those can be solved transcoding them first.
Minor playback lag observed when pressing play button on some cases.
I agree.
We've been using it on projects from 9 cameras to 2 cameras, mixed with 4K Canon G50, 4K Canon G60, 1080p from other Canons and Sonys, GoPro and Osmo Action. For the most part it's been pretty solid.
THAT said -- we just spent a day editing footage shot on simply two Osmo Actions and the editing laptop was regularly crashing. I was also using Boris FX for finishing with Particle Illusion and a few other things. I did note that my memory utilization with Vegas was pretty high on that project, and launching the PI interface brought it from 48% memory used to 72%. The laptop has 32GBRAM
Wondering -- I upgraded to V20 two months ago (8/18) and was intrigued by the "hey, we're going to roll out more frequent updates than in the past so y'all can benefit from bug fixes as they're made, and pass QC"
Two months later and no updates, it doesn't seem any more frequent than with prior updates.
Is that not the strategy anymore? 11 pages into "V20 Feedback"...
I thought I read a comment from VegasDerek here about extensive testing to ensure there weren't problems with updates that would result in them being pulled as happened twice with VP19. I can understand that.
Yep indeed, the Curves are buggy in HDR. You can't use them for contrast etc. Wheels are working
This issue is known and the development team is hard at work on a fix.
I thought I read a comment from VegasDerek here about extensive testing to ensure there weren't problems with updates that would result in them being pulled as happened twice with VP19. I can understand that.
Yes, exactly this. We've been testing this bug every which way it can be, and there's a huge pool of folks testing it on a wide variety of hardware configurations. We've been working on it for a long time now, and as such it should be near complete, but they are being very cautious about releasing it so they know it is as rock solid as we can get it when they do.
Is that not the strategy anymore? 11 pages into "V20 Feedback"...
It's still very much the strategy, just making sure we don't have repeats of VEGAS 19's emergency patches to fix bad updates. Hang in there, release should be VERY near if all goes well. Audio folks will smile, Folks that do lots of color grading will smile. Folks that do lots of masking, mesh warping, and other stuff that involves controls overlaid on the preview monitor will smile... not counting the smiles from certain long-standing bugs finally getting squashed.
Two months later and no updates, it doesn't seem any more frequent than with prior updates.
We attempted that in VP 19, and quite frankly, it was a disaster. We are slowing down the frequency of the updates to ensure they are actually stable. We are also explore other possibilities for getting changes out to the general public on a more frequent basis, but for now, we are looking to do larger but less frequent updates in hopes of having a more stable product.
It's still very much the strategy, just making sure we don't have repeats of VEGAS 19's emergency patches to fix bad updates. Hang in there, release should be VERY near if all goes well. Audio folks will smile, Folks that do lots of color grading will smile. Folks that do lots of masking, mesh warping, and other stuff that involves controls overlaid on the preview monitor will smile... not counting the smiles from certain long-standing bugs finally getting squashed.
so what about those folks that simply want faster playback? will they smile too?
Our #1 priority has been to fix crashes and stability. That is what this update is about. Next thing to tackle is improving the performance of our video engine. All these efforts are long, slow processes.
External midi controllers still confusing and don't work in Vegas 20?? I've read as much as possible online, watched the videos from earlier versions programming external controllers. I've tried painstakingly programming a generic control map for an Akai MidiMix, Launkey 88 and a Alesis VI25 for use in Vegas 20 using learn mode and also hand programming. In learn mode Vegas sees all my midi messages to make the template but when I save and apply it NOTHING works except for the master fader with any of these. All three of these devices work perfectly in all my other DAW and I can custom program them fine in all other DAWs. Does anyone here have an external controller actually working in Vegas 20? If so what brand and was there some trick you used to get it to work?? Like do I have to resave the template and restart or something to get things to stick? Thanks in advance for any help.
@JMacSTL Thank you. We will research and try to determine the issue here.
Hey Derek: Wondering if you'd found anything on the "enable auto fx windwos resize" issue whereby non-magix audio plugins cause resizing to occur no matter what. Thx.
No disrespect intended, but I'm going to have to try to find a different editing package. Vegas 20 just cemented that thought with a myriad of problems, the most serious of which is very sluggish performance. Click on a clip in the media area, and wait 1 or 2 seconds for the preview to start. Click play and wait one or two seconds for the preview to start. This in addition to no real solution for crashes. I'm at the point where I hit "Save" after every single thing I do in Vegas because it will crash multiple times during an editing session. I have gone back to version 19 because I cannot handle the sluggish performance in version 20. I've been a Vegas user for TWENTY YEARS! I hate to change after so much effort and being so familiar with the package, but I'm just at a tipping point of frustration.
@Tim-Kitchen, I've been a VEGAS user for Twenty Three years! VEGAS Pro 20 is extremely stable on my system to the point where I keep forgetting to save until way after I should have. Without knowing your source clip format(s), it's hard to give advice.
Here is a MediaInfo dump detailing info about most of the clips I'm using. I use 4K files from a Nikon Z6ii most of the time. I'd appreciate any insight into Vegas 20 performance issues or crash avoidance.
Format : MPEG-4 Format profile : Base Media / Version 2 Codec ID : mp42 (mp42/avc1/niko) File size : 292 MiB Duration : 20 s 145 ms Overall bit rate : 122 Mb/s Encoded date : UTC 2022-03-26 16:04:48 Tagged date : UTC 2022-03-26 16:04:48 NCDT : NCTG
Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.1 Format settings : 1 Ref Frames Format settings, CABAC : No Format settings, Reference frames : 1 frame Format settings, GOP : M=1, N=12 Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 20 s 145 ms Bit rate : 120 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 23.976 (24000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.605 Stream size : 289 MiB (99%) Encoded date : UTC 2022-03-26 16:04:48 Tagged date : UTC 2022-03-26 16:04:48 Color range : Full Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Codec configuration box : avcC
Audio ID : 2 Format : AAC LC Format/Info : Advanced Audio Codec Low Complexity Codec ID : mp4a-40-2 Duration : 20 s 139 ms Bit rate mode : Constant Bit rate : 256 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 SPF) Compression mode : Lossy Stream size : 629 KiB (0%) Language : English Encoded date : UTC 2022-03-26 16:04:48 Tagged date : UTC 2022-03-26 16:04:48
Performance... these are 8 bit 4:2:0 AVC files, which means they can be decoded in hardware if you have an intel processor with an integrated GPU (which shows up in VEGAS as "QSV"), or an AMD or Nvidia GPU (which show up as VCE or NVDEC, respectively). To enable hardware decoding, if it isn't already, go to File I/O settings in VEGAS preferences and set the device you want to do the hardware decoding there. If you see more than one option in there, experiment with them all. In some cases, if you have an intel integrated GPU and also have an AMD or Nvidia dedicated GPU, you can set the video tab of preferences to use one, and have the other do the decoding. For instance, you can have QSV do the decoding, and your Nvidia or AMD GPU can do all the rest of the GPU acceleration, which can result in better performance than just having one do everything.
Make sure your system is up to the minimum recommended specs for VEGAS Pro:
System requirements
Recommended for HD
Operating system
Microsoft® Windows 10 | 11
CPU
6th Generation Intel Core i5 (or AMD equivalent) or better with 2.5 Ghz and 4 Cores
GPU
NVIDIA® GeForce RTX or GTX 9XX series or higher with 4GB
AMD/ATI® Radeon with 4GB and VCE 3.0 or higher (Radeon Pro series with 8GB for HDR and 32 bit projects)
Intel® GPU HD Graphics 530 series or higher
RAM
16GB
Hard drive
1.5GB hard-disk space for program installation
Recommended for 4K
Operating system
Microsoft® Windows 10 | 11
CPU
7th Generation Intel Core i7 (or AMD equivalent) or better with 3.0 Ghz and 8 Cores
GPU
NVIDIA® GeForce RTX or GTX 9XX series or higher with 4GB (8GB RTX series recommended for 8K)
AMD/ATI® Radeon with 4GB and VCE 3.0 or higher (Radeon Pro series with 8GB for HDR and 32 bit projects)
Intel® GPU HD Graphics 630 series or higher
RAM
32GB
Hard drive
1.5GB space for program installation, solid-state disk (SSD) for media files.
Also make sure "Legacy AVC Drivers" is not checked.
You don't want Dynamic RAM preview to take up more than maybe 25-30% of your total RAM unless you are trying to preview something using DRP and it won't render the whole sequence to RAM, then you can increase it, some.
If you have an Nvidia or AMD GPU, you do not want to use the game ready drivers. Use Studio (Nvidia) or Enterprise Pro (AMD) drivers instead. This also affects stability.
As for stability issues, I recommend you make a new thread talking about any crashes you have, and include the above dump as well as your system specs, what you were doing when it crashed, (this next part is important) if you are able to reproduce the crash by doing the same thing over again... even if not, the rest of us can use the info about what you were doing when it crashed to try to recreate the crash. The first step to fixing a bug is reproducing it on another system.
I have a vegaspro 365 subscription But Vegas pro says I have no account. Thats NOT true every month I have money taken out of my credit card. I need to update my account credit card. How do I do I do this when my account says no account for vegaspro 365