Uploaded image for project: 'Opencast'
  1. MH-11801

Wowza streaming server needs flv: prefix for flv files

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed and reviewed
    • Affects Version/s: 2.2.0, 2.2.1, 2.2.2
    • Fix Version/s: 2.2.3, 2.3.0
    • Component/s: Backend Software
    • Labels:
      None
    • Severity:
      Non Functioning
    • Steps to reproduce:
      Hide
      Found the same bug for 1.6 (MH-10506) which was fixed for 1.6

      As in custom.properties described, Wowza needs the "flv:" tag to work properly.
      # Some newer streaming server versions expect an "flv:" tag within the rtmp URL.
      # Not every RTMP-streaming server is compatible with this (i.e. nginx), so this
      # is the compatibility mode to the old syntax.
      # true = without "flv:" tag - old syntax
      # false = with "flv:" tag - new syntax
      org.opencastproject.streaming.flvcompatibility=false

      Steps to reproduce (just copied them from the old issue):
      1. Install a Wowza 4 Media-Server following these instructions:
      https://opencast.jira.com/wiki/display/MHDOC/Wowza+Media+Server
      2. ingest a file with the default workflow (compose-distribute...) that produces an FLV video
      3. try to play the video and you get an Error Message: "Stream not found".
      4. When trying to test the stream with the Wowza engine manager I noticed that in Wowza 4 it seems that the prefix flv: before the stream-name is needed, otherwise the stream will not be found. Matterhorn omits the prefix.
       
      Actual Results:
       Stream is not being found. Changing the setting of "org.opencastproject.streaming.flvcompatibility=false" to true or false makes no difference. Also when inspecting the media package via the rest endpoint, the stream URL is not correct, because the "flv:" tag is missing.
       
       Expected Results:
       Player should play the stream correctly.
       
       Workaround (if any):
       in modules/matterhorn-distribution-service-streaming/src/main/java/org/opencastproject/distribution/streaming/StreamingDistributionService.java change:
      - String tag = "flv".equals(ext) ? "" : ext + ":";
      + String tag = ext + ":";




      Show
      Found the same bug for 1.6 ( MH-10506 ) which was fixed for 1.6 As in custom.properties described, Wowza needs the "flv:" tag to work properly. # Some newer streaming server versions expect an "flv:" tag within the rtmp URL. # Not every RTMP-streaming server is compatible with this (i.e. nginx), so this # is the compatibility mode to the old syntax. # true = without "flv:" tag - old syntax # false = with "flv:" tag - new syntax org.opencastproject.streaming.flvcompatibility=false Steps to reproduce (just copied them from the old issue): 1. Install a Wowza 4 Media-Server following these instructions: https://opencast.jira.com/wiki/display/MHDOC/Wowza+Media+Server 2. ingest a file with the default workflow (compose-distribute...) that produces an FLV video 3. try to play the video and you get an Error Message: "Stream not found". 4. When trying to test the stream with the Wowza engine manager I noticed that in Wowza 4 it seems that the prefix flv: before the stream-name is needed, otherwise the stream will not be found. Matterhorn omits the prefix.   Actual Results:  Stream is not being found. Changing the setting of "org.opencastproject.streaming.flvcompatibility=false" to true or false makes no difference. Also when inspecting the media package via the rest endpoint, the stream URL is not correct, because the "flv:" tag is missing.    Expected Results:  Player should play the stream correctly.    Workaround (if any):  in modules/matterhorn-distribution-service-streaming/src/main/java/org/opencastproject/distribution/streaming/StreamingDistributionService.java change: - String tag = "flv".equals(ext) ? "" : ext + ":"; + String tag = ext + ":";
    • Tags (folksonomy):

      TestRail: Results

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              laudel@uni-leipzig.de Sven Laudel
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                TestRail: Cases