Hi -- the MIDI 2 Scope application is not yet (April 2020) available for download, as the MMA is still working out some details before that happens. I expect that the release of this and other developer tools including the MIDI-CI workbench will be publicized here.

Hi Brett- it's been some months and in the meantime the MIDI 2.0 Spec has been finalized. Is there any progress on releasing MIDI 2 Scope ( and ideally the source code? 😉 )

MIDI Scope is currently only available on the github for corporate members of the MIDI Association.

MIDI Scope is currently only available on the github for corporate members of the MIDI Association.

By MIDI Association you mean the MMA.

That is unfortunate. But the consequence is that we, open source developers, are going to release new versions of our products for the time being without supporting the MIDI 2.0 specification, as we are not able to test it. For me, it would be in the best interest of the MMA members to incentivate the release of open source synths, and all kind of open source tools leveraging the new specification...

In my opinion, this is the same mindset as before the MIDI Association, when the specifications were behind a paywall. Now the specifications are available for download to everybody associated, but the test tools are not. It has sense that the MMA members could enjoy some advantage to release industrial products conforming the MIDI 2.0 specification, but the fact is that there are very little amount of MIDI 2.0 products out there in 2021 yet. The only product that is marketed as "MIDI 2.0 ready" is an expensive Roland controller, but what is a MIDI controller without at least one MIDI Synth to talk to?

Promise of Vast Improvements… But It Might Take Awhile

I want to strongly echo Pedro's comments. As an open source developer of music software and hardware.... keeping the test tool reserved for corporate members just means that my work will not support MIDI 2.0.

I can't imagine what the benefit to corporate members is by this approach? There are many many MIDI music things out there made by non-corporate entities that get a lot of use. MIDI libraries for Arduino; music systems like SuperCollider, Pd, and Tidal; hardware controllers of all sorts..... Where is the downside to having these things interoperate with new commercial MIDI 2.0 gear? If there is some rationale for the closed stance... please be transparent with it.

Hello,

The topic of Open Source developers has been under discussion for quite awhile inside The MIDI Association. We understand that Open Source developers are fundamentally different in the way they operate than for profit companies. We are planning on discussing this in depth in an MIDI Association annual planning session open to all MIDI Association corporate members scheduled for the beginning of February.

There is a mechanism within the organization that could work for Open Source developers which is a Special Interest Group. we have had one for the Game industry (the Interactive Audio Special Interest group) for many years. An Open Source Special Interest group could be granted access to the Github development tools. However this is not a decision that the MIDI Association Executive Board or Technical Standard Board could make on their own.

As it affects the rights of the current membership, it would probably need to be voted on by the membership as whole.

So please, continue to have this important conversation here as there are many corporate members of the MIDI Association who support developing a specific policy for Open Source developers.

As an organization we would still want to have some control over access to our Github which would include registration by anyone accessing it. Also Special Interest groups like the IASIG sometimes have a small membership fee to cover administrative costs.

In any case, we are here and we are listening so please continue to comment and discuss.

Hey,
I am an open-source developer. I am still on the edge if I should try to go the MIDI 2.0 route.

Some time ago you said:

We are planning on discussing this in depth in an MIDI Association annual planning session open to all MIDI Association corporate members scheduled for the beginning of February.

I am wondering, are there any updates? Thank you.

As an organization we would still want to have some control over access to our Github which would include registration by anyone accessing it. Also Special Interest groups like the IASIG sometimes have a small membership fee to cover administrative costs.

How much did you pay JUCE for using their framework, out of interest?

Any updates? zzz

There is no download for MIDI Scope or MIDI Work Bench yet.

The main reason is that MIDI Association corporate members have only recently been able to test things with Apple Monterey and Google Android.
As the organization that is responsible for making sure that not only MIDI 2.0, but even more importantly MIDI 1.0 still works, we have to prototype and valid all tthe work that we have done among our members before we release code and applications to the the general developer community.

Although we understand the frustration, we know the work we have been doing and the plans we have for the future.

We will be announcing some of those plans soon and you may want to keep an eye out on the MIDI Innovation Awards for new entrants in the next few weeks.

Entries close on April 30th so we are literally talking about two weeks.

> The main reason is that MIDI Association corporate members have only recently been able to test things with Apple Monterey and Google Android.
> As the organization that is responsible for making sure that not only MIDI 2.0, but even more importantly MIDI 1.0 still works, we have to prototype and valid all tthe >work that we have done among our members before we release code and applications to the the general developer community.

as developer with both corporate (software architect at native instruments) and open source (former maintainer of supercollider) interests i strongly disagree with this statement, but rather recommend a "release early, release often" or "technical preview" approach. the current approach of only providing tools to corporate members is detrimental as it prevents adoption of the midi 2.0 standard by applications and causes a chicken-and-egg problem

best regards,
tim