Hi, my broadcast company would like to transition from XSplit to xMix, but we've run into a problem. We use HTML for our game overlays, and these have worked fine for both OBS and XSplit. However, switching to xMix we ran into an issue. Both OBS/XSplit use a web browser that allows for Same-Origin Policy (which prevents a website to be able to access files outside of its origin) to be ignored. However, because VMix's browser uses Chromium, it is unable to, as far as I'm aware. This is because Chrome/Chromium refuses sites that are hosted on the computer (aka opening index.html in a folder on your computer) to access other files. With Chrome itself, you type this in Chrome's folder to ignore it: "chrome.exe --disable-web-security". I don't believe this works with vMix though.

So, basically, is there a work-around to let us have web files mingle with each other in their own folder? I'm doing research into it, but I figured I'd also ask in case someone has already run into this issue and found a solution. It's sort of like this, but I'm not sure how to apply it to vMix.

Thanks!

The issue isn't loading a website in particular, it's loading a local file that's trying to access a JSON/XML file that's in the same folder. This is something called "Same Origin Policy", which is a thing with all browsers, but Chrome in particular takes it to another level by also blocking local files from shaking hands with themselves. Chrome.exe can let you ignore that with a certain line of code when opening the exe file through Command Prompt, but we can't use that for vMix.

I also personally disagree with the idea that HTML encoding is worse than Flash, and in my eyes, Flash is inferior just because it's such a processor hog.



This is the kind of thing we do with HTML. Easing in text, images, and updating data live with StreamControl, which is a system that updates XML and/or JSON files on the fly with a very clean and customizable interface. We really don't want to transition away from it if we can help it, since it's also basically one of the industry standards for when we do commissions.

Did you manage to find a solution? I'm also transitioning my team from xSplit to Vmix and this is the only issue I've run into. I need to enable our overlays at least as a stopgap while I learn a better more native way to do this stuff in Vmix.

My overlays don't even need overriding same origin policy because of the way I engineered them but they don't function on Vmix anyway, the JavaScript just doesn't seem to run.

So the workaround you are looking for might involve setting up a web server, setting the correct Allow-Origin headers. Confirming it works outside Vmix without errors. Then just using it from within Vmix. Update your files as per normal and the web server should serve the files. Hope that works out.

Another workaround, maybe less elegant. Would be easy to do.

Run Chrome with the security disabled how you like it. Use desktop capture to bring that chrome instance in as a camera. Then you can just capture the pixels from your chrome configured how you like it rather than the "safe" configuration Vmix uses.