Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Keep us informed! I don't want to install new beta unless there is good news on the FCPX front. ;)

Its has been fixed! (On my late 2017 15" TB MBP). Weird scroll bar issue is gone too.

Still some oddness... project name in timeline says "(null)" next to it. But everything seems to work... plugins etc. I'll report more later as I really work it.
 
  • Like
Reactions: Chung123
Its has been fixed! (On my late 2017 15" TB MBP). Weird scroll bar issue is gone too.

Still some oddness... project name in timeline says "(null)" next to it. But everything seems to work... plugins etc. I'll report more later as I really work it.

project name shows fine here (so far...).
 
The issue with FCPX for me was fixed with a direct update (17A344b). However, I wanted to convert to APFS like last time, and downloaded the full installer and to reinstall directly. The full installer now automatically converted the start up drive to APFS, but the issue with FCPX reappeared. After restoring from the previous carbon copy clone and then updating directly from Mac App Store, everything is back to normal. (Of course I'm back to Mac OS Extended journaled) I'm confused. Is there something about APFS and FCPX on my specific Mac? It's just a hard drive format.

Update 8-20-17: I bought another SSD and did an experiment. I first did a clone backup of my start up drive beta 17A344b which is Mac OS Extended format.

I downloaded the standalone installer from the Apple Store linked from the beta.apple.com site.

I performed the full install and it reinstalled and converted the current start up drive to APFS.

Rebooted.
As expected, FCPX has the dark video window issue: start up drive is APFS.

Rebooted from the cloned backup of 17A344b.. and then used latest version of Carbon Copy Cloner to restore previous clone to the current APFS startup drive.

Rebooted. Final Cut Pro X is now correct... and my start up drive is APFS format.

It leads me to suspect there is either a issue with the standalone Hgh sierra Beta installer and my Mac Pro 5,1 with AMD 7950 or my current install has some kind of legacy issue or garbage.

Sent feedback to Apple just in case.

Might have to consider a format and clean install in the future.

Note: Carbon Copy Cloner as of this writing does not support creating bootable APFS clones of your startup drive. The copy needs to be on OS Extended format drive.
 
Last edited:
The issue with FCPX for me was fixed with a direct update (17A344b). However, I wanted to convert to APFS like last time, and downloaded the full installer and to reinstall directly. The full installer now automatically converted the start up drive to APFS, but the issue with FCPX reappeared. After restoring from the previous carbon copy clone and then updating directly from Mac App Store, everything is back to normal. (Of course I'm back to Mac OS Extended journaled) I'm confused. Is there something about APFS and FCPX on my specific Mac? It's just a hard drive format.

not sure, by my mac is APFS-formatted, and, outside of some random crashes in the previous beta (which 2 restarts seemed to have fixed), am not (yet) having any issues in the current beta.
 
  • Like
Reactions: Chung123
Starcraft II is terribly slow, below 10fps on 2880x1600 Ultra settings

My Specs:
10.13 Beta (17A330h)
MacBook Pro 15 Late 2016, Radeon Pro 455

Update: problem solved after update to 17A344b
 
Last edited:
not sure, by my mac is APFS-formatted, and, outside of some random crashes in the previous beta (which 2 restarts seemed to have fixed), am not (yet) having any issues in the current beta.

My Mac is APFS too... this beta did fix it.
 
Is anyone else having issues with the Photos app on any of these betas?

I'm using APFS, and my Photos library became corrupt during the APFS conversion, so I deleted it and I have attempted to redownload my iCloud Photo Library to new Photos Library database files, but it always gets stuck at "Updating x,xxx items...".

iCloud Photo Library works fine on my iPhone and iPad, but I can't seem to get it to download my photos on my iMac.

Anyone else have this issue?
 
Is anyone else having issues with the Photos app on any of these betas?

I'm using APFS, and my Photos library became corrupt during the APFS conversion, so I deleted it and I have attempted to redownload my iCloud Photo Library to new Photos Library database files, but it always gets stuck at "Updating x,xxx items...".

iCloud Photo Library works fine on my iPhone and iPad, but I can't seem to get it to download my photos on my iMac.

Anyone else have this issue?


Mine did also, it would crash everytime I opened it. I switched back to Sierra.

That was the only issue I had with the beta, id be tempted to re beta if this has been solved with the latest
 
Mine did also, it would crash everytime I opened it. I switched back to Sierra.

That was the only issue I had with the beta, id be tempted to re beta if this has been solved with the latest

Glad to know it’s not just me. Hopefully fixed in the next beta. Famous last words...
 
Glad to know it’s not just me. Hopefully fixed in the next beta. Famous last words...
Me too. Also I've been having a similar issue with iBooks and Messages has lost all of my conversations and I've not been able to get them back yet (they are still on iPad and iPhone). Strange that all the Microsoft (spit!) apps work perfectly but some Apple native apps are problematic.
 
Me too. Also I've been having a similar issue with iBooks and Messages has lost all of my conversations and I've not been able to get them back yet (they are still on iPad and iPhone). Strange that all the Microsoft (spit!) apps work perfectly but some Apple native apps are problematic.

Are you on the latest build?
 

Attachments

  • Screen Shot 2017-08-16 at 22.19.27.jpg
    Screen Shot 2017-08-16 at 22.19.27.jpg
    21.5 KB · Views: 239
So, Microsoft word has been listed as having issues since beta 1. Does anyone have any updates as to whether the issues are still present in the newest beta?

Thanks in advance!
 
So, Microsoft word has been listed as having issues since beta 1. Does anyone have any updates as to whether the issues are still present in the newest beta?

Thanks in advance!
I have 2016 office and I am not having major issues. Only issue I am seeing is, when I double to click to open a file, it stays in the background. I have to force kill and reopen the file.
 
Transmit Version 5.0.1 (46656) sporadically reverts to unlicensed, prompting to re-enter license info and activate.
 
I have 2016 office and I am not having major issues. Only issue I am seeing is, when I double to click to open a file, it stays in the background. I have to force kill and reopen the file.

Just saying office 2016, is really not enough. What version? The latest is now V 15.37.

Lou
 
So, Microsoft word has been listed as having issues since beta 1. Does anyone have any updates as to whether the issues are still present in the newest beta?

Thanks in advance!

I have 2016 office and I am not having major issues. Only issue I am seeing is, when I double to click to open a file, it stays in the background. I have to force kill and reopen the file.

I have had no issues with Office 2016, but I’m getting the Office Insider Fast Ring builds, so the latest version is 15.38 (170815). These tend to keep up with the macOS beta issues pretty well.
 
Still doesn't work on my Mac.

Run the PB installer, everything seems OK, reboots, goes right back to the login screen. No error message or anything.

2011 MBP with custom Fusion Drive. (Maybe it doesn't like that.)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.