MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
cuttime wrote:I also find myself using the "lost my cursor" feature way more than I ever thought I would...
With three monitors that I use in my day job, that is incredibly handy. Otherwise, a lot of performance and compatibility tweaks.
I haven't had any Finale issues since 14.5 but my iMac has a built in mic. No doubt, few of us use Finale the same way — if another's issues aren't affecting me, it's likely that I'm not using the features that triggers them.
DP 11.31; 828mkII FW, micro lite, M4, MTP/AV USB Firmware 2.0.1 2023 Mac Studio M2 8TB, 192GB RAM, OS Sonoma 14.4.1, USB4 8TB external, M-Audio AIR 192|14, Mackie ProFxv3 6/10/12; 2012 MBPs Catalina, Mojave IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5.2, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 Pro, Toast 20 Pro
Same here on Finale. It's working fine here, but I probably only use about 50% of it's features.
MLC, what's not working for you?
Phil
DP 11.23, 2020 M1 Mac Mini [9,1] (16 Gig RAM), Mac Pro 3GHz 8 core [6,1] (16 Gig RAM), OS 14.3.1/11.6.2, Lynx Aurora (n) 8tb, MOTU 8pre-es, MOTU M6, MOTU 828, Apogee Rosetta 800, UAD-2 Satellite, a truckload of outboard gear and plug-ins, and a partridge in a pear tree.
With El Capitán I just noticed I lost Menu Meters and XtraFinder
Apparently there are some hacks to force them into the system, but it involves messing with some security scheme with the Terminal, so that is a no-no for me.
I hope the developers come up with a working version for El Cap soon, especially Xtra Finder!
Mac Mini Server i7 2.66 GHs/16 GB RAM / OSX 10.14 / DP 9.52
Tascam DM-24, MOTU Track 16, all Spectrasonics' stuff,
Vienna Instruments SUPER PACKAGE, Waves Mercury, slaved iMac and Mac Minis running VEP 7, etc.
--------------------------- "In physics the truth is rarely perfectly clear, and that is certainly universally the case in human affairs. Hence, what is not surrounded by uncertainty cannot be the truth." ― Richard Feynman
With El Capitán I just noticed I lost Menu Meters and XtraFinder
Apparently there are some hacks to force them into the system, but it involves messing with some security scheme with the Terminal, so that is a no-no for me.
Looks like you have to disable SIP. I had to do that to make AlphaTrack driver work. So far, no problems though.
As reported by Gravity Jim, much improvement in speed, when going from Yosemite to El Capitan.
Many *hard-on-CPU* audio tasks run much smoother now on my system.
Mac Studio Ultra, 64 GIG RAM, Apollo Quad, OS 13.4.1 Ventura
DP 11.22, Yamaha Motif XS8, Novation MoroderNova, UAD Apollo and FX plugs, Lots of PLAY/OPUS libraries, Ivory 2, lots of Arturia titles, all 4 Spectrasonics titles, NI Komplete 13, BFD2-3, Addictive Drums 2, MachFive 3, Pianoteq 6, lots of UVI Workstation titles, All 5 MusicLab guitars-RealGuitar, RealStrat, RealLesPaulCustom, RealRickenbacker and RealEight.
Apple has enabled a new default security oriented feature called System Integrity Protection, often called rootless, in OS X 10.11 onward. The rootless feature is aimed at preventing Mac OS X compromise by malicious code, whether intentionally or accidentally, and essentially what SIP does is lock down specific system level locations in the file system while simultaneously preventing certain processes from attaching to system-level processes.
While the System Integrity Protection security feature is effective and the vast majority of Mac users should leave rootless enabled, some advanced Mac users may find rootless to be overly protective. Thus, if you’re in the group of advanced Mac users who do not want SIP rootless enabled on their OS X installation, we’ll show you how to turn this security feature off.
For those wondering, System Integrity Protection locks down the following system level directories in OS X:
/System
/sbin
/usr (with the exception of /usr/local subdirectory)
Accordingly, rootless may cause some apps, utilities, and scripts to not function at all, even with sudo privelege, root user enabled, or admin access.
Turning Off Rootless System Integrity Protection in OS X El Capitan 10.11 +
Again, the vast majority of Mac users should not disable rootless. Disabling rootless is aimed exclusively at advanced Mac users. Do so at your own risk, this is not specifically recommended.
Reboot the Mac and hold down Command + R keys simultaneously after you hear the startup chime, this will boot OS X into Recovery Mode
When the “OS X Utilities” screen appears, pull down the ‘Utilities’ menu at the top of the screen instead, and choose “Terminal”
Type the following command into the terminal then hit return:
csrutil disable; reboot
You’ll see a message saying that System Integrity Protection has been disabled and the Mac needs to restart for changes to take effect, and the Mac will then reboot itself automatically, just let it boot up as normal
You can also issue the command by itself without the automatic reboot like so:
csrutil disable
By the way, if you’re interested in disabling rootless, you may also want to disable Gatekeeper while you’re in the command line too.
If you plan on doing something else in the Terminal or OS X Utilities screen you may want to leave off the auto-reboot command at the end, and yes, in case you were wondering, this is the same recovery mode used to reinstall OS X with Internet Recovery.
Once the Mac boots up again, System Integrity Protection will be disabled entirely in OS X.
Checking the Status of Rootless / System Integrity Protection in OS X
If you want to know the status of rootless before rebooting or without rebooting the Mac into recovery mode, just issue the following command into the Terminal:
csrutil status
You’ll either see one of two messages, enabled indi:
$ csrutil status
System Integrity Protection status: enabled.
or
$ csrutil status
System Integrity Protection status: disabled
If at any time you wish to change the status of rootless, another reboot into Recovery Mode is required.
How to Re-Enable Rootless System Integrity Protection in OS X
Simply reboot the Mac again into Recovery Mode as directed above, but at the command line use the following syntax instead:
csrutil enable
Just as before, a reboot of the Mac is required for changes to take effect.
As previously stated, the vast majority of Mac users should leave rootless enabled and embrace System Integrity Protection, as most OS X users have no business in the system level directories anyway. Adjusting this feature is really aimed at advanced Mac users, whether IT, sysadmins, network administrators, developers, tinkerers, security operations, and other related highly technical fields.
Adjusting this feature is really aimed at advanced Mac users, whether IT, sysadmins, network administrators, developers, tinkerers, security operations, and other related highly technical fields.
...or DAW users that need their legacy AlphaTrack driver to load.
Long story short: SIP is a new level of protection not available in earlier versions of the Mac OS.
Apple has never wanted developers to write to those levels and with SIP enabled, those parts of the OS are no longer available to apps and utilities. As these apps are updated, this issue will diminish but certain legacy programs have ceased development — the only way they can run is to disable SIP.
DP 11.31; 828mkII FW, micro lite, M4, MTP/AV USB Firmware 2.0.1 2023 Mac Studio M2 8TB, 192GB RAM, OS Sonoma 14.4.1, USB4 8TB external, M-Audio AIR 192|14, Mackie ProFxv3 6/10/12; 2012 MBPs Catalina, Mojave IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5.2, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 Pro, Toast 20 Pro
