Are you running with the experimental CEF integration turned on? That’s known to crash and would create many instances as you describe.
If you mean the Use CEF as Web Browser option in the Display Settings… then yes - although the GUI doesn’t mention that it is experimental… but thats just me being picky.
Does the IE setup not have a memory error issue?
There are memory issues with Internet Explorer, although they’re much reduced in 1.7.3.
The CEF integration is experimental and known to cause issues, so I wouldn’t suggest running it in production.
okay then.
Well I switched to CEF as IE didn’t like displaying our AXIS IP CCTV camera ActivX feeds. They work fine in native IE on the Client, but not within XIBO… any suggestions?
You’ve done the registry patches to enable newer version of IE to be used?
Nope - guess I’ve missed them…
It’s in the FAQ here:
You may also need to change the Advanced Settings in IE to allow active content on local webpages (since you’re trying to run ActiveX)
Cheers, yes I had found that.
In that case enable mouse support on the Player, load your layout and then you should be able to interact with the webpage containing your ActiveX content and see why it’s not loading.
It’s just whatever version of Internet Explorer you’ve nominated so if it works in native IE it should be working in Xibo too - assuming you’ve made the registry edit in the correct location (especially if this is a 64 bit machine as you’ll need to make the edit in the 32 bit section of the registry)
Also ensure you’ve got the webpage media set to Open Natively as that should be the “purest” way of opening the webpage within the Xibo Player. The other modes will introduce iframes which may break whatever you’re trying to embed.
I’m using Embedded html…
Then you definitely need the setting in IE to allow active content to run on local pages. Did you find that and set it appropriately?
“Allow active content to run in files on My Computer”
OK. In that case I’d suggest then your embedded content isn’t working.
If you enable the mouse, then view source on the region with the page running, then you can save the page from Xibo, and then open that in IE to confirm that it’s doing what you expect.
My guess is the code you’re embedding is assuming that the activex control is being run from the camera itself rather than a page located on the C: drive - but you’ve given so little information about how you’ve set it up I’m really making educated guesses.
A detailed overview of exactly what you’ve done is the only way this is going to progress otherwise.
This is the Code I’m embedding. just to restate, displays fine with CEF.
<SCRIPT LANGUAGE="JavaScript">
var BaseURL = "http://192.168.106.139/";
var Camera = ""; // If you use an AXIS 240Q/241S(A)/241Q(A)/243SA, comment away this line by inserting "//"
// var Camera = "n"; // Change n to the Video source used in the AXIS 240Q/ 241S(A)/241Q(A)/243SA and remove "//"
// AXIS 207/210/210A/211/211A/212 PTZ/216FD/221/225FD
// var ImageResolution = "320x240";var DisplayWidth = "320";var DisplayHeight = "240";
var ImageResolution = "640x480";var DisplayWidth = "640";var DisplayHeight = "480";
// AXIS 213 PTZ/214 PTZ/231D(+)/232D(+)/240Q/241S(A)/241Q(A)/243SA PAL
// var ImageResolution = "352x288";var DisplayWidth = "352";var DisplayHeight = "288";
// var ImageResolution = "704x576";var DisplayWidth = "704";var DisplayHeight = "576";
// AXIS 213 PTZ/214 PTZ/231D(+)/232D(+)/240Q/241S(A)/241Q(A)/243SA NTSC
// var ImageResolution = "352x240";var DisplayWidth = "352";var DisplayHeight = "240";
// var ImageResolution = "704x480";var DisplayWidth = "704";var DisplayHeight = "480";
// This is the path to the image generating file inside the camera itself
var File = "axis-cgi/mjpg/video.cgi?resolution="+ImageResolution;
// No changes required below this point
if (Camera != "") {File += "&camera=" + Camera;}
var output = "";
if ((navigator.appName == "Microsoft Internet Explorer") &&
(navigator.platform != "MacPPC") && (navigator.platform != "Mac68k"))
{
// If Internet Explorer under Windows then use ActiveX
output = '<OBJECT ID="Player" width='
output += DisplayWidth;
output += ' height=';
output += DisplayHeight;
output += ' CLASSID="CLSID:DE625294-70E6-45ED-B895-CFFA13AEB044" ';
output += 'CODEBASE="';
output += BaseURL;
output += 'activex/AMC.cab">';
output += '<PARAM NAME="MediaURL" VALUE="';
output += BaseURL;
output += File + '">';
output += '<param name="MediaType" value="mjpeg-unicast">';
output += '<param name="ShowStatusBar" value="0">';
output += '<param name="ShowToolbar" value="0">';
output += '<param name="AutoStart" value="1">';
output += '<param name="StretchToFit" value="1">';
output += '<BR><B>Axis Media Control</B><BR>';
output += 'The AXIS Media Control, which enables you ';
output += 'to view live image streams in Microsoft Internet';
output += ' Explorer, could not be registered on your computer.';
output += '<BR></OBJECT>';
} else {
// If not IE for Windows use the browser itself to display
theDate = new Date();
output = '<IMG SRC="';
output += BaseURL;
output += File;
output += '&dummy=' + theDate.getTime().toString(10);
output += '" HEIGHT="';
output += DisplayHeight;
output += '" WIDTH="';
output += DisplayWidth;
output += '" ALT="Camera Image">';
}
document.write(output);
document.Player.ToolbarConfiguration = "play,+snapshot,+fullscreen";
</SCRIPT>def doesn’t like the html code being local… loads when the files is a network location, but not on c:\
So it may be a case of needing to put that file on a webserver somewhere then and load it with the Webpage media type in Xibo instead
well browsing to it from client in IE to a local Intranet server works fine, but XIBO still not loading it…
The View Source confirms it is the correct file - included a line on the webserver version that only it has…
All Xibo is doing is opening an IE browser control and loading your code in, so I’m afraid it might be that you have to tweak that code to get things working. Without having an Axis camera here to work with I’m afraid it’s not something we’re going to be able to help with
Hello. did some further experimentation and if the <meta http-equiv="X-UA-Compatible" content="edge" /> is changed to IE=10 the local pages seem to work on the client.