So I finally got around to installing midiIN

http://aminet.net/search?query=midiin

As fate would have it, it does not seem to recognize my MIDI keyboard at all, where as OctaMED has zero issues interfacing with my keyboard, though of course in OctaMED's case I am going MIDI out, where as with midiIN I'm trying to go MIDI in. I have my cables plugged in as they should be. OUT from keyboard, IN on the Amiga MIDI interface. All the settings are at default and should be ready to go, but when ever I press keys on my keyboard...

...nothing happens at all.

Anyone have experience with this app?

Anyone have experience with this app?

Yes.

First things first, you really need a dedicated machine to run it as it takes over the audio and won't play nice with any other apps that try to.

Secondly, you have to load samples into it's sample bank and map them to channels / note ranges. Once you have done all this gubbins, you can save the configuration for loading later.

Screenshot of it running on my actual machine

KarlOS: I loaded samples, figured I needed them, but still nothing. Is there something more I need to do?

KarlOS: I loaded samples, figured I needed them, but still nothing. Is there something more I need to do?

First of all, if you open the window with the big piano gadget on it (see screenshot), does it play sounds when you click on any of the piano keys?

If so, make sure that the MIDI checkbox in that window is enabled.

Loading samples alone is not quite enough. Each sample needs to be assigned to a MIDI channel and note range. The idea is that you can use multisamples and so on. I forget off the top of my head how you set this up. However, the amigaguide manual that should have come with it explains this IIRC.

If I get a chance I'll fire it up and see if there's any obvious settings you need to apply.

Ah, I think I remember now. The SET is used to specify the keyboard range that you can play that sample on.

In the screenshot in the post above, I mapped a collection of Mellotron choir samples across a 4 octave range. The samples were split into every A, C, D# and F#. So I made each one the centre of a 3 semitone range (except for the top and bottom), as follows:

F#2 from C2 to G2
A2 from Ab2 to A#2
C3 from B2 to C#3
D#3 from D3 to E3

F#3 from F3 to G3
A3 from Ab3 to A#3
C4 from B3 to C#4
D#4 from D4 to E4

F#4 from F4 to G4
A4 from Ab4 to A#4
C5 from B4 to C#5
D#5 from D5 to C6

Having gone through the ball ache of configuring that, I saved it off and now recall is just an ASL requester away

Regarding capture, MIDI In is not a sequencer, it's just a software sampler. If you want to use it to create any tunes, you need to use it as a slave to another machine running say OctaMED.

If you recall this:


Basically, the towered A1200 is running MidiIn and the desktop one is running OctaMED and controlling it over MIDI.

The MIDI tracking feature in midiIn is, as I recall, just to make the UI sliders (Pitchbend etc) and stuff update with the incoming MIDI data.

If that is the case, I don't understand how it works as it only allows me to click on one Key.

Have you tried clicking and dragging? Or shift-clicking?

WRT to not playing properly, do you mean it is distorted or just played at completely the wrong speed? IIRC, MidiIn expects samples it loads to have the correct recording frequency saved in their meta data. Samples saved from many tracker's inbuilt sample editors, often don't and just use whatever playback frequency "C-2" maps to (or similar).