MOTUnation.com

BTW, pan is CC10, not CC11. CC11 is expression.

My first rig with MIDI was an all Yamaha combination of a DX7, TX7, RX7 and QX7. No computer. The QX7 sequencer was two tracks (one to record into and one merged track for parts that were finished). It stored songs to data tape! I later moved up to an Atari with Dr. T’s KCS with Tiger (The Integrate...

I’m going to say that you are getting a sample rate mismatch that will come back to bite you later. DP I thinks it’s running at 48k but the incoming spdif is really at 44.1. When those files actually play back at 48k they will be too fast and up about a 1/2 step. Everything “appears” to be working f...

I should say, my explanation above is how the original MIDI spec was conceived. I agree that you could use audio automation for main mixing and CC7 for finer changes. My main point is that CC7 should only affect volume, whereas CC11 was defined as something that may do more than volume.

CC7 is for setting overall volume (think mixing board fader). You might be thinking of CC11 (expression) which is for dynamic changes (which may be just volume, but may also include timbral or other changes depending on how the patch is programmed).

It may just be the Mac Studio having problems with MTP-AV USB. I have one running with a MBP M1-Max (Monterey 12.3.1). Installed the latest MOTU MIDI driver and connected with an Apple USB-C to USB-A adaptor. Loses connection on sleep but otherwise seems to be working.

OK, so here's a good story. I have a recording session in two weeks where the engineer has asked to record both audio and MIDI from my rig. I think he wants to replace my Pianoteq sounds with Ivory after the fact. Whatever... but how am I going to get MIDI to him? I connect my Yamaha MOXF-8 to my ne...

Those functions are also available in MainStage. I use the chord trigger quite a bit when programming for pit orchestra stuff. Gets a bit much when used in a sound with fast attack, as all the attacks fall exactly together in an unnatural way, but for strings and such it’s great. I don’t use the arp...

The three things that slow down a bounce in my experience are:

1. Bounce to mp3, as Mike mentioned

2. Small buffers (yes, large buffer settings bounce faster)

3. Izotope RX plugins like noise reduction and de-reverb.

Anyone jump on this deal from UAudio? Native versions (no UA hardware needed) of a selection of plugins plus native versions of any plugins you already own. It’s a subscription. I might go for it as I had a bunch of UA plugs I owned on a PCI system that I haven’t been able to use since 2016.

I’m on an M1 MBPro. Build number on booting DP says 90329 and “check for updates now” says “no new updates are available “.

In regards to question 2. I have a MBP with M1 Max and there is no timing problem with MIDI.

My intel Mac is an iMac 18,3.

I did this test with my Intel Mac using a mic to record my fingers hitting the keys. MIDI data lined up with the audio when the track was assigned to a hardware MIDI device (Yamaha Steinberg USB driver). When the MIDI track was assigned to a VI the MIDI data was significantly behind the audio. Just ...

Just to be clear, the SWAM instruments from audiomodeling do not use Kontakt. The older ones from samplemodeling did.