From: Brent B. <br...@ke...> - 2018-07-06 05:00:11
|
Michael Schmitt via basilisk-devel <bas...@li...> writes: > Does it print the unimplemented control code value? What is it? > > Is it 15 (kSERDClockMidi, as defined in serial_defs.h)? Been busy with fireworks and food (US Independence Day)... I tried the experiment again. Yes, it is 15. > I wonder what would happen if you just changed the switch/case block to return noErr for that code. Well, I tried it. I added a new case: case kSERDClockMIDI: printf("DEBUG: I think I saw a serial port trying to do Midi\n", code); return noErr; // Midi? We never saw no Midi. I does print the message, especially when you try to setup OpCode Studio. However, the emulator is more unstable now, often crashes when the guest reboots. It's a shame; I was hoping maybe there was an easy fix. > Note: The source says that there are 4 types of devices: serial, > parallel, pty and midi, and that it returns an openErr if an attempt > is made to open a midi device. So I wonder what kind of device it > thinks it has. The behavior I'm seeing is very different in different applications. It'd be interesting to see all the different ways different software is trying to access the port, but I'm starting to see why this was never implemented. Maybe I will give up on this after all. -- - Brent Busby + =============================================== + "The introduction of a new kind of music must -- Studio -- + be shunned as imperiling the whole state, for -- Amadeus/ -- + styles of music are never disturbed without -- Keycorner -- + without affecting the most important political -- Recording -- + institutions." --Plato, "Republic" ----------------+ =============================================== |