![]() It has nothing to do with the VST to MAS plug in, it's very obviously native.ĭP running in Rosetta can run non native VSTs etc. I run plenty of native VSTs in native DP11. In order to use VST2 plugins you need the wrapper and in order to use the wrapper DP must itself be running in Rosetta. I believe the issue is that DP’s “VST2 to MAS Wrapper” is not AS native (and maybe can’t be). If a non AS native plug-in is AU format it will use Rosetta as needed without DP itself running under Rosetta. I believe it only applies to VST2 plugins. But, this doesn’t apply to all non AS native plugins. Not all that excited about going the VEP route, but it is a fallback position that is good to know can work.įirstly, to answer your question, DP must be in Rosetta to both scan and use the plugins in question. I'll spend the required time when Apple Silicon makes its entrance at Rancho Bohemia.īut I'll be keeping my 5,1 around for sure. DP11 on a fresh install of Mojave didn't make the machine happy either, so I abandoned that effort for now. ![]() GUI slowdowns annoy, even running DP10.13, and I find myself pushing the 12 core to its limits pretty regularly. I get plenty of work done on my 5,1, but run up against its limitations quite often. When we get a desktop M1 Pro/Max, as I anticipate will take place within the next few months, I will be looking at the software side of the equation very carefully and seriously considering taking the leap of faith the move to a completely new CPU/GPU architecture entails. That said, I'm excited to move into a new realm of performance. I can also see a MIDI response in MainStage as well when I trigger from the M-Audio.Īny help and/or suggestions are very much welcome and thank you for viewing this thread.As the M1 reportedly just matches my 12 core 5,1 in terms of overall horsepower, I'm holding off on a move to Apple Silicon, especially given the software considerations Michael and others have noted. It should be noted that when I'm in the Mac's Audio/MIDI preferences, I can see the MIDI signal and I can see it within Reaper as well but no sound whatsoever. ![]() It's hard to believe that I would need an external soundcard to achieve this in theory, the ability to route this should work with my current setup. I've also seen people building aggregate devices within OS X to compile all of the useful elements together but mainly with a soundcard of some sort. Where there has been people having success with Live, has anybody had any success with what I'm proposing? I'm especially looking to record the actual MIDI data into Reaper from MainStage. Yes.I understand I'm not using Live here but the main purpose of watching these videos is to get a general understanding of the routing scheme. The videos I've seen are people doing this with Ableton Live, Soundflower, and MainStage. I've seen a couple of videos on YouTube touching on this but not anything specific to Reaper. I have a grasp on how the routing is supposed to go but I'm obviously missing something. All 3 pieces of software are up to date and so is my OS. What I'm trying to achieve is being able to record audio and MIDI output from MainStage into Reaper via Soundflower. ![]() I do see that some of you have had success but I'm wondering if its the same success I'm looking for. I've been searching the net for a solution to get Reaper, Soundflower, and MainStage all working together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |