Xiangfu Liu wrote: > we should add a host-app folder under daily build. Hmm, maybe, if binary compatibiity across distributions is reasonable. Or get distributions to pick is up. That's slower but solves the problem for good :)
> (what else your apps we should include) >From my side, maybe the JTAG boot could be useful: http://projects.qi-hardware.com/index.php/p/wernermisc/source/tree/master/m1/jtag-boot/ That's all I can think of for the moment. At some point in time, we should probably also have a simple IDE for the PC, maybe just like the patch editor on M1, but with F2 sending the patch over to the M1 and running it there. > so we can start think about use the 'MIDI out' port. > is the 'MIDI out' just a mirror of 'MIDI in'? I think it should be relatively easy to support OSC -> MIDI as well. I used contrOSC (http://controsc.sourceforge.net/) as an example for how to converse between MIDI and OSC, and it also contains code for the OSC -> MIDI direction, including thread handling and such. Another useful source of information is oscsend.c: http://igoumeninja.org/en/uploads/Tools-Perl/perlModules/liblo-0.26/src/tools/oscsend.c For OSC -> MIDI, you'd want to look at oscdump.c: http://igoumeninja.org/en/uploads/Tools-Perl/perlModules/liblo-0.26/src/tools/oscdump.c I don't have any use case for OSC -> MIDI at the moment, that's why I didn't try to add such functionality as well. But yes, it would probably make sense to turn this into a "generic" and bi-directional MIDI/OSC gateway at some point in time. - Werner _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
