Korg Forums Forum Index Korg Forums
A forum for Korg product users and musicians around the world.
Moderated Independently.
Owned by Irish Acts Recording Studio & hosted by KORG USA
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

MIDI 2.0, MIDI-CI, Profiles and Property Exchange

 
Post new topic   Reply to topic    Korg Forums Forum Index -> Latest News
View previous topic :: View next topic  
Author Message
Yuma
Platinum Member


Joined: 13 Jul 2011
Posts: 652
Location: The Netherlands

PostPosted: Wed Jan 29, 2020 3:05 pm    Post subject: MIDI 2.0, MIDI-CI, Profiles and Property Exchange Reply with quote

Details about MIDI 2.0™, MIDI-CI, Profiles and Property Exchange
_________________
|| My music ■■ How to embed Youtube and Soundcloud on this forum ||
|| Korg Kronos 61 (with upgrade kit) ■■ Korg PadKontrol ■■ Cubase 5 ||
Back to top
View user's profile Send private message Visit poster's website
bpoodoo
Junior Member


Joined: 27 Dec 2019
Posts: 97
Location: Dallas, TX

PostPosted: Wed Jan 29, 2020 4:35 pm    Post subject: Reply with quote

After 37 years, I suppose it's time for an version update.

Looks OK from the 10,000 ft. bird's-eye view. Devil could be in the details and in the consistency of implementation among manufacturers. The introduction of bidirectional communication introduces the possibility of deadlocks, timeouts, etc. And I would rather they had specified XML (simpler) instead of JSON for Property Exchange. Debugging MIDI 2.0 data will likely require more than just a byte-level viewer.

Goodbye 5-pin serial cables and connectors (except for backwards compatibility). "Unless/until that plan changes, 5 pin DIN will only support the MIDI 1.0 Protocol."

Progress!
_________________
bpoodoo
Triton Extreme 88 w/MOSS
In the Attic: Casio CZ-101, Roland MT-32, Yamaha RX-21
Gone but not Forgotten: Ensoniq VFX-SD, Roland Super JX-10
Back to top
View user's profile Send private message
Mr_SamDoogie
Full Member


Joined: 01 Jan 2014
Posts: 224
Location: Netherlands

PostPosted: Wed Jan 29, 2020 6:35 pm    Post subject: Reply with quote

bpoodoo wrote:


And I would rather they had specified XML (simpler) instead of JSON for Property Exchange.
Progress!


Feel the same way about that wonder how that though process developed and why cause it seems its just the beginning.
_________________
In honor of the Groove and to all whom surrender to it, We say Thank You. And we take it Back.

Korg MW1, Casio PX5S & XW-G1, Roland JD-Xi,Yamaha Montage 7, Roland D-05, Bass Station II, Cubase Elements, Sonar X3 Producer.Handfull of IOs Apps iMPC,Animoog : Korg IMS-20,Module, IM1, Gadget etc.
Back to top
View user's profile Send private message
fomalhaut



Joined: 06 Jan 2015
Posts: 36

PostPosted: Wed Jan 29, 2020 7:03 pm    Post subject: Reply with quote

I don’t want to start a flame war but why do you think XML would be a simpler solution vs JSON?
Back to top
View user's profile Send private message
Bachus
Platinum Member


Joined: 23 Apr 2006
Posts: 2733

PostPosted: Wed Jan 29, 2020 7:18 pm    Post subject: Reply with quote

The standard is around for quite some time now
Seems only Roland is interested in making this work
_________________
Korg Kronos 2/88 , Korg PA4x, Mainstage3 +VSTsu, Kurzweil PC3X
www.keyszone.boards.net
Back to top
View user's profile Send private message
bpoodoo
Junior Member


Joined: 27 Dec 2019
Posts: 97
Location: Dallas, TX

PostPosted: Thu Jan 30, 2020 12:45 am    Post subject: Reply with quote

fomalhaut wrote:
I don’t want to start a flame war but why do you think XML would be a simpler solution vs JSON?


Both are certainly capable of representing structured data, not just a stream of bytes. If you can read and edit HTML, you can read and edit XML. XML is a familar syntax and general-purpose for representing data or document content. JSON I'm sure would work fine too. XML or JSON is an implementation-specific choice that seems to have been made early. It describes how the data is to be represented.

The more important decision, and what is germane to a MIDI 2.0 standard, is agreement on what data is to be represented, what is required, what is optional, etc.
_________________
bpoodoo
Triton Extreme 88 w/MOSS
In the Attic: Casio CZ-101, Roland MT-32, Yamaha RX-21
Gone but not Forgotten: Ensoniq VFX-SD, Roland Super JX-10
Back to top
View user's profile Send private message
bpoodoo
Junior Member


Joined: 27 Dec 2019
Posts: 97
Location: Dallas, TX

PostPosted: Mon Feb 03, 2020 7:42 pm    Post subject: Reply with quote

I wonder if the 31.25kbps data rate specification from MIDI 1.0 is going away in MIDI 2.0? It certainly is slow by today's standards, but it did provide guidance to manufacturers for the maximum data rate both their hardware and software designs needed to support.
_________________
bpoodoo
Triton Extreme 88 w/MOSS
In the Attic: Casio CZ-101, Roland MT-32, Yamaha RX-21
Gone but not Forgotten: Ensoniq VFX-SD, Roland Super JX-10
Back to top
View user's profile Send private message
Poseidon
Senior Member


Joined: 08 Jul 2018
Posts: 372

PostPosted: Wed Feb 05, 2020 7:45 am    Post subject: Reply with quote

To implement MIDI-CI and MIDI 2.0, you need a manufacturers SysEx ID. The fee is $US 250 a year.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Korg Forums Forum Index -> Latest News All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group