Excellent

I suppose there really isn’t a guarantee that a MIDI innovator would also know how to do a good sound mix.

@23:22 - Does Mike not understand that WiFi is just another network node? Why would it need further development past what's already being done???

this sounds like a very cheap keyboard

it's only a matter of time before someone does the old photocopier thing.

cool, nice to see newer videows from 1 ay ago be reccomended to me

extremely cool

Quiero hacer uno!! Compartes los planos?

Love this! Divergent thinking! You've reimagined sheet music.

I am certain this was already used in the 70s. It sounds like all that experimental audio in terrible film strips.

This would be an interesting way to scrub through samples, too.

I want to go to Stevie Wonders Meet and Greet where is it and how do I get to meet Stevie Wonder? He told me to find it online with his manager. How do I get to go there?

What are the accepted forms of query to one's equipment manufacturers getting them on-board w/MIDI 2.x Functionality onto Legacy Firmware in the events when the hardware always had its prerequisites all along in prescience? in Windows? a top half-a-bakers dozen would be great? thnx MIDI 2.0, its DocuMentors, Dev, and mgmnt team

thanks for featuring drumbeam in your report! we are so excited to release it later this year <3

The only realy interesting report I saw from Superbooth. I did not appear there, and I live in Germany. Anyways for next years interviews will be nice to setup a better interview equipment or reduce the crowd noise arround…

I hear the Sheer Childish Glee along with hugely expansive and mutually expressive unadulterated pleasure this brings to us all through Scott Tibbs' Piano Voicings herein. Thanx MIDI, was here with you in MPU-401 Daze. Yay for MIDI 2.x!

Unfortunately no, but perhaps they are waiting on the release of the Windows Open Source driver which is already in the hands of developers with a public release expected after testing is completed. You can help by reaching out directly to BandLab and encouraging them to support MIDI 2.0.

I've been a Cakewalk (Bandlab) user since the late 80s - did any of that team show up?

Excellent!

Last year before the new midi 2.0 clip file format was announced i had designed a similar in goal container format for my application usecase with in some ways similar goals to this. I'm very disappointed to hear that they are considering going the zip file route so many formats have moved towards over the years. In my eyes using a compression first format such as zip is a mistake, if one of the stated goals is to include asset data including audio and video data those formats are much better (and nore often) represented in a format specific compression format. Using zip compression for non-text potentially primarily audio/video data is just not good to me. Additionally embedded usecases for the format will suffer.

what about small processor designs that for example write/read from an SD card, zipping will cause a lot of complexity and code overhead for such devices that normally don't have support for compressing data or zipping/unzip files. Zip libraries may have bugs or become obsolete as well. it would be helpful to have a single uncompressed container file format such like legacy MIDI 1.0 has.

wow !

Smells like IPv6

Placing an arbitrary (private) data of a DAW (or Sequencer) is ALREADY implemented in SMF0, but 93% of old/modern “SEQUENCERS” (including DAWs) destroy them (can't handle SMF Sequencer Specific Meta Events)! Open a "MIDI 2.0 file" (which contain MIDI 1.0 compatible data) in that "program" then whatever you edit it or not - you are already LOST that data (even before saving it)! Some DAWs even have no System Exclusive events support (FL, Ableton, S1, Bitwig, …)! YAMAHA XF Chords may be placed outside the MTrk as a "junk chunk" (or a separate file, i.e. not included in the .mid file), but there is no "manifest" indicating it (but described only with a SMF Sequencer Specific Meta Event), YAMAHA SFF (Style File Format) contains more "junks" outside a first MTrk (CASM, OTSc, MDB, …) - all those "JUNK-chunks" in .MID files destroyed by 99% of all "sequencer(DAW)s"! /// XML? Who want to mess up with this aesthetic displeasure (especially for a musician)? I was very satisfied with that an old [INI] (but please, not TOML), which old Unreal Engine 1|2|3 use it… /// Notation? What about drums? /* [*]I've "invented" a clef for Drum-Machine|Sampler|Rompler… it looks as "some kind of a chip", linked with a "wire" from the left-bottom of staff line, where a small "rect" is placed)[*] */ assign a note position in a 12-line staff, a head (character), stem/beam direction, a "closed"/"opened"/whatever… hm… /// “video: how it relates to MIDI data and how it's synchronized”- is it possible to INCLUDE a stretching algorithm inside the "MIDI 2.0" file? O_o /// P.S. SMF0/1/2 are already nicely compressable, will this new container (chunk) already compressed (PK…)? Ouch… will an old "SMF2" (Multi-SONG) be called "SMF1.1" ? :))

Good demo Cory! I was thinking of what I would like for the next iteration of tones.... for me it would be even more faithful/accurate instrument tones. MIDI has gotten progressively better at that and I suspect having a higher bit sample range would be the big improvement. I am not sure what the bit range is now on my Roland but suppose it is 8 bit.... by doubling that to 16 bit or 16 bit to 32 bit would make a dramatic improvement. The problem is that when playing several notes at the same time on bass and treble, there is a limited maximum it can handle so that would require a next level of chips and computing power on the accordion. Sounds like a wish list for the Roland 9x ;-)

It should also be mentioned that there are many others actively involved in the creation of the Network MIDI 2.0 specification. The panel is a subset of (great) folks. :)

The plan for Windows is to integrate Network MIDI 2.0 into Windows MIDI Services as just another transport like our USB MIDI 2.0, Virtual Loopback 2.0, Virtual Device 2.0, and BLE MIDI 1.0 transport implementations. Apps will then use them like any other connection to a MIDI device, and won't need to have any explicit support for Network MIDI 2.0.

Hi guys! Great panel! Looking forward to see the specs approved and released.

Thanks for sharing ! This sounds very promising. I'm still using the long abandoned Copperlan for my Midisetup as it easily allows to extend my setup and comfortably route midi from any device to any device. But its reaching EOL as i already to run the Editor in a VM on a recent macs. So i'm really waiting for new solutions with Midi over Ethernet.

Nettes an Tasting Video Nice tosee that Some Person are working and Helping usto get more Accessibility to the Jeans that very Neis I hope in the Future. All global Players like Yamaha Cork and Roland will Jump on Two😂

"promosm"

It is such a great instrument

I'm very pleased and encouraged that this conversation took place. I've had a lifelong interest in audio and music production but have run into enumerable obstacles either through software inaccessibility, lack of opportunities, and competitive attitudes of industry professionals. It has only been in the past two years that I have begun to find a handful of tools that work for me, and have finally been moving forward a bit. I have signed up to the MASIG and hope this will lead to opportunities to connect directly with developers and companies. I have tried contacting various companies through standard web forms to offer advice and sugestions for future versions, but they have all gone unanswered. Thanks again.

Where is he?

So good that these products are being developed for all users. Great talk and very informative.

Finally!

This video isn’t a demonstration of MIDI 2.0 technically as pitch bend per note hasn’t changed in 2.0. It’s a demo of MPE, which was a late addition to the MIDI 1.0 spec, although it’s been updated for 2.0 including a high resolution control for CC74 or Brightness and Channel Pressure. MIDI CI is taking over for the sender and receiver configuration I believe. MIDI 2.0 is a 14-bit spec, where 1.0 was a 7-bit spec. 2.0 includes MIDI-CI, which is a bidirectional communication protocol that allows auto-configuration between hardware controllers and VIs. 14-bits gives you 16,348 steps instead of just 128. That’s 2 to the 7th power vs 2 to the 14th power.

NICE JOB! Thank you for moving the music forward.

sorry, i hate shorts, desub.

Perfectly put. That's why a lot of electronics from a lot of different brands that each have their own different functions use the same cables, plugs, programming languages, etc. Standards in Computer Science make technology extremely streamline as it is today.

Just a consumer so forgive me if this seems obvious. If I have a NI Kk mk3 keyboard which supports midi 2.0 and I have Cubase 13 pro which supposedly is midi 2.0 capable and I install the libraries from github will the two be able to interact using midi 2.0? Or do I need to wait for Cubase to release an update using these libraries? Also, importantly can it break the standard windows midi implementation?

One kind of extra data I could see as being very useful to include in MIDI containers is plugin patch data, i.e. parameter value sets, possibly including samples or impulse responses etc. referenced by these patches.

Please keep embedded devices and microcontrollers in mind, when standardizing the container format. IMO XML is too complex and insecure and needing an XML parser just to parse the container manifest would be overkill.

How does he do those freaking bass lines?!?!?!?!?!?!??!?!

The links mentioned in this video: Windows MIDI Services github.com/microsoft/MIDI Linux MIDI 2.0 Kernel and ALSA drivers docs.kernel.org/sound/designs/midi-2.0.html MIDI 2.0 Developer Collaboration GitHub including Workbench and various llibraries github.com/midi2-dev MIDI 2.0 Example code github.com/bome/midi2

De très bons modules 🎹👍. Par contre les démos sonores mélangées avec le son d'ambiance en direct n'est pas bon.

interesting layout of notes, chromatic horizontally, major thirds vertically