I'm not saying the function isn't useful, what I am saying is that to default to opening up with the middle section in slow motion is a bug.
Yes, you say you consider this to be a "bug" but what you have not indicated is what you would not consider to be a "bug." Do you want the entire file to open set to play back at the full 120 fps? The entire file playing in slow motion? The first half in slow motion but the last half at the normal 120 frame rate? The reverse? What I am trying to point out here is the no matter how Apple sets the slow morion control to open, a majority of users will, by your definition, consider the QT X Player to have a "bug" and that I could hardly care less how it opens since I will be forced to make adjustments to view my files anyway. To me, how the file should open is merely a "preference" that may or may not be different for each individual user and not a "bug" if it is opening the way Apple programmed it to open.
I rang Applecare about it in January and was put through to senior 2nd line support who confirmed it is a bug as it shouldn't do it and that they were aware of the problem since the GoPro 4 Black came out.
Are these the same senior support people who did not even know that the AVFoundation, Modernizer, and Convert modules were embedded in Mavericks (now also in Yosemite) and was (like QL) available to users at the Finder level without opening any dedicated application or that they only supported certain specific codecs and who use PC platforms for their daily duties instead of using a Mac as well might be expected of Apple employees? As to the QT X v10.4-GoPro 4 Black problem, maybe my comment was too cryptic. The latest QT X player app was introduced last October—not 2 or 3 months ago with Appleseed testing probably extending back another 3 to 6 months, and earlier GoPro devices also had 120 fps capabilities which is not a problem for people who use QL or any of the other previously mentioned apps to preview their files under Yosemite.
It only does it with 120fps clips which confirms it, as all other fps is normal.
Are you saying you have not tried the 240 fps mode or that you also want to redefine 50i and 60i frame rates as "high speed" recordings for the QT X v10.4 player? Once again I state that the QT X v1.4 appears to be doing exactly what it was programmed to do—automatically turn on the secondary slow motion control when "High-Speed" recordings (anything over 60 fps) are detected. Again, this is not a "bug" since this is what it appears to be programmed to do—an "automatic" feature that you don't want opening automatically. I agree that I would prefer to manually decide whether or not the slow motion control is activated or not but Apple's choice to implement automatic actions has been a hallmark of the QT X app since it was first introduced and is the primary reason I still use QT 7 Pro as my primary QT media player. I simply don't like the app controlling what I can or cannot do. I "get around" this by using a different media app to open and play the file at the actual recorded frame rate and use QT X v10.4 when I want to watch/preview a clip with a slow motion effect before creating an edited version of my source file with slow motion segments or slow motion instant replays.
There's at least 2 threads on here about it, there's loads of other forums with this problem highlighted and Apple themselves confirm there's an issue. I really don't see why you can't admit there's a problem with this and keep on defending it.
An issue for who? I fail to see a problem other than the one you yourself create by using the QT X v10.4 player in the first place. Your wounds are self inflicted. As to Apple confirming a "bug" exists, need I point out that you were talking to support people whose full-time job is to pander to the injured feelings of irate customers and who frequently have absolutely no technical knowledge regarding what you are talking about. Their job is to placate people. My philosophy is somewhat more flexible. If an app doesn't work the way I think it should, then I don't use it until or unless it is fixed by the provider. This could be a long wait for you and meanwhile I'm not waiting for the next major release of Mac OS X nor am I going to assume it will be fixed at that time.
To expect a company the size of Apple to sort this out within what is actually 3 months now (not 2 like I said yesterday) is not an unfair expectation! I'm no software programmer, but I wouldn't have thought this is a difficult problem to sort out as it only does it 120fps.
As I attempted to point out previously, since the introduction of the QT X player on 28 Aug 2009, no minor update to the player app has ever been released. The only revisions have been in the form of major updates associated with a new Mac OS X release. Unless Apple changes it ways, I would not expect this issue to be addressed until a completely new Mac operating system is released and historically Apple is not been inclined to drop automation features once they have been incorporated into an app. I am not saying that your expectations are not fair—just that they're not likely to come to full fruition as you deem appropriate.
As to how simple or hard a "fix" may be, it would likely depend on the manner in which it is currently implemented. In hopes that it might be a hidden PLIST file responsible, I've started to look over the 30 embedded PLIST files I've found to date. However, the detection and activation routines could just as easily be built into the other package or system resources or simply be a random placement of secondary control markers at the time the the software was last compiled—i.e., randomly changing each time the software is recompiled. If you are a programmer and this is so easy to fix, then I suggest you dig into the software and provide the Apple programmers with your solution.
