News for hackers. Stuff that matters.
Re:MIDI 2.0 Prototyping announced by kensai on Saturday January 19, 2019 @05:36AM (#18946339)
Why it is important in one paragraph:

“The MIDI 2.0 initiative updates MIDI with auto-configuration, new DAW/web integrations, extended resolution, increased expressiveness, and tighter timing -- all while maintaining a high priority on backward compatibility. This major update of MIDI paves the way for a new generation of advanced interconnected MIDI devices, while still preserving interoperability with the millions of existing MIDI 1.0 devices. One of the core goals of the MIDI 2.0 initiative is to also enhance the MIDI 1.0 feature set whenever possible.”

Re:MIDI 2.0 Prototyping announced by mastazi on Saturday January 19, 2019 @06:07AM (#18946421)
This is fantastic news, I can’t wait to have CC parameters with more than 128 levels. Does anyone know what the new resolution for CCs will be?
Re:MIDI 2.0 Prototyping announced by aasasd on Saturday January 19, 2019 @07:28AM (#18946693)
Open Sound Control has that, but support for the format is very selective.
Re:MIDI 2.0 Prototyping announced by mastazi on Saturday January 19, 2019 @09:59AM (#18947343)
Good point, OSC is pretty good I should invest some time looking into it
Re:MIDI 2.0 Prototyping announced by PascLeRasc on Sunday January 20, 2019 @08:05PM (#18956740)
If you're looking for information on OSC, I'm currently in a computer music class and we have a section on it: http://www.cs.cmu.edu/~music/cmsip/slides/06-networks.pdf
Re:MIDI 2.0 Prototyping announced by jcelerier on Saturday January 19, 2019 @01:00PM (#18948226)
if you want to check out a nice OSC project I invite you to test https://ossia.io the OSC sequencer I'm developping
Re:MIDI 2.0 Prototyping announced by shagrath on Saturday January 19, 2019 @07:13AM (#18946636)
They wrote 32 bits on the website (against 7 in the current spec)
Re:MIDI 2.0 Prototyping announced by phkahler on Saturday January 19, 2019 @08:47AM (#18947012)
32 seems excessive.
Re:MIDI 2.0 Prototyping announced by TheRealPomax on Saturday January 19, 2019 @12:34PM (#18948072)
Why? 64 bit chips are dirt cheap these days, if anything it's surprising they went for 32 bit instead of just going for 64 to buy the protocol one or more decades of "no one's going to run into the limitations of that".

Don't design it for what humans expect, design it for what the machines that need to talk to each other operate on. In that sense, 32 bits is the bare minimum you want in a new spec.

Re:MIDI 2.0 Prototyping announced by phkahler on Sunday January 20, 2019 @04:53PM (#18955841)
Because MIDI has very low bandwidth. People in complex environments doing complex things saturate it already. The new version may somehow allow higher bandwidth but it wants backward compatibility as well. We'll see, I'm sure this version will be better and I hope it becomes more popular again.
Re:MIDI 2.0 Prototyping announced by chillingeffect on Saturday January 19, 2019 @08:45PM (#18950428)
because the intent of a CC is to emulate a knob on a synth .

A synth knob turns a little less than 360 degrees. While 7 bits doesn't give quite enough resolution to have one degree per code, 32 bits would give 11 million codes per degree. Even a thousand codes per degree would suffice... but 11 million?

There would also be no analog to digital converter that could measure much more than 24 bits with any accuracy whatsoever.

And if you were to use your proposal of "just going to 64" it would multiply the space between the existing 11 million values between every degree on a knob by 4 billion. That would have 44 trillion variations of knob control. No one can sense that. if the knob was used to modulate e.g. LFO speed, it could send changes that wouldn't even be heard for millions of years.

Re:MIDI 2.0 Prototyping announced by boomlinde on Sunday January 20, 2019 @07:08AM (#18952667)
> because the intent of a CC is to emulate a knob on a synth .

The intent of CC is to facilitate control changes. Higher range means greater flexibility in what exactly this means. Just off the top of my head I can think of at least one realistic application where 360000 discrete steps simply wouldn't suffice but a higher range control protocol would be useful: precision audio seeking, because recorded audio used in music is often longer than 360000 samples.

Re:MIDI 2.0 Prototyping announced by peterlk on Saturday January 19, 2019 @12:18PM (#18947972)
Then you're not being creative enough. Digital turntables are extremely precise. I once hooked up my ns7 (1) to an old windows laptop, spun the turntable, and crashed the computer. I think that highly precise applications like this could find valid uses for 32 bit control
Re:MIDI 2.0 Prototyping announced by mastazi on Saturday January 19, 2019 @09:58AM (#18947336)
I know right? I was expecting 16 bit tops for CC.
Re:MIDI 2.0 Prototyping announced by boomlinde on Sunday January 20, 2019 @07:09AM (#18952670)
Plenty of potential applications of control change messages where 16 bits would be insufficient, for example precision seeking through recorded audio.
Re:MIDI 2.0 Prototyping announced by mastazi on Monday January 21, 2019 @07:14PM (#18964876)
Interesting, you're right for this type of things "MIDI" controllers usually had to resort to HID (e.g. platters on most DJ controllers), I'm curious to see how people will use MIDI 2
Re:MIDI 2.0 Prototyping announced by lightedman on Saturday January 19, 2019 @12:24PM (#18948010)
Wait until you start applying pitch shifting/note bending. You'll want that 32-bit resolution.
Re:MIDI 2.0 Prototyping announced by filoeleven on Monday January 21, 2019 @10:30PM (#18965796)
With this spec, my LFO can be on a separate device and spit MIDI to modulate sample-accurate playback of an entire season of a TV show (assuming that it can be loaded into memory) recorded at 96000k.

Talk about future proofing. No complaints here.

Re:MIDI 2.0 Prototyping announced by leoc on Saturday January 19, 2019 @07:17PM (#18950118)
Any chance there'll be a way to get a few channels of audio into the same container stream as MIDI 2.0, or at least down the same cable?