On Sun 14 Aug 2016 at 13:02:08 (+0200), ander...@notam02.no wrote: > b> https://de.wikipedia.org/wiki/Open_Sound_Control is sayed to > b> replace MIDI. Is this something usefull for lilypond? > > It should be. Storing and sending/receiving arbitrary data is > straightforward in OSC, in MIDI you'll have to build and parse sysex for > any non-standard (e.g. rhythms, beams, slurs, offsets, markups...). > > b> Can one save osc files like MIDI files? > > Yes. All information in any .ly file could be encoded in OSC format and > saved to files or sent along to other apps. SuperCollider and OpenMusic > are examples of apps supporting OSC as one possible score-file format.
Looking at https://en.wikipedia.org/wiki/Open_Sound_Control I can't see any reference to a file format. At the bottom, there's a link "Music notation file formats" which takes you to https://en.wikipedia.org/wiki/Category:Music_notation_file_formats which contains a link "Open Sound Control" under the heading Pages in category "Music notation file formats" and that nicely completes the circle with https://en.wikipedia.org/wiki/Open_Sound_Control The list which contains "Open Sound Control" also contains "MIDI file" which suggests the error is wiki's, not mine. So would I be right in thinking OSC is only a Protocol and not a File Format? > http://opensoundcontrol.org/files/OSC-Demo.pdf I'm not sure what I'm missing seeing in this page by not having "language pack for 'Adobe-Japan1' mapping" available. > https://www.midi.org/articles/white-paper-comparison-of-midi-and-osc One of the comparisons here is Standard File Format: MIDI: yes OSC: an implied negative. I've googled around for a file format, but all I find are applications and program fragments. OK, an application might be able to store an OSC protocol stream in a file, but that does not make that a file format. Cheers, David. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
