#Pro tools midi monitor upgrade#
#Pro tools midi monitor pro#
#Pro tools midi monitor software#
#Pro tools midi monitor mac#

#Pro tools midi monitor software#

I'm writing a book on digital music production, and one of the things I realized from my own experiences is that 'busing and routing' is very important but is not explained in a lot of detail for folks who (a) are not software engineers and (b) have not done so much work with real electric instruments, synthesizers, PA systems, microphones, and so forth.

#Pro tools midi monitor pro#

I downloaded and browsed the Pro Tools 12 (2020) User Reference, and it looks to be the same as Studio One Professional for MIDI from NOTION sent via External MIDI staves and a virtual MIDI cable created with the macOS Audio MIDI Setup application. ReWire and MIDI are sensitive to configuration, so if something is not configured correctly, then none of it works and it's often something simple that probably is not documented clearly anywhere. ĭoing MIDI and ReWire is good, because ReWire keeps everything synchronized. I don't have Pro Tools, so I can't be much help there. ReWire MIDI is nice, because it has it's own inter-application communication system, hence avoids needing to do it with External MIDI staves in NOTION with a virtual MIDI cable. It's also useful to understand that ReWire MIDI is supported by Studio One Professional (PreSonus) and Digital Performer (MOTU) but to the best of my knowledge at present, these are the only two that support ReWire MIDI. The reason is that ReWire provides its own virtual MIDI cables that use UNIX 'pipes' and are not like the virtual MIDI cables created with Audio MIDI Setup, so that's a possibility. If you are using ReWire MIDI staves rather than External MIDI staves, then MIDI Monitor will not see the MIDI traffic.

I would not try to 'backrev' the software, but there is another possibility. I have a 2012 MacBook Pro that is running macOS Catalina, so as time allows I will see what happens on it but at present I am focused on recording what I hope are simple, stupid, annoying, psychedelic, risqué, and perhaps amusing 'Not-Holiday' songs, because somebody needs to do it. If you check everything in 'Filter', it's a lot of data. I set the 'Filter' to show everything and then uncheck things I don't need to see once everything is working correctly and MIDI Monitor is capturing data. Ĭheck that you have MIDI Monitor configured correctly, which probably requires setting the 'Spy on output to destinations' stuff and getting the 'Filter' settings configured for what you want to see. However, there are a few things which are not shown in the screen captures-primarily the MIDI Monitor configuration, so this is the additional information I see here in the sound isolation studio. The screen captures you posted look good in terms of being what I expect to see.

#Pro tools midi monitor mac#

MIDI Monitor works on the Mac and actually is designed and programmed for macOS.

#Pro tools midi monitor upgrade#

I'm not going to upgrade anything, because (a) the software I have is working and (b) I don't want the mess with new version of anything.

Īnother thing I noticed is that the Audio MIDI Setup I am using is from 2015 and does not have the Properties tab-only the Ports tab. Recently, I purchased an effects plug-in from Waves, and afterward discovered it does not run on the Mac Pro (Early 2008), so unless I get an iMacPro, Waves products are off the table-other than the ones I already have from a year or two ago, as is the case with iZptope, where recently I decided to purchase Stutter Edit 2, which did not work but I found Stutter Edit 1 on eBay for $50, and it works nicely here in the sound isolation studio.

Products from Waves and iZotope require a newer Mac, and this is becoming more commonplace, which is what happens over time but is nonetheless annoying. Īll my digital music production software works nicely on the Mac Pro (Early 2008), but I am finding that some of it is no longer updatable, where for example the newest version of NOTION 6 does not run on this Mac Pro, which is fine with me. The information at the MIDI Monitor website says 1.3.2 is the most recent version that will run on the Mac Pro (Early 2008), but more specifically it advises 'If you're using an older version of macOS, use version 1.3.2 instead'. It works on the Mac Pro (Early 2008) running macOS El Capitan (10.11.6) and MIDI monitor 1.3 here in the sound isolation studio.

I did a bit of research and didn't find a lot of information, but so what.