Re: [LAD] MIDI 2.0 is coming
On Tue, 29 Jan 2019, Kevin Cole wrote: Never one to fear displaying my ignorance / laziness... In my limited readings, I had gotten the vague impression that OSC was sort of MIDI 2.0. Does MIDI 2.0 incorporate OSC or will they remain two distinct paths? Certainly OSC is a step beyond MIDI 1.0. But it has never been backwards compatable with MIDI 1.0 and does not try to negotiate for OSC and fall back to MIDI if it can't. OSC has next to no standards beyond transport which might explain its failure in the commercial world. Each OSC application makes up it's own set of commands. MIDI 2.0 still has a large number of predefined commands... larger than midi 1.0. However, the biggest reason it is not midi 2.0 is that it was not released by MMA... -- Len Ovens www.ovenwerks.net ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] MIDI 2.0 is coming
Kevin Cole wrote: > In my limited readings, I had gotten the vague impression that OSC was sort > of MIDI 2.0. OSC is similar to MIDI, and some parts could be translated from/to MIDI, but it is not compatible with MIDI. Regards, Clemens ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] MIDI 2.0 is coming
Never one to fear displaying my ignorance / laziness... In my limited readings, I had gotten the vague impression that OSC was sort of MIDI 2.0. Does MIDI 2.0 incorporate OSC or will they remain two distinct paths? ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] MIDI 2.0 is coming
On Tue, 29 Jan 2019 13:37:01 +0100 (CET), Jeanette C. wrote: >why should I use Linux and LV2 plugins, if they don't work with my >$1000 control keyboard? There's always hope. From the link posted by Louigi: "[snip] With previous MIDI feature additions, the challenge has often been getting companies to actually implement it. Take MPE [1] as an example – despite being officially adopted in 2018 to the MIDI spec, only a handful of companies (like ROLI and Moog) have added it to commercial products [snip]" [1] From https://www.midi.org/articles-old/midi-polyphonic-expression-mpe: "[snip] Music making products (such as the ROLI Seaboard, Moog's Animoog, and Apple's Logic) take advantage of this so that musicians can apply multiple dimensions of finger movement control: left and right, forward and back, downward pressure, and more. [snip]" I mentioned the Animoog's touch screen feature in the the LAU thread about Dominique's DIY Theremin. A song that still is in progress has short parts with something similar to a Theremin played via touch screen, using the Animoog. It's impossible to record by MIDI now, maybe Logic could do, but neither the iOS, nor the Linux software I'm using is able to record and play it via MIDI. I guess that Animoog even doesn't send the required data. I had to record it as an audio track over and over again. However, even the Animoog's special "keyboard" couldn't do the whole job, to get a better spooky Theremin howling sound I needed to add a little bit of a TalkBox effect and important to this thread, I had to rework the Theremin alike audio track using volume automation. If it would have been possible to use MIDI instead of an audio track, it would have been possible to move notes a little bit forward and backward instead of playing it again and again, but it still would have require to do some rework. Programming the used sound to use up and down movements of the finger to either do the desired howling or to allow volume control, would have been possible, but it would require to learn how to do it. I purchased a lot of proprietary virtual synth with a lot of features neither old fashioned digital, nor analog synth provide. Sometimes programming sounds using those new synth is easy to do, but often it has got a learning curve that IMO isn't worth the effort. IMO it's better to spend time to improve the skills to play a real instrument, this gains more to make good music, than learning how to program each gimmick, that doesn't gain as much as people guess. I like to get MIDI 2, but as pointed out by the QjackCtl GUI thread, it would be more important if virtual synth would care about e.g. MIDI 1 clock to sync delays, LFOs etc., something a lot of proprietary synth already do, but that is still completely missing for Linux. Host integration of virtual synth still needs to be improved especially for Linux FLOSS , but still for proprietary software for other OS, too. IOW I'm sceptic that MIDI 2 does solve much, since there are easy to use MIDI 1 features already ignored, such as using MIDI clock to sync LFOs of synthesizers. It's comparable to politicians sharpening laws, that are already sharp enough, but suffer from other issues such as bureaucracy or something else caused by reality. Sharpening a law that isn't/can't be used, doesn't solve an issue. Regards, Ralf ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] MIDI 2.0 is coming
Jan 29 2019, Louigi Verona has written: So, they just recently announced that MIDI 2.0 has entered the prototyping phase. Looks like it's getting serious! Here is some coverage, for example: https://djtechtools.com/2019/01/23/midi-2-0-is-coming-prototyping-of-new-generation-of-midi-devices-underway/ What do you guys think? What are the expectations here? Implications for Linux Audio? ... I am not a developer, as such, but I can see an obvious degree of openness and better integration with proprietary products. Additionally, I see a great chance for accessibility, in every sense of the word. New hard- and software products could find better integration wit Linux DAWs and accessible editors would be so much easier. Programming a certain type of interface for MIDI 2.0 "devices" would be very rewarding, in that they can, hopefully, support a wide range of "devices" in one go. Why a text based editor for one or two synths? Why a special OSC implementation for one controller? But there's good reason to write a text-based editor for a whole group of synths in one go or implement MIDI 2.0 controller support in a DAW. Also, why about other completely closed protocols? If they did their job well, I think there's hope for more usage of MIDI 2.0 instead of developing specialised systems. I guess that such design is not only expensive, but also costly. Even maintaining your own existing protocols and extending them in time must be cumbersome. But maybe I'm kidding myself here. :) Also, why shouldn't the other way work as well? If open software developers for Linux specific plugins and stand alone software support MIDI 2.0, one could use a much larger palette of nice hardware to control them. The reverse psychology: why should I use Linux and LV2 plugins, if they don't work with my $1000 control keyboard? There's always hope. Take it with a pich of salt, more of an opinion and a hope than well-founded reasoning. Best wishes, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * SoundCloud: https://soundcloud.com/jeanette_c * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * GitHub: https://github.com/jeanette-c * Twitter: https://twitter.com/jeanette_c_s Don't worry, you're gonna be alright, But Cinderella's got to go <3 (Britney Spears) ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] MIDI 2.0 is coming
So, they just recently announced that MIDI 2.0 has entered the prototyping phase. Looks like it's getting serious! Here is some coverage, for example: https://djtechtools.com/2019/01/23/midi-2-0-is-coming-prototyping-of-new-generation-of-midi-devices-underway/ What do you guys think? What are the expectations here? Implications for Linux Audio? Louigi Verona https://louigiverona.com/ ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
