Quick Time is no longer support Windows...

Marco. wrote on 8/31/2018, 2:06 AM

Since Vegas Pro 14 you don't need Quicktime to import H264 MOV files.

And there is no more Sony Vegas Pro since version 14.

Trensharo wrote on 9/1/2018, 8:45 AM

Marco, stop giving this incorrect information. That is completely false. H.264 MOV files require QuickTime.

FFS. Do you need screenshots to see this?

Marco. wrote on 9/1/2018, 9:31 AM

How comes MOV H.264 work fine here for Vegas Pro 14, 15, 16 without me having Quicktime installed?

"Do you need screenshots to see this?"

No, but a sample clip offered for download would help.

doubleJ wrote on 9/1/2018, 10:42 AM

I thought it came down to whether so4 whatever was being used.
If I disable that, QuickTime is required.
If I enable that, QuickTime isn't required.
JJ

Marco. wrote on 9/1/2018, 10:45 AM

Yes, and that I/O plug-in is enabled by default and can't get disabled without entering hidden system preferences.

Mindmatter wrote on 9/1/2018, 10:56 AM

Marco, on my machine with so4 enabled, Vegas can't read DNxHD without quicktime though.

OldSmoke wrote on 9/1/2018, 10:58 AM

Marco, on my machine with so4 enabled, Vegas can't read DNxHD without quicktime though.

I thought DNxHD requires the Avid Codec and not QuickTime?

Marco. wrote on 9/1/2018, 11:00 AM

Yes, DNxHD isn't H.264.

doubleJ wrote on 9/1/2018, 2:17 PM

Interestingly enough, I downloaded a bunch of random sample footage (trying to find videos that have embedded timecode) and I had some not open because of no QuickTime.

The odd problem is that I have QuickTime installed.

There were multiple files that wouldn't open.

File C:\Users\jj\Downloads\AVCHD_1280x720p_5994.gxf could not be opened.
File C:\Users\jj\Downloads\Capture0000.mov could not be opened.
File C:\Users\jj\Downloads\cymono1HD.avi could not be opened.
File C:\Users\jj\Downloads\NTSC_720p_MPEG_XDCAM-EX_colorbar.mov could not be opened.
File C:\Users\jj\Downloads\NTSC_SD_DV25_colorbar.avi could not be opened.
File C:\Users\jj\Downloads\NTSC_SD_DV25_colorbar.mov could not be opened.
File C:\Users\jj\Downloads\Swans720p-NTSC.mov could not be opened.

JJ

Trensharo wrote on 9/1/2018, 2:43 PM

How comes MOV H.264 work fine here for Vegas Pro 14, 15, 16 without me having Quicktime installed?

"Do you need screenshots to see this?"

No, but a sample clip offered for download would help.

Any video recorded on an iPhone to H.264 MOV, for example they won’t load without QuickTime, period. This has always been the case. It is still the case.

We’ve been over this.

Not uploading personal videos just because you are thick-headed.

Former user wrote on 9/1/2018, 2:44 PM

That image of QT is the installer, not the QT program. If you have not ran the installer, then QT is not installed.

Chief24 wrote on 9/1/2018, 2:59 PM

@doubleJ Saw your last post as well concerning Cineform codec, and that _JN had given you the link to Dr. Zen's page for that download. While you are at his (Dr. Zen: moviestudiozen.com) site, look for the QuickTime post as well. If you are running Windows 10, the version you have listed is not correct. You need to run the older version of 7.6.92, which the Good Doc has a link to, as well as installing (basically, just run it and don't do the "Player"). Of course, uninstall the current version you have first.

doubleJ wrote on 9/1/2018, 3:18 PM

That image of QT is the installer, not the QT program. If you have not ran the installer, then QT is not installed.

I understand that, but I can't give you a screenshot of the installed program.
There is no program to screenshot.
JJ

Former user wrote on 9/1/2018, 4:12 PM

Then it is not installed. I have QT installed on my Windows 10 with no problem.

Marco. wrote on 9/1/2018, 6:17 PM

I have a bunch of iPhone H.264 videos (iPhone 7 QHD 30p and HD 60p, 720p30 and iPhone 6s 320p30), on my system which import and playback well in Vegas Pro 15 and Vegas Pro 16. Even the 90° rotation meta data is read correctly by Vegas Pro. The decoder plug Vegas Pro 15 and 16 uses to decode these iPhone MOV files is so4compoundplug, not Quicktime.

Trensharo, the coarse language you use breaks community rule # 1 which isn't acceptable and won't be tolerated anymore.

john_dennis wrote on 9/1/2018, 8:02 PM

"H.264 MOV files require QuickTime."

That is not true.

The following Mediainfo is from one of my Canon cameras. All video from it was edited in Vegas Pro from 10-13 and I never had to load Quicktime to work with the files.

In Vegas Pro 10, they were decoded by:

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\Sony\Vegas Pro 10.0\FileIO Plug-Ins\compoundplug
Format: Sony AVC
Version: Version 1.0 (Build 1561) 64-bit
Company: Sony Creative Software Inc.

In Vegas Pro 11, they were decoded by:

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\Sony\Vegas Pro 11.0\FileIO Plug-Ins\compoundplug
Format: Sony AVC
Version: Version 11.0 (Build 701) 64-bit
Company: Sony Creative Software Inc.

In Vegas Pro 12, they were decoded by:

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\Sony\Vegas Pro 12.0\FileIO Plug-Ins\compoundplug
Format: Sony AVC
Version: Version 12.0 (Build 770) 64-bit
Company: Sony Creative Software Inc.

In Vegas Pro 13, they were decoded by:

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\Sony\Vegas Pro 13.0\FileIO Plug-Ins\compoundplug
Format: Sony AVC
Version: Version 13.0 (Build 453) 64-bit
Company: Sony Creative Software Inc.

In Vegas Pro 14, they were decoded by:

Size: 75.03 MB (76,826,596 bytes)
Created: Saturday, June 30, 2018, 6:04:55 AM
Modified: Friday, July 05, 2013, 9:26:08 AM
Accessed: Saturday, June 30, 2018, 6:04:55 AM
Attributes: Archive

Streams
Video: 00:00:18.919, 29.970 fps progressive, 1280x720x12, AVC
Audio: 00:00:18.919, 48,000 Hz, Stereo, PCM

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 14.0\FileIO Plug-Ins\compoundplug
Format: AVC
Version: Version 14.0 (Build 270) 64-bit
Company: MAGIX Computer Products Intl. Co.

When I load Quicktime now to work with iDevice video, I complete my task and restore the image of my system to a pre-Quictime state.

Gary-Akimoto wrote on 9/1/2018, 9:20 PM

But it was trust, sometimes, I input video, and even v16 pro it still ask me for install quicktime

https://4.bp.blogspot.com/-eqDxK04pRS0/W4tJPO96wdI/AAAAAAAAAZQ/lexZFiGqPnscf3o4VnHnBbifB5v3M_neQCLcBGAs/s1600/vegas2.jpg

https://2.bp.blogspot.com/-_jfaOOEGX_4/W4tJPM4jLFI/AAAAAAAAAZM/BHxy_woTBt4rCOo_INakeMetZOAuJsouACLcBGAs/s1600/Vegas16.jpg

Chief24 wrote on 9/1/2018, 9:31 PM

It shows in "Programs and Features". You have to go further down the list.

Former user wrote on 9/1/2018, 10:02 PM

If you have quicktime installed vp16 'damages' it. I don't know what vp16 does, but software, media and vegas plugins that require it won't work. Go to uninstall software, choose quicktime & in the uninstall options is 'repair quicktime'. Choose that.

I uninstalled that vp16 dumpster fire immediatly, so not sure if it continues to break quicktime on every run, hopefully not.

fr0sty wrote on 9/1/2018, 10:28 PM

If you have quicktime installed vp16 'damages' it. I don't know what vp16 does, but software, media and vegas plugins that require it won't work. Go to uninstall software, choose quicktime & in the uninstall options is 'repair quicktime'. Choose that.

I uninstalled that vp16 dumpster fire immediatly, so not sure if it continues to break quicktime on every run, hopefully not.

Resolume 5 requires Quicktime, and Vegas 16 has not corrupted its ability to run or properly play back .mov media on the system I tested it on.

Gary-Akimoto wrote on 9/1/2018, 10:34 PM

If you have quicktime installed vp16 'damages' it. I don't know what vp16 does, but software, media and vegas plugins that require it won't work. Go to uninstall software, choose quicktime & in the uninstall options is 'repair quicktime'. Choose that.

I uninstalled that vp16 dumpster fire immediatly, so not sure if it continues to break quicktime on every run, hopefully not.

Thanks, but since quicktime is no longer for windows, and apple is stop to update quicktime for windows, so I think Vegas is time to stop request Quicktime for use, and they need to find another solution for replace quicktime for use is better.

Former user wrote on 9/1/2018, 10:53 PM

I don't know why people are getting different problems with .mov media reading and encoding with vp16. You would think we would all be experiencing the same, if quicktime was already installed & vp16 installed. I should say my problems were with vp15 & quicktime aftering installing vp16 & an example of problem ofx plugin is mocha pro rendering a mov file. Other than opening vp16trial for it's initial run, I did not create any projects & removed it before I repaired quicktime

Gary-Akimoto wrote on 9/2/2018, 1:12 AM

I don't know why people are getting different problems with .mov media reading and encoding with vp16. You would think we would all be experiencing the same, if quicktime was already installed & vp16 installed. I should say my problems were with vp15 & quicktime aftering installing vp16 & an example of problem ofx plugin is mocha pro rendering a mov file. Other than opening vp16trial for it's initial run, I did not create any projects & removed it before I repaired quicktime

Thanks, but I know we can install quicktime to fix it, however, Quicktime is no longer support windows, so there are many problem(security, leak...) may come, so if Vegas Pro can support them without install Quicktime is better, because QuickTime is really old now(Last version : 2016-01-07)

Marco. wrote on 9/2/2018, 6:55 AM

"I input video, and even v16 pro it still ask me for install quicktime"

There may be several reasons:

- so4compoundplug is disabled in internal preferences.

- a non-standard combination of video- and audiostream is used in the MOV wrapper.

- a non-standard H.264 codec property is used (or at least one that is not known by Vegas Pro).

- maybe your video stream is not even H.264 coded but instead it is a codec not supported by so4compoundplug.