midi

Is the 127 note values in MIDI musically significant (certain number of octaves or something)? or was it set at 127 due to the binary file format, IE for the purposes of computing? 127 = 2 7 - 1 It's the maximum positive value of an 8-bit signed integer, and so is a meaningful limit in file formats--it's the highest value you can store in a byte (on most systems) without making it unsigned. In the MIDI protocol there are status bytes (think commands, such as note-on or note-off) and there are data bytes (think parameters, such as pitch value and velocity). The way to determine the difference

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . I made some research and it seems that Javascript and MIDI are not going well together these days. At least so Google says. As stated in this topic: generating MIDI in javascript , it is possible to create a file, either in Javascript or

I've been contemplating (re)building an app on iPad for some time, where I would use objective-C and DSMI to send MIDI signals to a host computer. This is not bad (I mean, except for actually writing the app). Now I'm contemplating perhaps developing the app for Android tablets (TBA). In Java, what options are available for MIDI message communication? I'm quite familiar with javax.sound.midi, but then I would need a virtual MIDI port to send messages to the host. On the other hand, if the app were done in Adobe AIR, what options would I have available for communicating with MIDI? Obviously

I'm trying to use the receivedMIDINoteOn function to flash a UILabel when the sequencer is playing a note. I have tried using the AKMIDIListener protocol with no success. Also I have made a sub class of AKMIDISampler and send midi to it from the sequencer. It plays the midi but the receivedMIDINoteOn is not called. This is what I have in the init() of the conductor: init() { [ahSampler, beeSampler, gooSampler,flasher] >>> samplerMixer AudioKit.output = samplerMixer AudioKit.start() let midi = AKMIDI() midi.createVirtualPorts() midi.openInput("Session 1") midi.addListener(self) } The conductor

My c# application must use multiple identical USB MIDI interfaces which are all from the same manufacturer. In device manager, all devices appear with the same driver name / CLSID - only the PNPDeviceID is different. When I list all MIDI inputs / outputs (using MIDI-dot-net), they appear as follows: ACME-MIDI: Port 1 1- ACME-MIDI: Port 1 2- ACME-MIDI: Port 1 Unfortunately, those names are not always the same for the same device. The ports of device 1 appear sometimes as "ACME-MIDI: Port 1" and sometimes as "1-ACME: Port 1" (they change e.g. after a reboot). I have used different ways trying to

I am hoping to get notifications of note on/off events in a playing MIDI sequence to show the notes on a screen based (piano) keyboard. The code below adds a MetaEventListener and a ControllerEventListener when playing a MIDI file, but only shows a few messages at the start and end of the track. How can we listen for note on & note off MIDI events? import java.io.File; import javax.sound.midi.*; import javax.swing.JOptionPane; class PlayMidi { public static void main(String[] args) throws Exception { /* This MIDI file can be found at.. https://drive.google.com/open?id

I'm trying to dynamically generate a small MP4 audio+video file directly from my Android app. My original plan of attack: The user enters some basic song data (a chord progression, etc) and the app builds a MIDI file. The system builds chord diagrams for each chord, and using a MIDI reader it generates the animations frames array that is timed to the MIDI Convert the MIDI into a raw PCM audio data <-- this S.O. question is specific to this point Apply the raw audio to the animation frames - and encode the audio and video frames into an MP4 Provide the resulting MP4 video to the user with