Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Audio / Video  |  Players  |  Apple QuickTime  |  Awful, simply awful

Apple QuickTime

Apple QuickTime

Multimedia player & authoring system.

Version:  7.6.2

   [ Views: 1647 ]

Awful, simply awful

Feedback Type:  Review

Contributed by: jaster--2008 Tuesday, October 04 2005 @ 04:29 PM PDT

Product Platform: MacOSX

Used Product For: 1-6 months

Recommend Product: NO

Does not come with an avi codec. Almost none of my movies will play on this. I went from a fully functioning OSX to a crippled finder with almost no movie functionability. DO NOT INSTALL. Once installed there is no way to reverse without having to reinstall OSX. Guess thats what you get since its free.   
Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

Price:

0 of 19 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

5 comments |

Awful, simply awful - Donal Briard

avi is not a codec. .avi is a file structure format, just like .mov. .avi is fully supported in QuickTime since v4.

Installing QuickTime 7 DOES NOT remove any 3rd party codecs you might have installed.

Now, what codecs where you using that no longer work? If you're not sure which one is affected, just reinstall it (them) into your library/quicktime folder.

Now, please, stop giving 1 star rating to applications you do not understand.

Reply to This

Wednesday, October 12 2005 @ 12:00 PM PDT


Awful, simply awful - dalizard

How did a standalone movie player cripple your Finder?

A little 'hysterical', methinks!

Reply to This

Wednesday, October 12 2005 @ 12:04 PM PDT


Awful, simply awful - foofoofoo

I don't know how the new quicktime hoses the finder, but it does.

My guess is it's trying to preview some files that the finder thinks it can handle but it really can't.

If I create an empty file called foo.swf, the finder chokes when the folder containing the file is opened. (And even after I reverted to qt6, it still freezes on Get Info, although I can't swear it didn't do that before I tried qt7.)

Does anyone know if it this is fixed in 7.0.3? Or if it doesn't happen under OS 10.4? (I'm still at 10.3.9, in part because qt7 is so broken for me.)

Reply to This

Tuesday, October 25 2005 @ 11:09 PM PDT


Awful, simply awful - Swift2

First, there is no "avi" codec. Second, you can get Xvid and DiVX codecs for the Mac, at the respective websites. There are many others available. Windows media can either be played with the Windows Media Player for OS X, If you don't mind spending a little money, you can get the Flip4Mac codecs, and you can play most .wmv files in Quicktime. So, if I can say, get a clue before you complain.

Reply to This

Wednesday, October 12 2005 @ 01:39 PM PDT


Awful, simply awful - astrby

I had a very similar problem to that of the original poster while trying to install a new version of QuickTime. This post is really for the novice (like myself) who may be panicking about their finder not launching and thinking they need to wipe their machines. This _might_ not be the case.

So here is what happened:
The auto-installer hung during the QuickTime installation and as a result I had to do a hard reboot. After restarting, my Finder would not start, Safari, Mail, Preview and a bunch of other pacakges would not launch.

Here is what I did:
1. Rebooted multiple times and panicked for about 30 minutes.
2. Noticed that when trying to launch a few of these failed applications that I was getting quicktime error messages. (e.g. Preview Launch error:

dyld: /Applications/Preview.app/Contents/MacOS/Preview truncated or malformed library: /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime (file is empty)

I noticed that the QuickTime executable listed in the error message had a size of 0 kb. I am assuming that this was a consequence of the hung update/hard reboot.

In a last ditch effort to avoid wiping my machine, I copied the QuickTime executable from my laptop (size ~3Megs) and replaced the 0kb file.

In my specific case, this is all it took to get me back up and running. I am not sure what other damage I may have done, but at face value everything else seems to be working now. I appreciate that this is a pretty specific problem, but since it doesn't seem like I'm the ONLY person with this problem, I hope this helps someone (if so, please drop me a quick note just so to fulfill my curiousity). Good luck.

Cheers,
Phil (astrby@yahoo.com)

btw, my machine: Dual G5 1.8Ghz

Reply to This

Monday, October 31 2005 @ 11:36 AM PST