About: MIDI choke   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

The condition that occurs when a MIDI sender, such as a sequencer, tries to send data at a rate exceeding what the cable is capable of transmitting. Although the data rate on a conventional MIDI cable is not fast by today's standards, it is still capable of sending about 1000 note on or note off messages per second (more if running status is used), so MIDI choke conditions usually are caused by other things: excessively dense Continuous controller data, or particulary System exclusive data. Most sequencers have a facility to "thin" controller data so that less data is sent without effecting the audible result, and often system exclusive transmissions can be rearranged and sent at different times to avoid the choke. When setting up a song in a sequencer, it is good practice to reserve one o

AttributesValues
rdfs:label
  • MIDI choke
rdfs:comment
  • The condition that occurs when a MIDI sender, such as a sequencer, tries to send data at a rate exceeding what the cable is capable of transmitting. Although the data rate on a conventional MIDI cable is not fast by today's standards, it is still capable of sending about 1000 note on or note off messages per second (more if running status is used), so MIDI choke conditions usually are caused by other things: excessively dense Continuous controller data, or particulary System exclusive data. Most sequencers have a facility to "thin" controller data so that less data is sent without effecting the audible result, and often system exclusive transmissions can be rearranged and sent at different times to avoid the choke. When setting up a song in a sequencer, it is good practice to reserve one o
dcterms:subject
abstract
  • The condition that occurs when a MIDI sender, such as a sequencer, tries to send data at a rate exceeding what the cable is capable of transmitting. Although the data rate on a conventional MIDI cable is not fast by today's standards, it is still capable of sending about 1000 note on or note off messages per second (more if running status is used), so MIDI choke conditions usually are caused by other things: excessively dense Continuous controller data, or particulary System exclusive data. Most sequencers have a facility to "thin" controller data so that less data is sent without effecting the audible result, and often system exclusive transmissions can be rearranged and sent at different times to avoid the choke. When setting up a song in a sequencer, it is good practice to reserve one or two bars of silence ahead of the first note, and use this period to send long sysex sequences, such as those that transmit patch data to a synth, so that these sysex strings don't conflict with note data while the song is playing.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software