IntenseDebate - jccrosby

11 years ago @ http://www.thekuroko.com - Aptana SDOCML & Code H... · 0 replies · +1 points

Hey Ze - I've encountered some inconsistencies with the way Aptana treats the SDOCML file. A couple things to try:
1) Try adding your JS libs as project resources
2) Open and close the project in Aptana
Also, I know Aptana & EXT has been updating and I haven't kept up with the updates. So it could be that the file format or content is just out of date.
Let me know if this helps any, and I'll look into some things on my end when I get a few free moments.

11 years ago @ http://www.thekuroko.com - Getting Started with H... · 1 reply · +1 points

Hi Harry -
I haven't ever thought of that. Conceptually it seems like it would be plausible - the only issue is that OSMF uses an F4MLoader Element (extended from Document Element) to load the XML using a URLLoader so there may be an issue with that and some work under the hood of the player to make it realize that it needs to load the XML in another way.

P.S. Sorry for the delayed response. My blog has been neglected lately.

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 1 reply · +2 points

Downloading 2.0 now. Heh.

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 3 replies · +2 points

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.

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 5 replies · +1 points

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?

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 1 reply · +1 points

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.

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 0 replies · +1 points

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

11 years ago @ http://www.thekuroko.com - OSMF Fix: "Local HDS" ... · 0 replies · +1 points

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.

11 years ago @ http://www.thekuroko.com - HTTP Dynamic Streaming... · 0 replies · +1 points

Good to hear. Thanks.

11 years ago @ http://www.thekuroko.com - Getting Started with H... · 1 reply · +1 points

The only real way to reduce the number of requests while using HDS is to adjust the size of the fragments and segments when you package the content. If you have to create fragments that are of a specific size then, this isn't an options. Have you thought about using a CDN to help with the number of requests. You could also look into other protocols like RTMP or even some sort of multi-cast solution to minimize the amount of requests hitting your server.

IntenseDebate Comment System

Connect with jccrosby

My blogs/sites

People I'm following

jccrosby