1920x1080 MOV Produce Issue with WIN10

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Solved by

Dec 06, 2015 12:48

If someone else could check this compatibility issue I'd appreciate it. I had a need to "Produce" a 1920x1080/30p (15Mbps) MOV file with PD14 on WIN10. Appears not successful for me. Moved project to WIN7 box same version QT(7.7.8) and PD and all is fine.

With PD14 on a WIN10, no 3rd party codec packs system
1) Add sample clip kites.wmv to timeline
2) Produce to either of the two 1920x1080 QuickTime profiles (all other QuickTime profiles work fine)
3) Is it successful?

Jeff

This message was edited 1 time. Last update was at Dec 06. 2015 12:48

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Dec 06, 2015 14:13

I tried it on my system both with the K-Lite Codec pack installed and after removing it (along with ffdshow and the MagicYUV codec). I was able to produce to QT 1920x1080 (15Mbps) 24p and 30p without problems, although all 4 versions have no audio in WMP. VLC plays sound and video normally.

Filename	Jeff 30p-A.txt	Download
Description	MediaInfo without codec pack
Filesize	3 Kbytes
Downloaded:	421 time(s)

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Dec 06, 2015 17:18

Thanks for the MediaInfo log. Strange, yours shows
Codec ID : qt 2005.03 (qt )
Which agrees with my WIN7 box that produces correctly. I've found on the WIN10 box if I keep video duration very short (~1.3sec) I can at least produce a file to look at, it produces
Codec ID : qt

Rather odd, can't find much info out on 2005.03 but pretty obvious is must be a different qt encoder.

I've uninstalled QT, uninstalled PD14 and reverted back to PD supplied QT which got installed with PD14 reinstallation and still get the plain qt Codec ID and non functional for any resonable duration video.

Jeff

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Dec 06, 2015 17:37

Well here's more info. When i produce on my original Surface Pro running Win10, everything works AND it's produced with "qt" codec. See attached!

EDIT: That machine does have the K-LITE codec pack installed yet it produces to the same codec as yours. Meanwhile my main desktop uses the qt 2005.03 (qt ) regardless of whether the K-LITE codec pack is installed or not. Curioser and curioser...

Filename	Produce.mov	Download
Description	Win10 Surface Pro with qt codec
Filesize	16906 Kbytes
Downloaded:	359 time(s)

This message was edited 2 times. Last update was at Dec 06. 2015 17:57

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Dec 06, 2015 17:58

I think just a red hearing of sorts perhaps, if you view your Surface Pro produce.mov on your other WIN10 box my guess MediaInfo will show qt 2005.03 (qt ) vs the just qt on the Surface Pro.

Jeff

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Dec 06, 2015 17:59

My DxDiag results if you want to scour them for clues

Filename	Main desktop.txt	Download
Description	The PC that used qt 2005.03 (qt )
Filesize	106 Kbytes
Downloaded:	430 time(s)

Filename	Surface pro.txt	Download
Description	The one that used qt
Filesize	77 Kbytes
Downloaded:	455 time(s)

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Dec 06, 2015 18:25

Quote: I think just a red hearing of sorts perhaps, if you view your Surface Pro produce.mov on your other WIN10 box my guess MediaInfo will show qt 2005.03 (qt ) vs the just qt on the Surface Pro.

Jeff

JL_JL

Senior Contributor Location: Arizona, USA Joined: Oct 01, 2006 20:01 Messages: 6091 Offline

Dec 06, 2015 19:17

Quote: What this doesn't tell is is why you're not able to produce to those two profiles...

Yep, have not isolated that yet. I'm beginning to think a CL issue on certain platforms with clqtkernelclient32. Maybe a few others with WIN10 systems would try over the coming days to see if more widespread than myself.

It is sucessfull if one keeps the same framesize and changes to RAW or Cinepak, the issue appears specific to H.264 and anything that uses the Main L4 profile. Main L3.1 profile is okay.

Jeff

optodata

Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline

Dec 06, 2015 19:29

Well, there are plenty of versions of that program floating around. I have 5 on my desktop system: