Support for OSC

Forums Forums dLive Forums dLive feature suggestions Support for OSC

Tagged: 

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #112286
    Profile photo of ChrisChris
    Participant

    Please consider support for Open Sound Control.

    #112290
    Profile photo of Tatsuya NakamuraTatsuya Nakamura
    Participant

    +1

    #112344
    Profile photo of andiabwaertsandiabwaerts
    Participant

    +1

    #113258
    Profile photo of George PuttockGeorge Puttock
    Participant

    +1000

    #113261
    Profile photo of SanjOkSanjOk
    Participant

    +1

    #113344
    Profile photo of Paulucci BakkePaulucci Bakke
    Participant

    +1+1+1+1

    #113357
    Profile photo of msteelmsteel
    Participant

    I’m not against OSC on dLive, but I’d be interested in knowing what people think the advantage would be. Are there tools people like to use that support OSC and not MIDI? I have done a little coding on both X32 OSC and dLive TCP MIDI. I prefer some aspects of each over the other.

    #115045
    Profile photo of jc2000jc2000
    Participant

    +1
    OSC support for all AH products!

    #116679
    Profile photo of BWFBWF
    Participant

    +1

    OSC definitely looks to be the future standard for audio / video system communication as it is much more flexible and easier to program, so it would be a fantastic addition to the range.

    OSC vs. MIDI

    We are now using OSC on projects where, in the past, we would have used MIDI. OSC is infinitely granular and bundled UDP messages occur simultaneously, continuously, and nonstop; where MIDI is limited to steps and divisions because it supports a very limited range of values. With OSC you can transmit multiple data types like 32-bit integers, floating point numbers, strings and more; while MIDI only transmits 1-byte integers 0-255. MIDI uses a compact binary message format with a limited number of fields. OSC uses a human readable, URL-style address format and can send data in forms of words or numbers. OSC also includes a picosecond-resolution timestamp while the MIDI beat-clock is low-resolution with a precision of about 20,833 microseconds. To boot, the OSC data rate is Gigabit speed while the MIDI data rate is only around 31,250 bits per second!

    briteliteimmersive.com

    #117717
    Profile photo of Carl NCarl N
    Participant

    +1

    #123024
    Profile photo of LaaxLaax
    Participant

    +1

    #123025
    Profile photo of LaaxLaax
    Participant

    Well, for starters DLive dosen’t have MIDI Ports, and downloading / Installing drivers on guest engineer’s PC/MACs is sub-optimal to say the least. Secondly, for most things (Qlab Remotes for example) a simple Midi Note is sufficient. Nobody likes to memorise and write convoluted HEX codes just to tell the PC “Go”(!), or worse, having to buy external BomeBox devices so you can send messages to lighting desks (Where installing A&H Midi over IP drivers is not an option).
    OSC is not the do all / end all solution, but it would help with some of MIDI-over-IP (and MIDI in general) shortcomings. And OSC seems to be growing in popularity a lot too.

    #124268
    Profile photo of kizza42kizza42
    Participant

    Coming from XM32, OSC is great and I would love it if dLive handled it, its somewhat human readable which makes editing things on the fly much simpler when I’m building up show control files on Qlab/Reaper.

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.