Telvue Playback Server and Cloudcast Integration With Drupal

stefanwray's picture

First under the Open Media Project and now under the Community Media Drupal Initiative there have been ongoing efforts to integrate Drupal with Telvue's products. Initially, this focused on Telvue's playback servers for the purposes of moving show metadata from Drupal to Telvue and moving Telvue schedule data back to Drupal. The "original" Telvue API had its limitations and developers made requests to add needed fields. Now, in addition to the Telvue playback server there is also a Cloudcast VOD server. The Cloudcast RSS feed references VOD files and metadata on Cloudcast. Similarly, there has been a need for new fields to be added to the Cloudcast API. So with the Drupal Telvue Module there are three locations where fields need to map: 1) Drupal Telvue module, 2) Telvue playback server, and 3) Cloudcast VOD server. Below is a chart showing these three locations and which fields are currently mapped now.

Although there has been some progress, what we have have is less than what we need. In consideration of the above, the problem is the following. There needs to be a field for a universal unique identifier (UUID) that is mapped from the Telvue API to Cloudcast API. This is important for connecting VOD files back to projects and shows on Drupal.

telvue_playback_cloudcast.jpg92.19 KB


With Aric's approval, I too

emilyf's picture

With Aric's approval, I too discussed this with Telvue, and here is the update I received from them:

"[We] do not have an ETA on when we will have a more elegant solution for the UUID's, but it is something we are looking. The only place UUID's are used at the moment is Connect. We would have to add UUID generation into Broadcast and CloudCast, and develop integration so that they are shared between services when the videos are distributed. Unfortunately it is not an easy task to complete and it will take time to provide a solution."

A pretty good (though ideally temporary solution) is to use expected filename to route through the entire process for the time being...RETN is doing this and it is working to push to telvue > go through broadcast server and into cloudcast > update media entity on show node with cloudcast url based on the same filename. If anyone is looking for more detailed info on how to set this up, let me know.

I posted some information last week also about setting this field to be unique in Drupal, you can read more about that here: