# Video player component woes (perspective workstation inadequacy?)

**URL:** <https://forum.inductiveautomation.com/t/video-player-component-woes-perspective-workstation-inadequacy/49577>\
**Category:** Ignition\
**Created:** [August 5, 2021, 4:37am UTC](https://forum.inductiveautomation.com/t/video-player-component-woes-perspective-workstation-inadequacy/49577 "2021-08-05T04:37:20Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 16, 2024, 5:24pm UTC](https://forum.inductiveautomation.com/t/video-player-component-woes-perspective-workstation-inadequacy/49577/9 "2024-12-16T17:24:37Z")

</div>

I'm not sure if this was documented anywhere besides a release note, but:

> These changes allow the user to enable the proprietary codecs and DRM technology (widevine) via system properties where JXBrowser is used. Three additional boolean properties were added to allow this:
> 
> - `ignition.jxBrowser.h264`
> - `ignition.jxBrowser.aac`
> - `ignition.jxBrowser.widevine`
> 
> These properties are specified in the JVM arguments field for the Designer and Vision Client Launchers and via perspecitveworkstation.l4j.ini; mac app's Resources/{Launcher}.json file; and modification of the shell script for linux.

---

_[View the full topic](https://forum.inductiveautomation.com/t/video-player-component-woes-perspective-workstation-inadequacy/49577)._