@thesammy58 Check that you have QT installed although if it worked with earlier VP versions it should still be there.

Thanks for replying, I do still have it installed and am able to open QT itself. I'm curious to see if anyone at all has actually gotten this to work with VP23 or if it's really just me. I know it's a pretty uncommon video type to render.

@thesammy58 said: "I'm curious to see if anyone at all has actually gotten this to work with VP23 or if it's really just me."

I installed Quicktime as a test for you and was able to render from Vegas Pro 22-250, but have been unable to render Quicktime from Vegas Pro 23-302.

I am a frequent user of the deprecated Quicktime plugin...

For what purpose do you need a Quicktime render, to get a render with alpha channel?

@thesammy58 said: "I'm curious to see if anyone at all has actually gotten this to work with VP23 or if it's really just me."

I installed Quicktime as a test for you and was able to render from Vegas Pro 22-250, but have been unable to render Quicktime from Vegas Pro 23-302.

I appreciate that. This is quite strange. My hope is the devs simply forgot to add it to the new render options window and that it hasn’t been discontinued.

Would love to see if any VP devs here could help us figure out what’s going on

The fact that it's on the deprecated tab means it's already been "discontinued."

@thesammy58

If you didn't get the information about Quicktime (on Windows) not being supported by Apple, here is the Wikipedia paragraph:

"On April 14, 2016, Christopher Budd of Trend Micro announced that Apple has ceased all security patching of QuickTime for Windows, and called attention to two Zero Day Initiative advisories, ZDI-16-241[130] and ZDI-16-242,[131] issued by Trend Micro's subsidiary TippingPoint on that same day. [15] Also on that same day, the United States Computer Emergency Readiness Team issued alert TA16-105A, encapsulating Budd's announcement and the Zero Day Initiative advisories.[16] Apple responded with a statement that QuickTime 7 for Windows is no longer supported by Apple.[14]"

I have system image backups that I can restore in less than five minutes, so I was willing to test.

Going forward, plan to keep an older version of Vegas to do conversions to other formats as the need arises. Apple Pro Res is supported by later versions of Vegas Pro. MagicYUV supports transparency and lossless intermediates. If the development team relents this time, consider yourself advised about what is eventually going to come.

@thesammy58 You need to be aware that Quicktime has been long discontinued for Windows, Ten years actually, yeah, Ten years..... The development team keeping it as a deprecated feature for so long is being kind.... In the Adobe world of Premier Pro and After Effects their is absolutely no trace or support for anything Quicktime.

Yes, I understand it is a “deprecated” feature that still, however, has an option available in the settings that suggests it is available for use. Get rid of the option if it’s unavailable.

If it’s been removed, okay. But I don’t see the point in defending the team here. There was no documentation of it being officially removed once and for all. This has already happened with VP23’s removal of the stereoscopic 3D feature (which was never listed as deprecated to begin with) and now it seems it’s happening again in a different form. VP23’s marketing team seems to have a transparency issue with its customers because users should not be finding out that a feature has gone completely missing after the fact—all because there was zero documentation anywhere of any feature removals.

It leaves me apprehensive to make purchases in the future because things keep vanishing without any prior warning.

@thesammy58 said; “… users should not be finding out that a feature has gone completely missing after the fact…”

I agree. There is a change log.  There is a trial.

@thesammy58 said; “… users should not be finding out that a feature has gone completely missing after the fact…”

I agree. There is a change log.  There is a trial.

So far I have yet to see the change logs referencing the above removals I mentioned or the manuals updated, even after a dev acknowledged months ago that the removal of stereoscopic 3D went undocumented and was not handled well. I imagine more users are continuing to find out the features they used and paid for have been unknowingly removed and have to find a refund.

Expecting your users to use a trial any time there is a new release does not seem like a good faith business model towards your consumers. Just be transparent instead of expecting them to perform a trial run in order to investigate every single feature to sleuth for any new removals themselves. We don’t get paid to be their quality control or beta testers. It’s especially clear that this wasn’t handled well either because the option for QuickTime support is literally still available in the settings.

It would be helpful if we knew which of the following applies:

1. QT rendering has been intentionally removed
2. QT rendering has been accidentally and unintentionally removed
3. QT rendering is supposed to be there but there's a bug

Considering that other renderers had to be modified (frame server, Voukoder, etc...) I would say that it was because QT was not modified to work with the new api (and won't be as it hasn't been updated in about a decade.)

Which means no.1 in my list applies.

QuickTime rendering has been removed. We still do decode some old formats with the QuickTime plugin (including DNxHD)...but we no longer have an encoder pipeline which uses QuickTime. It has been listed as deprecated for several years which means we will no longer be supporting it and since the rendering engine has changed, only encoders which we currently support were updated to work with the new engine.

QuickTime rendering has been removed. We still do decode some old formats with the QuickTime plugin (including DNxHD)...but we no longer have an encoder pipeline which uses QuickTime. It has been listed as deprecated for several years which means we will no longer be supporting it and since the rendering engine has changed, only encoders which we currently support were updated to work with the new engine.

I appreciate the information, thank you. It’s just becoming frustrating having to come to the forums asking for information from the developers themselves instead of being able to find some sort of documentation before the fact.

@VEGASDerek Thank you for the clarification.

@thesammy58 Your probable alternative is to use an Apple ProRes render template picking one that supports an alpha channel if you want transparency. They produce 'mov' files.

>It’s just becoming frustrating having to come to the forums asking for information from the developers themselves instead of being able to find some sort of documentation before the fact.

Two sides to this one I think .

On the one hand, relying on a deprecated feature is asking for future trouble (frustrating though it might sometimes be if there isn't a viable alternative available). But final removal of a deprecated feature should really be announced somewhere

On the other hand, we really should be told when a deprecated feature is being finally retired for good.

We've had several examples of Magix not properly telling us about stuff being removed (deprecated or not) - with Mocha Vegas being one of the more obvious recent examples

@VEGASDerek I don't get it. All that's lacking is Vegas writing into a mov container, instead of mp4. With the added option of substituting a 24bit or higher pcm/wav audio stream in place of the inferior sounding lossy ac3 or aac. Just like my better cameras shoot. With the same mp4 video stream and wav audio streams Vegas already has, so no special rendering engine support is needed.

Repackaging to a mov container externally is trivial to implement but Vegas could save users like myself the bother of post-processing after dual-pass mp4 and wav Vegas renders. It would also speed up Vegas default mp4 renders by not wasting effort on lossy audio.

I'm not sure if this is directly related to Quicktime. I'll get my ignorance out into the open right away.

@Howard-Vigorita I have often wondered why there was no facility for Vegas to write AVC streams along with PCM audio into a MOV wrapper. I've had cameras that have done so and Vegas has always decoded their output.

Incidentally, Vegas 23-302 still decodes these files just as Vegas 12 did.

Example

General
Complete name                            : D:\_Photos\2015\MVI_4271.MOV
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   2007.09 (qt  /CAEP)
File size                                : 175 MiB
Duration                                 : 40 s 916 ms
Overall bit rate                         : 35.9 Mb/s
Frame rate                               : 23.976 FPS
Encoded date                             : 2015-06-27 15:20:10 UTC
Tagged date                              : 2015-06-27 15:20:10 UTC
Writing hardware                         : Canon PowerShot G15
Copyright                                : 2014
com.apple.quicktime.rating.user          : 0.000
com.apple.quicktime.author               : John Dennis

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Constrained Baseline@L4.1
Format settings                          : 1 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 1 frame
Format settings, GOP                     : M=1, N=12
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 40 s 916 ms
Bit rate                                 : 34.3 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.691
Stream size                              : 167 MiB (96%)
Language                                 : English
Encoded date                             : 2015-06-27 15:20:10 UTC
Tagged date                              : 2015-06-27 15:20:10 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : sowt
Duration                                 : 40 s 916 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 7.49 MiB (4%)
Language                                 : English
Encoded date                             : 2015-06-27 15:20:10 UTC
Tagged date                              : 2015-06-27 15:20:10 UTC

I have refused to buy otherwise very good cameras that recorded audio into a lossy codec. Given the electronics in some cameras, sticking with PCM as an acquisition codec might have been a waste of time.

Fwiw, the deprecated QuickTime codec does not need to be installed to read or write mov packages by any software I use. I've only ever needed it for DNxHD. The mov spec includes pcm but the mp4-package spec does not which is why some camera makers are writing xavc with pcm which is out of spec for mp4 containers. I've been uploading all my YouTube videos lately in mov containers (repackaged w/ffmpeg) with 10bit hevc 4:2:0 video + 24bit wav audio and can play them in Vegas, Resolve, and all my viewers w/o a problem.

I just asked AI search-assist about mov licensing and got this answer: "Using a commercial application to write to a MOV container typically requires a licensing agreement." However, Vegas could easily save themselves the resources and liability by making the rendering plugin sdk public so anyone could write one for them.

I'm fine with Quicktime as a plugin no longer being supported as it's antiquated though agree that transparency and disclosure are a best practice to keep users informed.

VEGAS being able to write to MOV to use PCM WAV audio would be a good feature (without the QT plugin).

VEGAS being able to write to MOV to use PCM WAV audio would be a good feature (without the QT plugin).

+100

This is possible in Happy Otter. And I really wish this was an option in Vegas.

Jøran