Senidng a second time (Sorry, I forgot to send to the public list - and I added some new information.)
Here is my result: registered pm_exit with atexit() 0: MMSystem, Microsoft MIDI Mapper (output) 1: MMSystem, FireFly_808 MIDI-Port (input) 2: MMSystem, Microsoft GS Wavetable Synth (output) 3: MMSystem, FireFly_808 MIDI-Port (output) Type r to receive sysex, s to send, l for loopback test, m to send multiple, n to receive multiple, q to quit: l Connect a midi cable from [...] Sending 992 byte sysex message. Error at byte 0: sent f0 recd d3. I compiled my project using fpc, the dll is compiled using microsoft visual c++ 2010 express. The platform is Win7 64bit, however the program is compiled as 32bit (64bit gave me "application could not be started (0xc000007b)" on startup [or in german: Die Anwendung konnte nicht korrekt gestartet werden(0xc000007b)]. So i decided to switch to 32bit.) Midi Interface is a Phonic Firefly 808 (Firewire version). I also checked this with a selfmade MidiBox.org - core32 module (error at byte 0) and a tascam US122L. The tascam gave me this: Sending 285 byte sysex message. Error at byte 260: sent 4 recd f7. Sending 949 byte sysex message. Error at byte 259: sent 3 recd 0. I made music with all of these interfaces, and they always seemed to be ok. Using the Phonic Firefly and a program called "MIOS Studio" I even uploaded code to the MidiBox.org-board via SysEx, having no errors. So I think the problem is not related to the hardware. I checked something esle. I used to program MIOS Studio (which is known to be working) and sent midi sysex. My application received the right data. Mios studio received the same worng data as my program. this emans that receiving messages is fine, sendng isn't. Thanks for any help, Johannes Neumann Am 19.04.2011 23:13, schrieb Roger Dannenberg: > Johannes, > Interesting. Is this a Win32 or Win64 platform? and can you say > more about compilers, OS, midi drivers up-to-date, MIDI interface? > I've tested on Win32 using the sysex program in pm_test, which has a > feature to do a loop-back test: it generates random messages of random > length, sends them, and check the result. You might try this too for > another data point if you haven't tried it yet. Please let me know > what you find. > -Roger > > On 4/19/11 3:07 PM, Johannes Neumann wrote: >> Hello! >> >> I have trouble sending sysex via portmidi on a windows platform. When I >> send the following: 0xF0A4A310F7. I receive this one here: >> 0xA4000000A310F7. When I send this: 0xF0A4A31010305032F7 i get >> 0xA4000000A3101000A3305000A332F7. >> I checked the output by plugging a cable from MIDI Out to MIDI In and >> running a midi monitor. Whats wrong? >> >> Thanks for any help, >> Johannes Neumann >> _______________________________________________ >> media_api mailing list >> media_api@create.ucsb.edu >> http://lists.create.ucsb.edu/mailman/listinfo/media_api > _______________________________________________ media_api mailing list media_api@create.ucsb.edu http://lists.create.ucsb.edu/mailman/listinfo/media_api
