Is it usable under Windows with Winpcap?

I've directly written to Miller Puckette, he has addressed the bug and he told me that he will try to fix it in about a month and to use pd-044.3 downloadable from here for a temporary fix of MIDI in Windows, I hope that this could be useful to other people using MIDI SysEx in Windows

I've tried it on OSX and it works fine, so the newer pd Vanilla releases haven't fixed the [midiin], [midiout], and [sysexin] objects under Windows

I've downloaded the latest pd version, the [midiin] is displaying channel messages without problems, but nothing happens with SysEx messages, even with [sysexin]. [midiout] instead isn't working at all, it gives only an error on the pd console...

Thank you very much, I will try it and let you know. A pd-extended version is in work? Where I can find even an alpha or beta version of pd-extended?

Hello, I'm on windows 8.1, I've not tested this on other windows versions but I'm not able to make work this object, I've tried to send comma separate messages but every number is preceded by a number and followed by a 0. There's something that I'm missing.? No one needs to send SysEx messages under windows?

Thank you very much, that was what I was looking for

Maybe is a silly question but what is the right way to run pd? By executing the pd-extended.bat in the root folder or pd.exe inside the bin folder? What is the difference? The only one that I've noted is the command prompt that stays open after the startup if i run the .bat

Could you give a more in depth explanation? Maybe post the arduino code with comments and the pd patch

Problem solved! I've edited my abstraction so that the 30 toggles are splitted in 4 bytes, every byte outputs the number in hex form and a complete hex message is created by merging every byte. Now it works wonderfully! Thanks to everyone for the help|!