I used no profanity ...

Really? How about:

I do not care what other companies are doing like Adobe eg but this subscription bullsh1t has got to be dumped.

You would make more money by concentrating on quality than on bullsh1t version ...

I absolutely refuse to use this subscription BS

Replacing a letter within an expletive indicates full knowledge that the word being used is usually considered to be unacceptable.

... and it is Maxons right to offer it ...

I think that you may mean 'MAGIX'. Maxon doesn't own or release Vegas Pro.

Text To Speech just stopped working, I've restated, shut down you name it. it just wont generate speech. That's Vegas Pro 21 365. It works just fine on VP20. Whats up guys?

First, is there any way to sort this forum with the most recent first? Sort of useless to look for the most recent bugs/workaround after having to move to the bottom of the thread (it used to have the option to sort by the most recent).

Second, I have Pro Post Edit 21. I made the mistake of using it for a live project (small but live). Editing would freeze and crash about every 20-30 minutes. Fine, I saved often.

But most of my errors are now black frames. I have rendered it 10 times, each time I adjusted and then fixed the transitions where it would blink and turn black for a few frames. Sometimes only the straight transition worked, then only the swoop, and some I could never get to work without black frames showing up.

Each render produced a new set of render errors--most were wherever there was a crossfade, but a few occurred in the middle of any footage where I made the video slower. A video above is transitioning to the video below and then.... about 5-10 black frames show up and then it continues. It happens in multiple parts of the video.

It is a project stopper bug and I cannot get a single clean version to render. I am using mainly default settings, some of the video is coming from a Canon DSL, and other is coming from Camtasia (it is a software demo).

Anyone know of any viable workarounds?

BTW, I got notice there was an update (I am using 108), but I dismissed the message thinking I could select the help/software update later, but it doesn't show an update.

Thanks in advance - Ted

I think the issue may be with the Camtasia software. Try re-encoding it with a tool like ShutterEncoder (output format h264 is fine; if size is no issue ProRes is great) and right-click on the media to replace the file in VEGAS.

108 is the latest build of VP 21- the update is for VEGAS Image.

Can you add your CPU and GPU model to your signature?

GPUs can only accelerate certain formats... not sure XAVC-S is among those.

First, is there any way to sort this forum with the most recent first? Sort of useless to look for the most recent bugs/workaround after having to move to the bottom of the thread (it used to have the option to sort by the most recent).

Second, I have Pro Post Edit 21. I made the mistake of using it for a live project (small but live). Editing would freeze and crash about every 20-30 minutes. Fine, I saved often.

But most of my errors are now black frames. I have rendered it 10 times, each time I adjusted and then fixed the transitions where it would blink and turn black for a few frames. Sometimes only the straight transition worked, then only the swoop, and some I could never get to work without black frames showing up.

Each render produced a new set of render errors--most were wherever there was a crossfade, but a few occurred in the middle of any footage where I made the video slower. A video above is transitioning to the video below and then.... about 5-10 black frames show up and then it continues. It happens in multiple parts of the video.

It is a project stopper bug and I cannot get a single clean version to render. I am using mainly default settings, some of the video is coming from a Canon DSL, and other is coming from Camtasia (it is a software demo).

Anyone know of any viable workarounds?

BTW, I got notice there was an update (I am using 108), but I dismissed the message thinking I could select the help/software update later, but it doesn't show an update.

Thanks in advance - Ted

That sort of thing would happen to me if the events were not quantized. Have you tried that?

Try re-encoding the clip from camtasia using shutter encoder or handbrake. Also use the driver update utility in the help menu to see if vegas recommends different drivers.

Roger S: Following is my system (I also just added it to my latest Signature):

Windows 11 Pro, i9 (10500 - 20 logical cores), Corsair water-cooled, MSI Gaming Plus motherboard, 64 GB Corsair RAM, 4 Samsung Pro SSD drives (1 GB, 2 GB, 2 GB and 4 GB), AMD video Radeo RX 580, 4 Dell HD monitors.Canon 80d DSL camera with Rhode mic, Zoom H4 mic. Vegas Pro 21 Edit (user since Vegas 2.0), Camtasia (latest), JumpBacks, etc.

Roger S and fr0sty - Thanks for the tips on Camtasia--I rendered the file, so I can try another format. Also, I had problems with the latest AMD driver (caused colors to be off), so I reverted to a prior version that folks in the forum suggested--colors are working fine now. I have rendered using the CPU and without it--no difference with the black screen artifacts.

MindMatter - I suspected the quantized setting, but everything snaps to the frame and it says I have quantized enabled (I usually only uncheck it when I am doing music), but I'll double-check.

Thanks for the tips. I'll report back updates if I can get it fixed.

BTW, once I knew what to search for, Camtasia errors with black frames looked common. Here is the workaround within their forum (haven't tried it yet--but interesting to note). https://support.techsmith.com/hc/en-us/community/posts/360072040372-black-frames-added-at-splits-in-video

Nothing is fixing this. The errors are not just with Camtasia files. Most occur during transitions regardless if using other stock video or Camtasia screen captures. I have changed the properties, selected the offending videos, and tried no resampling, or variants, checked with quantization, I have now rendered about 20 different times trying different rendering formats and settings (Tried all Magix variants, the old formats, even Apple Pro Res). It is all the same--although the errors are often in different places (fix one, another pops up). The problem is that some of the errors only show up during rendering, but are not visible during preview, or even RAM preview.

I'm caulking it up to an overall bug in Vegas 108 build. Here is a rendered version I just posted on YouTube. It's about 3 1/2 minutes and some of the errors (black frames, hard transition with errors vs smooth transitions) occur within the first 60 seconds.

It still needs color correction for the face (don't judge it yet ;-), but I didn't want to introduce additional variables until I got the basic rendering corrected. It is posted as UNLISTED at:



Errors
:23
:31 (big error)
:48 - black blink, no transition (have tried different transition styles--some work, some don't, or don't work the next time it is rendered)
1:36 - black blink.

There are others throughout the video.

BTW, I have done dozens of similar videos with prior versions of Vegas (I started with Vegas 2.0--over 20 years ago) and I NEVER had this problem... ever. I may have to use my combined finished videos that have errors in different places and cover over other errors to end up with one that is usable (although run through the compression twice).

BTW, another prior fix was to go to options and turn off "close media files" not in use. This fixed this error in prior versions. However, if I select it in Ver 21, it freezes the timeline when it finds one of the prior errors (and yes, I re-started Vegas after applying the preference option). So that doesn't work.

Thanks for the glitches showing the errors in your video.

Can you confirm your CPU? the 10500 is an i5 processor. https://www.intel.com/content/www/us/en/products/sku/199277/intel-core-i510500-processor-12m-cache-up-to-4-50-ghz/specifications.html

If it has an iGPU please enable it in bios and then it should help with decoding in VEGAS. That may help with media issues.

Others are using the Radeon RX 580 and I haven't heard of issues in general (other than driver bugs which keep them from updating past 23.7.2).

Does rendering as MagixAVC/Mainconcept also show these issues?

In older versions of VEGAS, setting dynamic ram preview to 0MB for renders avoided some errors. Does that help? Alternatively turn off GPU acceleration in preferences/ video. Keep both enabled for editing as they affect performance.

My mistake in my profile--I just changed it. It is an i9 10850k (20 logical threads), not an i5. - I will enable the iGPU since it has it--let's see if that helps. I already run with a slightly older AMD driver for Vegas and it works fine, since the latest does not work at all (says I don't have the correct system resources).

BTW, I had two older Quicktime video b-footage files (had to Install Quicktime to view or import into Vegas). I also had the legacy Quicktime selected. I removed the Quicktime MOV files and replaced them with MP4 files.I then turned off legacy support, re-saved, and re-booted. It did not fix the problem.

Thanks for the new ideas,

- I have tried about 6-7 different rendering formats. The Mainconcept 2 profile only had a 1920x1080 25 frame option--throught it was odd that it didn't have a 29.97 profile. So, I didn't use it. I've got a custom profile rendering now to test.
- I have my dynamic RAM set to about 3 meg, since I seldom use it (all my drives are SSDs and with my horsepower and only have HD footage, I wouldn't normally use it), although I tested a few glitchy spots with dynamic ram and they were fine--but it still rendered with the black glitches.

I'm into this about 35 rendors and about 10 hours--have watched every video and tested every option. I probably could have re-built everything by now. BTW, I am using video created from Premier Pro (it was sent to me). Who knows, it could be that. I just asked them if they sent me the files from there camera, or from Premier. Let's see.

All I know is I have been making these kinds of software demo videos for over a decade and this is the first time, with Camtasia, photos, B footage, and a live narrator. I have had so many problems. I'll try the iGPU option, and report if I find a fix. I'm more than a little frustrated... after this many hours. Thanks again for your response.

BTW, the Mainconcept didn't make any difference--same bugs.

Please see my signature for two sample projects (known good) and good render settings. Do either render with glitches?

If you made changes based on YouTube videos, revert them all before doing tests. https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

MagixAVC with Mainconcept has 29.97 options:

For dynamic ram preview just test with 0 (off) or 5%, any number greater than 0 may show glitches if this is the cause of the problem.

How did you rerender the Camtasia file? You could even try converting to ProRes in ShutterEncoder or VEGAS which would eliminate it as a cause of any issues.

I enabled the iGPU. No difference--still errors during preview and for rendered videos. Yes, I have used MagicAVC with 29.97 (and I noticed it uses Mainconcept), but I also used the Mainconcept Mp2 below that). I have used about 8 of the different options (and variations within)--no change.

I'll test the dynamic ram (although I was only using 3 meg (and I have 64 GB) tomorrow. The sad thing is everything worked fine on similar projects using version 19.

Vegas is notorious for using almost every file format and producing great results. The Camtasia file was rendered using the default 1920/1080 MP2 export format (same as I usually do). However, this error is not just with Camtasia files--so that wouldn't be the problem.

Most of the errors occur at a TRANSITION point (between regular video, between Camtasia, or between two stock MP2 videos on the same timeline). It appears to be the transitions that are the common thread. So, I reverted many of my fade transitions (regardless of fade type--I tried them all) to straight cuts, but some just need fades. But I still need cross-fades in places, but then I get black frames before, and sometimes after, but most of them occur at the line of the transition.

I am going to re-construct it in ver 19 and chalk it up as a ver 20 error. I should have known better, Vegas 1st commercial releases are notorious for bugs (so is a lot of software). I was just hoping for an update that would get this fixed.

Thanks for all the suggestions. I am massively behind on other projects because of this.

Users are reminded of the OP which advises to "Please use this thread to post general comments on this update". Note that comments cannot be "split" off a topic and moved to a new topic. Specific problems may be lost here and not get the attention they deserve. Thank you for considering this.

I agree this would be better as its own thread.

Vegas is notorious for using almost every file format and producing great results.

That may have been the case a decade ago, but as VEGAS grew to use GPU capabilities it also became more picky about what types of media work well.

Anyway for transition glitches, try dynamic ram preview at 0MB and/or GPU preview acceleration in preferences/video to off.

Since you are using CPU-only render templates with Mainconcept, GPU encoding isn't a factor (MagixAVC also works with QSV, NVENC, VCE).

VP 21.108 isn't especially buggy and is basically a refinement of the last build of VP 20- there aren't hard distinctions between versions these days as the program is continually developed and updated.

Does anyone else think the Motion Capture is just plain awful? I miss the Vegas 17 Bezier method. I'm considering a refund. The Ai Masking sucks too

hello, definitely since the installation of version 21 nothing works correctly, (example)
when a project is open, if I want to add an ''audio track effect''
as soon as I add one! vegas crashes and shuts down by itself
I have to reopen vegas, reopen the project, start again what I haven't saved...
another error message "the sound mapper cannot be found" ...crash result (integrated realteck sound card asus motherboard).
can you help me?????? because I'm not moving forward with my projects at the studio.
thanks in advance
benoit from bg-events.net

@benoit-berdoux, open a separate post with your issues and include "B" and "C" from this POST if you want help.

Playing "20 questions" to get to something that can be easily addressed by including that information, saves users here in the forum a lot of time.

I just added several audio effects at the track level and no issues.

@benoit-berdoux opened a separate post here https://www.vegascreativesoftware.info/us/forum/vegas-crashes-as-soon-as-we-add-an-audio-effect--143123/

Please continue discussing his issue there.