@Jimigune I suggest you start a separate thread with your issues. And when you do, include the complete information from this POST, especially "B" and "C" if you want help.

I personally am not experiencing your issues.

Vegas Hub doesnt work now in VP21-300..
I've logged out and in again, it seems happy with the login and the hub explorer works but when I try to open the Hub window it says ' Checking login state... ' then I'm stuck on this screen with fidgeting dots and the message 'An unhandled error has occurred. Return to Home '.
The Hub does still work on Vegas Pro 20. Ideas anyone?

The same problem here...

JCD

Vegas Hub ne fonctionne pas, sauf pour la connexion. Message apparaissant dans la fenêtre : Une erreur non gérée s’est produite. Retour à la page d’accueil.

Quelqu’un a-t-il une solution ?

Merci

It's working here.

Pas de problem ici avec le Hub (no problem here with the Hub).

The fact that "oops MXF files don't work anymore and here's a weird non-intuitive workaround" is completely unacceptable. I know this post isn't productive, but this seems completely elementary to make sure an extremely widespread professional format functions properly before releasing a new build to the masses and screwing over a huge segment of professional customers with deadlines.

I paid for version 20 but never once used it past the testing phase because it was way too buggy and slow. (brand new machine, went through all the forums, did all the crap i shouldn't have to do to try to get it to work, but to no avail. stayed on v19 which is fairly stable)

Took the chance and upgraded to 21 and it finally worked with no insane issues! Then upgrade to the new build and everything failed. All my projects were screwed over. Deadlines missed. Customers unhappy. I'm sorry but this is completely unacceptable. And I feel stuck because when you dedicate 20 years of your life to an editng program you can't just "switch to something else" quickly and easily.

Apologies for the rant - but mistakes like this are completely unacceptable to professionals literally making their living off the program functioning at its most basic levels.

I've never heard of a professional upgrading software in the middle of an ongoing project...

More green frames cropping up in version 21. This time video from a Nikon Z5. Example on twitter.

Selecting the "enable legacy AVC decoding" in File I/O of settings appears to have worked to remove it. Probably not great if I have to rely on a depreciated bit of functionality. These green frames are concerning.

General
  Name: DSC_4326.MP4
  Type: AVC
  Size: 138.15 MB (141,464,467 bytes)
  Attributes: Archive

Streams
  Video: 00:00:44.895, 59.940 fps progressive, 1920x1080x32, AVC
  Audio: 00:00:44.895, 48,000 Hz, Stereo, AAC

Summary
  [TCFM]: 6

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 21.0 (Build 300)
  Company: MAGIX Computer Products Intl. Co.

ASUS Proart RTX 4060 8GB using the studio driver 552.22 this time.

In an old Intel i7-6700 PC build with 32GB of RAM and multiple SSDs. Primary editing drive is a Highpoint SSD7204 pci-e card with 4x1TB drives in RAID10. The temporary file folder is on the OS drive.

Windows 10 Pro 22H2, OS build 19045.4170.

I've never heard of a professional upgrading software in the middle of an ongoing project...

I'm in the middle of about 20 projects - so when should one upgrade? 😉 I've also never heard of a professional program losing one of its most completely basic functions - a standard professional file type that's worked for years - just stop working for no reason.

I've since quickly downgraded back to the previous build. Been using Vegas for 20+ years and no intention of switching. I appreciate Vegas and all the work that goes into it. Simply saying that loss of a basic foundational function is very frustrating. It's like if a new version of gmail was released but any email address with ".com' didn't work anymore. hahaha It's not a special feature glitching out, its a basic necessity.

Rhetorical question or you really want to know?

The fact that "oops MXF files don't work anymore and here's a weird non-intuitive workaround" is completely unacceptable. I know this post isn't productive, but this seems completely elementary to make sure an extremely widespread professional format functions properly before releasing a new build to the masses and screwing over a huge segment of professional customers with deadlines.

I paid for version 20 but never once used it past the testing phase because it was way too buggy and slow. (brand new machine, went through all the forums, did all the crap i shouldn't have to do to try to get it to work, but to no avail. stayed on v19 which is fairly stable)

Took the chance and upgraded to 21 and it finally worked with no insane issues! Then upgrade to the new build and everything failed. All my projects were screwed over. Deadlines missed. Customers unhappy. I'm sorry but this is completely unacceptable. And I feel stuck because when you dedicate 20 years of your life to an editng program you can't just "switch to something else" quickly and easily.

Apologies for the rant - but mistakes like this are completely unacceptable to professionals literally making their living off the program functioning at its most basic levels.

I am in same boat, rolled back to 208 but seriously considering a move to Davinci

I agree with Jeremy's perspective here on existing features. At some point you have to transition to a new version and are essentially locked in if you've done any work with that because project files are not backwards compatible. You can test a new version for a while which is the smart move, but you won't necessarily cover everything. Existing features should be a different situation than new features added to the software. I'd expect new features or beta features to not be perfect.

I should not have to search for settings to get a minimal level of editing functionality with common formats like HEVC encoded media generated with OBS and AVC encoded media generated with a common well known camera (Nikon Z5). I'm surprised more people are not having the green frame issues I've seen so far. Is it that difficult to commonly support video decoding on Windows? Maybe it's a Windows 10 vs. Windows 11 thing... who knows.

I've done a fair amount of software development and see it from both sides. I imagine Vegas Pro is a very complex software project and I don't know the state and how interconnected everything is, so I do feel for the developers here. They are probably pushed to produce features that generate new sales. They also probably don't have a lot of development and support resources. That said, Jeremy makes a solid argument regarding the stability of existing features.

We're in the midst of an update to the core functionality of VEGAS, its video engine. 21.300 introduced a new decoder that is handling AVC, HEVC and other formats. While much faster for some media and working well with NVIDIA GPUs finally, it's falling apart with some particular file formats. In my own testing MXF and also AVC with many reference frames, as well as anything with mono audio.

Hopefully it will be patched soon so you don't have to revert to 208 or enable legacy AVC or experimental HEVC (both the older so4compoupnd decoder) in preferences, file io.

No question, the issues with MXF files are significant, and will be corrected for sure by the development team, as Derek stated elsewhere.

To install an update during critical projects is always a question - I would not do that, if I have agreed to business deadlines. In that situation it is always a good idea to wait a little bit, what the experiences in the community will be. I have handled that always so - regardless, if it is Edius, Resolve or Vegas. Surprises can happen.

Roger is right - the new video engine is a mayor rework of Vegas that is not finished yet. New decoders have been implemented for some footage-types, but not for all. And where that has been implemented, we see signifianct increases in speed. But there seems to be no way to avoid the new video engine.

Updates can be problematic. Some will have a flawless transition, others, will be wondering what the heck happened. I can only speak for myself, and the transition has worked with my Panasonic footage. There are some minor issues, but so far, so good.

But if I have that "upgrade itch" that has to be scratched, what I do is have separate build projects. If I am working on a current project, I will save it to that Build, B208 European Bison. Then, when I start editing in Build 300 the same project, I will save it as B300 European Bison (my current project), so if there is something drastically wrong, I can go back. It's not perfect, but allows me the ability to at least go back to a point where I can continue to edit until things are fixed.

What I do have an issue with is this, when someone runs into a problem with the software, they say they are moving to another editor. I am personally tired of hearing it. Just move on if that is what you want to do. It's like they are taking a swipe at all those that are working on the software, looking for a perfect release without any possible issues. Most of us already have other editing software we can use. If Vegas is having an issue doing something that I need done, I have other choices. But for me, I prefer editing in Vegas than the other editing tools that I have. The developers have been good at fixing things. They come here, acknowledge the issues and give assessments on fixing it.

It's about development policy and how breaking updates are handled in regard to users. If something is barely functional and doesn't work with common formats, it should be something you enable rather than disable. Or at least should be a prompt upon first startup with instructions clear to the user where they can revert to the older functional decoding engines. Right now it's a "go find it if you can..." type of thing.

Imagine if a new user is giving Vegas Pro a chance and they basically have a non-functional editing experience. Are they going to stick with it until they diagnose the problem or get an update? Not likely.

I'm going to assume the people here willing to go as far as to use the forum are a small subset of the userbase. I don't see how this is an acceptable way to roll out large changes. I bought and downloaded this from the main store page so it's live and active for all customers.

I'm not saying that the final line of customers should not get beta features, but there should be levels of testers or at least an opt-in for people if large enough alpha/beta testing groups to cover a reasonable hardware/software/media base isn't viable on a company level.

I would not think that the developers would purposely release a "bonked" update. If I were testing, I would not have any of the issues the MXF format users are having. So I would report back that "all is well". And so far, for me and the format that I use to edit, it basically is.

Someone can always go back to a previous "working" build. I would never put my time sensitive work on a new patch/build. Never. But that's "me". I will start a new project though on it to see how it behaves and if there are show stopping issues for "me". But for new user experience, yes, first impressions are extremely important. But there is more to a new user experience. Computer hardware, drivers, knowledge on how to use the software, etc..

I have zero idea of how many people use the forum/reddit/social media. Maybe I am "old school" and have always looked for a user forum, lurk, and then decide if the software is worth it. Taking into account that most forums basically have "bugs" reporting going on. Rarely do you read of a success and "easy sailing".

And as far as I have read here in the forum, there are beta testers. It comes down to again, if their hardware/software/formats are the ones that show up problematic. Maybe a file "vault" of all types of video files from the different camera formats.

@ccscotty

There is nothing wrong what you state - theoretically. We can agree about those points very fast, I am sure. In practice you are faced by other issues too. Ressources, capacities, for example.

.

Using the legacy AVC decoder it simply didn't render output on this clip (0.5 speed). Though, if I resize the clip I see output in the display window while I'm resizing it. I disabled the legacy AVC decoder and had the same result so no idea what is going on there. An old bug related to rendering out slower than normal speed clips or some additional quirk to the partly new rendering engine?

I do have ollama downloading a model in the background but it's only that one clip so probably unrelated. The GPU isn't using all of its RAM so I don't think it's a lack of VRAM issue. Again, it's the one piece of a clip at 0.5x speed rendering out as black frames.

General
  Name: DSC_4328.MP4
  Type: MAGIX AVC
  Size: 155.53 MB (159,261,361 bytes)
  Attributes: Archive

Streams
  Video: 00:00:49.950, 59.940 fps progressive, 1920x1080x32, MP4 v2 - AVC
  Audio: 00:00:49.941, 48,000 Hz, Stereo, AAC

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: mxcompoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 21.0\FileIO Plug-Ins\mxcompoundplug
  Format: MAGIX AVC
  Version: Version 21.0 (Build 300)
  Company: MAGIX Computer Products Intl. Co.

And as far as I have read here in the forum, there are beta testers. It comes down to again, if their hardware/software/formats are the ones that show up problematic. Maybe a file "vault" of all types of video files from the different camera formats.

You make a good point there on having a vault. I think they should have an archive of projects and media files they render out to verify output if they don't already. This is called regression testing. Basically if the test cases are large enough then releases like build 300 would be rare unless management forced it before everything was fully tested. Something like this would be a mix of automated testing and human verification.

@ccscotty you can attach a screenshot directly in your post. Upload button on the toolbar.

Those of you experiencing issues with this update, the VEGAS team hears your cries and is addressing them. Be patient, please, while they properly test a fix.