Trying to slave pd to a DAW via Midi clock data. I'm not getting anything from [midirealtimein] and I've double checked that my DAW is transmitting Midi clock data on the same MIDI bus that pd is receiving on. Could someone test on their own system to confirm?

Running pd-ext 43.4 on OS 10.9.5

Worked last time I tried it on linux. Haven't tried it on the Mac that I can remember. If you are using Midi Patchbay, select the connection you are using and click then"other" tab. I'm not sure why "other" isn't just labelled "realtime filter" because that's the only checkbox there (at least on the version I have). Realtime is filtered out by default in M.P. so you have to make sure that box is checked.

UPDATE: apparently [midirealtimein] works in at least Vanilla 45.4 and using MidiPatchyBay as the Midi bus program (rather than OS X's native IAC driver)

Yeah, never use IAC. It's long been known to have problems (i.e. doesn't work) with realtime and system exclusive -- plus timing issues with everything else. Seems like an unfinished hack, really.

You can create all the virtual connections you need with Midi Patchbay, so there's really no need for it.

@NoDSP That's twice you've recommended MPB for me now, and twice it's worked! Well I'm officially sold now haha.

Yes I suspected you were getting yourself into that IAC mess again .

One thing that you can't do with MPB and PureData is route realtime from a device that sends active sense, since a.s. is a realtime message (MPB realtime filter can't tell the difference between clock, seq commands and a.s.) and [midirealtimein] will pass it through accordingly. It wouldn't be to much trouble to filter it out after [midirealtimein] but -- as you know from our previous discussions -- Pd has a leaky plumbing problem with active sense. Come to think of it that should probably be submitted as a bug report.