No supported media sources

Comments

6 comments

  • Avatar
    Aleksandar Kostadinov

    Hi Francois,

    May I please ask you to share more context into this issue. For example, what video are you trying to play and where? If you're using our Video Player what code are you using? Is there a URL or ways we can reproduce this issue? We can then use these details to investigate this further and advise on why you are seeing this issue.

    0
    Comment actions Permalink
  • Avatar
    francois munck

    Thanks for your answer,

     

    That error appears on all videos from the cloud. We are using your Video player, unfortunately i can't provide url for reproducing, but I can give your more info and code samples.

    Error in console

    Player code

    const cld        = cloudinary.Cloudinary.new({cloud_name: '{{ getCloudName() }}'});
    const demoplayer = cld.videoPlayer('video-player-frame')
    .sourceTypes(['hls'])
    .transformation({streaming_profile: 'hd'});

    And playing video by public id

    demoplayer.source(publicId, options);
    demoplayer.play();

    Please note, that video can be played by remote url without a problems, so video is exist and has correct publicId. Also, I checked all data that we use as parameters for player and they seems to be correct

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi,

    Thanks for sharing this.

    Since you are trying to play Adaptive Bitrate Streaming HLS for your videos, I assume you have you already created the derived videos with all the representations eagerly? Either at the time of upload or via the explicit method. Is that right?

    I believe you have also submitted a ticket with us directly via Zendesk about this issue. In order to investigate this further, could you please reply in that ticket and share your cloud name, and also the value you're passing as 'options' to the video player? We can then try to test this and reproduce from our side given that a link to your site is not available for us to test it there directly.

    Looking forward to your response.

    0
    Comment actions Permalink
  • Avatar
    francois munck

    Hi,

    I didn't understand about Zendesk, I leaved a message here and sent on the your email address, can we continue here?

    Firstly, about uploading video, we use uploading Widget with preset settings which including async eager transformations, and only when transformation is complete, we display video on our website. Transformation config:

     

    About 'options', in most cases options is an empty object, but some videos are trimmed and played with options {"start_offset":"7"}, that videos uploaded with properly configured preset with transformations "sp_hd/so_7/m3u8"

     

    Cloud name: origindata

     

    Url to reproduce: http://stage.100sport.tv/identification/identify-by-url/?urlId=SaE9vNFCnXxzYWx0eQXX
    Please, follow the current url and try to play any video

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi,

    Sure, we can continue here.

    Thanks for the URL example. I had a look and was able to reproduce the issue. I then looked at one specific video (public_id => top_football_videos/ncs1bljkrhatzbdky8ie). Looking at this video in the logs, I see that it was uploaded with the "trim_prod" upload preset. This preset has the eager transformations set to "sp_hd/so_7/m3u8". As a result, this was the specific transformations/representations that were eagerly generated and the request from the video player (in terms of options configured) should match this generated version.

    For example, I created two short JSFiddles which you can see below - 
    https://jsfiddle.net/r86efakd/1/
    https://jsfiddle.net/r86efakd/2/

    The two JSFiddles above load the video and specify the transformations configuration in slightly different ways but both work and play the video. For example, in the first JSFiddle, the transformation parameters all passed in the 'options'. In the second example, the streaming profile and sourceTypes are defined ahead of time and only the start_offset is set in the 'options'. This seems to be the approach you are trying to use.

    May I please ask you to double-check the exact parameters that are sent to the player when your site requests a different video source? You can use the JSFidldes as reference for a working example.

    Lastly, I noticed you're requesting an Edge version of the Video Player source code. We recommend you to use the stable releases in production only rather than Edge versions. You can use the following link (https://unpkg.com/cloudinary-video-player/dist/cld-video-player.min.js) which is what the JSFiddles use which would always redirect to the latest stable version.

    Please let us know how it goes.

    0
    Comment actions Permalink
  • Avatar
    francois munck

    Hi,

    Thanks a lot for your assistance, we have found the reason and its already fixed

    Best regards!

    0
    Comment actions Permalink

Please sign in to leave a comment.