[MW Forums]

Apple on Tuesday released QuickTime 7.0.1, an update to their multimedia technology. more

[Schneb]

One of the things I loved about Quicktime Pro 6 was the ability to choose MIDI tracks and change the instrument track by track. That is GONE in Quicktime Pro 7. When I upgrade, I do not expect to LOSE editing ability!

[fds]

The QuickTime Player application in QT7 is a complete rewrite from scratch in Cocoa.
They didn't go and remove former features to piss off users, they just did not re-implement everything.
The good news is that I hear you can still use the old QT Player application with QT7 installed on your system, if you're missing some feature which didn't make the cut for the new QTPlayer.

[jcraig]

Also, Garageband 2 has the ability now to directly import MIDI files (Dent Du Midi no longer necessary), thereby giving you the editing ability you lost in QT.

[funkboy]

This strange Quartz vulnerability is worrying. This sounds like Microsoft-style security leaks... how many of these are sneaking into the operating system with Tiger? Are some of the new "features" (especially internet hooks) of the new OS having negative effects on security? How can QuickTime even interact with the web? Sounds odd.
At least Apple is nipping these bugs before they're uncovered by the public.

[DPG4450Guy]

You're kidding, right?
Launch QT Player and under the File menu open a URL.
Geesh.

[Schneb]

Except that you cannot export MIDI in GarageBand. Sometimes you cannot import a particular MIDI file because it does not recognize one of the instruments. I was able to figure out which instrument this was, change it, then was able to import it. Don't get me wrong, I do love the import feature of GarageBand, but I also would like Quicktime not to lose the editing tools I have come to need for various reasons.
One of these reasons is being able to assign soundfonts to various MIDI files and play them in iTunes. One could be a player piano roll MIDI with a honky-tonk piano, the other could be an organ tune with a pipe organ soundfont. With Quicktime 6, all these MIDIs played with the soundfont I assigned them. With Quicktime 7 I can only choose one soundfont which means all my MIDIs with more than one track are broken until I switch back to the QT synthesiser.

[Schneb]

"They didn't go and remove former features to piss off users"
If this is true, they should tell you UPFRONT what they are excluding from the package so that you will not spend a non-refundable $30.

[Rugby]

In reply to:

---

If this is true, they should tell you UPFRONT what they are excluding from the package so that you will not spend a non-refundable $30

---

i.e. you didnt check what it could/couldnt do ? If a feature is important to you it could be worth to check if the new app still features it...lets face most major upgrades remove/add stuff
Quicktime specs

[scottellsworth]

Microsoft has security flaws because they introduce bugs at about the rate they fix them. This is because the OS has lots of interdependencies, upon which they depend.
Apple could certainly find themselves in this state, but this is not a likely thing at the moment, because they are working to keep it straightforward. Partly, this is because they do not have more money than anyone else, and thus they have to keep it simple, or they cannot keep it maintained with the staff they have.
Sure, OS X is complicated considered as a whole, but they have got good isolation between layers. Thus, Unix layer bugs are fixed at the unix layer, while QT bugs are fixed in QT. Rarely does a bug jump layers, and thus each team really has to concentrate on their own stuff doing what is expected.
Bugs like this one happen when the connections between layers change. Dashboard pushed a Quartz canvas directly into the Webkit/Javascript space, which meant that quartz suddenly had security responsibilities. They found and fixed this, probably by tightening the bounds on just what quartz could do, and thus the problem likely is no more.
This does not contradict what I said about strong layers - it supports it. When they weakened the wall between layers, two teams needed to agree on what needed to be done. They likely did the code equivalent of shoring that barrier back up again, so that this kind of bug will not happen here.
Scott

[Schneb]

The instrument editing feature is buried in the Get Info section. Neither Quicktime 6 specs, nor Quicktime 7 specs inform whether it can or cannot do this task. So how was I to find out other than unlock it after payment? What Apple needs to provide is a very clear link... Comparison between QTPro6 and QTPro7. This would only show the added or subtracted abilities and changes. They also need some sort of ability to refund due to a lack of informing the customer on their part. To not allow refund for any reason is dishonest and poor business practice.

[sigma8]

I've rather disappointed with QT7 as well, I snagged a copy of my QT6 player and now have two little Q's on my dock. The feature I miss most (which is the stupidest feature to disappear) is that you can't set in/out points on mpeg movies....but you can still set them on .avi or .mov or mostly any other playable file. Just not mpegs.
I realize you can't copy/cut the selection in mpegs, but it's still useful if you're trying to examine a scene for minute details. I tried watching this little snippit of a swordplay clip in slow-mo, and I still can't pull it off :-P

[Schneb]

Nor can you go fullscreen anymore without buying it. This was a dealbreaker for our company that USED to use Quicktime to send video CDs with Quicktime files. We cannot ask our thousands of members to upgrade to Quicktime Pro just to use the fullscreen option! Someone at Quicktime is NOT thinking!
What is the difference suppose to be between QT7 and QTPro 7? Editing! So let the player version playback properly, ie all the AV controls and fullscreen as in QT6. OK, so you want to edit? Let us edit, including the MIDI instruments.
I think the griping about QT7 has only just begun.