WsPlayer cannot play streams from FME that has VP6 format

Discussion in 'Web Call Server 5' started by phil, Apr 14, 2017.

  1. phil

    phil New Member

    I use Flash media encoder to send video streams to WCS.

    If it is H.264, it works fine.
    However, if it is VP6 it doesn't work. The player simply shows a blank page.

    Attached Files:

  2. Max

    Max Administrator Staff Member

    VP6 codec is not currently supported
  3. phil

    phil New Member

    Thanks Max.
    I'd like to ask if pushing VP6 to WCS can cause possible memory leak ?

    Because currently my memory is going up even there's no one playing any video.
    I know it might be because the keep.alive.algorithm=none
    but if that is enabled, FME cannot push streams to WCS.
  4. Max

    Max Administrator Staff Member

    We never tested this with VP6.
    So we need to test to know if it can affect on memory.
    What is your build number? Memory leaks and disconnections were fixed in latest builds. You can try to update.
    In latest builds it works well. RTMP uses keep.alive.algorithm=INTERNAL. So FME works and able to push streams to WCS with enabled keep alives.

    If you set keep.alive.algorithm=none, then viewers can't disconnect properly. It is a cause of leaks.
    So I would recommend to update to the latest build.
  5. phil

    phil New Member

    Thanks Max. I'm sorry I meant to say FFMPEG.
  6. Max

    Max Administrator Staff Member

    This option is better:
    Because if you disable keep alive at all, you will have a leak on websocket connections even if users disconnected.
    By the way, could you describe your issue with ffmpeg in details? What does not work?
    FFmpeg should work properly with
    and latest builds.
    If it does not work, please let me know. We will check.
  7. Max

    Max Administrator Staff Member


    Regarding Origin-Edge feature. We have recently implemented RTMP re-publishing (push) feature.
    Please look at our REST API examples:
    How to:
    1. Publish a stream.
    2. Re-publish this stream as RTMP using REST API.
    POST /rest-api/push/startup HTTP/1.1
    Content-Length: 73
    Content-Type: application/json
    "streamName": "cf58",
    You have to install latest build to get this working.
    Note, we didn't test this with RTMP source streams.
    We tested with WebRTC source only.
    Please let us know if you have any issues.

    All streams are currently re-published as RTMP H.264 AAC streams.

Share This Page