TOPIC:

davechap wrote:

So are most thinking a 10.0.1 update will show up tomorrow? We are due for an OS update too. I guess it's either this week or next, huh?

No that update came out over 2 years ago. Unless you mean "10.0.10" which wouldn't surprise me.
From my memory Apple did say there would be a new version of FCP X for the new MacPro but I don't remember them saying it would release the same day?

I'm thinking more the 17th now for the MacPro as there have been zero rumblings about inventory or price lists from hardly anywhere. Or maybe this is a benefit from assembling in the USA? Better secret keepers? I doubt it.

Seanus wrote:

No that update came out over 2 years ago. Unless you mean "10.0.10" which wouldn't surprise me.

Wow, yeah haha. 10.1 not 10.0.1. Although, I have that on a backup drive up if anyone wants to downgrade for nostalgia's sake.

BenB wrote:

Some observations:

4. Well, then third party plugins I paid a license for are free to any other editor I hand a project off to? Third party developers would never go for this.

Yes. That's a minor problem, but perhaps the Event could contain the Username used in the plugins, which ultimately should be linked to the App Store accounts rather than purchased and managed ala carte. I'm mostly speaking of custom templates by using the "Open In Motion" command. Many times these are not licensed ones but are rather just simple variations on the Basic Title one, etc. These should transfer within the Event and the user should have a right to distribute them with the project if they chose since they are merely settings for a title or generator to work properly.

BenB wrote:

13. Not sure what that is.

Storylines are great ways to use editing tools like rippling in connected clips and supers. You create a storyline by right clicking on a connected clip and selecting Create Storyline. This also happens automatically if you create a transition over a connected clip. They are like compound clips but have the advantage of remaining displayed against the primary storyline. This allows you to position them while seeing and hearing your content in the primary storyline which would not play back if you had to open them into a separate timeline like we do with Compound clips. I'm suggesting that story lines could be more versatile if they had connected clips within themselves without having to be completely isolated as compound clips.

BenB wrote:

15. It isn't a black hole. I know first hand that they actually do read them, take them seriously, and catalog them. It does have an influence on things.

Well I would recommend a method for Apple engineers and/or quality control to contact power users for info about bugs. I used to participate in the beta seeding programs for QuickTime and there were ways to reach people that actually could fix things. Apple has basically killed the old system of testing application software with beta teams outside a very very narrow group of organizations which probably don't reflect the actual industry. It seems that Apple by filtering everything through the Feedback page would be unlikely to process elaborate reports on specific bugs in software. Furthermore, to the user, it seems as if it is a black hole since for years many people in this forum and others have never received any feedback on bugs and with each round of software, the same bugs remain. One of the most notorious examples is the Text tool in Final Cut Pro 7. It would not display font names correctly and made it impossible to make font selections if your font set had more than just 2 versions of the typeface (normal and bold). This was crippling for such a basic and important tool and could have been solved very quickly if Apple Feedback had a way to reach the developers. But alas, the bug remained for many many product updates to the point where it became a very sore issue with users who relied on typing text directly into the NLE. My suggestion is for there to be a way to track one's bug report or suggestion and see how many others are asking for the same thing.

3: Simpler project/event management allowing individual folders to contain both used projects and events for easier transport.

Quite possibly coming, see alex4d’s blog posts. Or get iMovie.

12: Ability in timeline to "anchor" connected clips to the beginning of the timeline rather than just clips on the Primary Timeline. This would be useful for things like music tracks and predefined content where absolute time should not slide with edits to the Primary timeline.

I do that with secondary’s. works fine. You can do it now with CC's by adding gap at the head and extending it the the timeline head.

13: A way to make Storylines into Compound Clips if connected clips are needed within the story lines.

I’d be happy if CC’s would just show the timecode of, or playback with, the project they’re in. Or be able to be expanded in place like audio components. Hmmm… feedback time.

15: A way to report bugs to Apple which does not fall into an information Black Hole as is the case with the notorious and laughable "Feedback" page.

It may seem like a black hole. It’s not. It does get prioritized based on numbers though, from what I understand. I know they do contact folks though. They’ve emailed me a couple times

27: Ability to define Roles in clips that are already on the timeline. One should be able to manage the combined audio and video of a clip with a single role assignment.

You can already do that, unless you mean have it flow back to the master in the event. And I wouldn’t want that anyway, as I often want to redefine timeline roles without changing the master.

with beta teams outside a very very narrow group of organizations which probably don't reflect the actual industry.

That characterization is…not entirely accurate. At least if what I’ve been told is true. Which it is.

Great post though. Send feedback!

Great conversation. FYI this is post 945. Just 55 to go.

tpayton wrote:

Great conversation. FYI this is post 945. Just 55 to go.

54

Do you think when we hit 1,000 it will automatically unlock FCPX 10.1?

mthomas wrote:

Hey I'm looking forward to many things in the update. Here's my wish list:


1: Aperture integration. We should be able to use Aperture-styled project metadata and footage management. It would be best to actually have access to actual Aperture databases and be able to use the Aperture color correction controls if we wish to batch-color correct entire sets of footage before they enter our timelines. This would be an ideal staging area for footage before it hits the active timeline.

2: H265 transcoding from AVCHD and other formats upon ingest and very simple h265 proxy storage on iCloud. Proxy playback settings should be managed ala carte from clip to clip or at least from project to project. If proxies don't exist for certain files the system should revert to playing back original if present.

3: Simpler project/event management allowing individual folders to contain both used projects and events for easier transport.

4: Support for copying Used Motion Templates and Generators into Projects for transport from computer to computer. Store the used Motion Templates in the Event so a change to one doesn't break all the other projects using the same or similar Motion Template.

5: Support for FaceTime within the interface so remote participates can view the editing screen and editor's camera (much like Final Cut Theater used to do but better). An ability to record that stream for "proof" that one requested specific adjustments during the session.

6: Curves and other highlight specific LOG color correcting tools. The tools available to Aperture users would be particularly useful including Whites, Highlights, Mid Contrast, Shadows and Blacks.

7: Ability to view Vector scope over small targeted area, much like a spot meter for simpler measurement of skin tones in small areas of the footage.

8: Ability to "Snapshot" a project's state without having to duplicate it as a completely new version. Currently generating a new version is very tedious especially if you have compound clips which are stored in the Event.

9: iCloud syncing of projects and event databases which can update remote computers using proxy and/or original footage seamlessly. Apple should make it easier to use Proxy with projects and events since their computers are not shipping with large SSD's.

10: iTunes Store integration allowing people to post their finished content for sell, free playback or private viewing. An option for marketing and sponsorship would be useful. Furthermore, a digital usage tracking system could track your clips used, stock licenses, etc.

11: Actual 1080i pulldown added to footage sent out the Macbook Pro and MacPro's HDMI port. This should be a proper HDTV stream using standard color and frame rates. Currently, it is more like a computer monitor than an HDTV output.

12: Ability in timeline to "anchor" connected clips to the beginning of the timeline rather than just clips on the Primary Timeline. This would be useful for things like music tracks and predefined content where absolute time should not slide with edits to the Primary timeline.

13: A way to make Storylines into Compound Clips if connected clips are needed within the story lines.

14: A proper Manual accessible within the app and preferably detailed Multimedia Training tutorials available on iTunesU or iTunes Movie Rental system. Currently the Help topics are fairly useless, but could be more effective than a PDF manual. iPad integration of the training system would allow the iPad to control the mouse within the app if needed (for highlighting things, etc)

15: A way to report bugs to Apple which does not fall into an information Black Hole as is the case with the notorious and laughable "Feedback" page.

16: A way to Archive a project and used media to a new self-contained project while trimming the used clips to only show used parts with specific in/out handles. This should also include used Motion Templates.

17: A memory purge command which allows the user to flush RAM caches and vRAM to improve performance.

18: A way to convert 1080i at 29.97fps footage into 540P footage at 59.94fps. This would allow standard 1080i footage to be conformed to 2.5x slow motion in film projects with minimal artifacting.

19: The ability to send to Motion like the old days. I understand how it works in reverse now, but creatively most people don't create great content in reverse.

20: Broadcast safety flight check system integrated, checking for standard sound levels, color ranges and 4x3 crop compatibility.

21: Vimeo upload should have ability to replace existing video at same link if requested rather than just upload new video.

22: Some kind of documentation on how to script automations based on Metadata and end-product keywords. This could involve the automation of Roles allowing something like a phone number or URL to be automatically switched in multiple, automated exports.

23: Face Recognition lifted from Aperture/iPhoto and ability to track iPhone GPS with footage not shot on iPhone but at same time. Auto color matching feature could use Face recognition for skin tone isolation.

24: 3D LUT support for variety of camera formats including cLOG, sLOG, RedSpace, ProPhoto, AdobeRGB, Cineon, Arri.

25: Ability to apply effects AFTER color correction phase, rather just before. Many times effects can destroy color information before the color correction panels have a chance to see it. Make it possible to drag a color panel before the Effects panel sees the footage.

26: Color Panel Color Range Picker should have metrics available so one can fine-tune YUV or LAB color selections using sliders rather than just with a picker and a single slider.

27: Ability to define Roles in clips that are already on the timeline. One should be able to manage the combined audio and video of a clip with a single role assignment.

28: SAN locations should perform faster (perhaps by using local synchronization of the event and project library databases).

29: Include noise reduction filter, camera lens profiles, and other advanced image controls similar to the features of Aperture.

30: Use of Siri-like abilities to depict voices and allow transcription of dialog into metadata so keywords can be preserved and used throughout editing and delivery process. Automatic ducking of Voice and Music sound levels would be easy once dialog tracks are automatically defined.

I could keep going, but this is pretty long. Any thoughts on these ideas?

10. Yeah most likely wo't happen, unless they bring something like Ping back.
24. have you checked out LUT Utility for FCP X & Motion 5

I really like some of your other requests maybe some of them will come true?

As regards "23: Face Recognition lifted from Aperture/iPhoto"

Final Cut Pro X has had face recognition code in it for a while, maybe there'll be a good UI for it in 10.1.

FFFaceRegistryEntry
FFFaceDetectionInfo
FFFaceDetectionInfoCollection
FFFaceDetectionSegment
FFFaceRecognitionInfo
FFFaceRecognitionInfoCopying
FFFace

I've been following this thread and all the discussions in various forums and Facebook editing groups and wrote up a blog post about about it. Kind of a summary of what to expect and how to do the update:

Final Cut Pro X 10.1: What To Expect And How To Update

The clock is ticking!

For a second then I thought you meant there was a ticking clock on the website or something

Julian wrote:

Do you think when we hit 1,000 it will automatically unlock FCPX 10.1?

If I was privy to that information, unfortunately I would be under obligation to not disclose it.

I woke up with nervous anticipation, to wait for a possible update later to day?

This is killing me.


Please SIR....

After 9:30am on the East Coast of the USA and the Mac Store is still open. Assuming FCPX is tied to the MacPro i'm getting the feeling we're looking at the 17th now.

Disproportionate wrote:

I'm in the same boat, believe me! I've had a great year, and I'd love to have a nice big expenditure to counterbalance it.

You shouldn't post something like that on a public forum. Your clients might see it and it'll weaken your position when quoting jobs if they know you're sleeping on a mattress stuffed with money and lighting cigars with hundred dollar bills.

After a 3 week stretch of Motion tutorials, Mac Break Studio returns to a FinalCut episode today.

Maybe theres nothing to interpret here, but I've assumed they've had access to 10.1 and wouldn't have thought they would publish something about 10.0.9 today if 10.1 were going to be launched the same day. Or perhaps they aren't privy to the actual launch date…

Russ

cseeman wrote:

After 9:30am on the East Coast of the USA and the Mac Store is still open. Assuming FCPX is tied to the MacPro i'm getting the feeling we're looking at the 17th now.

But what does the "Great Carnac the magnificent" have to say?

Russ wrote:

Maybe theres nothing to interpret here, but I've assumed they've had access to 10.1 and wouldn't have thought they would publish something about 10.0.9 today if 10.1 were going to be launched the same day. Or perhaps they aren't privy to the actual launch date…

Russ

From what I've heard, testers and trainers aren't privy to launch dates until they're VERY near- like within a week. Sort of like how invites don't go out for Apple events until a week before.

Russ wrote:

After a 3 week stretch of Motion tutorials, Mac Break Studio returns to a FinalCut episode today.

Maybe theres nothing to interpret here, but I've assumed they've had access to 10.1 and wouldn't have thought they would publish something about 10.0.9 today if 10.1 were going to be launched the same day. Or perhaps they aren't privy to the actual launch date…

Russ

Why do you assume that the tutorial won't apply to 10.1 as well?
I think it would be a mistake for Apple not to launch Mac Pro and FCPX today, but I guess they know better so we'll see.

4. I'm mostly speaking of custom templates by using the "Open In Motion" command. Many times these are not licensed ones but are rather just simple variations on the Basic Title one, etc.

OK, they'd have to build some system in which third party paid for plugins had to register themselves with the databases. Could be coming, but I doubt it is a priority. All NLEs have this issue. But yes, it would be interesting to have.


13. I'm suggesting that story lines could be more versatile if they had connected clips within themselves without having to be completely isolated as compound clips.

Ah, have connected clips connect to the Secondary Storylines. That would be interesting. That could open some interesting possibilities, but do you think it could also make things too confusing eventually? Just thinking out loud. Something interesting to think about.


15. Well I would recommend a method for Apple engineers and/or quality control to contact power users for info about bugs.

I personally known of about two dozen end users the dev team contacted directly about FCP X bugs reported via this system. In my experience, with the number of entries they get on a daily basis, it is a system that works. Just my opinion.

But really good points to bring up. Glad you guys are speaking up.