1: anyone know what exactly Quantization actually does in a video
2: I have not had a crash problem in a long time, I guess I am going to go back and work in the last build if 19 until 20 comes out with another build as 411 is having 3 or 4 crashes on an a 10 hour edit session. Too back I can't drop back to the 1st or second build of 20 as it has that weird no starting thing going on. I also ready they had the same thing happen in 19. Oh well. Open to suggestions
1. Dividing a signal into partitions, in this case frames of video. Failure to quantize in VEGAS may lead to problems with GPU decoding (and crashes) or failed renders (black frames, hangs).
Hello... I am getting beyond frustrated with Magix
I have a 365 Post account and for some reason sound forge 17 does not want to register.
For months and months SF will not work nor let me register. I even deactivated the computer and still, no resolve.
*For the entire duration of my first year of my Vegas Post account, Vegas Image never worked.
I lost all interest in it.
*The Pro Title also is not functional in Vegas 20.
I have installed all the latest updates.
Its just bad... I've been on Vegas since Sonic Foundry.😡
I have a 365 Post account and for some reason sound forge 17 does not want to register.
Please make sure that you are attempting to register Sound Forge Audio Studio and not Sound Forge Pro as it is SF Audio Studio that comes with Vegas Post, not Sound Forge Pro. Please see the following from Vegas Pro's product webpage:
I have a 365 Post account and for some reason sound forge 17 does not want to register.
Please make sure that you are attempting to register Sound Forge Audio Studio and not Sound Forge Pro as it is SF Audio Studio that comes with Vegas Post, not Sound Forge Pro. Please see the following from Vegas Pro's product webpage:
Hey boss. I downloaded the appropriate files to update my POST 365 acc. It was asking to upgrade every time I opened Vegas pro 20. My Post 365 downloaded the appropriate version for my acc. I sent them a screen shot of my products and the error code to Tech support.
tic toc... still waiting for a reply days later.
After upgrading to Vegas 20. I upgraded also my computer to a core i7 12700 25mb cache and asus mobo prime b660. In short it's much faster than the previous one and I expected to get a significant improvement in vegas. BUT things got complicated when the memory got saturated every time I loaded a project with 5.7k videos and when the same project is loaded in vegas 19 (which is still on my machine luckily) everything worked fine. Vegas 20 was hanging after a few drags on the timeline and the machine needed cold reboot. Then i found this video on youtube and after following the steps, Vegas 20 is back to normal (I had 16gb ram and I used a nv2 memory on the board to cache memory to disk) I don't usually promote youtube channels but this videos might be of help to some of you: 
I can't explain why Vegas 20 was hanging/freezing and not Vegas 19 in the same project. But still I notice some pause for a few seconds before a video starts to play on the timeline.
With all due respect to the Vegas team for their wonderful job, i would suggest that they do some case scenario tests on different machines maybe at random as users are completely lost when using so many computer configurations out there. That could lead to some precious recommendations. Remember, if you have a PC it's so difficult to try other components to find where the problem actually lies.
Have you read the specifications for how much RAM is needed Vegas 20 for 4K an greater?
Not saying you can't edit, but....
I upgraded to 32gb as the recommended specs says. The problem is still there, the same project would stutter stop momentarily in Vegas 20 but Vegas 19's playback is neat and clean. If anyone who has both Vegas 19 and 20 could do a comparison test for playback with some effects added to the clip that would help.
Are the settings in preferences/ file io the same?
I upgraded to 32gb as the recommended specs says. The problem is still there, the same project would stutter stop momentarily in Vegas 20 but Vegas 19's playback is neat and clean. If anyone who has both Vegas 19 and 20 could do a comparison test for playback with some effects added to the clip that would help.
sure, upload a clip and give info on the effects
Copy and paste attributes no longer works for Video or Audio?
No problem C&P here with latest V20
@TVJohn What effect(s) did you have on the event? I tried several different effects, and one was the Broadcast Colors effect. Can you copy the video event that has the Broadcast Colors effect and then paste attributes to a different video effect?
Never mind. I just reset Vegas and now it's working.
I have noted that there were a couple of Pan Crop incidents not working that were solved by a reset.
In the preview window, while in zoom mode, is there a way to move up/down left/right?
In the preview window, while in zoom mode, is there a way to move up/down left/right?
Yes, there is. Move the mouse around while holding the mouse scroll wheel down.
Thanks, Vegas is getting better and better. If I may post a few suggestions for better editing experience:
An option to disable the "ignore event grouping" when enabling "ripple delete". Most of the time you tend to forget disabling the events grouping and in a ripple delete mode you can for sure spoil the sync of subsequent out-of-visible-range clips. It would be useless to use "ignore events grouping' when in ripple delete.mode.
The velocity envelope for 100% is too low on the timeline clip level. Lowering below 100% to a precise percentage is a tedious work. Of course you can maximize the height of the clip to do that but on time productivity; very bad.
Please add realtime clip duration display while resizing an event on the timeline.
Please add realtime clip duration display while resizing an event on the timeline.
It's been there for years. If you've got 'Event Length' checked under the View menu, the event's timeline length displays on the event itself. That length time display adjusts automatically with any trimming made to shorten or lengthen the event.
The velocity envelope for 100% is too low on the timeline clip level.
Yes, I fully agree. It would be much better to be 25 to 30% up from the bottom of the event's frame. I guess that it can't be too far up the frame because it might be confused with the volume envelope when that has been acivated.
why VEGAS Pro 20 411 update is crashing in every 5 minutes?
same project working smoothly on Davinci ..no crash or lag....
how can i downgrade my vegas to 409 update?
how can i downgrade my vegas to 409 update?
I'm fairly sure that the update prior to b411 was b403. There's no b409 linked in the Vegas release history, but there is a link for b403:
https://www.vegascreativesoftware.info/us/forum/vegas-pro-vegas-post-release-history--104998/?page=3
VP20 411 has been rock steady for me so far. No matter what I've tossed at it (and I beta test a massive plugin on it), and it's held up without a hiccup.
VP20 411 has been rock steady for me so far. No matter what I've tossed at it (and I beta test a massive plugin on it), and it's held up without a hiccup.
Yeah, but still the VST 2 / 3 audio support make it buggy and unusable as h*ll, since build 4.0.x
Crashes, freezes, shutdowns, stuttering, ghosting, etc... it's all common when you are using it as a serious audio engineer.
It's not about "a" plugin, "an" audio format, "a" project or "a" hardware set-up; it's all about Vegas and it's happening steady, always and very ease to replicate (but no one seems to care).
I'm using Vegas since version 3 (way back in 2000 of before, can't remember) as my primary DAW.
It even started as a native non lineair DAW, so that's not quite weird.
But since build 4.0.x adjusting / fine-tuning the VST 2 / 3 is almost impossible, and I am not the only one here with those bugs.
I am still stuck to build 360, using my own native compiled .exe to bypass the infamous start-up bug.
Today I did some editing (just sliding an interview of about 30 minutes) during 16 hours of work; Vegas did crash more than eight times, froze fifteen times and even did shut down two different systems.
(undo corruption, buffer overflows, GUI freezes and some X86 equivalent for kernel panic)
It is customary that some errors created in one version are corrected in the next version. This guarantees higher marketability of the product.
I think there won't be any more fixes for Vp20.
@Petersson, I did say it was rock steady for "me". I don't use VST's so can not comment on them and have to take your word. Your profile is blank and I have no idea of the hardware you are using. But with my computer listed in my signature below, 411 works in my workflow just fine. In addition, I beta test a very well known plugin company's software, so I will do all sorts of crazy things to break it, and Vegas has held up admirably. I edit a lot of UHD 4K 24P 10bit 4:2:2 footage, and no problems, rarely a crash after hours of editing.
The VST2's that I have used worked. I have no VST3's on my computer.
I will never deny anyone's experiences and just relate my own personal experiences with the software. Again for me and what I do, it works, and I can't ask for more than that.