Hello,

I've got the same issue .. I followed the different steps and I've already got the same issue !

THis was working with the version 15 of vegas ! That's not normal !

I've got a lot of .MTS files and when I render them to a MP4 file i lose quality. I want to render them to a AVCHD format.

MAGIX SHOULD HAVE a solution ! It is working on V15 and not workiong on V22 .. That's NOT NORMAL !*

@Jean-yves Your issue doesn't appear the same as the OP was going from mp4 to m2ts. You are going from mts to m2ts.

Anyway why cannot you render? Assuming VP22 has the same render options as my VP21 there's an AVCHD template in the Sony AVC/MVC render options.

Hi Ericnlz,

Yes i'm trying to render from mts (jvc cam recorder), to m2ts (avchd format)

When i want to render, i get an error message which tell me that com object can't be initialized ...

Same action in vegas 15 works fine.

I found a 'solution' on the net (uninstall all visualc++ package, then reinstall th elatest version ...) i did it ...but the issue is still there 🥴 i dont understand why this option (render to avchd) doesn't works in 22 version of vegas and is successful in 15 version ...

If you've got some ideas ...

Thanks,

Jyves.

... Of course i'm trying to use avchd template !

@Jean-yves What's your GPU and driver version?

Could it have something to do with the AC-3 (Dolby Digital) encoding, which is no longer supported since Windows 11 24H2 (new installations)?

(Microsoft no longer includes AC-3, but some video editing programs are programmed in such a way that they rely on the operating system's codec support.)

https://support.microsoft.com/en-us/windows/codecs-in-media-player-d5c2cdcd-83a2-4805-abb0-c6888138e456

@Jean-yves vegas-edit-user raises an interesting point with AC-3. Are you experiencing your problem with VP22 installed on a pc with a fresh install of Win11 24H2?

Hi,

Yes, i'm aware of this problem with ac-3 and windows 11.

On the same computer, on which the 24h2 version is installed, i can render an avchd file with the version 15 of vegas, but i can't with the version 22 !

So, m'y conclusion is that the issue is not linked to my OS but linked with vegas version ...right ? Could someone replay the problem on his / her platform ?

1- on a windows 11 24h2 version

2- on Vegas pro 22 version

3- import a mts file

4- render it to avchd 1920x1080 50ips

... Does it works ?

... I can add that even if ac-3 is not longer supported by Microsoft, vegas continue to 'play' the sound in the video (that's why i'm choosing vegas vs cyberlink ...)

If Vegas is playing the audio in your mts files then it's not an AC3 problem.

Unfortunately I don't have VP22 but all is okay on VP21. But my Win11 24H2 is not a fresh install but an update from an earlier Win11 build. Anyone checking with VP22 needs to state the nature of their Win11 24H2.

Oops - correction. My Win11 is 25H2.

Just for completion about ac-3 in Vegas Pro 22 ... after a clean install of Windows 24H2 (which excluded native Windows ac.3 support), Vegas Pro 22 build 248 re-introduced ac.3 support within VP. From the build 248 announcement:

• Support for AC3 media on Windows 11 systems with update 24H2 installed 

Build 248 was soon replaced by build 250 - the last VP22 build - but for other reasons.

I understood that an AC-3 decoding solution had been created within Vegas 22 by Magix (regardless of the operating system). But AC-3 encoding, which is linked to AVCHD export, was not reintroduced.
As far as I know, Vegas 15 still had a different AC-3 encoder than later versions of Vegas.

As I remember from burning Blu-Ray earlier versions of Vegas had AC3 and AC3-Pro. Around V15 the AC3-Pro was removed due to Licensing issues. The last version where you could work around this was V16. From V17 only AC3 standard version was available. I am a fan of AC3 as to my ears it provides a more open delicate sound than AAC.

@Jean-yves We haven't managed to solve your "COM" problem. What exactly does the complete error message say? A screen shot might be useful.

@EricLNZ Please find attached, a screen shot !

This issue is not present on version 15 - same OS / same Computer. !!

https://www.vegascreativesoftware.info/us/forum/rendering-issues-after-gpu-replacement-nvenc--150382/

It's caused by the nVidia driver 591. Please revert back to 581 and it will work again.

@Jean-yves Unfortunately you haven't told us what your GPU is and it's driver version.

If it is nVidia then as an alternative to jetdv's suggestion go, in VP22, to Options/Preferences and the Video tab and look at "GPU acceleration of video processing". What are your drop down options? Try a different one if there's one available. AVCHD rendering is old and personally I don't use my nVIDIA but use my Intel IGPU.

Hello Eric ! please find attached, the optons regarding my GPU acceleration .

As you can see, my configuration is very simple !

I'm using the 'defautl' hardware' installed on my computer (DELL Optiplex 3070 - micro format)

I try with the option 'deactivate' .. and the result is the same .. same issue !

(i have the same GPU on VP15 and it works :( ..

@Jean-yves The mystery deepens. Deactivating means only your CPU will be used so it seems it's not a GPU problem.

There have been many changes to VP between versions 15 and 22. Searching on the net for "The COM object could not be initialized" comes up with info way above me. There must be something on your system that VP 22 doesn't like or is it needs that is missing. I wonder if your Microsoft C++ items are up to date? If you haven't done so filing a ticket with Vegas Support may be needed to get it sorted.

If you render to an avc video file using either Sony AVC/MVC or MAGIX AVC/AAC using Blu-ray video stream templates do you get the same error message?

The templates for Sony AVC/MVC or MAGIX AVC/AAC output Blu-ray video streams without (AC3) audio and do not throw the COM object error.

I think the problem is that Vegas 15 still has the Pro Encoder for AC-3 and can therefore still encode Dolby. This Pro Encoder was later removed due to licensing issues.

Vegas 22 only has Dolby Digital decoding capability.
However, in configurations where previous versions of Windows were upgraded to 24H2 or 25H2, AC-3 encoding is still available via the AVCHD template.
This is supported because Vegas can still access the operating system-side codec in this case.

In Vegas 23, the AVCHD template has been removed anyway.

I think the problem is that Vegas 15 still has the Pro Encoder for AC-3 and can therefore still encode Dolby. 

I don't think that VP14 to VP16 had AC-3 Pro; rather, AC-3 Pro could still be used in VP14 to 16 if the following workaround was used (point 31):

31. How can I enable the Dolby AC-3 Pro encoder from VEGAS Pro 13 in later versions?

• The Dolby AC-3 Pro encoder was removed in VEGAS Pro 14. If you have VEGAS Pro 13 and DVD Architect installed, you can enable the encoder in VEGAS Pro 14, 15 and 16 (but not later versions) using this workaround.

Using the workaround, I still create AC-3 Pro 5.1 renders in VP16 for use in DVD Architect 6.

Vegas 22 only has Dolby Digital decoding capability.
However, in configurations where previous versions of Windows were upgraded to 24H2 or 25H2, AC-3 encoding is still available via the AVCHD template.
This is supported because Vegas can still access the operating system-side codec in this case.

@vegas-edit-user Are you 100% sure of your last line above? I ask because I wonder if with the Vegas AC-3 decoding fix there is a problem with VP accessing the Windows AC-3 codec. If so this would explain the problem that Jean-yves is experiencing.