I am no longer able to get Pro Tools 11.2.1 to respond to any MIDI input from any external keyboard using various hardware and cables in many configurations.
Hardware/OS Used:
1 - Intel Core i7 950 3GHz/18GB RAM
2 - Digi003 rack
3 - Four different MIDI input interfaces: Digi003, MOTU MIDI Express XT, and Eleven Rack, M-Audio Keystation 88es USB
4 - Two separate keyboards (M-Audio Keystation 88es, Korg M1)
5 - Two different MIDI cables
6 - Roland XV-3080, Alesis QSR rack synths
7 - Korg M1
Software Used:
1 - Windows 8.1 with latest updates to O/S (as of 2014-11-02)
2 - Latest Digi003 64-bit driver
3 - Latest MOTO MIDI Express XT drivers
4 - Latest Eleven Rack 64-bit driver
5 - The M-Audio Keystation 88es does not require a driver; it uses native Windows
6 - Pro Tools 11.2.1
7 - Native Instruments Komplete 10 with the latest updates for all instruments (as of 2014-11-02)
8 - Spectrasonics OmniSphere Ver 1.5.8d 64 bit, Soundsources Ver 1.0.2, and Patches ver 1.5.5
Installation Notes:
1 - This is a new computer that just came up ten days ago. It took several days to load all the software and related updates (including O/S)
2 - The computer has been cold started with all external devices and interfaces initially switched off, then on after boot-up
3 - The computer has been cold started with all external devices and interfaces initially switched on
4 - Pro Tools has been uninstalled and re-installed 3 times.
5 - Each of the previously mentioned drivers has been uninstalled and re-installed at least once.
6 - All software has been installed under "Run as Administrator" when executing the related installation package.
7 - My login for the machine is explicitly the local system administrator
8 - All USB Root Hubs have had Power Management disabled
9 - Windows Performance options->Visual Effects have been set to "Adjust for best performance"
10 - Windows Performance options->Advanced "Adjust for best performance of:" is set to "Background services"
11 - *VERY IMPORTANT* All of the above devices and interfaces work as expected in Reaper, Reason 8, and the Native Instruments free-standing hosts - only Pro Tools refuses to accept MIDI input
12 - *VERY IMPORTANT* Pro Tools actually DID work with MIDI input as expected for the first couple of days but then suddenly stopped for what seems as no apparent reason. I recorded several virtual instrument tracks in those 6-7 projects during that time.
13 - Neither new or the previously mentioned projects can receive keyboard MIDI.
14 - Pro Tools will no longer shutdown and must have its process killed in the task manager.
15 - No Pro Tools, music hardware/software, or iLok warnings/errors are recorded in the EventLog Application, Setup, or System Windows logs.
16 - Both keyboards can trigger the hardware synths when cabled directly as expected
17 - Receive indicators flash accordingly on the MIDI interfaces
Method of testing:
In PT11 -
1 - Created a new session
2 - From the main menu verified Options->MIDI Thru is checked
3 - From the main menu verified Setup->Preferences->MIDI "Default Thru Instrument" is set to "first selected MIDI track"
4 - Tried with and without setting up a new instrument from the main menu under Setup->MIDI->MIDI Studio Setup... using the associated MIDI input device being tested
5 - From the main menu verified Setup->MIDI->Input Filter... is set to Record All
6 - From the main menu verified Setup->MIDI->Input Devices... either all devices are enabled (with the exception of "FW 003 MIDI AsyncMidiControl" and "FW 003 MIDI MidiControl) or only the port of the MIDI interface being tested
7 - Created either a single stereo instrument track using Kontact 5, OmniSphere, or Absynthe in Insert A, -or- a single MIDI track assigned to none, the Roland XV-3080, the QSR, or the Korg M1.
9 - Selected either "All" or the specific MIDI interface being tested when testing the aforementioned created tracks
10 - Tried "Track Record Enable" both on and off when testing the aforementioned created tracks
In Kontact, Reaper, and Reason:
1 - Any of the MIDI approaches works as expected with any of the MIDI interfaces
Connectivity Used:
1 - Cabled the keyboard being tested to Port 1 In of the interface being tested (Digi003, MOTU MIDI Express XT, or Eleven Rack) and made sure the 88es USB cable was disconnected (when used in testing its power was supplied using a wall wart)
2 - Used the USB driver of the 88es (left MIDI Out disconnected on all other keyboards)
I have generated a SANDRA report but the upload is "invalid" (.txt) or does not have a "valid security token" (.zip) when attaching to this bulletin post. It appears only "bmp gif jpe jpeg jpg pdf png psd" files can be attached. This is odd this support forum does not accept TXT or ZIPed files since SANDRA files are specifically requested by the moderator. I will paste the contents of the report in a follow-up post.
Thanks for the help,
Jim
Hardware/OS Used:
1 - Intel Core i7 950 3GHz/18GB RAM
2 - Digi003 rack
3 - Four different MIDI input interfaces: Digi003, MOTU MIDI Express XT, and Eleven Rack, M-Audio Keystation 88es USB
4 - Two separate keyboards (M-Audio Keystation 88es, Korg M1)
5 - Two different MIDI cables
6 - Roland XV-3080, Alesis QSR rack synths
7 - Korg M1
Software Used:
1 - Windows 8.1 with latest updates to O/S (as of 2014-11-02)
2 - Latest Digi003 64-bit driver
3 - Latest MOTO MIDI Express XT drivers
4 - Latest Eleven Rack 64-bit driver
5 - The M-Audio Keystation 88es does not require a driver; it uses native Windows
6 - Pro Tools 11.2.1
7 - Native Instruments Komplete 10 with the latest updates for all instruments (as of 2014-11-02)
8 - Spectrasonics OmniSphere Ver 1.5.8d 64 bit, Soundsources Ver 1.0.2, and Patches ver 1.5.5
Installation Notes:
1 - This is a new computer that just came up ten days ago. It took several days to load all the software and related updates (including O/S)
2 - The computer has been cold started with all external devices and interfaces initially switched off, then on after boot-up
3 - The computer has been cold started with all external devices and interfaces initially switched on
4 - Pro Tools has been uninstalled and re-installed 3 times.
5 - Each of the previously mentioned drivers has been uninstalled and re-installed at least once.
6 - All software has been installed under "Run as Administrator" when executing the related installation package.
7 - My login for the machine is explicitly the local system administrator
8 - All USB Root Hubs have had Power Management disabled
9 - Windows Performance options->Visual Effects have been set to "Adjust for best performance"
10 - Windows Performance options->Advanced "Adjust for best performance of:" is set to "Background services"
11 - *VERY IMPORTANT* All of the above devices and interfaces work as expected in Reaper, Reason 8, and the Native Instruments free-standing hosts - only Pro Tools refuses to accept MIDI input
12 - *VERY IMPORTANT* Pro Tools actually DID work with MIDI input as expected for the first couple of days but then suddenly stopped for what seems as no apparent reason. I recorded several virtual instrument tracks in those 6-7 projects during that time.
13 - Neither new or the previously mentioned projects can receive keyboard MIDI.
14 - Pro Tools will no longer shutdown and must have its process killed in the task manager.
15 - No Pro Tools, music hardware/software, or iLok warnings/errors are recorded in the EventLog Application, Setup, or System Windows logs.
16 - Both keyboards can trigger the hardware synths when cabled directly as expected
17 - Receive indicators flash accordingly on the MIDI interfaces
Method of testing:
In PT11 -
1 - Created a new session
2 - From the main menu verified Options->MIDI Thru is checked
3 - From the main menu verified Setup->Preferences->MIDI "Default Thru Instrument" is set to "first selected MIDI track"
4 - Tried with and without setting up a new instrument from the main menu under Setup->MIDI->MIDI Studio Setup... using the associated MIDI input device being tested
5 - From the main menu verified Setup->MIDI->Input Filter... is set to Record All
6 - From the main menu verified Setup->MIDI->Input Devices... either all devices are enabled (with the exception of "FW 003 MIDI AsyncMidiControl" and "FW 003 MIDI MidiControl) or only the port of the MIDI interface being tested
7 - Created either a single stereo instrument track using Kontact 5, OmniSphere, or Absynthe in Insert A, -or- a single MIDI track assigned to none, the Roland XV-3080, the QSR, or the Korg M1.
9 - Selected either "All" or the specific MIDI interface being tested when testing the aforementioned created tracks
10 - Tried "Track Record Enable" both on and off when testing the aforementioned created tracks
In Kontact, Reaper, and Reason:
1 - Any of the MIDI approaches works as expected with any of the MIDI interfaces
Connectivity Used:
1 - Cabled the keyboard being tested to Port 1 In of the interface being tested (Digi003, MOTU MIDI Express XT, or Eleven Rack) and made sure the 88es USB cable was disconnected (when used in testing its power was supplied using a wall wart)
2 - Used the USB driver of the 88es (left MIDI Out disconnected on all other keyboards)
I have generated a SANDRA report but the upload is "invalid" (.txt) or does not have a "valid security token" (.zip) when attaching to this bulletin post. It appears only "bmp gif jpe jpeg jpg pdf png psd" files can be attached. This is odd this support forum does not accept TXT or ZIPed files since SANDRA files are specifically requested by the moderator. I will paste the contents of the report in a follow-up post.
Thanks for the help,
Jim
Aucun commentaire:
Enregistrer un commentaire