Rule without path restrictions What if I define a rule without restricting it to a certain Zoom path? If a rule has no path defined, then the rule implicitly applies to all the assets in the repository. While it may have been your intention to define an umbrella policy for all your assets, please make
Auto-Retirement FAQs Read More »
Zoom allows restrictions to be imposed on numbers of characters allowed in a string type metadata field at the time of ingest and during manual update. Follow these steps to apply this restriction: Log into the Web Management Console at http://[YourZoomServer]:8443 using your preferred web browser. Open Server Control Panel page from the left sidebar.
Maximum characters in a metadata field Read More »
Data Lifecycle Management in Zoom From 7.3 onwards, Zoom offers a more sophisticated data lifecycle management (DLM) experience. On the data ingestion side, the more tightly integrated VideoFX and VideoLX modules have become much easier to set up as well as pack more powerful new features like support for image sequences, etc. Post ingestion, the
Hierarchical Archive and the Job Hub Read More »
Zoom Hierarchical Archive Flow In Zoom 7.6.2, there are some changes in this module. Check this article for details. In the Asset Browser or Web Asset Browser, select one or more assets to be archived (Tier 0 to Tier 1) and select Archive from the Action menu. You could also right-click on the selected assets
Hierarchical Archive in action Read More »
Locale for Curator Server Follow these steps to set up Curator Server to use the new locale: Open wrapper.conf for editing from the conf folder inside your Zoom installation folder (Windows: [ZoomInstallDir]\conf and Linux: [ZoomInstallDir]/conf). Locate the line with the highest n for wrapper.java.additional.n in the file. Add 2 new lines for wrapper.java.additional increasing the value of
Locale setup for Curator Server Read More »
Locale for Preview Server Follow these steps to set up Preview Server to use the new locale: Open wrapper.conf for editing from the conf folder inside your Zoom installation folder (Windows: [ZoomInstallDir]\conf and Linux: [ZoomInstallDir]/conf). Locate the line with the highest n for wrapper.java.additional.n in the file. Add 2 new lines for wrapper.java.additional increasing the value of
Locale setup for Preview Server Read More »
From Zoom 7.3.1 onwards, new locales are supported in Zoom for use by all desktop and web-based Zoom Clients. To use these locales effectively with a Zoom Client, these should also be set up on all servers within Zoom, the Zoom MAM Server, Preview Servers, Curator Servers, and any HADR peers. Follow these steps on
Locale setup on servers Read More »
From Zoom 7.3 onwards, you can conveniently save or update one or more Zoom properties at a single place on the Zoom Server using the Web Management Console. These properties could be for use by the Zoom Server or one or more Zoom Clients. For a simple Zoom setup that does not use locations (as
Server Zoom Properties Read More »
Curator configuration in Zoom 7.3 is simpler and quicker, without having to edit any XML files or installing any services manually. All required services are installed with the Zoom Server installer and then the rest of Curator configuration is done using the Web Management Console only. Curator setup after Zoom upgrade to 7.3 You need
Curator Configuration (Zoom 7.3+) Read More »
VideoLX 3.0 is Evolphin’s lightweight proxy-based asset management module that lets Zoom users manage, store, and access high-resolution media files that are saved on high-speed bulk storage outside the Zoom repository. It is an upgrade to the previous VideoLX 2.0 with support for transcoding image and audio files, custom transcoding for different file types, location-based
Getting started with Zoom VideoLX 3.0 (Zoom 7.3+) Read More »
After Video LX 3.0 (Zoom 7.3+) has been set up as specified here, all check-ins to the Zoom repository will be screened for high-res assets. On a Zoom Client machine that is configured for a location set up for VideoLX, whenever a video asset is checked-in, it is compared against the ingest criteria as specified
VideoLX 3.0 in action Read More »
The Hub has a dashboard to track and monitor archive/restore jobs and it is accessed from Zoom’s Web Management Console. If you have installed Hub for AI, then the Hub Dashboard should be accessed as http://[HubServerIP]:8282/index.html. Check for more details. After your Hub is set up and all archiving parameters defined, you can view
Once all the setup for VideoFX 2.0 (Zoom 7.3+) is complete as described here, we are ready to see VideoFX 2.0 flow in action. A typical VideoFX 2.0 flow starts from the source file on the Client machine and ends on the low-res proxy checked-in to the Zoom MAM Server. Check here to see the
VideoFX 2.0 in action Read More »
Sometimes mounting shared network folders on a Windows machine becomes a very complex task as it depends on the flavor of Windows operating system in use and also the configurations that have been set up. Follow this post to mount a shared network folder as a new drive letter on a Windows system. A better
Using UNC paths on Windows Server Read More »
After Zoom is upgraded from Zoom 7.2 to 7.3, any SGL Archive scripts need to be updated as well. From Zoom 7.5 onwards, archive on ingest is not supported using SGL. As per VFX 2.0 in Zoom 7.3, we do not need Perl scripts to do Proxy ingest and hence Perl scripts are not needed
SGL Archive Script changes after Zoom upgrade Read More »
7.3 License Changes In one of the major enhancements of Zoom 7.3 release, it now supports integration with multiple VideoFX, VideoLX, and Vantage Servers. These ancillary Transcoding / Ingest Servers may be geographically distributed or be at the same geographical location. The system also comes with the ability to pre-configure location settings that in turn
Zoom VideoFX 2.0 is a proxy-based high-res asset manager that works with a third party transcoder, Telestream Vantage. It also supports external archives to be integrated into user-defined workflows. At the basic level, a VideoFX 2.0 setup should have an Ingest Server to interact with the PSAN and a Transcoder to interact with the third-party
Getting started with Zoom VideoFX 2.0 (Zoom 7.3+) Read More »
After you have installed or upgraded to the OpenID Connect-enabled version of Zoom, added your Zoom license, and created a default super admin account in Zoom, you are ready to integrate with an OpenID Connect provider. Since the configuration varies for each OpenID Connect (OIDC) provider, for the purposes of this article we assume you
Configuring an OpenID Connect Provider such as PingID Read More »
On a Ping setup, if the details of an LDAP user have not been pulled into Zoom (using the Web Management Console) and this user tries to log into any Zoom application using the global single sign-on, then the login is successful. But, this user is unable to access anything in the Zoom application as
LDAP user using Ping sign-on not able to access if not pulled in Zoom Read More »
After your servers have the VideoLX setup, we are ready to run the installer for archive/restore scripts. The installer should be run on the Zoom MAM Server. The installation package consists of all the scripts and the primary configuration file config.ini. This configuration file is the master copy containing all the relevant information necessary for the
Script installer for Archive/Restore with VideoLX Read More »
