Player FAQs

The player introduces several enhanced and refreshed features compared to the previous version, including:

• Barrier-free design – Improved accessibility for all users.

• Multi-audio playback – Support for multiple audio tracks.

• Chapters – Easily navigate through content with chapter markers.

• Customizable subtitles – Adjust subtitle appearance to your preference.

• Interactive transcripts – Read along and interact with transcripts in real time.

• Responsive embeddings – Optimized playback across different devices and screen sizes.

• Playback speed control – Adjust the speed for a personalized viewing experience.

• Player customizations – Tailor the player appearance and functionality

For full details please check our player homepage

The new version offers several improved and new features when compared to the old player. However, there are certain features from old player that have been excluded. Here are some key differences:

• Sharing video via a URL: The new player replaces the separate share, video, and preview URLs with a single page link, simplifying the video-sharing process. In addition, you can choose to show or hide video title and description and decide the video start time before sharing a video via new player

• Embedding Options: While the old player generated both HTML and i-frame embed codes, the new player only provides an i-Frame embed code. As a result, HTML codes are not supported in the new player, customer already using HTML embed codes can use the migration switch in the player generator to migrate their embed codes

• Analytics and user consent: While the old player allowed you to enable minimal analytics and for full tracking show the consent dialog within the player, the new player offers minimal analytics as default. In addition, the consent banner is now only shown on the shared page link and is no longer available within the player itself. For embedded videos, user consent must be passed to the player via the SDK using the AnalyticsMode setting

• Old API vs SDK: The old player relied on an API for integration, whereas the new player is built on an SDK, replacing the API-based approach. This change provides more flexibility and control over video playback and analytics. Developers integrating the new player will need to use the SDK's methods and configurations instead of API calls. For detailed implementation guidelines, refer to the documentation

While the above points highlight the key differences. Please click here to get a full comparison between our players.

The three old sharing pages were essentially the same, differing only in player size. However, the distinction wasn’t always clear, so they were merged into a single Share Page link for simplicity. Sharing pages are mainly used when embedding isn’t possible or for internal video reviews example. Users can still adjust the player size by resizing the browser window or using full screen mode.

Unlike before, the new sharing page link also offers some configuration options like hiding or showing title or description respectively on the page and starting video from a specific position.

More details here.

Currently no customizations are available for page links, therefore, a default banner is shown. Since its a standalone hosted page, the banner ensures compliance and gathers user consent before enabling full tracking.

The primary reason for discontinuing support for HTML embed codes is to avoid integration conflicts. However, there are several key benefits that iFrames offer, like:

• Security Benefits - Iframes operate within their own isolated container, meaning they cannot directly access or modify the parent page. This separation helps prevent security vulnerabilities associated with direct script embedding.

• Content Isolation: The content inside an iframe is isolated from the rest of the page. This is useful when embedding third-party content that you don’t control, as it prevents any potential conflicts with your main page’s styles, scripts, or functionality.

• Performance Considerations - While iframes require slightly more processing power, the advantages they offer—particularly in terms of security and compatibility—far outweigh this minor drawback.

Note: While the older embed code remains backward compatible for a transitional period i.e. until old player is still active, it is recommended to use the new iframe-based embed code moving forward. Refer to the migration guide for more details

You can enable the Responsive iframe Toggle in the Publish section of VMPro.

When enabled, the iframe automatically adjusts to fit its container, adapting to different screen sizes and orientations. This removes the need to manually set height and width values, ensuring a seamless viewing experience. More details here.

The new player offers two analytics modes: Minimal (default) and Full Analytics.

• Minimal Analytics ("minimal" mode)

  • Default analytics setting of the player

  • Does not require user consent

  • Tracks only the number of plays

  • No other user data or engagement metrics are collected

• Full Analytics ("full" mode)

  • Requires user consent

  • If the user accepts cookies, full analytics such as watch time, interactions, and other engagement data will be collected

Key difference: Minimal analytics works without user consent, while full analytics requires consent to collect engagement data, ensuring GDPR compliance.

For videos are played via a shared page link: Video managers can enable/disable a consent banner on that page via player generator.

• When enabled, the banner appears and tracking behavior follows the user’s choice:

  • User rejects cookies → Minimal analytics ("minimal")

  • User accept cookies → Full analytics ("full")

Note: There is no customization available for this banner yet.

For embedded videos: Use the provided SDK method ‘AnalyticsMode’ to send tracking information based on user consent. You can use this function to send consent information to the player based on user’s choice on your websites.

• AnalyticsMode: "minimal" | "full"

Important: Unlike the old player, the new player does not display a consent banner within the player itself. Enabling "Show consent banner" will only display the banner on the shared page link. For embedded videos, user consent must be handled via the SDK as outlined above. For details on the SDK function, please check our player SDK developer documentation.

Yes, the player offers an SDK (Software Development Kit), which replaces the old player API. Please refer to the SDK documents here to know more about how to use it.

An API (Application Programming Interface) is a set of rules that allow different software components to communicate. It provides functions and endpoints to interact with a system but requires manual implementation.

An SDK (Software Development Kit) is a complete package that includes tools, libraries, and pre-built components to simplify integration. It often uses APIs but provides a more structured and secure way to interact with a system.

While both the old Player API and the new Player SDK allow interaction with the player (e.g., play, pause, mute) and event response, there are key technical differences and advantages:

• Player Integration: The SDK interacts with an embedded iFrame, whereas the old API modified your page’s code by generating a player directly within it

• Modular Design: Built with ES Modules, the SDK stays isolated from existing code, improving control and security

• Optimized Performance: Unlike the old API, which loaded extra code, the SDK loads only what's necessary, leading to faster page loads

End of September 2025. That means we will no longer take requests on the old player and will not fix bugs, the old player will continue to function as it does.

The new player offers several benefits over the old. Visit the New Player homepage to find out more. Alternatively, check one on one comparison between the players here.

To switch to the new player, go to the Player Generator in VMPro and toggle the migration switch to "ON". Adjust the settings as needed and click ‘Apply’ to update shared page links and embed codes.

If required, you can revert to the old player by switching the toggle to "OFF" in the Player Generator. This restores previous HTML player configurations. Click ‘Apply’ to confirm, and your embed codes and shared links will return to using the HTML player

No, you do not need to manually replace each embed code. Once you switch to the new player in the Player Generator and click ‘Apply,’ all existing embedded videos and shared page links will automatically use the new player.

If you interact with the player via API (e.g., auto-playing videos before playback, handling player events, etc.), you may need to migrate to the new Player SDK. Refer to the SDK migration guide for detailed steps.

No, the player ID will remain the same, so existing embeddings won’t be affected.

Some settings will transfer, but not all. The new player has different configuration options, so you may need to adjust some settings manually in the Player Generator to match your requirements.

No, the migration will not affect business operations if the new player is properly configured and all prerequisites are met. The migration happens instantly upon clicking the switch.

No, the migration will not result in extra expenses. The new player is intended to replace the old player without additional costs.

No, all existing embed codes and shared URLs will automatically use the new player once you enable migration in the Player Generator and apply the changes.

Some settings and API functionalities may not transfer exactly. Manipulations on the HTML embed code player, such as custom styling modifications, will no longer work. We recommend thoroughly testing the new player, especially for advanced use cases involving API interactions. If any issues arise, reach out to support@movinimage.com.

The old player will continue to function but will no longer receive updates, fixes, or support after September 2025. To ensure continued improvements, security, and compatibility, we recommend switching to the new player as soon as possible.