Showing results for 
Search instead for 
Do you mean 
If you don't find an answer, please click here to post your question.
Reply
Highlighted
Occasional Advisor
Posts: 6
Registered: ‎01-08-2019
Accepted Solution

Dynamic Encoding Settings

[ Edited ]

Hi,

 

We are in the process of integrating our video optimization platform (https://lightflow.media) with Ooyala Backlot. The process is our platform analyzes the content to be published, takes the decission about what is the best bitrate ladder for that specific content and them publishes it through Ooyala. 

 

We successfully used Ooyala Backlot API in the past to publish content but for this specific use case, don't find the way of indicating to Backlot which encoding settings we want to use for each asset we publish. Is there any way for doing this? Something like creating an encoding profile and using it for a specific asset? We don't want to use a customer-scope encoding settings, but asset-scope encoding settings.


Accepted Solutions
Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

I've discussed this with our Backlot and OTS engineering team and they've confirmed that this is content awareness that you're trying to implement and it wouldn't be possible from our end as we do not support content awareness. It appears that based on the source file content, the processing profile settings (bitrate) change which is recommended by your bitrate ladder based on the complexity of the content.

 

Looks like your planning to provide bitrate information along with the video file to notify Ooyala (or OTS specifically) on which bit rates to be used for transcoding. The selection of bit rate per asset is not available in our public APIs for customers to choose. However, this option is available in manifest based ingestion and here's is the help article : (https://help.ooyala.com/video-platform/tasks/ingestion_ftp_xml.html) that shares more information on the same.

 

I am assuming that you must be of aware of the bitrates that you're ladder is recommending based on the content so I suggest that you can create your processing profiles with all the bitrates that your ladder comes up with based on the content. Once you've created the desired processing profiles, you can perform XML manifest ingestion. Based on the bitrate that your ladder suggest, you can use this tag <ooyala:profileguid> within the XML and can pass the corresponding processing profile ID for the towards the variable profile guide. 

 

Let me know if you have any other questions that I can help you with. 

 

Thanks,

Sanchit 

 

 

View solution in original post


All Replies
Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

This is Sanchit from Ooyala technical support and I'll be assisting you for this request. 

 

I understood that you're looking to integrate your video optimization platform (https://lightflow.media) with your Ooyala Backlot account. However, can you please elaborate your requirement a bit more? 

 

Since you've already stated that you've successfully used Ooyala Backlot API in the past to publish content, I would like to inform you that while uploading the content to your Backlot account using the Backlot API's includes the transcoding part (setting up the encoding profile) that's done by our transcoding services. The asset is ingested, transcoded and then successfully uploaded. The encoding profiles are already there in the processing profiles using the assets are transcoded post the ingestion and prior to getting successfully uploaded. Can you please share some context on your statement "something like creating an encoding profile and using it for a specific asset"? 

 

Once I have the above requested information from you, I'll go ahead and investigate this issue further and shall share my findings. 

 

Thanks,

Sanchit 

 

 

Occasional Advisor
Posts: 6
Registered: ‎01-08-2019

Re: Dynamic Encoding Settings

Hi Sanchit,

 

Thank you very much for your answer.

 

Just to give you some context, the idea behind our product is optimizing video streams. In its VOD flavour, given a video file (ex: an mp4 file) that you want to publish through Internet as an HLS/DASH stream, LightFlow recommends you the optimal bitrate ladder for each specific content. So, it will recommend you to use higher bitrates for content that has a lot of complexity (movie with lot of movement or detail); it will recommend you to use lower bitrates for low complexity content (a cartoon movie).

 

Furthermore, apart from the recommendation itself, LightFlow is integrated with third party video platforms and encoders so, when a user publishes a video title using LightFlow API, LightFlow gets the ladder recommendations for that title and transparently for the user publishes it in his video platform. Specifically for Ooyala, this implies LightFlow using Backlot API to publish a content indicating to it what are the recommended encoding settings figured out by LightFlow (set of bitrates and resolutions).

 

We feel quite comfortable using Backlot API to publish content but we miss the functionality about setting the set of bitrates and renditions (an encoding profile) used for encoding a video title. Looking at the documentation looks like there is a single encoding profile that is used for all the titles published under an specific account. 

Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

Thanks for the detailed explanation. 

 

As communicated in my previous email, while using the backlot API's for publishing content, it's our transcoding services/encoding profiles configurations that are being used for the assets. However, we do create multiple processing profiles with varying encoding settings based on the assets that are being transcoded at the backend and the end user can explicitly mention that processing profile ID within the XML that's being uploaded. Doing so, the desired processing profile is being picked up by the transcoding engine during the transcoding else the asset is transcoded using the default PP. 

 

For your use case, looks like the LightFlow API's will be instructing to the Backlot API on the encoding settings that are figured out by the LightFlow API's. I'll be discussing the possibilities of this with the Backlot engineering team and shall keep you posted as soon as I have more updates. 

 

Thanks,

Sanchit 

Occasional Advisor
Posts: 6
Registered: ‎01-08-2019

Re: Dynamic Encoding Settings

Yep, you got it right. Thanks for your answer and looking forward for your updates. Thanks!

Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

Thanks for the confirmation. 

 

I'll keep you posted as soon as more information from the backlot engineering team. 

 

Sanchit 

Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

I am still working on this and shall keep you posted with more updates as soon as I have them from the backlot engineering team. 

 

Thanks for your patience.

 

Sanchit 

Occasional Advisor
Posts: 6
Registered: ‎01-08-2019

Re: Dynamic Encoding Settings

Great, thanks for the follow up. 

 

Thanks!

Ooyalan
Posts: 13
Registered: ‎06-21-2017

Re: Dynamic Encoding Settings

Hi Team, 

 

I've discussed this with our Backlot and OTS engineering team and they've confirmed that this is content awareness that you're trying to implement and it wouldn't be possible from our end as we do not support content awareness. It appears that based on the source file content, the processing profile settings (bitrate) change which is recommended by your bitrate ladder based on the complexity of the content.

 

Looks like your planning to provide bitrate information along with the video file to notify Ooyala (or OTS specifically) on which bit rates to be used for transcoding. The selection of bit rate per asset is not available in our public APIs for customers to choose. However, this option is available in manifest based ingestion and here's is the help article : (https://help.ooyala.com/video-platform/tasks/ingestion_ftp_xml.html) that shares more information on the same.

 

I am assuming that you must be of aware of the bitrates that you're ladder is recommending based on the content so I suggest that you can create your processing profiles with all the bitrates that your ladder comes up with based on the content. Once you've created the desired processing profiles, you can perform XML manifest ingestion. Based on the bitrate that your ladder suggest, you can use this tag <ooyala:profileguid> within the XML and can pass the corresponding processing profile ID for the towards the variable profile guide. 

 

Let me know if you have any other questions that I can help you with. 

 

Thanks,

Sanchit 

 

 

Occasional Advisor
Posts: 6
Registered: ‎01-08-2019

Re: Dynamic Encoding Settings

Thank you for the detailed information. Looks like what I am looking for!

 

Just one more question. Are you exposing an API for creating profiles? I am looking in the API reference and don't see anything about that.

 

Again, thank you very much for your dedication. Really appreciated.

 

Thanks,

Jesús Oliva