New answers tagged

0

What do you mean by "16 step sequencer"? There's hardware 16 steps sequencer (eurorack stuff, drum machines, external sequencers) where you can select the pulse other than 4PPQN, to be compatible with hardware that have another PPQN value. PPQN can be relative measurement unit for int/ext sync signals, and it can be a "event time resolution", too. 4PPQN ...


2

Yes. Not sure what else I can say…


2

So far as the MIDI data is concerned, none of the meta messages are necessary, but they are useful when converting the MIDI to music staff notation. The key signature is important for defining the correct "spelling" of the notes - for example whether MIDI note 61 should be written as a C sharp or a D flat. It makes no difference to the sound, but the "wrong"...


3

The MIDI specification says: Device Inquiry The following two messages are used for device identification, and are categorized as Non-Real Time System Exclusive General Information messages (sub-ID#1 = 06). The format of the inquiry message is as follows: F0 7E <device ID> 06 01 F7 F0 7E <device ID> Universal System ...


1

If you're trying to identify a device, you're probably better off with the super crude string you get from the operating system. Even the device ID on windows can switch out on you if you disconnect USB and reconnect. And all you'll get back from a sysex is a manufacturer dependent set of binary numbers. On windows api it's midiInGetDeviceName or mmmmm, ...


1

I'm not sure, what you want to do later with that information, but looking at Standard MIDI-File Format Spec. 1.1, a META EVENT definition could be the solution: Cited explanation: FF 01 len text Text Event; Any amount of text describing anything.


1

piano pieces are easier to play on an unweighted board, trills, arpeggios and runs are much easier and less stressful on the muscles in your hands(older musicians typically have arthritis in their hands due to years of stress being put on them as a result of playing weighted keys and therefore typically can't perform as good as they used to), touch ...


0

asynchronous in type 2 means that each track is an independent sequence : type 2 track are not meant to be played simultaneously. This differs from type 1 where tracks are meant to be played simultaneously. In type 1, timing of each track starts at zero time. Type 1 often has a "tempo track" as first track containing all tempo information. I've not seen type ...


2

It's unknown MIDI event indeed. I'm the author of DryWetMIDI library. Here you can see all standard events status bytes: https://github.com/melanchall/drywetmidi/blob/develop/DryWetMidi/Core/Events/Info/EventStatusBytes.cs.


Top 50 recent answers are included