|
From: Bernard B. <be...@lp...> - 2007-01-04 21:46:26
|
>OK ... yesterday I was trying to get some actual development done amidst all >of the release preparations and I was attempting to disable the built-in >MIDI driver at compile-time. Is this happening with the 2.9.5 version, or with the version in which this in-built MIDI driver code has been disabled? >One problem that I ran into is that if both OMS and the built-in driver fail >to open while BP2 is initializing, the program just exits. This is of >course easy to change, but my question is whether there will be any bad side >effects from just continuing with no enabled driver. I cannot give a precise answer because I don't have access to the source code via the compiler (until Monday). I need to check what the program does at startup. I know it installs interrupts and the time-scheduler which is perhaps (this I need to check) used for both the in-built and OMS MIDI drivers. >I found that if I turn off OMS with the built-in driver omitted that BP2 >hangs. Does this also happen if you start the program with "-se.startup" in which "Use MIDI in/out" would be off? >So I think there may be a great deal more to do to correctly disable >the built-in. It seems to me that BP2 should automatically disable >real-time MIDI when both drivers fail or are not present, but I don't think >it is. I need to check in the code. For the time being, leave the in-built driver as it is, if you can backtrack to that version, and I will send you asap athe list of all that is implied at startup. Bernard |
