Mojave 10.14 - What works and what doesn't

Hi Roy.

All adapters have problems over SMB. But we are expecting driver updates very soon now. I will keep you updated.

- Ronny

Upgraded to Mojave last night.

Most everything seems to be okay, but I've got an issue with SNS globalSAN iSCSI initiator - the control panel is malfunctioning so I can't use it to connect to one of my shares. I don't use it so much anymore, and have access from another machine that's still on High Sierra, so not too scary.

I'm about to give the CLI a try, maybe I'll get lucky!

It looks like a problem with my Borisfx Continuum 11 inside FCP X. When you apply a filter, the picture goes black. I uninstalled and reinstalled but the same issue appears

[deleted]

(can you delete posts?)

ronny courtens wrote: Hi Roy.

All adapters have problems over SMB. But we are expecting driver updates very soon now. I will keep you updated.

- Ronny

All Adapters? Which are we talking about here?

"All adapters have problems over SMB" That means an Ethernet adapter, running SMB.

We have noticed significant slowdowns (-200MB/s) and even occasional disconnections when using Mojave over SMB. This affects any type of 10GbE to Thunderbolt adapter and will either be fixed by driver updates or by a coming Mojave bug fix. Not a big deal because no-one will ever update the OS of any workstation connected to a shared storage server unless the manufacturer of the server has announced full compatibility with the update.

- Ronny

Upgraded a couple of days ago from HS on a late 2013 rmbp on which High Sierra had been absolutely abysmal with screen issues, frequent crashes freezes etc etc.

Mojave seems much faster, much more responsive with no crashes in two days and everything thus far working really, really well.

I did not do a clean install either, if anyone else is using the same machine as me I would highly recommend it.

FCPX.guru wrote: ScreenFlow 8 (paid upgrade) makes it Mojave compatible. And on that note, for simple screen movie captures, the new capabilities in QT play are really great, if you don't need the SF specific editing tools.

I love Screenflow but don't really use any of it's editing features. I edit in FCPX. About the only thing I might do in Screenflow is turn off the mouse cursor sprite. However can Quicktime capture the screen at 60fps? I thought it was limited to only 30fps. I need 60fps and Screenflow does that.

FCPX.guru wrote: Seems FCPX does in fact work with eGPU now. Yay! Now to find someone who'll buy me one.

I'll buy you one if you buy me one. Actually I have a late 2013 Mac Pro Trash can. I'm not sure if it even has Thunderbolt 3 or not.

Is anyone else noticing this - I'm finding titles and effects are getting stuck loading when I open a project. I have a message reading 'Loading Vignette' for example and it's unplayable. I have a lot of 3rd party titles (from motionVFX mainly) and they seem to be most susceptible to hanging. Generally everything is feeling a little unstable in terms of performance and crashing so hoping for an update soon. I should do a clean install of the whole OS but I'm waiting for the time.

I have experienced massive performance lacks in Motion since updating to Mojave when using certain behaviors, most prominently with the "Align to" behavior (not sure if that's the right english term as I use the german version where the behavior is named "Ausrichten an"). Working with the object that has the behavior applied to is almost impossible, as every click brings up the beachball for 5-10 seconds. Interestingly this performance issues only occur on my 2017 imac but not on my 2015 MBP...

2017 5k iMac here too. Only a few months since the purchase...

robertdee wrote: 2017 5k iMac here too. Only a few months since the purchase...

So maybe it is the iMac gpu that causes issues in Mojave? Whatever it is, it's a pita. Let's hope Apple brings an FCPX/Motion update soon. It's about time now anyway...

After updating to Mojave every time I start FCPX 10.4.3 I get a com.apple.InfoHelper crash. I did a new Mojave and FCPX install and this error still shows and I don't have idea why. Can anyone give me some tips on how to find out the problem?

Thanks!
James

Are you sure this error doesn't say "com.apple.audio.infohelper"?. If it does, that may indicate that you have an invalid audio unit installed on your system, which you can try temporarily removing to see if you can get FCPX to startup. If the error is exactly as you have typed, then I have no real idea, other than it may indicate some type of incompatible plugin.
Have you tried to start FCPX by holding down both the OPTION and COMMAND keys? This will allow you to delete the preference files and often fixes issues. This is also recommended after starting FCPX immediately after an OS update or an update of FCPX.

Unfortunately, we did update! We have Mac Pros using Thunderbolt 2 Sanlink2 adapters.

That explain why we are suffering since Mojave. Beachball and playback issue but no connection lost

Any workaround?
Thanks!

For what it's worth, I haven't noticed any issues at all on my computers. One spanking new MacBook Pro [2.6ghzx6/32gb/512gb] that has only ever had Mojave. And just updated my Hackintosh and been working for two days in Mojave on that with no issues!

Hi Forum,

Getting ready to update to Mojave 10.14 from Maverick that's on a partitioned SSD MBPr (the other partition is allocated to HS that I run FCPX and other apps) now:

1. Would you advise a clean install or is it safe just to update from Maverick in the partitioned drive?
2. or is it safer to keep Mojave 10.14 on external newish fast M.2 drive (similar to Samsung 970 Evo) so I can rotate to boot Mojave 10.14 between iMac and MBPr?

Many Thanks

I've always run OS X updates, no clean installs, for a couple of decades, never any issues.

Technically, a fresh install can be safer/cleaner, I guess.

Only keep a Maverick partition is you have apps that won't run on Mojave. Otherwise, there's no reason to waste the space.

Usually I make a clean install, but I have just finished all projects, and so I became reckless and just updated. Noticed some strange behavior immediately. Cursor spontaneously changed to color picker or trim tool, clip selections suddenly changed (different clip on the timeline).
Reseted settings with alt+command+launch, and everything looks normal again, at least at first glance.