9 Replies
      Latest reply: Oct 27, 2017 8:47 AM by .flipper RSS
      .flipper Level 1 Level 1 (0 points)

        Okay, sometimes it'll launch, but as soon as a new window needs to be created, or media import is initiated, it crashes instantly. 10.3.4 is listed as compatible with High Sierra, so, I'm thinking that it's just me, being lucky. Fortunately I'm only looking at a single, pro bono, gig right now. No time pressure, but need to color correct an hour or two of music video (split into songs, correct, save...), and technically I could use Premiere, which is running just fine under High Sierra. But I have correction and filters loaded up for FCP, so I want to figure this out, if possible.

        • Re: Final Cut Pro X crashing in macOS 10.13 b9
          energiser Level 1 Level 1 (0 points)

          No issues here at all with Final Cut Pro (10.3.4), its stable and has not crashed once.

           

           

          " Fortunately I'm only looking at a single, pro bono, gig right now.  need to color correct an hour or two of music video (split into songs, correct, save...), and technically I could use Premiere, which is running just fine under High Sierra. But I have correction and filters loaded up for FCP, so I want to figure this out, if possible."

           

          You should not be using a beta version of Mac OS to perform production work. Beta software is for testing purposes, not for normal day to day use. Therfore use the current public release of Mac OS installed on your Mac, presumably Sierra.

          • Re: Final Cut Pro X crashing in macOS 10.13 b9
            Edmodder Level 1 Level 1 (0 points)

            Yep, having the same problem. I even deleted all my plugins and re-installed FCPX, same behavior. As soon as I try to import any media it crashes. At this point I've probably sent 150 crash reports to Apple because it now forces you to do so.

             

            Definitely my bad for installing the GM candidate, but if this happnes with the actual GM I'm going to be PO'd. I need Final Cut working...

            • Re: Final Cut Pro X crashing in macOS 10.13 b9
              Edmodder Level 1 Level 1 (0 points)

              Found the problem. My 2016 MacBook Pro 15" is connected via Thunderbolt to an external 4K monitor (Sharp PN-K321). In this configuraiton, it crashes every time I try to import any media (it crashes as soon as I select a file, in fact).

               

              If I disconnect the external monitor, Final Cut Pro X runs fine. What. The. Heck?

                • Re: Final Cut Pro X crashing in macOS 10.13 b9
                  zacksiri Level 1 Level 1 (0 points)

                  I'm having the same issue. Right now i'm running on the release version of high sierra if i disconnect the external display everything works.

                    • Re: Final Cut Pro X crashing in macOS 10.13 b9
                      .flipper Level 1 Level 1 (0 points)

                      The problem with external monitor/clamshell mode is a known bug, now, at Apple. An update to fix is in the works. For me it seemed specific to Final Cut Pro (10.3.4) as Premiere, Motion, and DaVinci Resolve were all working fine, in clamshell mode, or not. But like all new releases, there are some issues. I'm also experiencing odd, minor stuff like Calendars not syncing with iOS11/macOS 10.13, strange behavior in Logic Pro (inability to "Save" being rather a "killer."), and very minor other things...

                       

                      As for the geniuses on here who trot out the ancient (and trust me, widely known) advice to never run brand new OS's on production boxes, well, as horrifying as it must seem... somebody has to do it, otherwise the bugs would exist much longer than they will. I had exactly zero on my "plate" when I started testing the beta... and a project popped up on me, unsolicited. We're full speed ahead, currently (albeit, not in clamshell mode LOL)... no harm, no foul

                        • Re: Final Cut Pro X crashing in macOS 10.13 b9
                          KMT Level 8 Level 8 (9,645 points)

                          As macOS 10.13 HS is now public, user-centric queries/comments such as this are perhaps best put to Apple's public community support forums, run by AppleCare, and/or Apple's twitter support account, vs. risking off-topic here in the DevForums, thanks and good luck.

                           

                          From this link: https://discussions.apple.com/community/mac_os/high_sierra

                          "Announcement: macOS High Sierra is now available! If you have a question or knowledge to share with the community, we want to hear from you."

                           

                          Users can feedback via http://www.apple.com/feedback/- Individuals using betas are free to use the Feedback Assistant; devs can use the 'Report Bugs' link, below right.

                           

                           

                           

                            • Re: Final Cut Pro X crashing in macOS 10.13 b9
                              .flipper Level 1 Level 1 (0 points)

                              Off-topic? How do you figure? Just installed beta5 of the dev v. of 10.13.1, five minutes ago. Does that sound like current issues with the beta releases belong in public discussion groups? Come on, your profile says you're a pro, so do a little "pro" thinking before leading folks astray. It comes with the so-called "pro" turf.

                               

                              Meanwhile, for those who weren't misled into the pub forums, the latest iteration of the developer beta of High Sierra (10.13.1 beta5), as of today (10/27 8:30am PST) will STILL crash FCPX on launch, as in "instantly," when in clamshell mode on the latest model MacBook Pro.

                      • Re: Final Cut Pro X crashing in macOS 10.13 b9
                        ray goes Level 1 Level 1 (0 points)

                        Well, looking at the crash reports it seems there is some memory wrapping ocurring. This is based on quite low addresses shown. I will go through the pain of filing a developer report.