Category: Sequoia

Hello! I’m planning to upgrade my Logic and macOS from Mojave to Sequoia, and I have some questions about compatibility with my current gear. Specifically, I’m looking to know how well the following devices will work with the upgrade:

– Trigger Finger Pro
– Roland A-800
– Focusrite Scarlett
– Fantom X (I believe Roland hasn’t released a new driver for this model)

Also, I’ve heard good things about Sequoia when used with Logic X.

Is it true that most users have a positive experience with this combination? I appreciate any insights or experiences you can share regarding these devices and the upgrade process. Thanks in advance for your help!

I recently upgraded my Mac Mini M2 Pro from Ventura to Sequoia, and I have to say, my experience has been less than satisfactory. Here are a few significant issues I’ve encountered so far. First off, I face a frustrating problem with permissions on an external disk. I am unable to delete files from within the Canon Digital Photo Professional (DPP) app, which has been a major setback.

I have already started a discussion about this issue, hoping for a solution. Another annoyance centers around notifications. I enjoy playing simple games occasionally and had disabled Game Center. However, Sequoia introduced a “Game Mode” feature, which triggers a notification every time I start a game in full screen.

Initially, I found it manageable, but receiving the same notification repeatedly grew tiresome. I eventually discovered how to disable Game Mode, but upon launching a game, I was met with yet another notification about how to enable it in the menu. This constant interruption is frustrating. Additionally, I dislike how Apple has obscured the permission settings for software not from Apple or trusted sources in System Preferences.

Previously, I could easily click the “open anyway” button directly from the warning window. Now, I must navigate through System Preferences, which feels unnecessary and adds extra steps to the process. Lastly, the search function has slowed significantly. When I search for “birds” in a folder containing 6,000 images, I find that it takes ages to retrieve results, especially with external drives connected.

Previously, the search was instant, but now it can take over a minute, leading to a very inefficient experience. Given these concerns, I’m seriously considering whether it’s possible to revert to Ventura.

When I was using Mojave, the notifications had a handy feature that indicated how long ago they were received. For instance, it would say things like “A minute ago,” “2 minutes ago,” or simply “Now.”

This made it easy to gauge the timing of each notification. Currently, I am using the Sonoma operating system, but I have noticed that it lacks this time reference for notifications.

Instead, the notifications in Sonoma only display the content without indicating how much time has passed since they were received. This absence of a time marker can be inconvenient for users who like to keep track of their notifications more precisely.

Interestingly, I’ve heard that the Sequoia operating system does include this feature, showing the elapsed time for notifications similarly to how Mojave did. This could be an appealing reason for me to consider switching to Sequoia in the future for better notification management.

Overall, the difference in notification displays across these operating systems highlights the evolution of user interface design. While Sonoma offers improvements in other areas, the lack of a time reference can detract from the overall user experience.

It’s fascinating to see how different OS versions approach features that some users may find essential.

I recently installed iTunes on my M4 Max Studio using an impressive hack I found on MacRumors, so thanks to bogdanw for that! I’m thrilled that I can once again connect my 5th generation iPod to my Mac through iTunes. However, there’s a frustrating downside: my 21,000+ songs across hundreds of playlists did not retain the Show View Option settings I previously set.

In an attempt to fix this issue, I recorded an automated task using Automator’s “Watch What I Do” feature, but it failed to register mouse clicks, such as toggling View Option selections. I also tried using ScriptEditor, but as someone who isn’t too familiar with scripting, I had the same result. I’m curious if there is an automation tool available that can accurately register and execute mouse clicks during action runs.

I made sure to adjust the Accessibility settings under Privacy & Security in System Preferences for the relevant apps, so I don’t think it’s a permissions issue. I’m reaching out for help or any guidance you can offer on this matter. Your advice would be greatly appreciated.

Also, if I’ve mistakenly posted this inquiry in the wrong section, I apologize. I can easily delete it and move it to the appropriate place. Thank you in advance for your assistance!

The original message expresses some confusion regarding the necessity of using Recovery Mode on an M1 MacBook Pro (MBP). Having owned the device for over four years, the user notes they have never needed to access Recovery Mode.

They highlight that even without booting into Recovery, it is possible to create volumes and mount external Time Machine drives while logged in as an administrator or by entering the admin password from a standard account. This raises the question: why rely on Recovery Mode at all?

The user suggests that Recovery Mode should be a tool used only in emergencies, implying that if one must utilize it, something significant likely went wrong beforehand. The message also touches on the issue of an external Time Machine drive that sometimes disappears.

This appears to be particularly problematic when there are other drive issues, suggesting that the operating system might struggle to mount drives properly when conflicts arise. The user raises several troubleshooting questions: After unplugging and re-plugging the drive, does it mount successfully?

What happens if the system and the external drive are restarted? Additionally, checking Disk Utility—does the drive appear greyed out, and can it be manually mounted by right-clicking?

Furthermore, the user inquires whether the drive can be mounted on another computer. The goal is to isolate the problem to determine whether it lies within the operating system, the hardware of the external drive, or the formatting of the drive itself.

Identifying the source of the issue is crucial for effective troubleshooting.

Welcome to the world of MacOS! It’s great to hear that you love your Mac Mini M4, but I understand how frustrating it can be to deal with monitor profile issues. The problem you’re experiencing, where your custom monitor profile reverts to the default sRGB upon waking from sleep or exiting the screen saver, can certainly disrupt your workflow, especially for tasks like photo editing that require precision.

First, ensure that your custom display profile is set as the default profile in the Display Preferences. Go to System Preferences, then Displays, and select the Color tab. From there, choose your calibrated profile and make sure it’s specified as the default.

This may help prevent the reversion to sRGB. If the problem persists, consider resetting the NVRAM (non-volatile random-access memory) on your Mac. This can sometimes resolve issues related to display settings.

To do this, restart your Mac and immediately hold down the Option, Command, P, and R keys for about 20 seconds. This may clear any odd configurations causing your custom profile to be lost when the system sleeps. Another potential fix is to check for software updates.

Ensure that your Mac is running the latest version of MacOS, as updates often include fixes for various bugs and issues. Lastly, if these options don’t work, you might want to explore third-party calibration software that allows for better management of display profiles. Some programs offer advanced settings and can help retain your custom profiles even after sleep mode or screen saver activation.

I hope these suggestions help you maintain optimal calibration for your monitor and streamline your photo editing process. Good luck!

It’s great that you’re taking the initiative to reinstall the software on your second-hand MacBook Air M1. Your question about the impact of the installation method on performance is valid, as many users have had varying experiences with different methods. When it comes to reinstalling macOS Ventura (Sequoia), you essentially have two options: using a bootable USB drive or utilizing the Recovery mode. Both methods will ultimately result in the same operating system being installed, but there are some differences to consider.

Using a bootable USB drive can sometimes provide a cleaner installation experience. This method usually allows you to start fresh, ensuring that any previous system remnants are completely removed. Additionally, it gives you the option to format your drive before installation, which can help eliminate any lingering issues from the previous setup. Many users feel that this method can lead to improved performance and stability.

On the other hand, using the Recovery function is often more convenient, especially if you don’t have access to a USB drive. Recovery mode reinstalls the operating system directly from the Internet, which can save time and effort, but it may not provide as thorough a clean as a USB installation. Some users have reported inconsistencies in performance with installations made via Recovery mode compared to using a bootable drive. In summary, while both methods will reinstall macOS Ventura, a bootable USB might offer a slight edge in terms of a clean slate and potentially enhanced performance.

Ultimately, try whichever method feels best to you, and hopefully, your experience will be positive.

Has anyone else experienced issues with disk space utilization on MacOS Sequoia? It seems that the reported numbers have become increasingly disconnected from reality. Recently, I made significant changes to my file system that should have resulted in a 200GB increase in available space.

However, Sequoia claims I have only saved 10GB. To add to my frustration, Omni Disk Sweeper, a tool I typically rely on for accurate real-time tracking of disk usage, has also become unreliable. Now, it reports the same overview numbers as MacOS, although its detailed directory summaries still seem to function correctly.

Although I am aware that I have more disk space than what is being reported, I am concerned about the potential for running out of disk space in the future. It is unsettling to think that I may underestimate my available resources based on the inaccurate information provided by MacOS. I don’t want to find myself in a situation six months down the line, thinking I have sufficient space, only to discover that I am mistaken due to these inconsistencies.

This situation raises questions about the reliability of the tools at our disposal for managing disk space on MacOS. While the detailed summaries from Omni Disk Sweeper are still trustworthy, the overview figures have lost credibility. This inconsistency poses a challenge for users who rely on accurate data for effective file management.

As we navigate this issue, it remains crucial to find solutions that restore faith in the system’s reporting mechanisms.

It has been observed that version 15.3.1 did not resolve the disk space discrepancies. Currently, Finder indicates that there are 300GB of free space on the internal SSD. However, when using the terminal command ‘df -h’, it shows only 214Gi of available space. Adding to the confusion, the disk space analyzer reports that there are 230GB free.

Given these conflicting numbers, it seems likely that Finder is misrepresenting the available disk space. In fact, Finder previously indicated around 220GB of free space, and no actions were taken that could have freed up a significant amount of disk space since then. This discrepancy raises questions about the reliability of Finder’s storage reporting. Additionally, it is important to note that the AI feature is automatically re-enabled after any software update.

If you prefer not to use the AI function, it is essential to remember to disable it again following an update. This is a small but crucial detail for users who wish to maintain their preferred settings without the interference of automatic changes. In summary, the varying reports of disk space across different tools suggest an issue that may need further investigation. Keeping track of updates and settings, such as the AI feature, is also key to ensuring optimal device performance.

I am posting this in the Sequoia forum because I suspect that the issue relates to security features in Sequoia. I have a new Mac Mini (M4) running Sequoia 15.5, and I have installed all the latest security updates. I am using an AppleScript in Script Editor that is designed to open the Terminal app and send three commands. However, the script executes successfully occasionally, while at other times it fails due to a keystrokes permission error.

A standalone app created from this script encounters the same inconsistency. I have the latest version of Python3 installed on the Mini. The standalone app is crucial for me, as I want to set it as a login item so that it runs automatically in the event of a power failure and the Mac Mini reboots. The script used to work flawlessly on my previous Mac Mini (2014 Intel).

Here’s a brief overview of the script:

1. The script waits for 30 seconds to allow the Mini to fully reboot. 2. It opens the Terminal.

3. It changes the command line to the “pigs” directory located in my user account. 4. It runs a Python script named pigs.py.

5. Finally, it enters the administrator password via sudo. The main issue is the inconsistent execution. There seems to be no pattern to when it works or fails; it feels random.

Previously, this script worked perfectly for about ten years on my older Mac Mini. I have reached out to Apple Support, spending around 40 minutes trying to troubleshoot, but they could not identify the problem. Given that the script occasionally runs without issues, this seems to indicate a potential OS issue. Any advice or suggestions would be highly appreciated.

Thank you,

Mark