For some reason if I output midi from pd to a saved ableton file that I had routed before I saved it, it will either work for one bang, or a couple and then stop working completely. Sometimes it won't even work from the start.

Now if I use the same exact program on a new, unsaved ableton file, it will work indefinitely, no problems at all.

I know it's not the midi router either because the same thing occurs when I use midiyoke or loopmidi.

It's a bummer too because if it can't be fixed then I can't do any midi routing with pd on any files I've saved in ableton, I can only do it one time on a new project before I save it. I don't know if the fact that the file is saved or not is the root cause of this problem - it's just the only correlation that I've detected.

I did notice that when I open these saved files that the lettering in the midi input channel is colored orange to indicate there's an error. When I pick a different available port the orange goes away with no error signaling. But then this problem occurs.

I'm definitely routing properly since I can get it to work perfectly in a new, unsaved ableton file.

Does anybody know what's happening here?

Thanks in advance.

I dont understand you problem exatly, but it sounds like a infinite midi loop.

What os are you using? If you just need to rec midi from pd to ableton try disabling the midi-out in live and/or the midi-in in pd. It solved a similar problem I had using touchDAW

I can't explain it but now it works. The only thing I noticed different was that as I kept resaving it slightly differently in an attempt to troubleshoot, the orange lettering of the midi input doesn't come up anymore. Maybe it routed weird the first time I saved it and so it was mucking it up whenever I'd load it again?

Thanks for all the input guys, much appreciated!!