Soundflow took over my midi controller, I can no longer get it to work.

Thanks for postin here @Heath_Ripplinger

And again sorry for the situation.

Can I get you to take a screenshot of the MIDI Input Enable window, that can be opened from;

"Setup" => "MIDI" => "MIDI Input Devices..."

Are you using MIDI in SoundFlow for anything else? Eg. are you triggering SoundFlow commands from MIDI devices?

The easiest solution right now might be to turn off the SoundFlow MIDI feature completely until we can work out what is going on.

If you know how to edit a json file, you'll need to add this key/value pair to your appSettings.json:
"disableMidiInterface": true,

For example, after adding it, your appSettings.json could look like this:

{"debugAppState":false,"disableMidiInterface":true,"channel":"stable","enableAudioEngine":false,"useStreamDeckHid":false,"flags":{},"disableIcon":false,"autoLaunch":true,"firstRunCompleted":true}

appSettings.json is found in ~/Library/Application Support/SoundFlow/v2/appSettings.json

Note: You can't edit the json file with TextEdit, as TextEdit inserts invalid characters into json files and renders them unusable (which means SoundFlow will overwrite your changes on next start).
You'll need to use a code editor like Visual Studio Code.

If you would prefer not to do this let me know and I'll send you an edited version of your appSettings.json settings.

@Heath_Ripplinger - just chiming in here. Please let us know if the above steps make any difference / or if you need help implementing them.

It would be very helpful for us to see the screenshots Kitch requested above, if you're still seeing issues.

Just to clear some things up:

• SoundFlow doesn't have code that instructs Pro Tools which MIDI device to use. Third party scripts you install from the Store could potentially do that, but in SoundFlow's built-in commands that we provide, there are no such code that has that ability. I should also mention, I've not seen anybody make such a script. This indicates that if there's some functionality in Pro Tools that automatically switches your routing, it's more likely to be a bug in Pro Tools.
• SoundFlow doesn't install any drivers, MIDI or otherwise. This also means, when you quit SoundFlow, no SoundFlow-related code is running on your system. To uninstall it, simply quit it and drag it to the Trash. If you're still seeing issues when SoundFlow is not running, again, the issue is more likely to be between Pro Tools and your MIDI device, as SoundFlow has no influence or control over how they communicate with each other.
• The way SoundFlow integrates with MIDI is using macOS' standard APIs for how to communicate with MIDI devices. We don't send any information or messages to MIDI devices unless instructed to do so by a macro or script. So this is also not a likely cause for the issue you're seeing.

To further investigate and help sort out what's happening, can you elaborate on this?

My midi controller was re-routed to soundflow in pro tools.

Can you show us a screenshot of this so I understand more directly what you mean by being re-routed?

After creating the blank untitled session to get a screenshot for you. I went back to the original corrupted controller session and it works again. I have no idea why. I feel dumb. It remains to be seen if it will do this again as it has already happened twice. But last night, it had definitely re-routed to one of those soundflow midi devices that you see in the screenshot. It did it all by itself after about 1 minute using midi on an instrument track. If there's one thing soundflow has accomplished for me at this point, it would be making me look stupid. 😂