
1. Open Finder and go to your "Macintosh HD."It is recommended you delete the special permissions you added to the Library and Preferences folder above after Squeeze is successfully installed.
2. Right-click on the "Library" folder and select “Get Info”
3. In the Info window click the padlock at the bottom and enter your admin password.
4. Under "Sharing and Permissions" click the [+] and add your user name to the list and click "OK."
5. Change your Privileges to “Read and Write”
6. Close the Info window for the "Library" folder
7. Open the "Library" folder
8. Find the "Preferences" folder, right-click it and select “Get Info”
9. In the Info window click the padlock at the bottom and enter your admin password.
10. Under "Sharing and Permissions" click the [+] and add your user name to the list and click "OK."
11. Change your Privileges to “Read and Write”
12. Close the Info window for the "Preferences" folder
13. Open the "Preferences" folder
14. Find a file named “com.SorensonMedia.Squeeze 6.plist” and/or "com.SorensonMedia.Squeeze 4.plist" and delete it (If there are more than one .plist files with Sorenson Media or Squeeze in the name, delete them all.)
15. Run the Squeeze installer once more. You can download it from www.sorensonmedia.com/downloads
Recent Forum PostsAre you still running into this issue? Did you ever submit a support ticket? 
Rich, Squeeze 8 has a 3GPP Format Constraint in the MP4 format. This allows you to use the Sorenson MPEG-4 Pro codec and will result in an H.263 output file with the .3gp file extension. 
AvidRay, I would love to discuss this with you a little more in depth. I haven't done much with QuickTime Timecode Tracks before, can you explain more about what you are looking for and how this... 
This usually is the result of a DV capture in a NLE program and then exporting a QT ref file.
You will need to either export a self-enclosed output from your editing program or apply a crop... 
Are you still running into issues with compression speeds? Looking at your system specs it would seem unlikely that the encode time should take that long. 
