 Configuration of Pro Tools and MPC-2000 and other MPC Models for sync ...
|
| Configuration of Pro Tools and MPC-2000 and other MPC Models for sync using MIDI Beat Clock and MIDI Time Code on Windows XP Pro Tools 6.9 or Higher. |
Configuration of Pro Tools and MPC-2000 for sync using MIDI Beat Clock and MIDI Time Code on Windows.
1) The following setup is for both MTC and MIDI Beat Clock. (When using MTC provide a bar or two of pre-roll)
2) With Pro Tools LE or Pro Tools HD version 6.x, you'll need an interface with MIDI capability such as a MIDI I/O, Digi 002 rack or mixer, Digi 001, or third party MIDI interface.
3) Verify that there is a device created , GO TO Setups menu, MIDI Studio and create a MPC 2000 by clicking "create" choose manufacture and model then the Input Port and Output port on your MIDI interface. Check the properties to check for any preferences to enable MTC or MIDI Beat Clock.
In Pro Tools:
1) go to Setups > Peripherals > Synchronization > Generic MTC > port = DIGI 002 (or, other MIDI Interface of choice)
2) Go to MIDI -> MIDI Beat Clock -> make sure boxes for Enable MIDI Beat Clock and MPC 2000 are filled in.
3) Session setup > Frame Rate =30 and MTC to port = MPC 2000
In the MPC 2000:
1) go to > MIDI Sync> Frame Rate=30, MIDI Clock (stands for MIDI Beat Clock; Choose either MTC or MIDI Beat clock here), receive MMC=off, Port 1 (There are 2 MIDI INS and 2 MIDI outs on the MPC 2000; VERIFY the MIDI cable going from the MIDI interface into either MIDI IN Port 1 or MIDI IN Port 2 corresponds to the Port selected on the MPC 2000's Midi sync menu)
7) press PLAY on the MPC 2000 (it will wait for sync from Pro Tools
8) press PLAY on Pro Tools; it will trigger the MPC 2000.
[Page View]
|
|
|
After playing my MIDI wind controller, I am not able to trigger the same ...
|
| After playing my MIDI wind controller, I am not able to trigger the same sound module from other MIDI controllers (ie. MIDI keyboard). |
MIDI wind controllers keep sending MIDI data to the sound module even after playing has stopped. If you check the MIDI port lights on your MIDI Interface where the MIDI wind controller is connected, you will see lights still flashing after the user has stopped playing the wind controller. Somehow, this ongoing MIDI data prevents other controllers from triggering the same sound module. No audio will play out of the same sound module because it is NOT receiving MIDI from Pro Tools.
The workaround in Pro Tools is to playback the MIDI notes recorded into Pro Tools from the MIDI wind controller. Now, the user should be able to play a MIDI controller keyboard and trigger the same sound module to play.
Note: there must be some parameter to change on the MIDI wind controller to limit the MIDI data. (ie. note off/on commands).
[Page View]
|
|
|
MIDI problems? Does AMS not recognize your MIDI Interface? Is MIDI communication ...
|
| MIDI problems? Does AMS not recognize your MIDI Interface? Is MIDI communication with all programs flakey? |
Trash the ByHost folder, located in:
/Users/"your user name"/Library/Preferences/ByHost
Specifically there will be a file named:
com.apple.MIDI.xxxxx.plist
(the xx's will be replaced by a number specific to that User account)
[Page View]
|
|
|
Moving the faders on the JL Cooper CS-10 MIDI controller cause Pro Tools ...
|
| Moving the faders on the JL Cooper CS-10 MIDI controller cause Pro Tools to crash. Transport controls work without problems. |
Verify that you are using a supported MIDI Interface. For the complete list go to: http://www.digidesign.com/compato/
This crash was reported with a Pro Tools 6.2 HD system on Windows XP Pro using a MIDIMan interface.
[Page View]
|
|
|
In Pro Tools 6 the MOTU MIDI Interfaces will not transmit or receive MIDI ...
|
| In Pro Tools 6 the MOTU MIDI Interfaces will not transmit or receive MIDI to and from Pro Tools. |
When the Digi 002 or Digi 001 midi driver (DIOOSXMIDIDriver.plugin) is present in the Midi drivers folder MOTU Midi interfaces, like the Midi Time Piece will not send or receive midi into Pro Tools
Work around,
To get the MOTU interfaces to send and receive midi
- Move the DIOOSXMIDIDriver.plugin folder out of the Midi Drivers folder and place it on the desktop.
- Restart the Mac
- Now the MOTU interface should work correctly
- This will consequently disable your midi ports on your 002 or 001
[ The DIOOSXMIDIDriver.plugin can be found in the Mac HD>Library > Audio>Midi Drivers ]
[Page View]
|
|
|
MIDI Interface Offline in Pro Tools 6.0
|
| MIDI Interface Offline in Pro Tools 6.0 |
If your MIDI interface goes offline when making changes in AMS while Pro Tools is running, you may need to quit and relaunch
both Pro Tools and AMS.
From the Pro Tools 6.0 TDM ReadMe.
[Page View]
|
|
|
"Bounce handler cannot keep up (DAE Error -9132)" when attempting to ...
|
| "Bounce handler cannot keep up (DAE Error -9132)" when attempting to bounce audio. May be accompanied by an assertion error "FF_AudioProperty.cpp", line 33 |
This error has been seen when a MOTU Fastlane MIDI interface is used in conjunction with Pro Tools 6.0. The MOTU Fastlane is not a supported MIDI Interface.
[Page View]
|
|
|
The use of Multiple MOTU Fastlane USB Midi Interfaces in Pro Tools 5.3.1 ...
|
| The use of Multiple MOTU Fastlane USB Midi Interfaces in Pro Tools 5.3.1 Windows is unsupported. |
The use of MIDI input from multiple simultaneous MOTU Fastlane USB MIDI Interfaces may result in MIDI note loss. MIDI input from multiple devices and/or channels from one MOTU Fastlane, as well as MIDI output to multiple MOTU Fastlanes, is supported.
[Page View]
|
|
|
Setup for routing the click track to an external MIDI device when using ...
|
| Setup for routing the click track to an external MIDI device when using Mbox. |
The click track in Pro Tools is a MIDI click and must be routed to a MIDI device in order to hear it. The click is NOT audio.
1) Connect your MIDI device to an external MIDI Interface via MIDI cables. MIDI Device MIDI OUT to MIDI IN on MIDI Interface. MIDI Device MIDI IN to MIDI OUT on MIDI Interface. (MIDI Interfaces are made by Midiman, MOTU, Emagic, etc.)
2) Create an OMS Studio Setup (verify synth modules are connected) Follow pages 9-11 in Getting Started with Mbox Guide.
In Pro Tools: Setups Menu > OMS Studio Setup. (If it says “Please Find OMS: Double-click on Desktop > Mac Hard Drive > Opcode Folder > OMS Applications > OMS Setups). OMS must recognize your MIDI interface. Configure your MIDI devices that will be connected to the MIDI Interface.
3) In Pro Tools, double-click on the Metronome Icon on the Transport or follow step #4.
4) MIDI Menu > Click Options > Ouptut > Choose MIDI device to route the click to, channel 10 (Where drum sounds usually reside). Select “During Play and Record”. Make sure the Metronome is highlighted on the Transport, which means the click option is enabled.
5) MIDI Menu > Input Devices. Verify that your MIDI device(s) is enabled in the Input Devices window. Verify that MIDI Thru is enabled in the MIDI Menu as well.
6) In Pro Tools > File > New Track > Create an Aux. Track, if your MIDI device is connected to the Mbox via a Source Input Jack. If your MIDI device’s audio is playing through an external mixer disregard this step. Because the Mbox only has two inputs, it might be more practical if the L & R audio outputs of the MIDI device are connected to an external mixer to monitor the MIDI device.
7) If the MIDI device audio output is connected to the Mbox: Select the Inputs for the Aux. track to reflect the Inputs used to connect the MIDI device to the Mbox. (ie. If your MIDI device is connected via 1/4" audio cables to Source Input 1 or 2 on the Mbox, select In1 or 2 as Input choice on audio track). Push up the volume on the fader of aux. track to hear MIDI device. If your MIDI device’s audio is playing through an external mixer disregard this step.
8) To set the Tempo in Pro Tools: MIDI Menu > Change Tempo > Type in your tempo in the BPM (Beats Per Minute Box) hit Apply. Or Deselect the "Conductor" on the Pro Tools Transport and type in the tempo for Quarter Note =120.00 BPM and hit enter.
9) Press Play on Pro Tools transport and you should hear the click track.
[Page View]
|
|
|
On a Windows machine, using a MOTU MIDI Interface: An error has occurred ...
|
| On a Windows machine, using a MOTU MIDI Interface: An error has occurred in your program... Pro Tools LE is causing a general protection fault in module. MOTU mxxt.drv. - Or - An error has occurred in your program...This program has performed an illegal operation. Detail: PT LE caused an invalid page fault in module dsi.dll at 0167:38018a52 |
There can be a driver conflict between the MOTU and Digidesign 001 MIDI drivers. This setup will disable the MIDI driver for the Digidesign 001 to prevent the conflict.
To disable the Digidesign 001 MIDI driver in Windows:
1) My Computer > Control Panel > Multimedia (Windows 98SE) or Sound and Multimedia (Windows ME)
2) Click on the Devices Tab
3) Click on MIDI devices from the list.
4) Right-click on the MIDI for Digidesign Multimedia Devices > Properties > Choose "Do not use MIDI features on this device".
5) Restart
6) This will prevent the use of the Digidesign 001 MIDI port.
This will prevent the use of the Digidesign 001 MIDI port. The Digidesign 001 MIDI port will not show up as an MIDI output selection for a MIDI track. But, the alternative is not to be able to use the MOTU MIDI interface.
[Page View]
|
|
|
