Jump to content

Search the Community

Showing results for tags 'midi 2.0'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • News & Announcements
    • Product Release Info
    • Frequently Asked Questions
  • Cakewalk Products
    • Cakewalk by BandLab
    • Instruments & Effects
    • Feedback Loop
  • Community
    • Content
    • Tutorials
    • Songs
    • General Music Discussion

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 2 results

  1. MIDI Association Feb 23rd news on MIDI 2.0 MIDI 2.0 prototyping session at Winter NAMM 2019 At the MIDI 2.0 prototyping session at NAMM, a number of MIDI 2.0 features were demonstrated. There have been over 100,000 people who have visited the MIDI.org site in the past month viewing the information on MIDI 2.0. We have been monitoring the comments on various websites and wanted to provide some more information about MIDI 2.0. to clarify several points. ---------------------------------------------------------------------------------------- Will MIDI 2.0 devices need to use a new connector or cable? No, MIDI 2.0 is a transport agnostic protocol. -Transport- To transfer or convey from one place to another -Agnostic- designed to be compatible with different devices -Protocol-a set of conventions governing the treatment and especially the formatting of data in an electronic communications system That's engineering speak for MIDI 2.0 is a set of messages and those messages are not tied to any particular cable or connector. When MIDI first started it could only run over the classic 5 Pin DIN cable and the definition of that connector and how it was built was described in the MIDI 1.0 spec. However soon the MIDI Manufacturers Association and Association of Music Electronic Industries defined how to run MIDI over many different cables and connectors. So for many years, MIDI 1.0 has been a transport agnostic protocol. MIDI 1.0 messages currently run over 5 PIN Din, serial ports, Tip Ring Sleeve 1/8" cables, Firewire and Ethernet and all the different variations of USB cables. --------------------------------------------------------------------------------------------------------------------- Can MIDI 2.0 run over those different MIDI 1.0 transports now? No, new specifications need to be written for each transport. There is a new Universal Packet Format that will be common to all modern transports that will help make this work move quicker. The new Universal Packet contains both MIDI 1 .0 messages and MIDI 2.0 messages plus some messages that can be used with both. The most popular MIDI transport today is USB. The vast majority of MIDI products are connected to computers or hosts via USB. USB is the first target for MIDI 2.0. ---------------------------------------------------------------------------------------- Will MIDI 2.0 provide more reliable timing? Yes, and not only that the timing for MIDI 1.0 can also be improved. One of the new messages that can work with both MIDI 1.0 and MIDI 2.0 are Jitter Timestamps. Goals of JR Timestamps: -Capture a performance with accurate timing -Transmit MIDI message with accurate timing over a system that is subject to jitter -Does not depend on system-wide synchronization, master clock, or explicit clock synchronization between Sender and Receiver. Note: There are two different sources of error for timing: Jitter (precision) and Latency (sync). The Jitter Reduction Timestamp mechanism only addresses the errors introduced by jitter. The problem of synchronization or time alignment across multiple devices in a system requires a measurement of latency. This is a complex problem and is not addressed by the JR Timestamping mechanism. ---------------------------------------------------------------------------------------- Can MIDI 2.0 provide more resolution? Yes, MIDI 1.0 messages are usually 7 bit (14 bit is possible by not widely implemented because there are only 128 CC messages). In MIDI 2.0 velocity is 16 bit and the 128 control change messages, 16,384 Registered Controllers, 16,384 Assignable Controllers, Poly and channel pressure and Pitch Bend are 32 bit. ---------------------------------------------------------------------------------------- Can MIDI 2.0 make it easier to have microtonal control and different non-western scales? Yes, MIDI 2.0 allows direct pitch control of individual notes ( see video) More MIDI 2.0 info...
  2. At the MIDI Manufacturers Association (MMA) annual meeting during Winter NAMM 2020, MMA members unanimously adopted MIDI 2.0 specifications including: MIDI Capability Inquiry, Universal MIDI Packet (UMP) Format and MIDI 2.0 Protocol, MIDI CI Profiles Rules, MIDI-CI Property Exchange Rules, Property Exchange Foundational Resources and Basic Resources. Here's why that's big news for music technology. MIDI 2.0 Means Two-way MIDI Conversations MIDI 1.0 messages went in one direction: from a transmitter to a receiver. MIDI 2.0 is bi-directional and changes MIDI from a monologue to a dialog. For example, with the new MIDI-CI (Capability Inquiry) messages, MIDI 2.0 devices can talk to each other, and auto-configure themselves to work together. They can also exchange information on functionality. MIDI 2.0 gear can find out if a device doesn't support MIDI 2.0, and then simply communicate using MIDI 1.0. Higher Resolution, More Controllers and Better Timing MIDI 2.0 re-imagines the role of performance controllers, the aspect of MIDI that translates human performance gestures to computer data. Controllers (CC) are now easier to use, and there are more of them: over 32,000 controllers, including controls for individual notes. Enhanced, 32-bit resolution gives controls a smooth, continuous, "analog" feel. New Note-On options were added for articulation control and precise note pitch. In addition, dynamic response (velocity) has been upgraded. What's more, major timing improvements in MIDI 2.0 can apply to MIDI 1.0 devices. In fact, some MIDI 1.0 gear can even "retrofit" certain MIDI 2.0 features. Profile Configuration MIDI gear can now have Profiles that can dynamically configure a device for a particular use case. If a control surface queries a device with a "mixer" Profile, then the controls will map to faders, panpots, and other mixer parameters. But with a "drawbar organ" Profile, that same control surface can map its controls automatically to virtual drawbars and other keyboard parameters. A device can also map to dimmers if the profile is a lighting controller. This saves setup time, improves workflow, and eliminates tedious manual programming. Property Exchange While Profiles set up an entire device, Property Exchange messages provide specific, detailed information sharing. These messages can discover, retrieve, and set many properties like preset names, individual parameter settings, and unique functionalities. Basically, that means a MIDI 2.0 device will discover everything it needs to know about another MIDI 2.0 device. For example, Cakewalk by Bandlab could display everything you need to know about a synthesizer onscreen, effectively bringing hardware synths up to the same level of recallability as their software counterparts.
×
×
  • Create New...