export full quality video from quicktime player 10

>> codecs, settings, and workflow <<

The output from Qt10 is:

Format H264 1620 x 1000

Data size 734 kb

Data rate 1.10 Mbit/sec

Source file was built from jpgs:

Data size 26.28 Mb

Data rate 78.73 Mbit/sec

Workflow was: open the source, add a 16 bit sound clip, and export

There were no settings. This is why I asked for help. I thought there might be hidden controls that I was not finding.

This may explain some of your loss in quality. Unfortunately it is still unclear if the "source" file is video or still in the form of an image sequence at this point since you did not include frame rate or resolution information. Therefore, let me try to create a possible scenario based one my somewhat older digital camera. I take photos using a 24.1 MP (6000x4000) NEF/JPEG format. These photos are imported to my system at 300 ppi which display at very high quality on my iMac 5K monitor. Unfortunately, if I then import the JPEGs into a QT player window without cropping, the default display reference is automatically reduced to 72 ppi but still display the same as the original JPEGs when both windows are scaled to the same display dimensions for comparison. Unfortunately, if I then export the QT data using the 1080p export option, I wind up with 1440x1080 video frame which is equivalent to only about 1.6 MP or roughly only 1/15th the original JPEG resolution. To further complicate matters there a different strategies that can be employed when playing the final QT file. It can be a "true" video having a constant fixed frame rate or what might be called a slideshow or time lapsed image sequence. For example, let's say I want to create a 10 second 30 fps clip from 10 JPEG images with each image displayed for 1 second. In the first case, a 30 fps file would consist of 300 frames with each second containing 30 frames based on each JPEG image. However, QT also has the ability to create/play Variable Frame Rate (VFR) files. In this second case, a 1 fps file is created containing only 10 frames, each of which displays for a full second. I would normally assume the QTX employs the former strategy exclusively while QT7 Pro can create either type of file.

There were no settings. This is why I asked for help. I thought there might be hidden controls that I was not finding. Of course, when I went back to QT7, I didn't really know what settings would be optimal.

QT7 is your best bet if you want maximum control over the encoding process and ease in the creation of a constant frame rate Photo-JPEG image sequence that is to be exported as a "video" clip while a current, compatible video editor would be the better choice if you are more interested in customizing the content (transitions, titles, layering audio, independent control of individual JPEG images, adding Ken Burns effects, etc.) in a "project" environment.

If you want to use QT7 Pro and your source JPEGs are all in the same orientation, at the same resolution, and stored in a folder in an alpha-numeric filename display order sequence, then I'd use the "Open Image Sequence" option to create an Apple Photo-JEPEG image sequence at a specific, uniform display rate (frames per second or seconds per frame duration). This file can then be saved in its current Apple Photo-JPEG format and re-opened in QTX to add audio as you previously did. (I.e., you may want to try this and compare the results to your previous QTX output. In my case, the output data rate was more on the order of 4 Mbps). Or, if you prefer, you can add your audio to the QT7 Photo-JPEG video and then export the merged data directly to H.264/AAC for distribution or ProRes422/LPCM as an alternative archival format to the Photo-JPEG with or without audio at a user optimized video data rate.

>> QT7 Xpro . . . still run under High Sierra <<

How is this possible? I found both iMovie HD and Qt7 unresponsive back when I upgraded to OS X 10.10

You can think of Snow Leopard thru Mountain Lion as having a combined QTX/QT7 structure embedded in the OS that switched between QTX and QT7 routines as needed for playback. However, beginning with Mavericks, Apple essentially embedded separate structures to support QTX and QT7 playback independently. These changes meant that all post-Leopard QT7 based apps had to be redesigned to work properly. iMovie HD 5 was not supported by Snow Leopard and iMovie HD 06's compatibility ended with post-Snow Leopard operating systems. As to QT7, a special version was supposed to be automatically installed for users upgrading from Leopard to Snow Leopard if a "Pro" license was detected during the upgrade. If you wish to use QT 7 Pro under High Sierra, you will have to go to the download web page for the version compatible with Mac OS v10.6.3 and later operating systems and then transfer your license from the older system to the newer one. Be advised that High Sierra may the last macOS to support the QT7 Player. As to its being "unresponsive" following your upgrade to macOS v10.10, not sure if this was due to an upgrade from pre-Mac OS X v10.6.3, the compatible player becoming corrupted during upgrade, or a loss of registration code during upgrade.

I will try again to learn the current iMovie. (I loved iMovie HD, but the new interface is baffling.

As a video NLE (Non-Linear Editor), it is more closely related to FCP/FCPX than to iMovie HD. And, while it has a steeper learning curve, the latest macOS version does include many new, built-in features you would probably like once you learn to use them properly.

I added clips and images and a sound clip to make a short 10 sec movie. Looks beautiful. It should be about 26 mb. When I export it, it is less than 1 mb and is so mushy as to be unwatchable. Help!

using QTplayer 10.4 on High Sierra.

To make optimum suggestions to improve quality, it would be best to know more about your current workflow—i.e., source content resolution(s), codec(s), targeted encode settings used, etc., as well as, your specific export workflow currently being used that created a <1 MB file and why you think think the output should be on the order of 26 MBs for a 10 second clip.

Basically, a 10 second, 26 MB file implies a level of quality roughly equivalent to Blu-ray (1080p AVCHD) having a video data rate on the order of 20-21 Mbps. Unfortunately for you, QTX is programmed to use a context adaptive encode strategy that would output AVC (H.264) video with a data rate in the range of 25-30% that of the Blu-ray AVC data rate. A <1 MB, 10 second clip equates to approximately 800 Kbps or a data rate better suited to low-resolution mobile devices or You-Tube use which returns us to the question of how you are exporting and/or sharing your edited content.

Because the source material added up to 26 mb.

The size of a file is approximately equal to the combined total average data rate of the data content times the playback duration of the file. Your estimation would only be true when the compression format, data rate, and other encode settings of all of your source file are the same as those of the output file. Since different codecs can have drastically different efficiency ratings, it is not unusual for the size of your final edited output file to be drastically different from that of your source files. For instance, a 10 second 480p DV-25 source clip would likely have a file size on the order of more than 35 MBs and a DV-50 file of the same resolution more than 70 MBs but an AVC file of the same resolution and similar quality might only be 3 MBs or an HEVC file on about 2 MBs. I typically use much lower data rates to achieve acceptable results since modern codecs like AVC and HEVC are both very efficient and highly scalable in comparison with "legacy" codecs.

I think you are telling me that I need better software than QTplayer 10 to make quality video.

No, what I'm saying is that it is impossible to make valid comparisons regarding file size and rendering quality without knowing what codecs, settings, and workflows were used to create the files being compared. If you are unable or unwilling to discuss such information, then it is unlikely that anyone will be able to help you here. Just posting Inspector window images of the input and output files could be of help.

I already knew that but was surprized at the extreme (35 to 1) compression ratio

While definitely not typical, a 35:1 (or 26:1 based numbers you previously provided) change in relative codec efficiency is not that extreme. While 10:1 is probably more normal, I've transcoded data between "legacy" archival compression formats such as Animation to modern distribution codecs like AVC/HEVC in the 160:1 to 200:1 range. Once again, codecs, settings, and workflows must be considered when comparing changes in file size and quality.

could not find any of the usual controls to select quality level, so was wondering if I was missing something.

As previously stated, QTX employs a context adaptive export strategy that automatically selects "Higher Quality" target data rate, profile, and level settings based on your selected export/share resolution option while the Finder level encode option allows use of "Higher Quality," "Greater Compatibility", and/or editing/archival context adaptive options. There are no "manual" export options associated with QTX but QT7 Pro and MPEG Streamclip still run under High Sierra if desired.

The exported file looked bad, even on a small iphone screen

Without more information we don't know if the problem is in your source content or output workflow. For all we know you are creating 360p H.264/AAC MOV file and displaying it on a 1080p iPhone and expecting it to look like a 4K recording.

but even if it had been ok, I still wanted to archive a higher quality version to view on my MacBook.

Okay, this is where an alternative app should be used. Since the release of Mavericks, all macOS version include the ability to encode intermediate editing/archival ProRes422/LPCM MOV files. Unfortunately, QTX does not have a dedicated export option to unconditionally create such files. On the other hand, the Finder level encoder does have this capability but cannot edit your files before encoding the date. So if you want to both edit and encode such content, then use a modern video editor like iMovie or FCPX or a legacy app like QT7 Pro or MPEG Stremclip while they remain functional under High Sierra (or on your older platform).