This plug-in is using YouTube to store and convert your video files. Once installed movies uploaded to ImageVault will be stored on your configured YouTube account. This means ImageVault will be able to preview, publish and stream movies using the YouTube API. From the editors perspective there should be no difference between working with locally stored files or movies stored on YouTube.

Note: This example implementation is currently not working with the YouTube servers. Uploading a video does not longer work. YouTube has, since this plugin was written, deprecated the API used in this example. To make this plugin work, the authentication and API calls must be modified to use the new authentication protocol (oauth2 for devices) and implement calls to the YouTube API using the new YouTube API v3.

You are free to modify this example and provide an updated implementation yourself.

Sorry for the inconvenience /Team ImageVault


The required assembly, ImageVault.Core.YouTube.dll, is included in the normal installation. It is located in the bin folder under the Core Instance created (C:\ImageVault\Core{instance}\bin).

In order to activate the YouTube plug-in the following SQL script should be executed:

    --BEGIN PostInstallation
    --register InformationGenerator
    IF NOT EXISTS(SELECT * FROM dbo.[TypeRegistrations] WHERE Type=
    'ImageVault.Core.YouTube.YouTubeMediaInformationGenerator, ImageVault.Core.YouTube')
    INSERT INTO dbo.[TypeRegistrations]([Type]) VALUES(
    'ImageVault.Core.YouTube.YouTubeMediaInformationGenerator, ImageVault.Core.YouTube')
    --register storage
    IF NOT EXISTS(SELECT * FROM dbo.MediaStorageTypes WHERE Type=
    INSERT INTO dbo.MediaStorageTypes([Type],[Priority]) VALUES(
    --register converter
    IF NOT EXISTS(SELECT * FROM [dbo].[MediaConverterTypes] WHERE [Type]=
        INSERT INTO [dbo].[MediaConverterTypes] ([Type] ,[Priority]) VALUES (
        'ImageVault.Core.YouTube.YouTubeConverter,ImageVault.Core.YouTube', 999)
    --END PostInstallation

This will register the required types for storage, conversion and creation of media information.


In order for the plug-in to be able to connect to YouTube a developer account is required. This should be configured in the config file for the Core service. The configuration file can be found here

<?xml version="1.0" encoding="utf-8"?>

            <add key="YouTubeMediaStorage_Username" value="{YouTube-Username}" />
            <add key="YouTubeMediaStorage_Password" value="{YouTube-password}" />
            <add key="YouTubeMediaStorage_DeveloperKey" value="{YouTube-DeveloperKey}" />


The Developer key can be found by logging on to the following address

Restart the Core service once the configuration file is updated.


The source code for the connector is available as an example on how to extend ImageVault.


Extends the ExternalMediaContent base class.

This is the implementation of a MediaContent that will be used internally to handle media files stored in YouTube


Implements the IMediaStorage interface.

This class is responsible for deciding if it could store a file, and if asked to make sure the file is stored in YouTube.


Extends the MediaConverterBase base class which in turn implements the IMediaConverter interface.

Is responsible for converting a movie, which is done by asking the YouTube API for a thumbnail.


Implements the IMediaInformationGenerator interface.

Generates media information like width, height and content type. Is also responsible for how the media should be published. In this case using an iframe containing the player code.

comments powered by Disqus
+46 (0)480 - 31 47 95
Swedish website