This use case is typically combined with transcoding performed on the publisher’s side, after which the output files are pushed directly to CDN hosting, or to a local intranet delivery source. In this case, Kaltura essentially only manages the metadata while media files themselves are delivered directly from the publisher through a CDN to the viewer. Linking between the files and a Kaltura entry can be done through the KMC, API, or drop folder xml ingestion. See Kaltura Drop Folders Service For Content Ingestion.
Can't find what you are looking for?
Never miss a thing!
Subscribe to our customer newsletter and our release notes updates, so you always get the best out of Kaltura.
Learn everything you need to know to get started
Select a topic of your interest:
Translation Disclaimer
Please note that many of the pages in our website have been translated from English using machine translation tools. Kaltura cannot guarantee the accuracy of these translations. When in doubt, please refer to the English version of the text. You are welcome to share any inaccuracies with Kaltura that you detect, however, Kaltura is under no obligation to implement the suggested changes.
We’re excited to introduce you to our new KMS and KAF player V7 replacement tool
Check out the new Player Upgrade tool in your admin page.