Ticket #262 (closed enhancement: fixed)

Opened 6 months ago

Last modified 3 months ago

play response=metafile support for Wowza-server

Reported by: Michiel.Schok Owned by: arjen
Priority: major Milestone: MediaMosa 2.1
Component: Core Version: 2.1.4
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours:

Description

When using wowza (1.7 or 2.0) server for streaming content of flv or mp4 containers, the play-request returns a playlink where the protocol is RTMP.

At the moment (version 1.7.3), the &mode=metafile parameter on the /asset/{id}/play request yields the following result:

containerresult
flvis not specified
mpeg.qtl file with an rtmp-link within. Quicktime launches and complains because rtmp is not supported

It would be nice if for both of these containers, the &mode=metafile would result in a smil-type file.
That file could then be used to instruct JW-player to play the file. See http://developer.longtailvideo.com/trac/wiki/Player5Formats#RTMPStreaming for an ultrashort example.

Ideally, what would be realized, is that an end-user is capable of
* on his own site,
* using an own JW-player,
* using a 'permanent EGA-link' which returns a MediaMosa metafile,
* have a streaming experience.

For instance, using the SURFmedia call
http://www.surfmedia.nl/app/video/{asset_id}/play?format_id={mediafile_id}&mode=metafile returns to the client the metafile that VP-core generates with a

[get] /asset/{asset_id}/play?mediafile_id={mediafile_id}&response=metafile&user_id=foo

On a POC-server at http://richmedia.showcase.surfnet.nl/20100108/ is a demo, which works after a manually obtained ticket is entered in the playlist.txt .
That playlist.txt in a smil-file, and should be 'generated' by the core.

Change History

Changed 6 months ago by Frans

  • milestone changed from MediaMosa X.X to MediaMosa 2.1

Changed 5 months ago by Frans

Submitted to VP-Core Trac: http://vpcore.trac.madcap.nl/ticket/122

Changed 4 months ago by MC-arjen

  • version set to 2.1.3

planned for 2.1.3

Changed 3 months ago by Frans

We missed the release notes of the MM 2.1.3 version.
Is this one solved in 2.1.3? Should this be closed?

Changed 3 months ago by Michiel.Schok

At the moment, response is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <header>
    <item_count>1</item_count>
    <item_count_total>1</item_count_total>
    <item_offset>0</item_offset>
    <request_class>mediamosa_rest_call_asset_mediafile_play</request_class>
    <request_matched_method>GET</request_matched_method>
    <request_matched_uri>/asset/$asset_id/play</request_matched_uri>
    <request_process_time>0.0473</request_process_time>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[GET] asset/Qn7IMA7PjJL3olqDYfttgIQ0/play?mediafile_id=7W7LiSKNf1CimckLg0YibJlo&amp;response=metafile&amp;user_id=foo</request_uri>
    <version>2.1.3.578:254d05f6869a</version>
    <request_query_count>19</request_query_count>
  </header>
  <items>
    <item id="1">
      <output>&lt;smil&gt;
  &lt;head&gt;
    &lt;meta base="rtmp://wowstreaming.test.snkn.nl/vod" /&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;video src="vpx-acc/g2Zg6ZGoFdXMYRdREkifbaZa.mp4" /&gt;
  &lt;/body&gt;
&lt;/smil&gt;</output>
      <content_type>application/x-shockwave-flash</content_type>
      <ticket_id>g2Zg6ZGoFdXMYRdREkifbaZa.mp4</ticket_id>
    </item>
  </items>
</response>

At least the content_type should be changed, and I'm missing the 'app_id' in the src parameter, my guess is that a '/5' should be added.

Changed 3 months ago by forgacs

  • owner set to arjen
  • status changed from new to assigned

Changed 3 months ago by MC-arjen

  • version changed from 2.1.3 to 2.1.4

Michiel, can you retest this?

Changed 3 months ago by Michiel.Schok

Unfortunately, I'm still missing the '/5' (the app-id) in the src parameter.

<response>
  <header>
    <item_count>1</item_count>
    <item_count_total>1</item_count_total>
    <item_offset>0</item_offset>
    <request_class>mediamosa_rest_call_asset_mediafile_play</request_class>
    <request_matched_method>GET</request_matched_method>
    <request_matched_uri>/asset/$asset_id/play</request_matched_uri>
    <request_process_time>0.0646</request_process_time>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[GET] asset/Qn7IMA7PjJL3olqDYfttgIQ0/play?mediafile_id=7W7LiSKNf1CimckLg0YibJlo&amp;response=metafile&amp;user_id=foo</request_uri>
    <version>2.1.4.594:55f14ee154f5</version>
    <request_query_count>19</request_query_count>
  </header>
  <items>
    <item id="1">
      <output>&lt;smil&gt;
  &lt;head&gt;
    &lt;meta base="rtmp://wowstreaming.test.snkn.nl/vod" /&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;video src="vpx-acc/r1QQGiqFAvQXic8DVVo3B68e.mp4" /&gt;
  &lt;/body&gt;
&lt;/smil&gt;</output>
      <content_type>application/smil</content_type>
      <ticket_id>r1QQGiqFAvQXic8DVVo3B68e.mp4</ticket_id>
    </item>
  </items>
</response>

If I manually add those characters, it is working.

Changed 3 months ago by Michiel.Schok

  • tested changed from no to yes
  • accepted changed from no to yes

On VP-Core acceptance servers, it now working.
Needed version is at least: <version>2.1.4.619:445d9de94f74</version>

If Madcap can close, I already tested and accepted this.

Changed 3 months ago by Frans

  • status changed from assigned to closed
  • resolution set to fixed

I'll close instead...

Note: See TracTickets for help on using tickets.