Page Comparison

...

For older Gateway versions, obtain the optional stand-alone package for video clipping and install it on Gateway servers with no additional configuration. In addition to the RPM tool, install the supporting framework for multimedia formats i.e. FFmpeg, which Swarm provides preconfigured within a Docker container.

1. Copy the package for video clipping to a server that is running Content Gateway. See Gateway Requirements for more information about all the gateway server requirements.

   caringo-videoclipping-VERSION.noarch.rpm

2. If the server is running Content Gateway 6.0 or earlier, upgrade Gateway (version 6.1 and higher support drop-in features such as video clipping). See Gateway Installation.

3. If Content UI is version 6.1 or earlier, upgrade it to support this feature. See Content UI Installation.

4. Install the package. 

   Code Block
   language bash
   yum install caringo-videoclipping-VERSION.noarch.rpm

   The installation creates a “features.d” directory under /etc/caringo/cloudgateway/ where Gateway detects optional dynamic features.

5. Install multimedia support via FFmpeg. Swarm provides it preconfigured in a Docker container. 
   From an Internet-connected machine, 

   1. Check the Docker is installed.

      Code Block
      language bash
      docker info

      If the Docker is not installed, install the Docker package and start the daemon. Check the status and enable it system-wide. See docs.docker.com/install/linux/docker-ce/centos/ for more information.

   2. Verify Docker by running a container test.

      Code Block
      language bash
      docker run hello-world

   3. Load the provided container for FFmpeg.

      Code Block
      language bash
      docker load < caringo-gateway-VERSION.feature.ffmpeg.via.docker.VERSION.x86_64

6. Gateway creates /var/spool/caringo/cloudgateway/features directory for spooling video clips. Gateway denies starting in absence of the directory.

7. In setting iptables rules, Docker closes external TCP access to port 80 (although ping and ssh still work). Explicitly open port 80 again for clients to access Gateway. 

   Code Block
   language bash
   firewall-cmd --add-port=80/tcp --permanent firewall-cmd --reload systemctl restart docker

8. Repeat the above process on any remaining Content Gateway servers.

9. Restart the Gateway server(s).
   On reboot, Content Gateway detects the feature. On a page refresh, Content UI displays the clipping control for video content.

...

The Content UI adds the scissor  icon to the right of the video control bar on video-format objects with a sufficient number of frames to clip. Check the Gateway installation if the icon does not appear. Selecting the icon toggles the video clipping toolbar open and closed.

...

Three ways to set the time span of the clip. Select a method based on the precision needed:

• Drag the green and red bars

• Select a bar and use the left and right arrow keys to move it frame by frame (supported in Chrome)

• Enter minute:second[:millisecond] values in the Start Time or End Time fields

The default format for Clip Name is {original-name}-{start}-{end}.{filetype} but it can be customized. The clip name dynamically reflects the selected start and end times unless the field contains a custom value. This becomes the object name after selecting Create Clip:

The tool writes the clip to the same bucket as the source video.

The following shows an example of a clip with the default name beside the original video.

...

Each video clipping event logs multiple operations to provide auditing through the process, which might take a long period. Gateway creates video clips asynchronously to accommodate requests of all sizes and acknowledges the request with an INVOKE message, which appears first in the audit log. The acknowledgment references the future JSON result object. The JSON result displays the outcome of the clipping request as Sucess or Fail, the FFmpeg exit code, and the duration, capturing the same information as if it is synchronous.

...