Can anyone at Magix tell me when 365 subscribers will be prompted for the V21 update ?
I didn't get prompted to upgrade. But if you go to your Magix account (https://www.magix.com/), download the installation program again for 365. Install, and you will be installing v.21
Edit: MAGIX account link corrected: https://www.magix.com/int/support/my-service-center/
I've downloaded Vegas 21 on the subscription. Trying to edit 4K footage from a Sony FX6 and the program is so laggy I can't work even in "preview" mode. No FX added. I have a FAST computer.
Specs: - Windows 10 Pro for Workstations, 64-Bit
- Intel(R) Xeon(R) E-2286G CPU @ 4.00GHz
- 65365 MB RAM
What's the media format? If HEVC try unchecking legacy in preferences, file io. Do you have a GPU?
I have a FAST computer.
Intel(R) Xeon(R) E-2286G CPU @ 4.00GHz - 6 Cores, 12 threads
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.
Not exactly fast... The CPU is almost 5 years old and below recommended specs for 4k. Your best bet us to use proxies. Right click on your media and select "create video proxy". from there, set the preview quality to either "preview" or "draft", you'll find the place to set it just above the preview monitor. It'll take some time to create the proxy, but when done, you'll notice a huge difference in playback speed.
OK, I have now got the full working version V21. It is good to see Mocha Vegas now available in Vegas Pro. The question I would ask is if I were to purchase Vegas Effects would it have Mocha in Vegas Effects like After Effects does.
Hi, I have VEGAS Post 20 and I installed trial version of VEGAS Post 21, now I have to restore the PC back to before the install, because it replaced VEGAS Effect & VEGAS Image, and now I can't access VEGAS Effect in either version V20 or V21 nor standalone. it keeps saying you need to activate VEGAS Post and I did that many times. I need VEGAS effect to work with V20 at least while I'm testing other features in V21
it replaced VEGAS Effect & VEGAS Image
oh dear …
I find it very odd, almost bizarre that I cannot open a clip in Vegas effects from Vegas 21. My Vegas Effects is 2 years old, and I know there are those that will say it's not what Magix do or have ever done, and that I will have to purchase a new copy to access VE from V21. So why then can I access Vegas Image from V21, but not VE.
From where I am sitting it looks as though Magix does not have much confidence in the latest version of VE, or that there is so little difference between the VE versions. It also seems very mercenary and small minded of Magix to explicatory design V21 no to be able to access older versions that they have already sold to their customers.
I am using many other add-ons that are way older than 2 years from within V21.
If Vegas Effects was truly worth changing/upgrading I would do so, but to be honest I will consider other applications first if this is their attitude.
Pretty sure there's a workaround to use older versions of Effects. Did you search the forum?
Vegas Pro 21 installed and working well (alongside v20 for now, I'm on the pro 365 subscription). What's the latest advice on settings for getting the best playback with HEVC files please (from A7siii)? If I tick 'use legacy HEVC codec' I get just about useable playback without proxies. If I uncheck the legacy option I definitely need proxies for useable playback. Is the legacy option still likely to cause more crashes? Or is it down to individual set ups what will be most reliable? AMD 6700xt and 5900x system. I'm happy using proxies so the main benefit would be for better playback when switching up to Good/Best for grading.
Update: After more editing time on V21, I notice that proxies go with the HEVC decoding option selected. i.e. Proxies generated with legacy HEVC decoding unchecked aren't recognised if you switch legacy back on (and vice versa). So it looks like I'll be sticking with legacy HEVC off as all my V20 proxies were created with it off. That explains a weird problem I had moving from V19 to V20 when I thought it had lost all my proxies. Nice to learn something new on a Friday afternoon...
where do i get a trial period for vegas pro21 please. it is urgent
From 'Free trial' underneath the purchase options in https://www.vegascreativesoftware.com/us/vegas-pro/?_ga=2.34439649.1562069070.1668563166-702914177.1667974548 on Vegas Pro's product webpage.
@fr0sty / @pierre-k / @VEGASPascal (can't mention him?)
I did install Vegas 21, build 108 and tested it against some of my submitted bugs.
Please see those threads for more details;
CONCLUSION
____________________________
Long story short : the future looks promising, but many of the bugs are still there.
I decided to stay / stick with Vegas 20 / build 370 for the moment, especially because of bug 1, which makes daily work frustrating in Vegas 20 / build 4.x.x and Vegas 21 / build 108.
Once this bug is squashed, I will try again and "jump" to the next build.
For now, I think Vegas did make the right decision to focus more on audio and the development, because it's worth it.
I know you want to have Vegas perfect, just like I do. But if you only work with sound, don't you want to try other software?
I've been using Cockos Reaper for years for sound and music editing. It has exactly the same controls as Vegas. In addition, marking events with the right button is revolutionary.
The Vegas folks have a lot of catching up to do.
The Vegas folks have a lot of catching up to do.
That's why I am trying to help the team with detailed, constructed, archived and well documented bug-reports.
Audio is 50% of a good video, so it's not "just" audio.
And Vegas is a dedicated DAW, like it started way back in the first place.
But if I understand you well, this is the advice;
Sorry, but I want Vegas to become better and more usable and the only way to do that, is by reporting bugs and creating bug-squashing iterations of your product.
BTW. I did use Reaper, Studio One, etc... but the workflow / GUI / interface (and integration with Sound Forge Pro) is not half as good as Vegas.
I like Vegas, that's why I use it, that's why I try to help squash those bugs.
And last but not least: I am working on a single audio-project for about ten years now (using Vegas). I am about half-ways so I have some years to go. And I can't switch development environment after 6 years of hard work. I still have to work with Vegas (20 / build 370), also because you can't open Vegas 21 projects in Vegas 20 once you decided to jump across (the brige).
________________________________
The Vegas-team even hired a dedicated audio-developer and almost 3 out of 5 bugs (reported by me) are now squashed, or at least become better (less worse).
So someone is listening.
But if I understand you well, this is the advice;
- Don't disturb the Vegas-team with annoying bugs they created themself
- Don't use Vegas for audio, only use it for video (muted)
- Other software is way better than Vegas; don't use Vegas
- Vegas is bad, they have a lot of catching up to do, so don't post here
Neither option.
That's right... Cockos Reaper is better for more complex audio work at the moment (due to the same control style). However, if I only need a third-party Maximizer plugin for voiceovers and a limiter for output, then Vegas is ideal. The internal Vegas plugins are old and most unusable, but I believe this will change.
I didn't mean anything else. And if so, I'm happy to write it.
I am not hostile. We both have the same goal.
I am not hostile. We both have the same goal.
@pierre-k I just want to help those folks out there as well 🙂
But I do some "serious audio sh*t" with Vegas, and no single other software can do that.
Reaper is fun for basic audio, not serious editing (and sound restoration) in combination with thing like RX and Melda.
By the way, besides an old-skool audio-engineer I am also a professional (like "I make money with it") software developer.
I "see" why and where those bugs take place, and it's in the core of the system.
The enveloppe audio-bug e.g. for example is not strictly "an audio bug", it's a sign there is fundamentally something wrong with the way Vegas handles 3rd party plugins; that's serious sh*t.
So when they are able to fix those "audio related" bugs, also the "non audio" bugs are gone; it makes the core of Vegas better (where it fails now).
And that's good news for all of us.
It would be great if there was one developer on the team who specialized in various small improvements that would make our daily work easier.
I remember boom - Event Handles for events.
People were euphoric about it. It was a wonderful idea. And it is said that the development only took a few hours. There is nothing like that in the latest version, except for the highlighted icons. Which is very little.
I looked in the archives and here is a list of my old wishes. Some of them are still not implemented, which is a shame.
https://www.vegascreativesoftware.info/us/forum/automatic-windows-fx-resizing-update--136512/
https://www.vegascreativesoftware.info/us/forum/speedy-edit-with-the-right-mouse-button--104440/
https://www.vegascreativesoftware.info/us/forum/vegas-pro-feature-requests--134374/
@Petersson Thank you for your feedback. We will try to get those issues fixed and shipped with a next update.
I have a special note on Bug 1 from your list though: Build 370 of VEGAS 20 may seem to have " better performance" just because the communication between host and plugins was missing on many different levels. We are now monitoring the state of VST plugins in a very detailed way, which yes, has slowed down the performance here and there at first, but as you saw yourself, the initial automation envelope bug was fixed. Thank you once again for reporting that. We will try to improve the other way around too, but I just want to explain why this is not "a sign there is fundamentally something wrong with the way Vegas handles 3rd party plugins" - it is just that some plugin providers really need such parameter changes sent from the host to be explicitly done on the GUI thread, which interferes with your mouse movement and causes this lag. It is a problem and we will come up with a solution for it now that you made us aware of that, but at least we are sure that all changes are recorded correctly. We believe that this improved communication between VEGAS and the plugins is worth knowing about and in our opinion worth the update. Thank you once again
I simply use Vegas to edit and render GoPro videos. I always look forward to the next version being released. However, V21 feels more like "time to pay your yearly subscription" than feature improvements that I've seen in previous releases.
Vegas Pro 21 installed and working well (alongside v20 for now, I'm on the pro 365 subscription). What's the latest advice on settings for getting the best playback with HEVC files please (from A7siii)? If I tick 'use legacy HEVC codec' I get just about useable playback without proxies. If I uncheck the legacy option I definitely need proxies for useable playback. Is the legacy option still likely to cause more crashes? Or is it down to individual set ups what will be most reliable? AMD 6700xt and 5900x system. I'm happy using proxies so the main benefit would be for better playback when switching up to Good/Best for grading.
Update: After more editing time on V21, I notice that proxies go with the HEVC decoding option selected. i.e. Proxies generated with legacy HEVC decoding unchecked aren't recognised if you switch legacy back on (and vice versa). So it looks like I'll be sticking with legacy HEVC off as all my V20 proxies were created with it off. That explains a weird problem I had moving from V19 to V20 when I thought it had lost all my proxies. Nice to learn something new on a Friday afternoon...
@gabgilson This proxy comment is not how VEGAS is supposed to work. The proxy files are 720p XDCAM regardless of the source file and are used when preview is set to draft or preview. Want to see the original file at full resolution? Switch to best/full (though you know that). Are you saying there's a new bug where they are ignored depending on the decoder selected? Let me try testing that here.
For whether legacy or non-legacy HEVC decoding is best it depends on the media and the GPU. From what I can tell the new version uses modern GPUs' ability to decode HEVC. Legacy also uses the GPU but in different ways. With my Intel iGPU it's generally better using the modern decoder. I can't say for AMD.
What's your HEVC type? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/
I simply use Vegas to edit and render GoPro videos. I always look forward to the next version being released. However, V21 feels more like "time to pay your yearly subscription" than feature improvements that I've seen in previous releases.
@Hamilton53 ... You are not alone here. I did not upgrade to Sound Forge Pro 17 because it didn't offer me anything I already used and needed in Sound Forge Pro 16. It's always a good idea to check out the new features in upgrades to see if they are useful for you - and there are always trial versions for you to check it out before buying.
I loaded two HEVC 10-bit files (Canon and Sony) that play back horribly on my laptop without a proxy file. With legacy HEVC off I made proxy files. They were used on playback (full framerate). I changed the preferences to legacy HEVC and tried again. I still have full framerate, not the <1 FPS I was getting before.
Switching back to best/full I am getting a terrible framerate.
So from what I can tell with this computer at least and these test conditions proxy files are working normally.
I loaded two HEVC 10-bit files (Canon and Sony) that play back horribly on my laptop without a proxy file. With legacy HEVC off I made proxy files. They were used on playback (full framerate). I changed the preferences to legacy HEVC and tried again. I still have full framerate, not the <1 FPS I was getting before.
Switching back to best/full I am getting a terrible framerate.
So from what I can tell with this computer at least and these test conditions proxy files are working normally.
@RogerS Thanks for checking this. I've just tried it again with a fresh V20 project (in case it was something to do with jumping from V20 to V21) and same thing for me again. I have a proxy created with legacy off playing fine. When I turn legacy on, it doesn't see the proxy. If I right click on the file in the media explorer the 'create proxy' option reappears. When I switch back to legacy off (closing and opening vegas needless to say) then the create option is greyed out. See below for media info dump in case useful.
a7siii\CS38918.MP4
Format : XAVC
Codec ID : XAVC (XAVC/mp42/iso2/nras)
File size : 1.13 GiB
Duration : 1 min 1 s
Overall bit rate : 158 Mb/s
Frame rate : 59.940 FPS
Encoded date : 2023-08-02 09:13:26 UTC
Tagged date : 2023-08-02 09:13:26 UTC
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1 min 1 s
Bit rate : 150 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.302
Stream size : 1.07 GiB (95%)
Encoded date : 2023-08-02 09:13:26 UTC
Tagged date : 2023-08-02 09:13:26 UTC
Color range : Full
Metas : 3
Codec configuration box : hvcC
Audio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 1 min 1 s
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 11.2 MiB (1%)
Encoded date : 2023-08-02 09:13:26 UTC
Tagged date : 2023-08-02 09:13:26 UTC
Other
ID : 3
Type : meta
Format : rtmd
Codec ID : rtmd
Duration : 1 min 1 s
Bit rate mode : Constant
Encoded date : 2023-08-02 09:13:26 UTC
Tagged date : 2023-08-02 09:13:26 UTC