VOGONS

Common searches


Search results

Display options

Re: does dosbox support MIDI IN yet?

Hi, To update on this: I haven't touched anything for a while. However I did not give up and will try to finish up the patch, and (finally) hook up the real mpu-401 that's sitting on the shelf here :) Hmm, it's already 3 years from when this message was posted, it's time to pick up and finish it. I …

Re: MIDI input patch

Hi, Yes, all the various patch versions are (AFAIR) on the sf.net, although I wouldn't call it finished. I did some more development and input code cleanup last year but eventually got sidetracked so it's sitting unfinished (and I didn't even visit Vogons for some time...). Probably will be getting …

Re: MIDI input patch

Conductor, used by many intelligent mode programs, allows to queue commands, like tempo change or turning on off various features, during playback. You can try, in Texture, to turn the metronome "on" during playback and see what happens if you then stop and start. Second issue was that sometimes …

Re: MIDI input patch

A non-debug build to test for timing (and everything else). Have fun. Also includes a cleanup of some parts mpu401 code and at few other places. Also locking scheme for input got improved, it is always good to be careful with that stuff (especially as it's harder to debug). I also noticed a minor …

Re: MIDI input patch

midioptions is correct. It's that way in latest iteration of the patch (that's on sf.net). Right, if mpu401 is configured to intelligent mode, but program initializes uart mode, input will be triggering first mpu401 irq and then a sb16 irq, displaying your message. Although it isn't practically a …

Re: MIDI input patch

Maybe it defaults to sound blaster based midi input for your application (sb uart). Try with midioptions=inputmpu401 in the midi section of dosbox.conf (other options are inputsbuart, inputgus and inputauto). SB16 input mode (as far as I remember :D) is on only if intelligent mode of mpu401 is off, …

Re: MIDI input patch

OK, here is a build which is identical except that the patch I posted here isn't included. If you will have timing and corruption problems with this build (as I expect), then we found the problem and I will post a formatted patch against CVS version and propose inclusion in CVS. Regarding input …

Re: MIDI input patch

It's not (only) midi status related. .cpp is source, of course. Try this build, it contains midi input patch, above change, and cakewalk fix. (source files changed from the last midi input patch version are in the archive).

Re: MIDI input patch

Yes, but MIDI uses a separate message for "note on" and "note off", and pitch band is just sent between those two. Then there is also MIDI "status"(which is also preserved even if there is a realtime messages between two notes). MIDI status means that you can omit first byte of the message if …

Re: MIDI input patch

OK, I didn't realize that you send actual 0xF8 (midi clock) messages out. that can certainly create problems with dosbox if your sequencer interrupts normal midi or sysex with realtime msgs. Here is description how realtime midi (0xF8-0xFF) should be handled: http://www.cotse.com/dlf/man/midi/ …

Re: MIDI input patch

I checked and sequencer plus actually uses UART mode. Only the driver, at loading, checks if there is intelligent mode, but later sequencer just sets UART mode with 0x3F and that's it. Does this app support midi input from mpu401? If yes, it is a first test case that uses mpu401 IRQ to input in UART …

Re: MIDI input patch

janfry: So I decided to give it a try, but I am not able to reproduce your issue. How exactly to record from a different location in Prism? dbarton: Which version of sequencer plus are you using? There is downladable "Gold" version, but this one uses UART mode. Anyway I'm completely confused with …

Page 1 of 15