Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-3238

FIWARE.Request.Tech.Data.Stream-oriented.Kurento_issues

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      To the kind attention of Kurento experts,
      we are currently working on our project using Kurento technology, but
      unfortunately we have encountered some issues and we would like to have
      your support.

      1) We need to record our video streams, but it seems that this kind of
      feature is not supported for h.264 videos, but only for VP8 format ones. We
      can save the file of the video with the recorder endpoint, but it's empty.
      Will this feature be available for h.264 videos?

      2) We've noticed that the ImageOverlayFilter has been implemented recently
      in KMS, we would use this feature but it seems that there is not a
      documentation about this filter nor a tutorial, hence we're not able to
      integrate it in our project yet.

      3) A month ago, we have requested support about video transcoding quality,
      we had been told the issue would have been fixed in one month by exposing
      the capability of selecting the video quality from the API. Is this feature
      ready?

      4) We will need to stream more than one video in the same interval of time.
      In this situation, how the KMS would handle the load? Will it be necessary
      a cluster of KMS servers?

      Thank you very much.

      _______________________________________________
      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: Leonardo Galteri <leonardogalteri@gmail.com>]

        Activity

        Hide
        llopez NaevaTeC Development Team added a comment -

        Hi,
        Thank you vey much for your patience. These are the answers for your questions

        1) Given that Kurento works with live videos, we cannot support H.264 recording because the standard container (MP4) is not compatible with live formats. This means that you can only record in WebM container (VP8 codec) and, once the clip has been recorded, you can post process for converting to MP4 using ffmpeg or any other equivalent tool.

        2) ImageOverlayFilter is only available on Kurento Media Server v 6.0. KMS v 6.0 shall be released soon. In the mid-time you can install it from Kurento public ppa repository. Please, follow instructions in this link for installing KMS v 6.0

        http://www.kurento.org/docs/current/mastering/kurento_development.html

        Look for the section entitled "Kurento Media Server" and remember that the package you need to install is "kurento-media-server-6.0"

        Once you have installed KMS v6.0, you can use the ImageOverlayFilter. Please, see in the following URL for an example on how to use it.
        https://github.com/lulop-k/kurento-imageoverlay

        3) This feature has been made available in KMS v6.0, you can access it again installing KMS v6.0. However, KMS v6.0 selects transcoding quality automatically when working with WebRTC. In other words: if your pipeline is sending streams using WebRtcEndpoint the transcoding quality will be automatically selected basing on WebRtcEndpoint feedback (sent from the browser). Otherwise, if your pipeline is not sending to a WebRtcEndpoint, you can select the transcoding quality using the methdo "setOutputBitrate". You can see how to use this method in the example specified above:
        https://github.com/lulop-k/kurento-imageoverlay

        4) KMS scalability depends on the number of legs (flows being exchanged), on their quality and on the processing you require (e.g. transcoding and recording increase CPU requirements). If you run out of resources using a single KMS instance, you'll need to instantiate additional KMSs. However, we don't provide any capabilities for clustering KMS. It's the application you develop which needs to provide the appropriate logic for managing different KMS instances in the way you want.

        Best regards.

        Show
        llopez NaevaTeC Development Team added a comment - Hi, Thank you vey much for your patience. These are the answers for your questions 1) Given that Kurento works with live videos, we cannot support H.264 recording because the standard container (MP4) is not compatible with live formats. This means that you can only record in WebM container (VP8 codec) and, once the clip has been recorded, you can post process for converting to MP4 using ffmpeg or any other equivalent tool. 2) ImageOverlayFilter is only available on Kurento Media Server v 6.0. KMS v 6.0 shall be released soon. In the mid-time you can install it from Kurento public ppa repository. Please, follow instructions in this link for installing KMS v 6.0 http://www.kurento.org/docs/current/mastering/kurento_development.html Look for the section entitled "Kurento Media Server" and remember that the package you need to install is "kurento-media-server-6.0" Once you have installed KMS v6.0, you can use the ImageOverlayFilter. Please, see in the following URL for an example on how to use it. https://github.com/lulop-k/kurento-imageoverlay 3) This feature has been made available in KMS v6.0, you can access it again installing KMS v6.0. However, KMS v6.0 selects transcoding quality automatically when working with WebRTC. In other words: if your pipeline is sending streams using WebRtcEndpoint the transcoding quality will be automatically selected basing on WebRtcEndpoint feedback (sent from the browser). Otherwise, if your pipeline is not sending to a WebRtcEndpoint, you can select the transcoding quality using the methdo "setOutputBitrate". You can see how to use this method in the example specified above: https://github.com/lulop-k/kurento-imageoverlay 4) KMS scalability depends on the number of legs (flows being exchanged), on their quality and on the processing you require (e.g. transcoding and recording increase CPU requirements). If you run out of resources using a single KMS instance, you'll need to instantiate additional KMSs. However, we don't provide any capabilities for clustering KMS. It's the application you develop which needs to provide the appropriate logic for managing different KMS instances in the way you want. Best regards.

          People

          • Assignee:
            llopez NaevaTeC Development Team
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: