MacInTouch Amazon link...

macOS 10.15 Catalina

Apple, News
What does that mean: Was she unable to find the font settings in Mail's preferences, or did she edit the font settings there and the settings did not stick?
She didn't explain, but whatever the problem was seemed to clear up after she waited a while. That makes me suspect the problem was Apple Mail's slow processing of mail after the upgrade on her 2015 Mac. I have seen similar problems after other upgrades that affect my large email archives.

I experienced this issue yesterday (may have been the first time I've searched for a message since upgrading to Catalina. I found this solution elsewhere that worked for me: 1) Quit Mail; 2) Shift-Launch Mail and Quit; 3) Repeat 2; 4) Reboot; 5) Launch Mail normally, and Search function was restored.
In my case it was a completely clean install of Catalina. I tried what you mention and more. What oddly worked was adding "/" to the privacy tab rather than dragging "Macintosh HD". I say oddly, because, once "/" was added, Spotlight stopped searching "/" for everything except Mail, which started working. Mail continued searching once "/" was removed, and search worked again for everything else.

On other machines which were updated from Mojave, there were no issue with search in Mail.

I have found another bug in Catalina – if Mail is the frontmost application, and you try to click the name of a document in the Recent Items submenu of the Apple menu, you get the error message "The application “Mail” does not have permission to open <filename>."
I was not trying to open the document in Mail; I was trying to open the document in its default program (as if I had double-clicked it in the Finder). This only happens with Mail; the behavior is normal if another app is frontmost.
Works just fine for me.

That page explains the problem in the last section:
I didn't want to spend a lot of time researching, but it was pretty easy to find these:
It may make sense to support a Windows-only product - that's a business decision. And Microsoft absolutely deserves kudos for supporting applications clear back to DOS in Windows 10. But it seems a little disingenuous to imply, as the developer did, that just out of the blue Apple shipped an OS that doesn't support Carbon or 64-bit apps. If they couldn't figure out which way the wind was blowing after more than ten years, it makes me wonder how on-the-ball they really are.

I have an Epson V330, and when I look that up on VueScan’s extensive list of scanners supported, the support page says ... which appears to mean that for Catalina it just doesn't work until suitable 64-bit drivers are developed.
Epson provides two sets of "drivers". One is to support Apple's Image Capture. The other is for the Epson "native" apps.

VueScan can leverage Image Capture (so basic scans would work), so VueScan Pro may be the more impacted offering. The "it works" can be just basic scanning support. If VueScan can issue the commands for the more advanced features, then the Image Capture driver would be good enough for the Pro version too.

Epson's Image Capture (ICA) driver supports macOS 10.15 (and hence very probably is 64-bit).

Ric Ford

I didn't want to spend a lot of time researching, but it was pretty easy to find these:
Let us know when you find detailed documentation about APFS, third-party APFS utilities, or support for kernel extensions in Catalina....
If they couldn't figure out which way the wind was blowing after more than ten years, it makes me wonder how on-the-ball they really are.
They're hardly the only company struggling to deliver Catalina-compatible Mac software or struggling with Apple development issues, as Sam has previously noted:
And Adobe, the software giant and leading-edge developer that succeeded on the Macintosh platform and which is presumably very much "on the ball", still has macOS Catalina compatibility issues. See below for music/audio software compatibility issues for a long list of other companies, some of which are assuredly "on the ball."

Ric Ford

Comprehensive notes about Catalina compatibility from a leading audio retailer:
Sweetwater Sound said:
macOS 10.15 Catalina Compatibility List
Many musicians and engineers are affected by macOS compatibility problems when upgrading, and we don’t want your studio temporarily out of commission while you’ve got work to do. In this guide, we will show you everything you need to know about compatibility for Apple’s new Mac operating system: macOS 10.15 Catalina. Before you update to Apple’s new Mac operating system, follow this guide to make sure all of your software and each of your devices remain compatible with your Mac. Revisit this page for up to date compatibility information.

They're hardly the only company struggling to deliver Catalina-compatible Mac software or struggling with Apple development issues...
No argument, and one of the reasons I read MacInTouch is to try to stay informed on these topics.
Let us know when you find detailed documentation about APFS, third-party APFS utilities, or support for kernel extensions in Catalina...
I don't know, of course, but I doubt that audio software would need to be concerned with kernel extensions or what the underlying file system happens to be. Companies that do need to worry about things like that (Bombich) seem to be coping despite the snags.

Epson provides two sets of "drivers". One is to support Apple's Image Capture. The other is for the Epson "native" apps. VueScan can leverage Image Capture (so basic scans would work), so VueScan Pro may be the more impacted offering. The "it works" can be just basic scanning support. If VueScan can issue the commands for the more advanced features, then the Image Capture driver would be good enough for the Pro version too.
Epson's Image Capture (ICA) driver supports macOS 10.15 (and hence very probably is 64-bit).
Thanks. What I find under Epson scanners when I look the list of applications About this Mac are:
EPSON Scan: 5.1.1f2 11/6/14, 64-Bit (Intel): No
Location: /Applications/Epson Software/EPSON

EPSON Scan Settings: : 5.1.1 11/6/14, 64-Bit (Intel): No
Location: /Applications/Epson Software/EPSON Scan

EPSON Scanner: : 5.7.25 6/21/19, 64-Bit (Intel): Yes
Location: /Library/Image Capture/Devices/EPSON
Get Info String: 5.7.25, Copyright(C) Seiko Epson Corporation 2002-2015 All rights reserved.

Epson Scanner Monitor: 4.6.2 12/9/17, 64-Bit (Intel): No
Location: /Library/Application Support/EPSON/Scanner/ScannerMonitor/Epson Scanner
If that's the Epson Image Capture driver you mean, does that mean I could use VueScan but not VueScan Pro?

I'd like to do the update to Catalina, however, since I use a fair bit of music software, I can't. Just about every music software vendor I deal with (Steinberg, Native Instruments, IK, PlugIn Boutique, Arturia ) have sent me warnings that their products are currently not capable of running under the new Mac operating system and that I should be patient.
In fact, one of the vendors I deal with, Melda, recently put up a page on their website suggesting that maybe it's time macOS users started switching over to Windows 10.
What I can't understand is this: surely, as vendors and developers themselves, that the music software companies should be testing the betas of upcoming OS upgrades to ensure that they work with their products, and have updates available when the OS comes out or not too long after?
This is doubly troubling as the upcoming Mac Pro update is supposed to only be able to run Catalina on launch - and I can't imagine those users will be wanting to boot into Windows to run their music and DAW tools.
... I’m using [Apple’s] Logic Pro and most of my programs are working perfectly. Native Instruments is working fine with it, as well.

Catalina is a total show-stopper for me. I tested it on an old MacBook Air. So many of my GUI/UX tweaks, 3rd-party apps, etc don’t work.

Productivity has gone down the toilet.

FolderGlance DOA. The single biggest contribution to my workflow gone. I have big screen – having contextual menu app to allow me to work on files etc. by two-finger touch was remarkably useful. Now I am expected to travel the pointer to the bottom of screen, use the dock every time I want to do something? Seriously? Improvement in productivity and efficiency? Not!

Happy that cDock and Bartender work, but no CM for Finder is a deal breaker.

As always with Apple, it's all about form over function. I don’t need hundreds of new emojis, or all the other tweaks planted in the OS for the kids, I need a machine to work on. Meanwhile Apple doing everything in its power to reduce the usefulness of their gear.

And please spare me the “security, security, security…” waffle. I need to run Java for Cold Fusion db, I run without SIP, and I want my Mac to look like I want, not for Jony and his minions. I need control over my machine.

Apple has become the very embodiment of the foe in the 1984 commercial: bland, no control, no customization or personality, bland, bland, bland GUI/UX.

I did update this 2018 Mac Mini from Mojave 10.14, but had only been using the computer for a month or two after replacing an older 2012 Mac Pro quad-core that stopped booting after a Mojave security update. Could have fixed it, but figured it was time to finally upgrade that hardware...
Your comment about the 2012 Mac Pro quad-core no longer booting after an update is why I have held off on updating my 2010 Mac Pro quad-core, with a Metal-capable GPU, to Mojave. Having a bricked machine scares me.

I'm curious about what you might have been able to do to fix it.

Switching to Windows: it's not so simple for much of the user base.

I did it, but still use (and own) a 2012 Mac Mini. I find that much of the designer software (e.g. Adobe) works well (if not better) on Windows. Some things are not as simple, though; you have to Alt-### to get a character that on the Mac is just Shift-Command-#. Much easier to look up symbols, too. Windows allows older software to run (but some drivers do not run, and Windows 10 has some security there for a reason). But the biggest factor is cost: with a used Windows 7 laptop, I upgraded to Windows 10 at minimum cost (the OS upgrade was free, using the Windows 7 key, and a RAM upgrade was $40. The SSD was the most expensive upgrade at $100. I now have a viable laptop that I have used to neighbors diagnose their car issues, configure hardware, print to printers that Apple drivers are no longer supporting, and can run some software tools that are not on the macOS platform (nor need a store to install from).

But I wonder if Apple cares. They left many high and dry with Apple Server and its RAID (going to Pegasus). Its enterprise support is a joke. Its educational support is worse. JAMF is now the main contender at backed management. And Apple Remote Desktop is still slow. They all but abandoned AirPort users. Even their HomePod is overpriced compared to Sonos or Amazon (ok, Bose is still the king of expensive speakers for home). You would kill Sonos and Amazon if the HomePod were $99 or $199 with an Apple Music subscription. And why only black or white? Has no one seen home interiors before (wood, stone, glass, steel, beige, greens, blues...)?

Sure, there may have been adequate developer notifications that 32-bit suport is going away, best prepare! But the time between OS rollouts is shorter than ever. Didn't Mojave come out a year ago? Does it give developers, let alone customers, enough time to test their programs? Software is getting costlier, not cheaper, with subscriptions. It may be more convenient for the developers to push patches/updates but is not without consequences to you and me.

Where I work, I fear that, if we order new Macs, they will have Catalina. And there are several app vendors (Quest, which took over KACE from Dell) that are at least 6-9 months behind OS releases — KACE inventories and allows installations, Code 42 (formerly CrashPlan), Adobe products (Cloud, Acrobat...) and some VPN clients. I.T. used to be able to test and have time in advance of rollout. Not anymore.

This mentality of software upgrades, rather than updates, is going to buck soon. The scale of phone costs will be forcing one to lease-only, as with computers (Mac Pro starts at $6000)... and now with AppleCare+ on a monthly cost... as long as you own your phone.
Yet, aside from my phone and iPad startup speeds, the mac ]OS is still slow... or at least computers are, in startup. (Irony: a friend who was a big Mac user now has some killer nVidia RTX2080 GPU setup.)

... Possible fix for dock: you could write down (or screen shot) what is in your dock, and go into your user Library/Preferences and drag the prefs to the desktop then kill the dock to reload it (or logout/login or reboot) to see if the problem fixes with fresh prefs. (I've had to do this fix in the past for myself, and other users when the dock wouldn't behave itself.)
Thanks, but l already tried just removing my Dock prefs and letting the OS fall back to its defaults. Didn't work. With the most recent macOS 15.1 betas, the Dock has cleared up, but Mail still doesn't display properly, among other issues.

Well, Catalina keeps sounding worse and worse, the more I read. I know that I’ll have to move to it eventually but am in no hurry.

It occurs to me that I might have fewer problems if I did a clean installation and then restored my software and documents from Time Machine. How has this worked for those who have tried it?

I have to ask, is anyone up here really using Catalina?
My definition of using may differ from yours. My wife and I are using Catalina to run Adobe CC, Microsoft Office, Final Cut Pro X, TheSkyX Professional (astronomical observatory control) and other astronomy software, listening to our music, watching our videos. visiting our web sites, reading our mail, making backups with SuperDuper, scanning with VueScan... on our four Macs that are new enough to run Catalina. In short, we're doing what we do with our Macs. Except for using Thoth. For that we have a trio of older MacBook Pros.

I confess, however, that we are just lowly working people. We know nothing of betas on two volumes, broken docks, kernel linking issues, or the like. We're users, not experimenters.

Ric Ford

Rogue Amoeba Software said:
Third-party Audio Units on MacOS 10.15 (Catalina)
... Unfortunately, in MacOS 10.15 (Catalina), third-party Audio Units may fail to work as you expect. A change made by Apple means that all software must be “notarized” by their security systems. Non-notarized software is entirely prevented from running on Catalina.

This change means many older third-party Audio Unit plugins will not work at all on Catalina. This issue will occur in any modern Audio Unit host, including SoundSource, as well as Apple's own GarageBand and many others. When attempting to use third-party Audio Units, you may encounter non-functional plugins, error messages, or other undesirable behaviors.

Ric Ford

Guilty. But if I'm not understanding the issue, it would be nice if somebody could explain it [for me].
In addition to all the other links we've already mentioned, here's some more information:
Next Level Sound said:
Why Music Producers and Engineers Shouldn’t Upgrade to Mac OS 10.15 “Catalina” Immediately

... Separate from the blocking of 32-bit apps from running is a new security implementation in Mac OS 10.15 "Catalina". ... So ANY application, driver or plugin installed on "Catalina" MUST have this certificate from Apple or it WILL NOT RUN! ... Programs from vendors that are out of business are toast.

... When you consider the myriad of things a DAW is doing in the foreground (and many more in the background like accessing files, folders, plugins, libraries, etc.) it is easy to see how this can create a headache for the developer. Each of these functions requires authorization or permission from the OS. There are LOADS of things the developer must anticipate and handle in the DAW ecosystem. One misstep could mean incredible frustration for the end-user not to mention a program instability, increased crashes etc.

The Plugins themselves will need to ensure these checks are in place and devices like "iLOKS" will also have to be coded to not only work with the DAW but the OS itself. Even if a DAW is fully 64-bit it will most likely have to be updated to work flawlessly with "Catalina".

Another critical issue is that the DAW must be coded so that it includes all the permissions/entitlements for EVERY "ILOK" protected plugin! That is going to take quite a bit of time and there will always be those few that are missed in the first few rounds.

Drivers in "Catalina" will have no "by-pass" option. If the driver isn't verified by "Apple" it will not work. If you have older hardware (scanners, printers, interfaces, synths, etc.) that require a driver to run they may no longer work. If you are faced with issues like these you now have a bigger and more expensive problem on your hands!

With practically every software and hardware vendor recommending that you do not install "Mac OS 10.15" at this time, upgrading to "Catalina" isn't a good idea, in fact, it shouldn't even be considered. Until you are absolutely sure that your applications, hardware, and plugins are fully compatible with this release it is best to wait. Patience may save you many wasted hours troubleshooting problems, patching software and dealing with malfunctioning plugins and those hours are better spent on making music.

Ric Ford

Is there any Catalina replacement for InDesign? Is there a reasonable way back to Mojave?
You may be able to restore many of your documents from Catalina back to a newly installed prior system, and probably even many of the applications, but restoring preferences/settings is likely to be a problem, and Apple-managed files/libraries also may not migrate back. The ~/Library folder is probably a nightmare to coordinate/revert.
Anyone who wants to revert to Mojave from Catalina should have a Mojave backup, taken prior to the update. The challenge, then, is to locate the documents subsequently added and changed in Catalina and somehow migrate those files back to the Mojave system – an exercise that may not be easy. If any file/library formats have changed, those may not work again in Mojave.
Unfortunately, Apple's one-way Migration Assistant only updates newer systems, it won't help revert back to an older system.
Here's some additional discussion that might be helpful:
Macworld said:
How to downgrade macOS from Catalina or Mojave to an older version
With macOS Catalina arriving on Macs, it's sure to be the case that you installed the updated only to regret it later. Perhaps you discovered that an app you rely on no longer works or is buggy, maybe you just hate one of the new features, or perhaps there is a problem with Catalina that makes you wish you hadn't installed it straight away.

Luckily it is possible to downgrade, but unfortunately, Apple doesn't make it as easy as it could.

This article will help you downgrade from any version of the Mac operating system to an older version - so if you are looking to downgrade from Catalina, Mojave, High Sierra, Sierra, El Capitan or even one of the Big Cat versions of Mac OS X, then read on!

Alternatively, you could protect yourself from being lumbered with an operating system that doesn't run the way you want it to (or doesn't run the apps you need) by installing it on a separate volume (also known as dual booting) or running it on a separate drive, so, maybe after reverting back to an older macOS, you might like to try that instead.

Have been dealing with family matters and other business recently but now am back on track with testing Apple's latest shenanigans (Catalina, installers, etc) and updating MacStrategy. First up: Catalina and FireWire booting…

Using a test Mac Mini 2014, I installed a clean, up-to-date macOS 10.14 Mojave to the internal storage. Downloaded the latest Catalina installer and quit it when it fully downloaded. I then connected an external FireWire 1TB (spinning) drive. Formatted it as macOS Extended (Journaled). Copied some files back and forth - all worked fine as external "storage". Ran the Catalina installer and pointed it to the external FireWire drive - the FireWire drive's icon was greyed out and when hovering over it I actually got a message that stated "Catalina cannot be installed to this drive as it is connected via FireWire".

So, I quit the Catalina installer and formatted the external drive as APFS and re-ran the Catalina installer and pointed it to the external FireWire drive - the FireWire drive's icon was still greyed out and I got the same error message.

So, I disconnected the external FireWire drive, installed Catalina to the internal drive, booted and installed Carbon Copy Cloner. I then re-connected the external FireWire drive (which mounted okay) and cloned the macOS 10.15 installation to the external FireWire drive. Opening System Preferences > Startup Disk, the external FireWire drive does not show up but booting with the Option key down to the boot manager, the external FireWire drive showed up. However, selecting and booting from it got an Apple logo and boot progress until eventually it stopped with the no entry/no access symbol.

I can therefore confirm, with my limited/basic testing, FireWire is not supported for booting macOS 10.15 Catalina!

Epson provides two sets of "drivers". One is to support Apple's Image Capture. The other is for the Epson "native" apps.
... Epson's Image Capture (ICA) driver supports macOS 10.15 (and hence very probably is 64-bit).
Worth a try. Epson's product page for the V500 and maxOS 10.15 links to ICA driver v5.8.7 (released a few weeks ago on October 7th), which says it supports macOS 10.5 through 10.15. But the driver description also has this cryptic footnote:
Epson said:
This file applies to numerous Epson products and may be compatible with operating systems that your model is not.
(For comparison, if you request macOS 10.14 from the Epson site, you are offered three different driver packages. The ICA driver, "Scanner Driver v3.2.8.0" (April 2016, supporting macOS 10.3 through 10.14), and "Scanner Driver and EPSON Scan Utility v4.0.2.0" (September 2015, supporting macOS 10.5 through 10.14)

Assuming the ICA driver actually works with a V500 on Catalina (someone is going to have to actually try it to be sure), then you should (at minimum) be able to use Image Capture to run the scanner.

If VueScan uses the ICA driver, then that would also be an option. The web page doesn't say which driver it uses, only that Apple should auto-install it, which implies, but doesn't state that it is the ICA driver:
VueScan said:
Epson Perfection V500 Driver for Windows 10, macOS & more
You need to install the Epson driver to use this scanner on Windows x86 and Mac OS X. On Mac OS X, this is normally already installed by Software Update, so VueScan should just work.
So, to anyone with a V500 that has already upgraded to Catalina, go download and install (if necessary) the Epson ICA driver and see if you can scan via ImageCapture. If you can, then download and try VueScan. And please let us know the results of your tests.

In addition to all the other links we've already mentioned, here's some more information...
Dear all, here's my ten pence worth... updates and upgrades for musicians, producers and sound engineers are just about the most difficult to steer through, especially with a .0 release.

We've all had updated systems while dealing with SCSI, USB, Firewire, and Thunderbolt interfaces and external drives, let alone coping with drivers, and with plug-ins, whether they be AU VST or ProTools systems...

The update caveat is always the same: don't update until everything you use is confirmed as functioning with the new system.

FWIW, my ancient studio 2008 Mac Pro-based system (running Mac OS X 10.6.8 and Logic Pro 9) runs long-gone plug-ins and will never be updated. All is fine there.

However, my modern demo systems (2015 iMac and 2016 MacBook) run Logic Pro X (latest version) and are currently using (in Catalina) Vienna Symphonic Orchestra plugins and instruments from Ujam and Garritan 100% successfully.

In my experience, check the website, see if Catalina compatibility is confirmed, and then and only then, update. Beware that the hugely important interface manufacturers such as MOTU have Catalina updates, and, to date, most of their audio interfaces do not work with Catalina.
MOTU Inc. said:
MOTU and macOS Catalina
USB and "Hybrid" audio interfaces
We are working with Apple to complete 64-bit versions of the drivers and supporting software for the MOTU audio interfaces listed below, and will have an update to share soon. In the meantime, please note that the MOTU products listed below will not work on macOS Catalina. If you wish to continue using them, please continue to do so on macOS Mojave.
All obvious, I appreciate, but always worth repeating.... Having worked in large studios for many years, these things stay fresh!

For those interested in getting Aperture to run on Catalina, Nik Bhatt has written up some simplified instructions. Nik is the author of RawPower which accesses the underlying Apple RAW engine functionality and is available for macOS and iOS. He worked for Apple for many years and led the RAW Camera and Core Image teams. RawPower is a very nice editing app.
Now wouldn't it be nice if someone could come up with a similar hack for QuickTime 7 player? I've posted on MacInTouch previously about the frustration of using the more recent QuickTime versions when all I want to do is "cut, copy, and paste" video. This simple task was in every QuickTime version up to QuickTime 7. The current versions' ability to "split" is a clumsy substitute. Still haven't found a simple, easy, substitute for QuickTime 7, which now goes away with Catalina. Holding off on Catalina for that reason.

Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts