understanding URLResource

Hi -

One thing looks out of place about your example is the .mp4 extension on the video.  Streams of H.264 content don't normally need the extension.  The other caveat is if the FMS server you are using has instances, you'll need to use a StreamingURLResource instead of a URLResource, and pass the urlIncludesFMSApplicationInstance as true.  A good sanity check is to test your url again the Flex VideoDisplay component, or the FLVPLayback component. 

In sprint 9 I have it working like this.

v = new VideoElement(new NetLoader(), new URLResource(new URL(videoURL)));

So instead of URL it would be..

v = new VideoElement(new NetLoader(), new URLResource(new FMSURL('rtmp.url'))));

If it doesn't work with the Flex VideoDisplay class, it's most likely the wrong URL.   This can be the result of a typos or missing application.   Could you post your URL?  If not, the general format is rtmp://myserver.com/myApplication/myvideo .  Your example URL seems to be missing an application.

Test this in your app.

var v:VideoElement = new VideoElement(new URLResource(REMOTE_STREAM));
private static const REMOTE_STREAM:String = "rtmp://cp67126.edgefcs.net/ondemand/mediapm/strobe/content/test/SpaceAloneHD_sounas_640_500_short";

That's taken directly from the examplePlayer inside trunk.

Hey thanks.

Not setting urlIncludesFMSApplicationInstance=true had been my problem for several hours today. This is the only place I have seen it mentioned.

If you are using LimeLight's CDN to deliver mp4, you need to set urlIncludesFMSApplicationInstance=true.

Cheers,

Ben Mishkin

Sagebit, LLC

Hi Ben,

Not only LimeLight uses instances. Application and application instances are

used quite a bit in the FMS world and the file type wouldn't have anything

to do with the app instance. Sounds like a uri issue or a parse issue

between the stream name and connection string. So you are saying that

setting this value to true resolves an issue with mp4s and not needed for

flvs?

Thanks,

Bob

Yes.

We use Limelight CDN, which uses application instances. But I hadn't even noticed that we needed to set urlIncludesFMSApplicationInstance=true, because our flv URLs of the form

rtmpe://llnwqa.fcod.llnwd.net/a1218/o18/quickstart/limelight_sample_flashmovie

(which assumes the '.flv' extension)

were working without it. But when we tried an mp4, like

rtmp://llnwqa.fcod.llnwd.net/a1218/018/mp4:path/to/test.mp4

the video would not load until we set urlIncludesFMSApplicationInstance=true.

Ah, that doesn't sound right being the instance has nothing to do with the

file type and adding the prefix. Maybe some one at adobe can confirm that

this is intentional and working as intended.

Thanks for the heads up on this Ben.

Bob

Bob is right, it doesn't have anything to do with the file type or prefix.  For the first URL, it turns out that we can establish a connection with or without urlIncludesFMSApplicationInstance.  When set to false, it connects to:

rtmpe://llnwqa.fcod.llnwd.net:1935/a1218

When set to true, it connects to:

rtmpe://llnwqa.fcod.llnwd.net:1935/a1218/o18

Not sure why both URLs work, but in general you should stick with the true param for Limelight streams.