PT 10.3.8- now VIs being constantly triggered

[js_nyc]

After de-installing PT 10.3.7 and clean installing 10.3.8, any time I instantiate any one of my VIs, there is this constant trigger (about every 2-3 seconds) which then generates an audible sound loop on a preset, making the VI unusable. This happens even when the VI is not record-armed. Tried changing all MIDI clock and other issues. De-installed 10.3.8 and re-installed. Trashed prefs, etc. Cannot figure out where this phantom pulse/trigger command is coming from. Using an old Oxygen 61 through USB as a controller, but this problem occurs even when the controller is not assigned to the VI track. Please let me know if anyone has any suggestions/solutions. Thanks.

[js_nyc]

Update: this "trigger" is also recorded as a MIDI event- on the lowest note and at random intervals (please see attached picture). I can obviously delete this "low note" in the MIDI track, but the constant trigger/pulse still sounds during the playback of these tracks, making them unusable. Please let me know if anyone has an answer. Thanks.

[Stig Eliassen]

First thing I would try is to disconnect the keyboard, and then launch Pro Tools. Does it still happen?

[js_nyc]

Originally Posted by PT Lover

First thing I would try is to disconnect the keyboard, and then launch Pro Tools. Does it still happen?

Thanks for the reply. Yes, this still happens even when the MIDI keyboard is not connected (via USB).

[Stig Eliassen]

Ok.

Not familiar with that keyboard; does it also have MIDI ports on the back? If yes, are those connected?

[js_nyc]

Originally Posted by PT Lover

Ok.

Not familiar with that keyboard; does it also have MIDI ports on the back? If yes, or those connected?

Yes it does have MIDI, but I am only connected through USB- have not had to use MIDI in years...

[Ale]

I am not sitting at protools right now.
I had this behavior in PT 7.xx . Unfortunately I am not remembering exactly what was the problem. I had some sort of internal miditrigger in the system.
I think it was caused by an old waverider plugin. Try narrowing down with disabling the midi inputs in the midi setup (uncheck midi input devices in PT)and see what happens.

Ale

[Stig Eliassen]

Originally Posted by js_nyc

Yes it does have MIDI, but I am only connected through USB- have not had to use MIDI in years...

Any footswitch or MIDI gear connected to the 003 rack?

[js_nyc]

Thanks everyone for all of your suggestions. I started today from only PT I/O Aggregate settings, and the problem was gone. Added in the MIDI keyboard, PreSonus FaderPort (one at a time), and the problem was still gone. I then returned to the 003 Rack as playback engine, and all was still right! I think maybe in troubleshooting yesterday, I forgot to power-cycle the 003 Rack during the processes. Anyway, will still keep my eye on things. I have to use the MachFive Version 3.1.4 instead of v3.2, since all my Multis went to blank defaults in previous PT sessions (which was the beginning of my long troubleshoot journey in the first place).

[Stig Eliassen]

Originally Posted by js_nyc

Thanks everyone for all of your suggestions. I started today from only PT I/O Aggregate settings, and the problem was gone. Added in the MIDI keyboard, PreSonus FaderPort (one at a time), and the problem was still gone. I then returned to the 003 Rack as playback engine, and all was still right! I think maybe in troubleshooting yesterday, I forgot to power-cycle the 003 Rack during the processes. Anyway, will still keep my eye on things. I have to use the MachFive Version 3.1.4 instead of v3.2, since all my Multis went to blank defaults in previous PT sessions (which was the beginning of my long troubleshoot journey in the first place).

Thanks for reporting back.

Let us know how you get on. Sometimes these things can be hard to track down.