The first prototypes of Macs running Apple Silicon are now out in the wild, and speed tests are starting to appear that suggest that performance worries may be overblown.… Read More iMacs Running Apple Silicon In Emulation Mode Already Faster Than Macbook Air
Apple announced the most significant change to the Mac platform in 15 years, that it is transitioning from using Intel processors to ‘Apple Silicon’.… Read More Apple Dumps Intel At WWDC, Promising Faster Macs & Vast Application Options
The Live Loops grid in Apple’s new Logic Pro X 10.5 has a hardware controller – and you might even own it already. Apple includes plug-and-play support for the Novation Launchpad line in the latest Logic. It’s a new angle on launching sound and patterns – well, literally and figuratively. You’ll want to physically rotate […]
The post Novation Launchpad is a ready-to-play controller for the new Live Loops grid in Logic Pro appeared first on CDM Create Digital Music.
Apple has announced availability of Logic Pro X 10.5, a major update that brings new creative tools for electronic music production the digital audio workstation for Mac. Version 10.5 comes with a professional version of Live Loops, a completely redesigned sampling workflow, and new beat-making tools. “The Mac and Logic Pro X are essential tools […]
The post Apple releases Logic Pro X 10.5 with Live Loops, Sampler, Step Sequencer & more appeared first on rekkerd.org.
The update introduces an amped-up version of Live Loops, a redesigned sampling workflow, and new beat-making tools.… Read More Apple Logic Pro 10.5 A Massive Release For Electronic Musicians
Every price point in Apple’s notebook lineup has recently gotten an update, with revisions to the 13″ MacBook Pro this week. And they’ve fixed the keyboards. So if you’re in the market for a Mac, which should you get? We know from sales figures that even in the midst of dueling economic and health crises, […]
The post Apple’s sweet spot: which MacBook do you want for music making now? appeared first on CDM Create Digital Music.
Apple appears to have accidentally leaked an upcoming version of Logic Pro with the signature feature of Ableton Live – nonlinear pattern launching.
While spotted on Reddit, the source of this leak at the famously secretive company appears to be … Apple itself. As I write this, the screenshot is still live on a public education site:
Credit where it’s due (“am I missing something” is right!):
If this is real – and not a mock-up that accidentally wound up on the page – it represents a landmark. That landmark might best be described as “what took you so long,” arguably, given that Apple Loops have been a feature of Logic Pro and GarageBand back to the reveal of GarageBand in January 2004. (Time flies!)
We can pretty easily analyze the screenshot. At the top, new icons appear to let you view a nonlinear Session View-style layout, the normal track arrangement, or both. (In this screen shot, the two are side-by-side.)
As with other copies of Live’s signature Session View, the horizontal and vertical axes are flipped. So whereas Live shows you tracks the way channel strips appear on a hardware mixer, vertically, Apple opt for a view more like a software DAW. Tracks are laid out horizontally, so that they match up with the arrangement.
Really, my issue with this is that you wind up with kind of a jumble of interface elements. That’s been the challenge in other DAWs trying to do the same. (An ill-fated effort in Cakewalk nee SONAR springs to mind; MOTU has tried the same in DP, but it’s a bit too soon to know yet how DP users are responding.)
Part of the appeal of Ableton Live is that the entire engine and software operation are structured around the idea, and the UI is clean and compact as a result. Here, part of the reason people may have responded that the image was fake was that it gives the user a lot to digest.
You’ll also see X/Y-pad effects at the bottom, including a filter and repeater – aping something that was in Ableton Live way back at the start.
I’m not sure how users will receive this. It could represent a blow to Ableton in the crucial education market, however, regardless – because it might allow education buyers to standardize on just Logic seats. But it represents a challenge independent software developers face, up against a company the size of Apple, when it comes to value.
On the other hand, I wouldn’t assume anything until there’s official word from Apple. Given this absolutely represents some kind of screw-up, it’s possible the screenshot itself is not representative of something Apple will actually ship.
And I wouldn’t worry too much about Ableton – the company has proven time and again that users are loyal to its workflow and simplicity, whatever the competition. Those of us sometimes swapping between Logic and Live might meanwhile just find this a welcome convenience. Time will tell.
Mainly I’m just sorry for whoever is working at home who may have, erm, just let this out.
The post Did Apple just leak a new version of Logic with Ableton-style clip launching? appeared first on CDM Create Digital Music.
macOS Catalina, the next Mac release, dramatically tightens security and removes 32-bit compatibility. That will cause incompatibilities with music software, requiring updates. Here’s what you need to know.
Catalina compatibility checklist
macOS Catalina (10.15) is expected to ship in October, replacing Mojave (10.14).
DAWs and other software using plug-ins: Requires updates to work.
Drivers: Installation and operation requires update to work.
32-bit software, software that accesses 32-bit libraries: Incompatible. Cannot be used past macOS Mojave.
Software using legacy video libraries: Incompatible. Cannot be used past macOS Mojave.
Plug-ins: May require update for full compatibility – but may run inside updated DAWs, and will install if the user overrides OS’ installer requirements.
Hardware: If a driver is required for operation, you’ll need an updated driver and installer. Driverless (class-compliant) audio and MIDI gear is unaffected.
Tightened Mac security
It’s worth acknowledging that security concerns are justified, even for consumer operating systems. Malware tools targeting users may be designed to exploit your computer’s resources, steal data, and impersonate you or even steal your money. At best, they can at least make your system unstable.
It’s also not just “a Windows thing”; recent attacks have singled out the Mac, too. For instance, security researchers uncovered an insidious piece of code found in downloads from a piracy website called VST Crack, embedded in pirated versions of software including Ableton Live. The software would embed itself on your system and start mining cryptocurrency. These threats do not impact the legitimate copies of the same software, so yes, this is an added risk when you pirate software.
All OS vendors regularly patch security holes; the approach in macOS Catalina (10.15) is more proactive. Apple are making some changes to the way the OS itself notifies you of activity by software and asks for your approval, a bit more like you had seen previously in iOS or Android. They’re also implementing tougher defaults for installers. And since malware works by running additional code on top of other code or memory, Apple are adding protections against running that code.
The issue here is not that these changes are unwarranted or even entirely unexpected, but that they bring a lot of change at once that will require you to update software – especially music software – in order for it to work properly, or at all.
Let’s look at those two changes separately: one is the change for installers (called “notarization”), and the second is a new set of requirements for how software is granted access to vital information (the “hardened runtime”).
The two requirements are related, because Apple won’t approve installers unless they also comply with the hardened runtime standards. So let’s take a look at the hardened runtime and entitlement permissions first.
Entitlements and the hardened runtime
Let’s recall here how malware works: it runs additional code that you didn’t intend to run, then gives that code access to something vital on your system (like your data, or microphone). So obviously, what Apple is doing is attempting to prevent those two things.
The first thing you’ll notice on macOS Catalina is that the Mac starts asking you for permission a lot more often. So now, the first time you print a score from notation software or try to open a file dialog to browse the desktop, you’ll get a pop-up asking if you really want to do that. That’s a bit annoying, but it’ll only happen once, and then will remember your permissions. And the reason it’s there is, of course, malware might otherwise perform the same task without your consent. You’re already familiar with this behavior from phone apps on Android and iOS; this is effectively the same idea, now on your desktop computer.
With a common, monolithic app, providing these permissions (called “entitlements”) is fairly easy. But music software isn’t monolithic. Your DAW is running all sorts of libraries and plug-ins and so on. Unfortunately, the exploits Apple is targeting in malware – “code injection, dynamically linked library (DLL) hijacking, and process memory space tampering” – also look a lot like the behaviors your DAW performs normally. And your DAW also needs to handle entitlements for plug-ins. In addition to the DAW needing your permission to access certain folders, for example, it also needs to ask your permission if a sample instrument like KONTAKT wants to access files, as well.
Here’s the bit you’ll really need to care about – if you’re upgrade to macOS Catalina, you will need to be prepared to upgrade your DAW, too. Providing this compatibility is complicated, so it’s likely that most developers will be able to support only their latest release – meaning you may require a paid update to that first.
The good news is, theoretically this burden falls on the DAW, not individual plug-ins. (Plug-ins may still require an update, because of the removal of 32-bit code and other portions of the OS required for compatibility, and because of new installer requirements.) But you will need to update any software working with plug-ins, or you may find software won’t run properly or will fail to run altogether.
It’s also likely that even with updates, some software will not work properly immediately after Catalina’s launch. Developers are still learning how to use this new feature of the operating system, and Apple’s frequent OS updates mean they have little time to do so. Also, an additional side effect of the new security requirements is to break the ability of plug-in developers to debug their plug-ins in DAWs, meaning testing is – for now – more difficult. That may slow compatibility and testing.
If you plan to use an older version of a DAW, you’ll want to avoid updating past macOS Mojave (10.14). If you do intend to update – or to buy a new Apple machine once Catalina is pre-installed and required by default – you should plan to use the very latest version of your DAW, and double-check that Catalina is supported. And even with listed Catalina support, expect there could still be some wrinkles immediately after the OS ships.
Once those pieces are in place, though, you will be able to use DAWs and plug-ins as you always have – just with some more pop-ups the first time you do something like access the file system or connect audio hardware.
(One illustration of how entitlements requirements might surprise you – someone on Reddit noticed the Live “computer keyboard” setting, which passes QWERTY keys to MIDI notes, suddenly broke in the Catalina beta. That makes sense; it would require the entitlements provided by the coming Live 10 update. And obviously, malware would love to be able to take your computer keyboard input and route it somewhere else without asking.)
Installer requirements and drivers
The other change in macOS Catalina is to require installers to be “notarized” by default (whereas previously it was a non-mandatory option). This means developers will submit installers to Apple for verification, and that they fulfill certain requirements for how those installers are built. (These requirements largely have to do with how they link against the Mac SDK and following new guidelines like the hardened runtime.)
This is not the same as the App Store approval requirements on iOS (or similar stores from Google and Microsoft). Apple aren’t looking at the software itself, only verifying the installer is built according to their standards. The process takes something like an hour currently, not days or weeks as the stores can. And most importantly, Apple will allow users to override the installer requirement. As with Gatekeeper in current versions of macOS, you’ll get a dialog telling the installer or app was blocked, but you’ll still be able to choose to run something anyway. (Right-click, choose open, and you’ll be given option.)
Apple developer documentation on the notarization feature:
Notarizing Your App Before Distribution
Unverified plug-ins may also continue to work inside DAWs – depending on the DAW you’re using. This means in theory, you’ll be able to install and attempt to use plug-ins, even if they haven’t been updated for Catalina. You would need to override plug-in notarization requirements for the installation from dmg (Disk Image) files, but once a file was installed, a DAW may be able to support it, theoretically. Your mileage may vary when it comes to actual use, however; the advantage of the installer requirement may be that it gives a clue that a developer has tested on Catalina.
PreSonus has just announced for their Studio One DAW that not only will you need to update Studio One itself, but many plug-ins will also need an update. In their case, plug-ins built before June 1, 2019 will still need to be signed (the earlier method of verification for Apple developers). Plug-ins built after that date will need to fulfill Catalina’s tougher requirements – notarization and the hardened runtime.
Drivers for hardware will hit a hard wall. Unverified drivers will not function on the new OS. This means if you have older hardware that doesn’t have updated drivers and installer, you won’t be able to use it. There’s no ability to override this requirement.
End of the road for 32-bit and legacy libraries
Just as significant as the security changes, Apple is ending support for 32-bit code starting with Catalina. This is a hard barrier – you won’t be able to use “bridge” tools for 32-bit plug-in compatibility, for instance. Any 32-bit app, library, or plug-in will simply refuse to run.
It may not be immediately obvious that software makes use of 32-bit code, either. A 64-bit application may still make use of a 32-bit library. For instance, Ableton tell CDM that they found their previous versions of Live would attempt to call a 32-bit library on startup. These apps may not fail gracefully; they may simply crash. This means even if you’re using a 64-bit and 64-bit plug-ins, you will want to verify compatibility with the vendor before upgrading.
If you have 32-bit plug-ins or older software you rely on, you will likely want to stay on macOS Mojave. Once you upgrade, this software will cease to work. This may also mean you want to retain an older Mac running Mojave or earlier, for backwards compatibility.
Apple has also ended long-deprecated libraries, including the older video library (called QTKit).
Case study: Ableton Live
Ableton provided CDM with access to their compatibility process. An update to Live 10 will support Catalina’s new requirements at launch. This involved a series of changes, which may be typical for DAW developers. In Ableton’s case, it meant the following updates:
· Rebuilding the installer with notarization support and its requirements
· Removing all 32-bit code and libraries (including one 32-bit library that will cause previous versions of Live to crash on launch)
· Providing full compatibility with Max
· Transitioning video code to the latest AVFoundation (from a now-unsupported version of QuickTime)
The move to AVFoundation is good news for anyone working with video – even if you use an older macOS version like Mojave. There’s improved video export performance and new codec options.
Ableton also say you should expect that these updates mean you can use Live with existing plug-ins under Catalina. Based on what plug-in developers tell me, though, you should still anticipate there may still be some issues to resolve with individual plug-ins if you upgarde, and DAW developers like Ableton may not be aware of all of these situations on internal testing alone.
Because of the number of changes to be made, Live 9 will not support Catalina. Conversely, as Apple deprecates older OSes, Live 10 won’t support some of the older versions of macOS. Here’s what will be compatible:
Live 9: macOS 10.7 – 10.13 officially supported; 10.14 unofficially supported
Live 10: macOS 10.11 – 10.15 supported (macOS 10.15 requires the Live 10.1.2 update for Catalina, minimum)
Ableton have also published a technical note. The headline is about Live 9, but it also includes useful resources for Live 10 users:
Compatibility with other software
Many developers CDM contacted were not yet ready to make an official statement on Catalina. Off the record, a significant number of developers reported problems.
Native Instruments published a blanket statement saying simply none of their products are compatible:
PreSonus has published a technical note explaining that you’ll need not only an update to their Studio One DAW, but also to most (or all) of your plug-ins, as illustrated above:
Studio One 4 on Mojave and Catalina – Notarization, Hardened Runtime, and how it affects 3rd-party plug-ins
Apple has not necessarily had full support for a new OS even for its own pro software; I’ve contacted Apple to ask if Logic Pro will support Catalina at launch but have not yet gotten a response. (There is a precedent of Apple’s own pro apps sometimes lagging their OS, before you make the assumption that they two will be in sync.)
How should you upgrade, and when?
Here’s a simple piece of advice: don’t update to Catalina immediately. As with any major OS change, music installers, drivers, and DAWs will benefit from more time and testing. Since musicians have complex and diverse setups, odds are you rely on something that won’t be immediately compatible, or that interactions between tools could create unexpected results.
If you do update, you should absolutely make a full backup so you can easily roll back. Time Machine backups can also provide some ability to remove OS updates.
You can also create an external installation of the OS on any drive that is formatted to macOS extended Journaled. It’s probably worth buying an inexpensive drive to test first, especially with an update this significant.
Macworld has two helpful articles (also linked by Ableton):
If you’re a developer and want to share your compatibility information, please get in touch.
The post macOS Catalina will be incompatible with much of your music software; here’s what to know appeared first on CDM Create Digital Music.
Published on Aug 28, 2019 LOOK MUM NO COMPUTER
“long before the #apple #macintosh. Making a song on a apple ii by using the dms drummer against its intended purpose! uh oh. #8bit weapon
more info on DMS can be found here :-
Downloads of the files aswell as other loops etc and even an extra video content of what else came with the apple ii is available over here
Logic Pro X 10.4.5, seen onstage at WWDC, is now available. And yes, it supports the new ultra-high-end Mac Pro – but there are fixes and performance optimizations for everyone, with or without new machines.
10.4.5 looks like the most pro-oriented Logic Pro in a long time. Apple has been aggressive with its update cadence for Logic for years running now, even with free upgrades, and this version is no exception.
This release also marks the end of the road for Mac OS X 10.12 Sierra. The new minimum OS requirement is 10.13.16 High Sierra. (Mojave is seeming stable these days, and it’s summertime, so maybe now is a good time to do a full backup and take the plunge.)
First up – yes, the banner feature from Apple’s perspective is that the new Logic runs on the new Mac Pro. Under the hood, that means support for up to 56 cores, the kind of massive multiprocessing the new Mac Pro can do.
The use case for this kind of processing power is slim, but then, that’s what the ‘pro’ concept is all about. Doing artist relations, you may have a film composer with advanced technical needs and a shelf full of Academy Awards. Even one user in your user base can be critical.
That said, I think the real story here is that Apple is shaking the tree across the whole code base – meaning these performance optimizations and fixes could benefit you even if you’re running on a beat-up older MacBook, too.
So, think really big track counts – which could be meaningful since even some mid-range CPUs can theoretically churn through a lot of tracks, to say nothing of that shiny Mac Pro tower.
Increased Number of Tracks and Channels, up to:
1000 stereo audio channel strips
1000 software instrument channel strips
1000 auxiliary channel strips
1000 external MIDI tracks
12 sends per channel strip
Way back around 2006, I heard from a Macworld reader complaining about lifting exactly these limitations and how I didn’t mention them in a review. (See above: that one user thing.)
There’s a bunch of other new features that are serious DAW improvements – and almost no mention mention of any fictional artificial drummers.
An all-new DeEsser 2 plug-in
16 ports of MIDI clock, MTC, and MMC from Logic – yeah, expect to see a Mac Pro in broadcast/film/TV applications running audio
Mixer configuration can be set to your own user-definable defaults (huge time saver there, finally)
A clever automatic duplicate erase when you’re merging MIDI recordings
And some new keyboard shortcuts to save you time when editing:
- Option + Shift while rubber-band selecting in the Piano Roll: new time Handles selection.
- Option-click track on/off button: loads/unloads the plug-ins on the channel strip (wow, easy A/B!)
- Shift-double-click Tracks background: start playback from that position.
And for the “I have an old beat-up MacBook you can pry out of my dead fingers” crowd – finally Freeze works the way it should. (How many of you were desperately freezing tracks while cursing Logic as the CPU meter refused to go down?) From the release notes:
“Freezing a track now unloads its plug-ins to free up resources.”
There are also fixes and performance optimizations and workflow and display improvements throughout. As you’d expect, fixes are concentrated on newer features – Smart Tempo, ARA, Flex, and the like.
So you don’t get any earth-shaking new features unless you’re really into de-essing, but what you do get is some evidence the Apple engineers are working through their log of stuff.
Logic Pro X 10.4 release notes (Apple support, 10.4.5 stuff is right up top)
Full disclosure: I will now this week refresh my MacBook Pro’s OS and then Logic release.
Hey, say what you will about Apple, but Logic Pro these days is pretty accessible from a user experience perspective. There’s some powerful and numerous competitors that either fail that ease of use test or that simply lack features you need to get big jobs done in scoring and the like. Maddeningly, a lot get the ease right but lack features, or have insanely powerful features but demand you contort your brain to use them. (Once upon a time, an earlier version of Logic was also far harder to use.)
I know from CDM’s own site stats and plenty of anecdotal evidence that all this matters to music makers. It’s not just Apple brand loyalty that makes Logic last.
The post Logic Pro X 10.4.5 is all about huge projects, with or without a Mac Pro appeared first on CDM Create Digital Music.