Ive a feeling this is going to be a big change. look at EigenD, work out how this moves forward.Įigenharp info only from here … EigenD native/arm.Then start looking at native (arm) builds Where next? short term plans The general idea is I first want to ensure that I can build and run my projects under Rosetta (so Intel). Then I need to start looking at specific projects of mine. This is kind of where Im at, Ive still a bit to figure out on the development environment, but its looking promising. With this started to take my first steps into both compiling for ARM and Intel on the M1. worked out how to get homebrew working, so that I could install cmake. So the soundplane ‘issue’ started to lead me into step 2, setting up a dev environment. Ok, this is not a big deal, and I kind of expected it… and I know Randy will look into it.Īlso, its open source, so I can dig in to … step 2 - development My first fail, basically its application crashes. So, I was very impressed by this point - I had expected niggles, some oddities, but it did just seem to work.Īt this point, I moved onto areas I expected problems…low level hardware integration. imagine building a track on the go on your ipad, then coming back to the studio, running the same app on your mac… but sync’ing it to your daw, and feeding its audio/midi into your daw to develop the track… in concept I did this yesterday ! This could be a really interesting feature in the futureĮ.g. IOS apps - ok these are a bit disappointing, as many iOS developers have withdrawn the right to use on macOS … perhaps they want to test etc.īut for the ones I could get… I could get midi integration, audio integration (via loopback) and ableton link sync. (its great for routing audio around apps) One amazing thing… I installed Loopback, which they have a public beta for the M1, this also worked a treat. VCVRack, seems fine… looking forward to trying some ‘heavy patches’ on it. (k, this was software iLok, I need to check the hardware dongle for cubase, but Im still on cubase 7, not sure if I want to install!) UVI Falcon… hah, this uses iLok bound to fail - nope works U-he, Madrona Labs, Vahalla plugs … boring, they work too Then tested audio interfaces … I use a Percussa SSP and Zoomo H5 - again fine ! I then tested midi connectivity, using my mioXM … for both midi input (keyboard) and clock sync - again 100% ok ! Installed Logic, Final Cut Pro (for youtube videos), Bitwig Studio, Ableton Live 11 (beta)Īll worked fine including the Push 2 for Live and Bitwig !Īnd indeed, as per reviews, it all feels very snappy regardless of using Rosetta or not. Step 3) looking at migrating various software to arm step 1 - music computer Step 2) set up dev environement to build both arm and intel builds Step 1) set it up as a computer for music I plan to make some videos on the M1 and how usable it is… but thought id blog some details here, also if you have any questions of things you wnat me to try - ask away. That said, I desparately needed a new mac for both development and music. Though I still thing this mac mini format is very attractive considering price etc. I think generally, most are wise to wait a bit… this is going to end up being the ‘base model’ we can expect faster/more powerful mac book pros and iMac, mac pro next year. You’ve likely seen review videos etc already, so you won’t be surprised to hear its fast.īut what I want to know is it useable today… or do we need to wait for things to settle down a bit, for developers to ‘make the transition’. I know quite a few of us here are mac users, so thought I’d share my experiences, and plans…
0 Comments
Leave a Reply. |