This discussion is archived
1843 Views 9 Replies Latest reply: Jul 18, 2008 1:48 PM by David M Brewer
Your audio settings may have been changed.
1. Open Audio MIDI Setup (/Applications/Utilities/), then check the Audio Output setting.
2. Change the Audio Output setting to 44100.0 Hz.
3. Quit Audio MIDI Setup.
More info on why this happens, here:
http://docs.info.apple.com/article.html?artnum=30083220" 2.1GHz iSight iMac G5, 250GB HD, 1.5GB RAM, Mac OS X (10.4.11), iLife 6.0.3, Toast 7.1.3, iTunes 7.6.2, QTPro 7.5, Safari 3.1.1, iChat 3.1.9
If you choose to go backwards from Quicktime 7.5 to 7.4, remember to save your Quicktime Pro registration number before deleting Quicktime.
Next, VLC is a stand alone program but will use your quicktime codec. FFMpex is also a stand aalonne program, but uses it's own Codec. You can watch an AVI file in this program to verify that it really does have sound.
Real player and Quicktime share !
I know, that we all use the software update software, but, Codecs in your library folder do not upgrade automaticly like your programs do.
Download perian 1.1, and install it. Then reboot. try your AVI files.g-4 dual 533mhz, Mac OS X (10.4.8)
What have you selected there? Should be Internal Speakers)20" 2.1GHz iSight iMac G5, 250GB HD, 1.5GB RAM, Mac OS X (10.4.11), iLife 6.0.3, Toast 7.1.3, iTunes 7.6.2, QTPro 7.5, Safari 3.1.2, iChat 3.1.9
yes, the output is the external speakers. Everything else that uses audio works fine i just cant seem to play movies in quicktime.. This is the message i get - "You may experience problems playing a sound track in (Movie Name).mov because a software component needed by the movie could not be opened."
This is listed in the article posted earlier...2.16 GHz macbook, Mac OS X (10.5.2)
Did you repair permissions after the update?
If not, do so now, then try running the update again.20" 2.1GHz iSight iMac G5, 250GB HD, 1.5GB RAM, Mac OS X (10.4.11), iLife 6.0.3, Toast 7.1.3, iTunes 7.6.2, QTPro 7.5, Safari 3.1.2, iChat 3.1.9
Alright, im right in the middle of repairing permissions right now. Can anyone send a link that explains what exactly that does (I reallly have no idea what repairing the permissions means/does)2.16 GHz macbook, Mac OS X (10.5.2)
What are permissions?
Every file and folder on a Mac OS X hard drive has a set of permissions—settings that determine which user(s) have access to each item, and exactly what that access is. For example, permissions dictate whether or not a particular user can open and edit a particular file. But permissions also determine which items the operating system—or specific parts of it—can access and modify, and which files are accessible by applications.
What does repairing permissions do?
The Repair Disk Permissions function—the process that actually performs the task of repairing permissions—examines certain files and folders on your Mac’s hard drive to see if their current permissions settings are what Mac OS X expects them to be; if discrepancies are found, the offending permissions are changed to match the expected settings.
(In Mac OS X 10.3 and later, repairing permissions also performs one other, unrelated, task: If the invisible /tmp symbolic link—which is linked to the /private/tmp directory—is missing, the link will be recreated.)
Why is it necessary to repair permissions?
If permissions on particular files are “incorrect”—i.e., not what Mac OS X expects them to be or not what they need to be for your Mac’s normal operation—you can experience problems when the operating system tries to access or modify those files. For example, you may have trouble logging in to your account, printing, launching applications, or even starting up your Mac. Similarly, if an application—from Apple or a third-party developer—needs access to a particular file or folder to function, and the permissions on that item have changed in a way that prevents such access, the application may not function properly (or at all). The Repair Disk Permissions function can fix such problems by ensuring that certain files have the correct permissions.
There’s also a security element here: Many system-level files have permissions set a particular way so that applications or users that shouldn’t be meddling with those files can’t. If the permissions on certain system-level files somehow get changed so that access to those files is no longer restricted, you’ve got the potential for a major security issue. Repairing permissions can resolve such issues by resetting permissions on those files to prevent unauthorized access.
How do I repair permissions?
The Repair Disk Permissions function is part of Apple’s Disk Utility (in /Applications/Utilities). After launching Disk Utility, select the desired disk—generally your startup disk—in the list to the left, then click the First Aid tab. At the bottom of the First Aid panel, click the Repair Disk Permissions button. (You could instead use the Verify Disk Permissions option to preview any potential repairs before performing them, but for most users there’s little benefit from this extra step.)
Permissions can also be repaired via the shell (Terminal) by using the command sudo diskutil repairPermissions /. However, it’s unlikely that the typical user will ever need to perform the task in this manner. It’s useful if for some reason Disk Utility itself won’t launch, or for repairing permissions on a remote Mac when connected via Remote Login (SSH), but otherwise you’re just as well served using Disk Utility.
How does the Repair Disk Permissions function know what the “correct” permissions are?
When you use Apple’s Installer utility to install software (such as Mac OS X itself or an OS X update), the installation package (the .pkg file you double-click to begin installation, or that Software Update downloads in the background for an automatic installation) generally leaves behind a receipt—a smaller Mac OS X package that includes information about every file installed, including the permissions each file should have. This receipt is placed in /Library/Receipts. When you run the Repair Disk Permissions function, it examines the receipts in the /Library/Receipts directory of the disk being repaired—which means the feature works only on volumes with Mac OS X installed—and compares the information in the receipt with the actual files on your drive. If the Repair Disk Permissions function finds a file with permissions that differ from what a receipt claims they should be, that file’s permissions are reset to their receipt-specified values. (If you’re curious about the information contained in a receipt, the easiest way to view it is to use the utility Pacifist; simply drag and drop the appropriate receipt into the Pacifist window and you’ll be presented with a list of all files installed by the similarly-named installation package, along with each file’s original permissions.)
It’s worth noting here that although the function is called “Repair Disk Permissions,” what is actually happening is that files’ permissions are being reset or restored to a particular state. It’s possible—though not common—for a particular file’s permissions to differ from what a receipt claims they should be without those permissions actually being “broken.”
Are all files affected by Repair Disk Permissions?
No. As you may have inferred from the above description, only those files installed using OS X’s Installer utility and whose installation packages leave behind a proper receipt in /Library/Receipts are affected by the Repair Disk Permissions function. This means that most of the files affected by the Repair Disk Permissions function are system-level files, application files, or system add-ons—not applications installed by drag-and-drop, and not your documents or other user-level files.
If repairing permissions is useful in general, why doesn’t Apple recommend it as routine maintenance?
Apple does, quite explicitly:
It’s a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software.
That’s taken from Mac Help—in both Panther and Tiger—right on your Mac. Similar statements can be found in other Support articles, one of which is:
http://docs.info.apple.com/article.html?artnum=2575120" 2.1GHz iSight iMac G5, 250GB HD, 1.5GB RAM, Mac OS X (10.4.11), iLife 6.0.3, Toast 7.1.3, iTunes 7.6.2, QTPro 7.5, Safari 3.1.2, iChat 3.1.9
Repairing permissions should take less than a minute. And to add to Klaus1 statement, you should close all applications when repairing permissions.g-4 1.2 gig 1.5 gigs of ram, Mac OS X (10.4.11), Quicktime 7.5-FCS-