You now have to double-click on the name in the right side when the Smart Playlist is selected - it seems you can't rename it in the list of playlists on the left side any longer. (I created a new one just to test this - took a few tries to find where you could rename it now.)More iTunes/Music annoyances: I cannot name a new smart playlist or change the clever name Apple has decided to bestow on it. Seems to be based on the selection criteria as parsed by Apple's (almost intelligent) AI (absolute ignorance). Existing smart playlists appear to continue to function. Play counts/dates are updated. Changes applied.
No cloud music here at all; it's all on my Mac and, by extension, my iDevices. No subscription to Apple Music. Or Match. If that matters.
So I'm wondering if this is just me? And, thank god this isn't a production machine. And this isn't production software.
That page explains the problem in the last section: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.
Melda said:Switching from OSX to Windows
So what is the problem with Apple anyway?
Imagine you are a builder (the software developer of a DAW/plugin...) and you started creating a big factory some time ago. You have built the foundations, walls, started putting some equipment for various companies (your customers, the users) in it. And obviously the factory needs a roof, right? You started building your factory with a very specific roof manufacturer (Apple) in mind, which uses some odd roof attachment system, not a perfect one, but it does the trick. But suddenly this manufacturer comes in and says "sorry, we have a new attachment system, for which you need to make your factory one meter shorter and change the attachment bolts". Of course you, being the builder, know this is a total nonsense and all they need to do is a little gadget (converter) from the old roof attachment system to the new one. But they just won't do that, and even worse, they won't let you do that either. They just won't install the roof until you remake the entire factory. So you as a builder are in trouble. Your customers asked for this roof, which isn't special in a way, it just has a specific colour that other roof manufacturers don't make (and there are many of them, cheaper and often better ones). But to make it all work, you have to spend a huge amount of time rebuilding your factory for no good reason and after that some equipment (ProTools 10) now won't even fit in, because the factory will be too small. That's a situation without a reasonable solution and it happened several times before, but it seems to be getting worse than ever.
So the real question is, do you want the developers of your DAW and plugins to spend their days trying to fix the problems arising from system upgrades, or to improve their own software products, making them more functional, more powerful, faster, stable and easier to use? If it's the latter one, then the only solution seems to switch to Windows. The only one, who can make a difference is you, the customer.
I’m using it on one of my two work computers (2018 Mac Mini i7) to use it in a production setup and test it before our regular users do (they have been told to hold off on updates until around x.x.3 as normal - for most of them I just tell them when it's safe).I have to ask, is anyone up here really using Catalina? All through the public beta, I had Catalina running on two volumes, a "clean" volume, and a volume that is a clone of my "working" volume. There have been gross differences in the function between the two volumes with different things breaking between each.
On the "working" volume with the release of Catalina, the Dock will not display; although, checking Activity Monitor, it is running. "Killall Dock" will cause it to display. When I click on the Mail icon in the Dock, only the Activity window opens. A second click on the icon will open the main Mail window....
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.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?
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.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.
Works just fine for me.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.
I didn't want to spend a lot of time researching, but it was pretty easy to find these:
Epson provides two sets of "drivers". One is to support Apple's Image Capture. The other is for the Epson "native" apps.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.
Let us know when you find detailed documentation about APFS, third-party APFS utilities, or support for kernel extensions in Catalina....I didn't want to spend a lot of time researching, but it was pretty easy to find these:
They're hardly the only company struggling to deliver Catalina-compatible Mac software or struggling with Apple development issues, as Sam has previously noted: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.
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.
No argument, and one of the reasons I read MacInTouch is to try to stay informed on these topics.They're hardly the only company struggling to deliver Catalina-compatible Mac software or struggling with Apple development issues...
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.Let us know when you find detailed documentation about APFS, third-party APFS utilities, or support for kernel extensions in Catalina...
I'm going to take a wild guess here that you're not in the audio field, either as a professional or an amateur.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.
Thanks. What I find under Epson scanners when I look the list of applications About this Mac are: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).
If that's the Epson Image Capture driver you mean, does that mean I could use VueScan but not VueScan Pro?EPSON Scan: 5.1.1f2 11/6/14, 64-Bit (Intel): No
Location: /Applications/Epson Software/EPSON Scan.app
EPSON Scan Settings: : 5.1.1 11/6/14, 64-Bit (Intel): No
Location: /Applications/Epson Software/EPSON Scan Settings.app
EPSON Scanner: : 5.7.25 6/21/19, 64-Bit (Intel): Yes
Location: /Library/Image Capture/Devices/EPSON Scanner.app
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 Monitor.app
... I’m using [Apple’s] Logic Pro and most of my programs are working perfectly. Native Instruments is working fine with it, as well.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.
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.
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 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...
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.... 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.)
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 have to ask, is anyone up here really using Catalina?
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.
In addition to all the other links we've already mentioned, here's some more information:Guilty. But if I'm not understanding the issue, it would be nice if somebody could explain it [for me].
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.
Is there any Catalina replacement for InDesign? Is there a reasonable way back to Mojave?
Here's some additional discussion that might be helpful: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.
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.
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 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).
(For comparison, if you request macOS 10.14 from the Epson site, you are offered three different driver packages. The ICA driver, "Scanner Driver v22.214.171.124" (April 2016, supporting macOS 10.3 through 10.14), and "Scanner Driver and EPSON Scan Utility v126.96.36.199" (September 2015, supporting macOS 10.5 through 10.14)Epson said:This file applies to numerous Epson products and may be compatible with operating systems that your model is not.
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.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.
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.In addition to all the other links we've already mentioned, here's some more information...
All obvious, I appreciate, but always worth repeating.... Having worked in large studios for many years, these things stay fresh!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.
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.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.
The current VueScan release notes:... 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...
I should have some time to run some experiments on some "clean" OS instances in the next couple of days, but I suspect what happens in this mode is that VueScan is limited to the same set of abilities that Image Capture is. You are just getting the VueScan GUI.If your scanner isn't on this list, VueScan may still work with your scanner if you can find a WIA driver (Windows) or an Image Capture driver (Mac OS X) on the scanner manufacturer's web site.
For many years (since System 1.0) my occupation has included testing the viability of using a new macOS on various work computers. For Catalina, I started with a clean system install, as well as clean installs of all applications. Microsoft Office and Adobe Creative Cloud, plus a diverse group of utilities. We use Apple Mail, and my previously archived messages were all imported manually, as were all documents. It's a tedious process, but when a major OS upgrade is involved, this often saves a lot of trouble over time.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?
diskutil list ... /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - 40.0 GB disk3 Physical Store disk0s2 1: APFS Volume Catalina 40.0 GB disk3s1 ...
sudo diskutil apfs resizeContainer /dev/disk0s2 0
I have a V500 with VueScan. Works fine in Catalina (upgraded via migration).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.
I, like you and many others on this forum, am fed up with Apple for a variety of reasons. However, in my opinion, their products are not as good and their support is not what it used to be.I'm getting more and more fed up with Apple. Their products are good and their support is top notch, but the gap is narrowing between them and Windows. Pretty soon these two will be equally bad. In the last few years it seems as though Windows usability has gone up while Apple's has gone down.
As an Amazon Associate I earn from qualifying purchases.