We were primarily testing with just the URL. But I can see about setting up a few workstations/tablets/mobile tests.
This is very cool, I am very much looking forward to trying your module!
This may be a tall order but have you thought about PTZ controls?
Yeah I have, but we actually don't have any on site surprisingly. So it would be hard for me to test.
I was able to get the columns to adapt properly as the screen stops down to mobile size. This way there is just a single column on mobile, 2-3 columns on tablet and whatever you set for desktop.
Looks like its having some issues with showing up in the workstation, so I'm looking into that.
So from what I'm seeing it seems that the Workstation doesn't come with any proprietary codecs. This works for PC because browsers like chrome /edge ship with codecs (h.264 + AAC) built in.
I don't think there is anything I can do about that. So this might not be an option for clients using Ignition's Workstation. Even If I were able to include the codec (which I don't have plans to) the codec would need to live in the workstation application, not in the gateway.
If you have obtained a license to re-use AAC/H264 in your application (this is not an IA licensing problem, but a patent owner negotiation problem), you can provide system property overrides to your workstation launcher config and we'll toggle the proprietary codecs on when we construct JxBrowser:
-Dignition.client.jxBrowser.h264=true (legacy: ignition.jxBrowser.h264)
-Dignition.client.jxBrowser.aac=true (legacy: ignition.jxBrowser.aac)
Which toggle these JxB features.
Note that this is completely offline and based on the honor system. But make sure you pay the patent holders their money.
I had a distribution question for anyone who's published on the Exchange:
My module bundles MediaMTX (RTSP -> HLS) so it runs fully offline / air-gapped, nothing extra to install. That puts the .modl at ~50 MB, well past the Exchange's 10 MB limit (per-OS splits don't get close either), so I can't upload the package itself.
That leaves two paths:
- Skip the Exchange — host the .modl on GitHub Releases and link it here
- Small Exchange upload with docs + the GitHub download link on the Exchange for discoverability, with the actual .modl hosted on GitHub.
Note: I'd like to keep a genuinely useful free version available, and offer paid tiers for larger multi-camera deployments for larger businesses to fund ongoing support and development.
Is using a link-only "hosted elsewhere" Exchange entry frowned on? Or should I just make a post and use the GitHub page to distribute it?
The exchange isn't the right place to distribute a module. You either need to sign up and distribute it via the third party module showcase, or just host it externally e.g. GitHub.
If you ever want to sell and play nice with IA licenses, then the showcase is mandatory. Otherwise you invent your own licensing.