Learn From Lisa Blog

Coolness: OSMF 2.0 released

[UPDATE: OSMF has been deprecated by Adobe, sorry to say]

Adobe has released a new version of the Open Source Media Framework this week, with some major improvements to adaptive bitrate logic, and some new APIs that now include interesting attributes such as “Doneness” and “Liveness”.

Updates include:

  • Two modes for adaptive streaming: manual and automatic
  • Better automatic switch operation
  • More information to the Quality of Service (QoS) information and history
  • Enhanced metric base, factory and repository
  • Optimized rule engine to better handle bandwidth CPU
  • “Best-Effort Fetch” addresses common server-side problems of “liveness” and “dropout”
  • “Doneness” allows your player to recognize the difference between HDS content lapsing because it reached the end of the bootstrap file, versus lapsing due to a server issue
  • Customizable HDS adaptive bitrate algorithm (an advanced feature)

More details on the changes can be found on the SourceForge page, on the OSMF Blog, and on FlashStreamWorks.com. You can see OSMF 2.0 in action with Strobe Media Playback here.

Posted in: HTTP Dynamic Streaming, OSMF, Prebuilt Players, Web Video News

Leave a Comment (4) ↓

4 Comments

  1. Mike June 4, 2013

    Hi Lisa,
    Is OSMF dead? I’m having a problem with a “Buffering…” message appearing after each video finishes playing.

    I’m trying to find support, but it doesn’t look like they’re continuing to respond to any posts posted in user forums, and the OSMF.org website’s “contact us” button no longer works.

    Any suggestions? (On either the problem I’m having, or in finding support).

    Thanks!!

    reply
    • Lisa June 4, 2013

      Hi Mike,
      Unfortunately, it does seem that the momentum around OSMF has stalled. 🙁 Did you try posting to the adobe.com forums?

      reply
  2. Kev Man October 19, 2015

    It never did live up to its over-inflated (typical Adobe) hype. It was too bulky. Too complicated for someone to casually learn enough to get it to work. You had to dedicate way too much time an effort for something that should be as easy as a few lines of JS. Not a whole library of .as files and compiling.

    reply
    • Lisa Larson-Kelley October 19, 2015

      I totally agree. It had so much promise, but ended up being bulky, not flexible, and finally, floundered with a lack of support or a community. It still lives on in the Primetime product, but Adobe has abandoned the OSMF open source effort. Sad. 🙁 In defense of its bulkiness, it did do a lot in one package (encryption, etc.).

      reply

Leave a Comment