새로운 패치를 작업 중이지만, 땅콩 품질 관리 과정을 밟아야 하기 때문에 너무 기대하지 마세요. 그동안 빌드 302를 사용하는 것이 좋았습니다. 이 버전이 더 많이 업데이트되고 있습니다. 현재 "공식" 출시입니다.

I’m aware that build 302 has a ProRes issue, as many users already know. For someone like me who needs to produce videos on a daily basis, this creates a very urgent situation. If it were a simple bug, it would be easier to understand. However, when a rollback happens without any official announcement, it emphasizes not only the importance of proper quality assurance, but also how critical the speed of patches and improvements is for users.

@yoo-changyun When you sit down and wait untill Vegaspro is completely bugfree, you probably will wait forever...

As build 356 is withdrawn, roll back to build 302 and start editing (the cursor moves) and continue your editing with the next build that will be released probably soon. Just forget 356.

@yoo-changyun  베가스프로에 버그가 완전히 없어질 때까지만 기다릴 수 있었을 거에요.

빌드 356이 더 이상 사용되지 않도록, 빌드 302로 되돌린 후 편집을 시작하세요(커서가 첨부입니다). 이후 곧 출시될 예정입니다. 제작 356은 귀하입니다.

That’s why, even though I purchased VEGAS Pro 23 back in September, I’m still working with VEGAS Pro 22.

@yoo-changyun at the moment I'm also editing a large project in VP22 and I will probably finish that project in VP23.

I agree with your points about the next patch and also that ProRes has issues in both 302 and 356.

For chroma key have you tried color corrector secondary? I found it more configurable than the chroma keyer.

I am still on build 356, and I stay clear of ProRes. I am working on a project in that build, and did experience only once a cursor not moving (which different than a typical Vegas hang issue), and once black stills in the preview.
But after shutting down Vegas and opening again, the issue has not returned yet.

However, the silence of the Vegas team (lack of open communication) is very worrying. A silent retreat of an official build is not acceptable in my book. A non-silent retreat of an official build with an explanation why, is the proper way of communication in my book.

I also find it a strange business policy to charge for a version that is still in beta. Using users as beta testers to develop the product, only to sell it off cheaply on Humble next year.
Then loyal users pay good money again for a new, buggy version that will take a year to develop. And then the cycle starts all over again. 

I am still on build 356, and I stay clear of ProRes. I am working on a project in that build, and did experience only once a cursor not moving (which different than a typical Vegas hang issue), and once black stills in the preview.
But after shutting down Vegas and opening again, the issue has not returned yet.

However, the silence of the Vegas team (lack of open communication) is very worrying. A silent retreat of an official build is not acceptable in my book. A non-silent retreat of an official build with an explanation why, is the proper way of communication in my book.

When the acquisition was announced, I expected more staff and better support, but I can’t recall a situation where communication felt this lacking. Honestly, it feels like customer management has been handled very poorly.

Do the VEGAS administrators actually read posts on this forum? Even if they’re just quietly monitoring it, it’s hard to understand how nearly a month can pass without any kind of announcement. There hasn’t even been a basic message like, “We’re aware of the issue and are working on it.” Looking through other posts, I see many users saying they never received a response after submitting support tickets. When the acquisition news first came out, expectations were high about increased staffing and improved support, but since the acquisition, the lack of communication feels especially sever

다음 패치에 대한 대기에 동의하며, ProRes 302와 356 모두에서 문제가 관련되어 있다는 점입니다.

크로마 키 관련 색상 코렉터 세컨더리를 업무로 보셨나요? 저는 크로마 키어보다 옵션이 더 다양하다고 생각합니다.

Of course, I’ve tried them. If you compare the tools that many people are using today, it’s clear that modern editing software is evolving at a very fast pace. Honestly, aside from precise cut editing, I feel that many basic features have already been surpassed by other programs.

VEGAS’s chroma key often struggles even with well-shot footage. At first, I assumed the issue might be with the source material, but when I test the same clips in other software, they key out cleanly—without requiring any additional plugins.

Title work in VEGAS also has clear limitations with the built-in tools, often forcing users to rely on plugins or create titles in other programs and import them afterward. When comparing features such as AI masking, motion tracking, effects, and automatic silence detection for synchronized cuts, it’s difficult to say that VEGAS is clearly ahead in any of these areas today. Even its intuitive workflow—one of the main reasons I originally chose VEGAS Pro—has become less distinctive, as other programs can now achieve effects that once required multiple manual steps in VEGAS with a simple drag-and-drop action. That’s why I’ve been feeling a strong sense of urgency lately.

That said, I’m not asking for everything to be fixed at once. At the very least, I’m hoping for a stable state where the software can be used reliably without major issues. However, since the acquisition, we’ve seen silent rollbacks with no communication or announcements. Looking through forum posts, many users also report that they haven’t received any response from customer support. Honestly, it makes me wonder how things are being managed right now.

베타 버전에 비용을 청구하는 것을 환영합니다. 사용자들을 베타 테스터로 활용해서 제품을 개발한 다음, 내년에 헐값에 팔아도 괜찮습니다.
증상 원본 사용자들은 또 다시 변경 사항을 반영하여 버그 투성이 있는 새 버전을 사게 하기, 그 버전 개발에도 1년이나 할게요. 그렇게 악순환이 반복되는 거죠. 

Exactly. It feels less like being a user and more like being a tester—constantly identifying and dealing with bugs. I really hope the software stabilizes as soon as possible.

Your translation, if it is supposed to be a quote, is incorrect!

>When the acquisition was announced, I expected more staff and better support
It is certainly a same that a year after acquisition, users of Vegas are not really seeing any benefits from it - support seems to have almost vanished, and comments from Vegas reps have alluded to the team being small and thus overworked and unable to deliver all the things they'd like to. Not the development team's fault, but strongly indicative that we are not really seeing any obvious investment in the product

if the team releases betas and quietly and without apology pulls them, they will lose the last of their patient users.

Vegas probably needs to hit rock bottom a second time to change publishers and developers.

Development of the new video engine in Vegas Pro 23 was a major focus for the development team. That’s a significant investment. Naturally, more work is still required, as such a major overhaul isn’t without its challenges. Further improvements are needed there. Let’s see how things progress.

Due to not being able to use multicamera editing in Vegas, I started looking at other programs. I looked at Corel's Pinnacle video studio, but it really stunk. I also looked at Kdenlive which was pretty impressive, but I'm too used to Vegas to switch to anything else. I'm not even good at Vegas to begin with, but at least I can get projects done, while it feels like other NLEs are fighting you at every step.

Excallibur may make sense for you, as Vegas plugin. It is not free, but it is a great tool.

Due to not being able to use multicamera editing in Vegas, I started looking at other programs. I looked at Corel's Pinnacle video studio, but it really stunk. I also looked at Kdenlive which was pretty impressive, but I'm too used to Vegas to switch to anything else. I'm not even good at Vegas to begin with, but at least I can get projects done, while it feels like other NLEs are fighting you at every step.

@MikeLV I cut my Multicam teeth on Vegas over the past decade making it the only workflow I really know and am totally comfortable with. And it's only gotten better for me over the years with performance improvements in hardware and Vegas engine development. If you can't adapt comfortably to it, you might like Resolve's approach. I don't but many do. I don't necessarily suggest switching apps completely. You could do your multicam cuts among cameras in Resolve or another app, render an intermediate, then bring that single clip into Vegas to completion.

@Howard-Vigorita I took a look at Resolve a while back before purchasing Vegas 21 I think it was. I found it to be a very confusing program to use. Way above my skill level. I always come back to Vegas after looking at other programs. Even on my old system from 2013, it still runs pretty well, and I can get stuff done with it, except the multicamera stuff, although I found a workaround (switching camera angles by splitting and muting/unmuting the top track camera events wherever I want to show the camera track below) for that which I guess I'll have to use instead of the built in feature for it.

@MikeLV The big advantage I find with my Vegas multicam workflow is that I can pretty easily tweak cuts among cameras after expansion without starting over or rendering a new intermediate. I only render a new intermediate of audio mixdowns when I want to tweak them... but Vegas renders audio in seconds for even the most complex and lengthy project mixes that I do.

@MikeLV
Resolve is a great tool, IF you are willing to spent more time then for Vegas to train yourself in Resolve. Sure, that can be done. A good way to to that would be to use structured coursesm, for example from Udemy. Take two courses - one for a beginner in Resolve, to become familiar with the overal editing and working in Resole. And then another one for color grading.

I found it hard to select a good course there, but this one seems to be good for the color grading part: https://www.udemy.com/course/the-ultimate-color-grading-bootcamp-in-davinci-resolve/

Vegas will require less preparation, what may be one of the important advantages for you!