I've watched music production videos for many, many years and your channel is literally the best. No fluff, no gimmicks, clear and concise explanations, and great editing. Thank you for the quality content
Its really surprising to me that juggernaut companies like Native Instruments still doesnt have full native m1 support. I religiously use kontakt and komplete kontrol a LOT so im holding off on buying an m1 simply because of them. Totally agree with your rant about it. They should pull themselves together and make that happen rather than focusing on their new lame subscription businessmodel.
I'm thinking alot of their products have an old code base. They still haven't 100% adopted VST3 yet on Reaktor. I'm guessing they are trying to come up with a way of doing it in a unified way. I'm thinking some of their products, it probably isn't an easy task especially with products that haven't gotten any updates in years (FM8, Absynth) probably more because they ran into some type of roadblock or a critical developer left the company, or with Products that is on an old codebase (Reaktor, probably alot of other NI products as well). It's weird that now Arturia is starting to come across as a worthy competitor to NI when in the 2000s, I think NI was usually considered better and Arturia was even know to be a bit buggy back then. Arturia has managed to keep their codebase up to date and modernized. That said their product line isn't as diverse as NI which probably made it alot easier to standardize and roll with the punches of new technology. I think the bigger company can have more obstacles than a smaller company as they will have more random things to worry about which can make a muddier vision. That said on the flip side I think bigger companies often use that to their advantage in a sense as they are so big that they know that many users will hold off on updating newer technologies because the user will have so much invested in the big company so in a sense their adoption rate can somewhat slow the adoption rate down as other companies can follow suit. VST3 is one example where some DAW companies immediately got on board where it took some a few years and others like Ableton like 10 years (finally) and some like Reason still haven't fully adopted but I think if NI started supporting VST3s in like 2012 or something Ableton would have been more or less forced to implement at a faster rate. Its probably mostly a good thing though as I guess the biggest reason these things aren't getting adopted fast enough is bugs (or the fear of introducing new bugs or breaking something). Going to M1 or VST3 for some programs probably "break" a great deal of the code and a huge chunk of the program has to get rewritten (even though to the end user alot of the changes might be unnoticeable), which for some smaller programs this could be pretty easy but for larger programs, it can be a very hard task. That said though Im sure NI feels the heat as so many newer developers are adopting much faster and if they wait too long, some of these new developers will more or less start filling in the gap with new products of their own forcing NI's hand.
@@jsmacks11 Native Industries went crazy and it was their executives that even had to step down. It went from being the top dog with Google execs visiting them to being a jumbled mess of divisions just fending for themselves. I used to be a big NI fan years ago, even my setup used to be all NI with maschine, S25, KA6, S4 all hooked in a production dj thingbut their planned obsolescence is too aggressive, their tech support used to be a joke, Traktor wont even support stream up to recently with the other player already eating and crapping NI lunch, releasing a bunch of "cinematic" plugins instead of really creative stuff like Pigments... oh boy... so many things that company has done so wrong... I think their merge with iZotope was just their execs knowing nothing about how to compete with other companies like Arturia and Novation just getting way better and NI having failed to deliver a proper DAW and just taking maschine from a thing that made sense to a Wish copy of ABleton. I'm still keeping their stuff since I know them (well used to) inside out but the moment it doesnt get further support or break, I'm running away from NI as fast as possible.
Or Mac should stop making products that aren't compatible with software that everyone uses. I've bought older macs that aren't even compatible with their own softwares. Fuck Mac.
This was so helpful!!! I was going crazy not understanding why my plugins were showing up in Live 10 and not 11. It defaulted to the universal build for 11, but once I used the Intel version everything is showing up. Lifesaver!
Thanks soooo much for this video. I've recently upgraded my 2015 Mac Mini Intel to the 2021 Mac Mini M1 Silicon, and jumped right in on the Ableton 11.1 update to M1 Silicon. I did a cloud transfer from my old Mini to the new, then updated Ableton. Now, it's all about going thru all my plugins (80+) & solving their individual issues. At one point, the CPU meter for all individual tracks were showing 3 bars out of 6 bars on the meters on a completely new & empty project. I re-installed Ableton 11.1 again & that issue went away (hopefully for good). Can't wait to get it all back together again...
I've been on the beta for a while and native Ableton flies on the Macbook Pro M1!! Waiting for Native Instruments to go native, but at the pace they're going I can wait seated. Will try reinstalling everything with AU for the available ones. Thanks for breaking it down!!
yeah im SOOOO on the fence as to whether to wait until NI drops apple silicon native or to install the au right now. I'm trying to sit on my hands until then but who knows how long its going to be. It really is unacceptable how long this is taking but NI and Izotope are under 1 roof now hmmmmmmmmm.
@@SeedtoStage Yeah, I've been checking at their forums and trying to add some pressure too but there's no timeline given except "we're working on the native solution". I'll go with the AU for the moment so I can use native Ableton. It's just going to be a pain in the ass to reinstall everything XD
Great news, thanks for the advice. I'm still running Live 11.1 Suite on a 2012 MacBook Pro and am happy with the much snappier performance compared with before. Fewer glitches running M4L. Yes, some VST Plugins disappeared but (surprise, surprise) VST3 versions were available. Maybe my next production laptop will be M1?
Wow thank you! I just updated (on 2019 Mac intel) and all but two companies vst's were missing. Missed that Intel only download the first time around. 👍
I didn't know that AU's are still running under Rosetta 2 now. Good to know. They sure are running with a lot less RAM drain than my VSTs were under Rosetta 2 (previous 11 version).
I thought this might be the case, I was excited by your video about M1 but had reservations about plugins which I use a lot of (not playing Live as it were). Think I will sit on the fence and see where this goes, but some excellent VST aren't supported any more. Bit like the jump from 32 to 64. Your videos on this subject are super useful and well thought out, many thanks
Great video, Ableton lets you have vsts and au versions of plugins on daw at the same time. So if I'm hearing you right I would get best performance by using native vst plugins instead of au plugins. What's confusing is if I open a au plugin like the Diva synth it says arm64 which I think means its native. The vst version of Diva also says arm64. Also most Izotope plugins are now native but if you use an au version and go to options it still says silicone au meaning its native I think. So my real question is do you think some au versions of plugins are fully native and some are not? Also I use Logic Pro (native version) and it seems to only give me the choice of using au plugins.
For anyone moving to Apple Silicon, running Monterey...with an external ssd for your libraries, etc...make sure the external ssd is formatted to AFPS, not Apple Journaled.
The alternative is that Ableton needs to enable Live to run plugins in sandboxes. Bitwig does it already and can therefore support any type of plugin format while the DAW is running native Silicon code. But I doubt this is going to happen in the near future.
@@SeedtoStage it's an absolute miracle they were even able to transfer the code to Silicon 🤣 but we are still waiting for dials to support the scroll wheel... in 2022 and counting :)
What if I'm using Ableton 11 - not 11.1 but using an M1 pro chip. All my plug ins currently work in this format. Should I upgrade to 11.1? or will all my plug ins break?
Maybe A little off-topic, but could you go into how to approach making music with your improv sessions? Like it's just a jumbled mess of chords, what can I do with that?
Hey man, I figured you'd be the best person to ask. I recently bought teletone audio plugins, installed native access to run them and they still don't work. The plugins aren't silicon compatible. I wonder if you have any info on those particular plugins. Sorry to ask this way but I'm dying to use them hahaha
hey thanks for the info. i'm still a bit confused. i only use AU plugins (for many years). Are any AU plugins silicon native? Your post leaves me with the impression that all AU plugins have to use a Rosetta 2 wrapper. Surely this won't be the status quo going forward.....? thanks in advance for clarification
Hey i had the same thought! If i Run Ableton 11.1 native on Silicon and start a .au plugin will my mac start an instance of rosetta for every plugin i load? Thought the other way around: Does it only use 1 instance of Rosetta when i start ableton 11.1 via rosetta? Thx for help
just got M1 14 inch Mac book pro. Unfortunately, I'm stuck with Monterey OS which is kinda being buggy over with certain VSTs and Ableton. I had some odd fan issues where I had to download the fan control to stop from keep running. After hours of testing, it seems the Arturia plug ins (Pigment)and giving me odd spikes in CPU (like over 70-100). Its odd because Arturia made it M-1 compatible. The spikes go away once I minimize it to the back ground, which is odd. Other than that, all works great, but I am having weird issues with my Audio interface (minifuse which is a Arturia product). I think its time for me to move on to Focus rite. I got the minifuse for the extra USB but that thing is not working too well.
Or maybe they have to ramp up their revenue by using bold marketing in order to have the funds to pay for additional development. Is it hard or easy to convert software into Apple Silicon? Does it require a boat load of programer hours? Do programers work cheap?
Hey guys, so can someone confirm: if I'm currently using Ableton 11.0 with an M1 Pro chip and upgrade to 11.1, would I still be able to see and run all the same plugins I'm currently using on 11.0 (since they're all running through Rosetta)?
Thanks for the video as always great work and easy to understand! Still waiting for my macbook pro to arrive! Also, does anybody have any tips for people that are transitioning from windows to macos? thanks!
I have a new M1, coming from another Mac. My advice is to finish whatever projects you can on the old one and start new ones on the M1... Hardly brilliant and not always doable, but efficient.
I had Ableton 11 beta all dialed up on my M1. Now that I upgraded to Ableton 11.1, do I have to install all plugins again or is there a smooth way to transition?
Thanks! Great as always. Any tips on when Ableton usually goes on sale? I have Ableton 9 suite and I'd like to upgrade to 11, but I heard that it goes on sale periodically
Black Friday or whatever they were on sale last year. I asked the same question at that time and got responded to like I was some kind of idiot (on FB).
That's why I've ditched my NI Plugins and went to Arturia - even bigger companies getting away from Kontakt Sampler and think of an independent sample workstation (Spitfire). I mean, NI is ALWAYS behind with every new OSX Update and I'm tired of waiting for them. Goodbye NI...
Thanks for the quick breakdown. I only use the AU version of my plugins (no VST). Would you recommend I use the VST versions instead to maximize CPU usage?
well if youre on an apple silicon device, youre gonna want to use the silicon native vst versions if youre goal is to maximize both cpu and minimize potential crashes with rosetta.
@@rac06oon No. There is almost always no difference in efficiency between an AU and VST on the same processor architecture. The underlying plugin code is the same. It's just wrapped differently.
@@rac06oon Its only collaboration you’ll need to keep in mind. If you use AU plugins in a project and send it to someone using a Windows PC, then they can’t use them. They run the same, but compatibility is different :-)
cool, but i cant understand why this update is avalable to windows pc. I can download it, but im not if only MAC related :) OR if i spend time downloading just to find out it wont install due to my win11 machine..any1 on win11 that have tried? (yes i read the release notes)
I have had several problems rendering with 11.1. The rendering stops at about 90% and an alert message appears saying "Render aborted due to internal error". I've never had a problem with rendering before.
Thanks for the video! I'm currently using the beta version of Ableton 11, has the same compatibility with the Mac M1 processors as the last normal updated version of Ableton or are there some differences? Thanks
they seem identical at the moment but i imagine the beta will cease working here soon and ableton will quickly release another update to 11.1 once all the grievances come flooding in due to it simply being new.
In a way though this conversation really highlights the value behind universality and is a slight negative to apple. If a company is going to insist on remaining so vastly not inter compatible perhaps the burden of bridging that gap between itself and the rest of the developing world should be on its own shoulders. Yet again as a developer you would want to make sure your software was highly compatible to make sure your audience was as broad as possible like backwards compatibility. Ah the paradox of choice
I personally think FL studio and Ableton Live are doing it best. Both can run in either silicon native or intel audio units via rosetta. Any other solution for apple silicon at this moment in time is less compatible.
@@SeedtoStage FL Studio, Ableton Live, Logic Pro, Studio One, and others can all run Intel AUs via Rosetta2 while the host is running natively. This is because they all use Apple's provided AU Hosting Service, which does the bridging for them. Bitwig can run Intel VSTs via Rosetta2, because the DAW and the plugin host are separate processes which communicate via local network sockets.
I think the information in this video about Audio Units is either not correct or perhaps inadvertantly misleading. You show "Ableton Devices + VSTs + Audio Units = Silicon + Rosetta", which would be true for Intel versions of AUs, but AUs can also be Apple native. For example, the Arturia V Collection instruments and Pigments AUs, clearly show "arm64" for me.
Defnitely not misleading. This is how Ableton 11.1 universal handles plugins. "When used on an Apple Silicon computer, the Universal build of Live 11.1 only recognizes VST2 and VST3 plug-ins natively compiled for Apple Silicon. However, many Intel-based Audio Unit plug-ins will display and load, thanks to the macOS feature AUHostingCompatibilityService." help.ableton.com/hc/en-us/articles/4410323149074
ARM versions of AU plugins already exist - e.g. Arturia V Collection synths are available now as "arm64" versions. The difference between AU and VST is that an arm64 application can host intel versions of AUs (via a Rosetta 2 layer), but cannot run intel versio of VSTs. In order to run an intel VST on an M1, you need to use the intel version of the host application.
@@CitizenOfEverywhere alright thanks for the clarification I was just confused by the list at 1:30 since it didn’t include the case “only Ableton devices + supported AU Plugins = Fully Silicon Native”
Great video just have 2c I'm not sure what your development background is, but I personally try not be overly surprised that big companies with massive product lines - some including legacy products - are struggling to get Apple Silicon versions out. With big companies they need to go through a beta testing phase and everything, otherwise they'll be flooded with support tickets (which they can barely handle as-is). I think it's okay to keep inquiring, but also to try to see both sides. This is mostly Apple's fault for introducing new hoops to jump through, although Rosetta is good enough for most, but let's not bully companies for not blindly jumping when Apple says jump. It's not always in a companies best interest to immediately drop everything they're doing, and zero companies have extra teams of programmers just sitting around waiting for stuff to do, just so users have some extra CPU which they probably don't need anyway.
M1 has been the worst cmputer i've ever worked on, have lost so many projects, horrible sound pops and feedbacks, an ongoing nightmare . And to think I actually paid for this crap.
Guys - forget 'Silicone support' and focus on this for a minute: GPU AUDIO is coming to APPLE! What? Go check this out! m.ruclips.net/video/IFdgymosszA/видео.html
It's much worse. Have you tried using Ableton on an M1 Pro or higher at 96kHz on Ableton 11 Native? Many third party plugins that need Rosetta 2 won't multithread, so you can't chain a load of them on one track before the 3.2 GHz "performance core" craps out. I'm getting perhaps a 20% gain over my 2019 i9 MBP on my M1 Ultra, whilst others won't even load and run at 2048 buffer! WTF? I bought the Ultra to run Ableton at 96kHz as I use a lot of IR based plugins that sound a lot better at 96kHz. But can Ableton 11 native manage these R2 plugins? Nope! Just one Acustica plugin used over 25% of Ableton's CPU whilst the cores themselves are doing nothing. Total multithread fail. But put it into Rosetta 2 mode, and suddenly it's way better. as Ableton is now multithreading plugins. This means Native Ableton 11 isn't close to being ready yet and plugin makers are lying when they say their plugs are Apple Silicon ready. Either Ableton native can't handle using Rosetta 2 plugins and native ones at the same time or many plugin makers haven't bothered multithreading their M1 plugs (But did for Intel/AMD). Nice work Ableton and plugin makers, who saw for decades that M1 multicore was the future and didn't code their plugins to use more than one thread.
Mud, mud, glorious mud.....I just want to write some tunes. FFS why do I have to bother with all this technocrap? Sick of upgrades, this don't work with that, that don't work with this, so you need mount washington 15.095 latest OS BS. What a mess. Sick with what you got, if it ain't broke, don't fix it.
I've watched music production videos for many, many years and your channel is literally the best. No fluff, no gimmicks, clear and concise explanations, and great editing. Thank you for the quality content
My favorite part is the last bit where you drop hard truth about these companies lack of M1 support. Good stuff as always. Thanks dude.
Its really surprising to me that juggernaut companies like Native Instruments still doesnt have full native m1 support. I religiously use kontakt and komplete kontrol a LOT so im holding off on buying an m1 simply because of them. Totally agree with your rant about it. They should pull themselves together and make that happen rather than focusing on their new lame subscription businessmodel.
I'm thinking alot of their products have an old code base. They still haven't 100% adopted VST3 yet on Reaktor. I'm guessing they are trying to come up with a way of doing it in a unified way. I'm thinking some of their products, it probably isn't an easy task especially with products that haven't gotten any updates in years (FM8, Absynth) probably more because they ran into some type of roadblock or a critical developer left the company, or with Products that is on an old codebase (Reaktor, probably alot of other NI products as well).
It's weird that now Arturia is starting to come across as a worthy competitor to NI when in the 2000s, I think NI was usually considered better and Arturia was even know to be a bit buggy back then. Arturia has managed to keep their codebase up to date and modernized. That said their product line isn't as diverse as NI which probably made it alot easier to standardize and roll with the punches of new technology.
I think the bigger company can have more obstacles than a smaller company as they will have more random things to worry about which can make a muddier vision.
That said on the flip side I think bigger companies often use that to their advantage in a sense as they are so big that they know that many users will hold off on updating newer technologies because the user will have so much invested in the big company so in a sense their adoption rate can somewhat slow the adoption rate down as other companies can follow suit. VST3 is one example where some DAW companies immediately got on board where it took some a few years and others like Ableton like 10 years (finally) and some like Reason still haven't fully adopted but I think if NI started supporting VST3s in like 2012 or something Ableton would have been more or less forced to implement at a faster rate. Its probably mostly a good thing though as I guess the biggest reason these things aren't getting adopted fast enough is bugs (or the fear of introducing new bugs or breaking something). Going to M1 or VST3 for some programs probably "break" a great deal of the code and a huge chunk of the program has to get rewritten (even though to the end user alot of the changes might be unnoticeable), which for some smaller programs this could be pretty easy but for larger programs, it can be a very hard task.
That said though Im sure NI feels the heat as so many newer developers are adopting much faster and if they wait too long, some of these new developers will more or less start filling in the gap with new products of their own forcing NI's hand.
@@jsmacks11 Native Industries went crazy and it was their executives that even had to step down. It went from being the top dog with Google execs visiting them to being a jumbled mess of divisions just fending for themselves. I used to be a big NI fan years ago, even my setup used to be all NI with maschine, S25, KA6, S4 all hooked in a production dj thingbut their planned obsolescence is too aggressive, their tech support used to be a joke, Traktor wont even support stream up to recently with the other player already eating and crapping NI lunch, releasing a bunch of "cinematic" plugins instead of really creative stuff like Pigments... oh boy... so many things that company has done so wrong... I think their merge with iZotope was just their execs knowing nothing about how to compete with other companies like Arturia and Novation just getting way better and NI having failed to deliver a proper DAW and just taking maschine from a thing that made sense to a Wish copy of ABleton. I'm still keeping their stuff since I know them (well used to) inside out but the moment it doesnt get further support or break, I'm running away from NI as fast as possible.
Or Mac should stop making products that aren't compatible with software that everyone uses. I've bought older macs that aren't even compatible with their own softwares. Fuck Mac.
This was so helpful!!! I was going crazy not understanding why my plugins were showing up in Live 10 and not 11. It defaulted to the universal build for 11, but once I used the Intel version everything is showing up. Lifesaver!
im running Windows 11 and 50%+ of my plugins have disappeared after updating to Live 11.1
Thanks soooo much for this video. I've recently upgraded my 2015 Mac Mini Intel to the 2021 Mac Mini M1 Silicon, and jumped right in on the Ableton 11.1 update to M1 Silicon. I did a cloud transfer from my old Mini to the new, then updated Ableton. Now, it's all about going thru all my plugins (80+) & solving their individual issues. At one point, the CPU meter for all individual tracks were showing 3 bars out of 6 bars on the meters on a completely new & empty project. I re-installed Ableton 11.1 again & that issue went away (hopefully for good). Can't wait to get it all back together again...
I've been on the beta for a while and native Ableton flies on the Macbook Pro M1!! Waiting for Native Instruments to go native, but at the pace they're going I can wait seated. Will try reinstalling everything with AU for the available ones. Thanks for breaking it down!!
yeah im SOOOO on the fence as to whether to wait until NI drops apple silicon native or to install the au right now. I'm trying to sit on my hands until then but who knows how long its going to be. It really is unacceptable how long this is taking but NI and Izotope are under 1 roof now hmmmmmmmmm.
@@SeedtoStage Yeah, I've been checking at their forums and trying to add some pressure too but there's no timeline given except "we're working on the native solution". I'll go with the AU for the moment so I can use native Ableton. It's just going to be a pain in the ass to reinstall everything XD
ya I've also been on the beta! It's for sure better but I really miss my Izotope and waves plugins!
The best video by far I found on this issue! Thanks for the quality information on this topic.
Great news, thanks for the advice. I'm still running Live 11.1 Suite on a 2012 MacBook Pro and am happy with the much snappier performance compared with before. Fewer glitches running M4L. Yes, some VST Plugins disappeared but (surprise, surprise) VST3 versions were available. Maybe my next production laptop will be M1?
Can't wait for your ableton 11.1 walk through.
Don't forget U-he. They updated several of their synths, including Hive 2 and Diva, to run natively on the M1.
Wow thank you! I just updated (on 2019 Mac intel) and all but two companies vst's were missing. Missed that Intel only download the first time around. 👍
Can you add a link to the KVR forum you referenced to find out what is native and what is not? Thanks, great video!
I didn't know that AU's are still running under Rosetta 2 now. Good to know. They sure are running with a lot less RAM drain than my VSTs were under Rosetta 2 (previous 11 version).
I thought this might be the case, I was excited by your video about M1 but had reservations about plugins which I use a lot of (not playing Live as it were). Think I will sit on the fence and see where this goes, but some excellent VST aren't supported any more. Bit like the jump from 32 to 64. Your videos on this subject are super useful and well thought out, many thanks
Great video, Ableton lets you have vsts and au versions of plugins on daw at the same time. So if I'm hearing you right I would get best performance by using native vst plugins instead of au plugins. What's confusing is if I open a au plugin like the Diva synth it says arm64 which I think means its native. The vst version of Diva also says arm64. Also most Izotope plugins are now native but if you use an au version and go to options it still says silicone au meaning its native I think. So my real question is do you think some au versions of plugins are fully native and some are not?
Also I use Logic Pro (native version) and it seems to only give me the choice of using au plugins.
For anyone moving to Apple Silicon, running Monterey...with an external ssd for your libraries, etc...make sure the external ssd is formatted to AFPS, not Apple Journaled.
The alternative is that Ableton needs to enable Live to run plugins in sandboxes. Bitwig does it already and can therefore support any type of plugin format while the DAW is running native Silicon code. But I doubt this is going to happen in the near future.
i would love that. Totally agree. I wonder if it is even possible to do that with Ableton's legacy code.
@@SeedtoStage it's an absolute miracle they were even able to transfer the code to Silicon 🤣 but we are still waiting for dials to support the scroll wheel... in 2022 and counting :)
I would consider doing a nice clean install and check the native plug ins one by one
so you're saying whenever you use AU they are non silicon native? Do AUs only run in Rosetta? What about native AU's?
Those damn CEO's and Suits!!
well I’m staying on ableton 10 until they figure it out I’m ready to upgrade though
Hey so I'm using Ableton 11.1 for windows but non of the new devices are showing (shifter and the align device). Do you know what is going on here?
What if I'm using Ableton 11 - not 11.1 but using an M1 pro chip. All my plug ins currently work in this format. Should I upgrade to 11.1? or will all my plug ins break?
Having done this on Apple products from 68k to PPC, from PPC to Intel, and now Intel to Silicon... it takes four years every time... four years.
Maybe A little off-topic, but could you go into how to approach making music with your improv sessions? Like it's just a jumbled mess of chords, what can I do with that?
thanks so much for the clarification and the rant is 100% justified
Plugin Alliance m1 native , is dropping in march ..🙏🎵✨
Thank you for this video, really helpful!
very informative. maybe ill get an apple silicon mac next year...
thank you for this. I thought I was not going to be able to use VCV Rack
Hey man, I figured you'd be the best person to ask. I recently bought teletone audio plugins, installed native access to run them and they still don't work. The plugins aren't silicon compatible. I wonder if you have any info on those particular plugins. Sorry to ask this way but I'm dying to use them hahaha
I am here after upgrading to Mac Studio Ultra on Monterey and seeing missing plugins. I totally overlooked that the Mac would ship with Monterey ;-/
omg thank you for making this video!!!
hey thanks for the info. i'm still a bit confused. i only use AU plugins (for many years). Are any AU plugins silicon native? Your post leaves me with the impression that all AU plugins have to use a Rosetta 2 wrapper. Surely this won't be the status quo going forward.....? thanks in advance for clarification
Hey i had the same thought! If i Run Ableton 11.1 native on Silicon and start a .au plugin will my mac start an instance of rosetta for every plugin i load? Thought the other way around: Does it only use 1 instance of Rosetta when i start ableton 11.1 via rosetta? Thx for help
Any tips on moving plugins from 1 computer to another?
I think it's time for a studio tour :)
just got M1 14 inch Mac book pro. Unfortunately, I'm stuck with Monterey OS which is kinda being buggy over with certain VSTs and Ableton. I had some odd fan issues where I had to download the fan control to stop from keep running. After hours of testing, it seems the Arturia plug ins (Pigment)and giving me odd spikes in CPU (like over 70-100). Its odd because Arturia made it M-1 compatible. The spikes go away once I minimize it to the back ground, which is odd. Other than that, all works great, but I am having weird issues with my Audio interface (minifuse which is a Arturia product). I think its time for me to move on to Focus rite. I got the minifuse for the extra USB but that thing is not working too well.
Thanks man, well explained
Great vid, subbed
Cool tutorial as always ! Keep doing your great work :) Many thanks
11.3 and it still doesn't actually properly support the new silicon macs - it doesnt utlise the right threads and a lot of people are talking about it
My AUs are crashing out 5-10 times a day on M2 Air. Any idea how to fix it...?
M1 updates are slow but any M1 news is good news
Or maybe they have to ramp up their revenue by using bold marketing in order to have the funds to pay for additional development. Is it hard or easy to convert software into Apple Silicon? Does it require a boat load of programer hours? Do programers work cheap?
Feeling chaotic with the plugin stuff and Apple silicon, is like doing the same in Linux. Hopefully with this pressure we can have more order again.
Hey guys, so can someone confirm: if I'm currently using Ableton 11.0 with an M1 Pro chip and upgrade to 11.1, would I still be able to see and run all the same plugins I'm currently using on 11.0 (since they're all running through Rosetta)?
2:47. Run ableton in Rosetta mode.
Looooool ableton. I can't find my FabFilters or OTT now 🤣😅
I was hoping you’d be a PC guy so you could tell us whether or not to upgrade to Windows 11.
my official advice is to switch to apple silicon haha
@@SeedtoStage So you say Macbook Air is totally enough, probably even with 8gb ram.
Thanks for the video as always great work and easy to understand!
Still waiting for my macbook pro to arrive!
Also, does anybody have any tips for people that are transitioning from windows to macos?
thanks!
I have a new M1, coming from another Mac. My advice is to finish whatever projects you can on the old one and start new ones on the M1... Hardly brilliant and not always doable, but efficient.
@@velosobruno well,glad that that was my plan all along
what im so confused..... so none of the plugins i just bought wont work???? dafuq!!!!!
I had Ableton 11 beta all dialed up on my M1. Now that I upgraded to Ableton 11.1, do I have to install all plugins again or is there a smooth way to transition?
What’s the best approach to this upgrade if you don’t have M1 machine? I don’t feel like jumping through a lot of hoops right now, if I don’t have to.
yeah just don’t worry about it the hardware already works for the old plugins :)
maybe Ableton will introduce a VST2 rosetta bridge for the unsupported plugins. Like in Bitwig....
Thanks! Great as always. Any tips on when Ableton usually goes on sale? I have Ableton 9 suite and I'd like to upgrade to 11, but I heard that it goes on sale periodically
Log into your account. You’ll probably get a pretty decent discount since you have a version of ableton. I got a good discount from having live lite
Black Friday or whatever they were on sale last year. I asked the same question at that time and got responded to like I was some kind of idiot (on FB).
Thanks
Ableton usually offers a 25% sale on Live (including upgrades from older versions) during the Black Friday / Cyber Monday weekend.
They're on sale on black fridays
Wait...so to use a Silicon Native plugins I need to use VST or VST3? Thank you for the info !
Yep, its all right here too: help.ableton.com/hc/en-us/articles/4410323149074
No, that's not correct. You can use native AUs, and even mix them with Intel AUs.
@@mwdiers Thanks !
@@SeedtoStage Thanks for the article !
Great video. Thanks!
That's why I've ditched my NI Plugins and went to Arturia - even bigger companies getting away from Kontakt Sampler and think of an independent sample workstation (Spitfire). I mean, NI is ALWAYS behind with every new OSX Update and I'm tired of waiting for them. Goodbye NI...
So I still run a MacBook intel based. When I update to 11.1 I obviously have to choose the (MacOS intel only) path not the universal one, right?
That's right!
Very well said 🙏
Thanks for the quick breakdown. I only use the AU version of my plugins (no VST). Would you recommend I use the VST versions instead to maximize CPU usage?
well if youre on an apple silicon device, youre gonna want to use the silicon native vst versions if youre goal is to maximize both cpu and minimize potential crashes with rosetta.
@@SeedtoStage what about on an intel machine? actually what about if someone use the au versions instead of the vst ones? does affect that anything?
@@rac06oon No. There is almost always no difference in efficiency between an AU and VST on the same processor architecture. The underlying plugin code is the same. It's just wrapped differently.
@@mwdiers Thank you very much!!!
@@rac06oon Its only collaboration you’ll need to keep in mind. If you use AU plugins in a project and send it to someone using a Windows PC, then they can’t use them. They run the same, but compatibility is different :-)
cool, but i cant understand why this update is avalable to windows pc. I can download it, but im not if only MAC related :)
OR if i spend time downloading just to find out it wont install due to my win11 machine..any1 on win11 that have tried?
(yes i read the release notes)
I have had several problems rendering with 11.1. The rendering stops at about 90% and an alert message appears saying "Render aborted due to internal error". I've never had a problem with rendering before.
as with any new release, there are going to be growing pains. I usually keep legacy builds of live on my computer when working with a new version.
Thanks for the video! I'm currently using the beta version of Ableton 11, has the same compatibility with the Mac M1 processors as the last normal updated version of Ableton or are there some differences? Thanks
they seem identical at the moment but i imagine the beta will cease working here soon and ableton will quickly release another update to 11.1 once all the grievances come flooding in due to it simply being new.
@@SeedtoStage ok thanks!
Thank you......🤘
In a way though this conversation really highlights the value behind universality and is a slight negative to apple. If a company is going to insist on remaining so vastly not inter compatible perhaps the burden of bridging that gap between itself and the rest of the developing world should be on its own shoulders. Yet again as a developer you would want to make sure your software was highly compatible to make sure your audience was as broad as possible like backwards compatibility. Ah the paradox of choice
I personally think FL studio and Ableton Live are doing it best. Both can run in either silicon native or intel audio units via rosetta. Any other solution for apple silicon at this moment in time is less compatible.
@@SeedtoStage FL Studio, Ableton Live, Logic Pro, Studio One, and others can all run Intel AUs via Rosetta2 while the host is running natively. This is because they all use Apple's provided AU Hosting Service, which does the bridging for them.
Bitwig can run Intel VSTs via Rosetta2, because the DAW and the plugin host are separate processes which communicate via local network sockets.
I think the information in this video about Audio Units is either not correct or perhaps inadvertantly misleading. You show "Ableton Devices + VSTs + Audio Units = Silicon + Rosetta", which would be true for Intel versions of AUs, but AUs can also be Apple native. For example, the Arturia V Collection instruments and Pigments AUs, clearly show "arm64" for me.
Defnitely not misleading. This is how Ableton 11.1 universal handles plugins. "When used on an Apple Silicon computer, the Universal build of Live 11.1 only recognizes VST2 and VST3 plug-ins natively compiled for Apple Silicon. However, many Intel-based Audio Unit plug-ins will display and load, thanks to the macOS feature AUHostingCompatibilityService." help.ableton.com/hc/en-us/articles/4410323149074
So are AU Plugins dead now?
Or are there ARM versions of AU coming in the future?
Or do the AU versions of visible VSTs also support Apple Silicon?
ARM versions of AU plugins already exist - e.g. Arturia V Collection synths are available now as "arm64" versions. The difference between AU and VST is that an arm64 application can host intel versions of AUs (via a Rosetta 2 layer), but cannot run intel versio of VSTs. In order to run an intel VST on an M1, you need to use the intel version of the host application.
@@CitizenOfEverywhere alright thanks for the clarification
I was just confused by the list at 1:30 since it didn’t include the case “only Ableton devices + supported AU Plugins = Fully Silicon Native”
What a silly-con :P
Great video just have 2c
I'm not sure what your development background is, but I personally try not be overly surprised that big companies with massive product lines - some including legacy products - are struggling to get Apple Silicon versions out. With big companies they need to go through a beta testing phase and everything, otherwise they'll be flooded with support tickets (which they can barely handle as-is). I think it's okay to keep inquiring, but also to try to see both sides.
This is mostly Apple's fault for introducing new hoops to jump through, although Rosetta is good enough for most, but let's not bully companies for not blindly jumping when Apple says jump. It's not always in a companies best interest to immediately drop everything they're doing, and zero companies have extra teams of programmers just sitting around waiting for stuff to do, just so users have some extra CPU which they probably don't need anyway.
How many people already use a M1? maybe 1% of the ableton users...... so just wait for the plugin updates
M1 has been the worst cmputer i've ever worked on, have lost so many projects, horrible sound pops and feedbacks, an ongoing nightmare . And to think I actually paid for this crap.
Guys - forget 'Silicone support' and focus on this for a minute: GPU AUDIO is coming to APPLE!
What?
Go check this out! m.ruclips.net/video/IFdgymosszA/видео.html
Or the devs will never release an AU or Silicon version 🙃
they won't spend huge amount of resources to develop new versions for the 2 or 3 users that have the M processor
come on Native move your asssss!!!!
Apple ecosystem is a nightamare for developers to support. Even simple os updates brake their compability. On windows it just works.
With more peoples like you speaking out the thru in RUclips maybe a company like Native Instrument will update to M1 and stop chassing money. Thanks
It's much worse. Have you tried using Ableton on an M1 Pro or higher at 96kHz on Ableton 11 Native? Many third party plugins that need Rosetta 2 won't multithread, so you can't chain a load of them on one track before the 3.2 GHz "performance core" craps out. I'm getting perhaps a 20% gain over my 2019 i9 MBP on my M1 Ultra, whilst others won't even load and run at 2048 buffer! WTF?
I bought the Ultra to run Ableton at 96kHz as I use a lot of IR based plugins that sound a lot better at 96kHz. But can Ableton 11 native manage these R2 plugins? Nope! Just one Acustica plugin used over 25% of Ableton's CPU whilst the cores themselves are doing nothing. Total multithread fail. But put it into Rosetta 2 mode, and suddenly it's way better. as Ableton is now multithreading plugins. This means Native Ableton 11 isn't close to being ready yet and plugin makers are lying when they say their plugs are Apple Silicon ready. Either Ableton native can't handle using Rosetta 2 plugins and native ones at the same time or many plugin makers haven't bothered multithreading their M1 plugs (But did for Intel/AMD). Nice work Ableton and plugin makers, who saw for decades that M1 multicore was the future and didn't code their plugins to use more than one thread.
This is frustrating....
( seedtostage )
rip guitar rig :/
check your Audio units?
Mud, mud, glorious mud.....I just want to write some tunes. FFS why do I have to bother with all this technocrap? Sick of upgrades, this don't work with that, that don't work with this, so you need mount washington 15.095 latest OS BS. What a mess. Sick with what you got, if it ain't broke, don't fix it.
No one is forcing you to upgrade. You do you.
Waaaaayyyyyyyy too confusing!
Izotope is a definitely a greedy company. Never gonna use any of their plugins no matter what new product they are gonna release in the future!
what a joke