Rodney

Waves V12.7 plugins work in my set up with an M1 Mac mini, Big Sur 11.3.1. However, I did have to pay £140 to upgrade. Version 12.7 is not considered native but they do work when running Logic natively.

Abbey Road Saturation

I am running an M1 Mac Mini with Big Sur 11.3.1 with Logic Pro 10.6.2. I have all of my plugins working within Logic under Native M1 mode. But in order to do this I had to open Logic Pro X in Rosetta first. I then unticked opening Logic in Rosetta and went back in native M1 mode. You might be surprised that all of the following plugins and VSTs work in Logic whilst running natively in M1, but the intel based additions are opened in an AU wrapper. The audio plugins and VSTs that I am using within Logic Native M1 are: Fabfilter (Native) Ample Sound (Intel) Native Instruments (Intel) - Joshua Bell Violin - Kinetic Toys - Monark - Scarbee Mk I - Scarbee Rickenbacker Bass - Symphony Series Complete Collection - Una Corda EastWest (Intel) -Pianos Synthogy Uprights II (Intel) Copied samples from old hard drive. Toontrack (Intel) - Superior Drummer 3 UVI (Intel) - Italian Keys Waves V12.7 -Too many to list 100+ Note - Avoid StudioRack at the moment IKMultimedia -TRacks (Intel) Sonarworks (Intel) -Ref4 Izotope (Intel) -RX7 Hope this helps anyone transitioning onto the new M1 system. Remember open Logic in Rosetta first and then go back to native. Kind Regards Rodney

Hi edurbrow, Beat mapping can be incredibly frustrating but I am sure you know how important it is when creating an authentic song without the sterile clinical metronomic beat. When I beat map, I only do it on one track. That track also needs to be around -12db for transients to be picked up by the software. My first track is normally an acoustic guitar so I have to run the signal very hot and end up having to turn my monitoring down. Another way to beat map effectively is to finger tap the beat onto it’s own track and beat map that. Once everything is aligned that track can always be turned down or muted. There are also a few features in beatmapping such as auto align to bars, beats, 1/8s etc. This can come in handy sometimes. However, most of the time I beatmap manually, especially when there is a time signature change. Good luck Rodney

Hey Nath, I will be going down the M1 path shortly and I am eagerly waiting to see what tomorrows Apple Spring Event 2021 will yield. However, the software companies in particular appear to be dragging their heels in regard to making their products compatible with M1 native silicon. In particular, I am hoping that Waves, Native Instruments and Toontrack SD3 get native support. Regards Rodney

If it were me I would buy a new M1 Chip Apple device. Either the Air, MacBook Pro or the Mac Mini. If I were not able to afford it right now, I would keep saving my money until I could. These are next generation devices that are 3x more efficient than anything the comes before. They also match the performance of devices that cost more than twice the price. Regards Rodney

I think I understand.... So I could assign four buttons to no mode (modeless) under the Zone of my controller (nanoKontrol2). Of those four buttons two could be assigned to moving one mode at a time up and down at a time. The other two buttons would change modes with a greater value of 9.00 to move ten modes at a time. Regards Rodney

Hi Des99, I am looking at my navigation scheme now and I am able to create modes (pages) and move up and down the modes with two controller buttons. This has been somewhat of a revelation. However... Now that I can scroll between modes easily, I am trying to find out how to scroll between Zones. Perhaps my thinking is off but this is my general view of how I want to set up my controller If I treat Zones as if they are chapters in a book for example Editors, Faders, Synths, Midi FX, Channel Strips, EQ, Compressors etc And the Modes of each Zone (the pages of these chapters) for example (Zone) Editor (Modes) Audio Editor, Piano Roll, Step Editor, Score Editor etc Then I could navigation my whole system with four buttons. Two for Zones, Up and Down and two for Modes, Up and Down. This would make navigation extremely quick and efficient. I have managed to set the Up and Down buttons to navigated the Modes. What I am struggling with is how to use the Controller to navigate the Zones. Is this possible? Kind regards Rodney

Brilliant! This is the kind of stuff I really want to get to grips with. I will have to read a bit more of the Logic Pro X manual now that I have gained a bit more insight into these functions. Do you know of any online classes that teach these types of midi functions? Preferably video. Kind regards Rodney

Hi Des99, After a few more days of midi mapping plug-ins, I have found that when mapping on/off buttons, Lo7 is the way to go. If a parameter in the plug-in is an on state, Lo7 gets an instant reaction. Whereas, if a button is assigned 00 (0), or 7F (127) it has a chance of temporarily being mismatched to the plugin parameter. For example if a plug-in filter is on, and I want to turn it off a values of 7F (127) will give a redundant message. Lo7 appears to be working the best with toggle on/off parameters with no redundant state switching. Regards Rodney

Ok! I stand corrected : )

Big Sur is running your software in translation mode through Rosetta 2. Basically pre Big Sur software is considered legacy. Although it will probably run the same or faster on current hardware, it’s real purpose is to run on M1 chips. On Big Sur Logic will run in either of two modes, native for M1 chips or in translation under Rosetta 2 for intel chips. Expect to see a three fold increase (x3) for Logic running natively under the M1 chip.

Hi Des99 I am getting to grips with how the full set up is going to work, however there is one extra thing that I would like to know before I get started. The value input message for example B9 50 7F is what I am trying to decipher. Especially the last two digits which appear to vary. B9 is channel ten 50 is midi cc info 7F ? I don’t know This also varies between three different values 7F, 00 and Lo7. I am assuming that 7F is on 00 is off Lo7 low bit info? as opposed to Hi7 Would you be able to clarify this for me as I will probably type these values in relation to the controller? I think that knowing the difference between 00, 7F and Lo7 will help me to remove any bugs that may appear. Kind regards Rodney

Hi Des99, Thank you for the foresight. With that in mind, I think I will attempt to reassign some of the additional transport controls such as Cycle, Track and Marker selection buttons to bank or modifier buttons. Along with the eight solo buttons as the main means of mode selection I could put the into some sort of category. ‘Solo’ buttons for EQs, ‘Track + Solo’ for Compressors, ‘Track - Solo’ for Reverbs etc. By using the additional transport controls as modifiers then I could get up to 56 controller patches for plugins. I am not going to rush into this as the schemata might change and once I have started, I really don’t want to go back to the beginning again. Kind regards Rodney

Looking over the thread that you linked to it appears that the number of mapped plugins are limited to the number of physical mode changing buttons on a midi controller. Is it possible to have two buttons on a midi controller that move up and down through a list of mapped plug ins? Thus not limiting the number of plugins that could potentially be mapped. Kind regards Rodney