15 responses

  1. Jordan
    May 8, 2012

    Hey John, This is exactly what I'm trying to do, but I'm unfortunately having trouble implementing your directions. Is there any chance you'd be willing to share the source to properly override all of these classes? Thanks, Jordan

    • jccrosby
      May 17, 2012

      Jordan – did you get the email I sent with the samples?

  2. Chris
    May 17, 2012

    Hi John,

    I've pretty much got this working now I think – great solution – except…I'm stuck at the last hurdle! Doh! Is there any hope you'd be willing to post your source code for this so us mere mortals can get this fix working please? :)

    cheers!

    Chris

  3. Chris
    May 17, 2012

    Hi John,

    to clarify my above comment – I'm actually finding a problem with the IndexHandler, the streamName appears to be incorrect, I keep getting a Stream not found media error from the core of the player, tracing out request URL is in the format:

    streamname/mainfest filename/streamnameSeg1-Frag1

    and it can't seem to find the fragment…any thoughts on this at all? The folder containing the manifest and fragments is in the same directory as the player SWF…

    Cheers again for any help you might be able to provide

    Chris

    • jccrosby
      May 17, 2012

      Chris, the path looks correct to me for HDS content, do you have the fragments locally or just the manifest file? OSMF expects the fragments (the files with the streamnameSeg{#}-Frag{#}) to be in the same directory as the manifest file.

      There are a couple of ways you can get the Fragments – the simplest is to inspect the HTTP calls (Firebug or charles) when a player is playing back the HDS content & then download the files – that is pretty manual though. Another was is to extract the fragments from the packaged content. This involves parsing through the segment files created when packaging the content and pulling out the fragment data – essentially reproducing what the HTTP Origin Module does. The file spec for F4V (http://www.adobe.com/devnet/f4v.html) has the necessary info to parse through the segment files.

      Hope that Helps – John

      We have built a tool to extract the fragments that was up on the now defunct Adobe Marketplace and have yet to get the app up somewhere it can be purchased.

  4. Chris
    May 17, 2012

    Hi John,

    I've got all the segment .f4f and.f4x files locally, so – (ray of light starts to appear in my head), I need the fragments, NOT the segments in the same directory as the manifest file.

    Also, to be *even* more specific about the path being parsed b the IndexHandler, it's:

    streamname/manifestfilename.f4m/streamnameSeg1-Frag1

    so the path actually contains the manifest file extension along with the name, I'm not sure if that's supposed to be the case or not? Seems a little odd though…

    Cheers for the reply, much appreciated!

    Chris

    • jccrosby
      May 17, 2012

      Yep – fragments are the key. You're right the .f4m in the path doesn't look right. I'm not sure why it would be keeping that around. What version of OSMF are you using?

      • Chris
        May 17, 2012

        I'm using 2.0 – the latest SWC

      • jccrosby
        May 17, 2012

        That might be part of the issue, I haven't testing the local playback with 2.0 much – I've been working wtih 1.6. I'm sure they changed something that broke the path for local content. Oh joy.

      • Chris
        May 18, 2012

        I dare you to test it more ;)

      • jccrosby
        May 21, 2012

        Downloading 2.0 now. Heh.

      • Chris
        May 24, 2012

        I don't turn dares down, either ;)

  5. Chris
    May 17, 2012

    Actually, as a thought – is there any way I could get some more info on the F4Fragment Extractor – is it an Air app, or a native runtime program – and how would I go about purchasing it off you, etc etc?

    Yet more thanks (running out of interesting ways of being flattering!)

    Chris

    • jccrosby
      May 17, 2012

      Ha! Thanks.
      If you wouldn't mind emailing me (john [AT] realeyes.com) a little info about the project you're working on, I'm sure we can work something out with the extractor.

      • Chris
        May 17, 2012

        done :)

Leave a Reply

 

 

 

Back to top
mobile desktop