Web Camera: libvlc.dll error

[simplextech]

I tried the Web Camera widget and I get an error about libvlc.dll not found when I load IV.  I have VLC installed on both the server and on my client.  I can load the camera page in my web browser (firefox).

[simplextech]

Error resolved by installing 32 bit version of VLC. Yet no video. The IV widget loads to a black screen. I have the same URL open in a browser and it works fine. I changed the resolution down as well to have a smaller image in IV but just a black box still.

[simplextech]

Even with WebRTC the WebURL part of the widget is not loading. However a standard RTSP feed loaded fine.

[gReatAutomation]

I had to install the DLLs into the Windows System directory. Also, how are you viewing the IV for the cameras? Directly on the CQC machine itself? A "slave"? Are you running CQC in a VM and trying to view it in the VM (I could never get a VM solution working properly).

[gReatAutomation]

Even with WebRTC the WebURL part of the widget is not loading.  However a standard RTSP feed loaded fine.

What URL are you using for the camera feed in the WebURL? The HTTP stream or the RTSP stream?

I had thought that to use WebURL you have to feed it an HTTP stream.

[simplextech]

I had to install the DLLs into the Windows System directory. Also, how are you viewing the IV for the cameras? Directly on the CQC machine itself? A "slave"? Are you running CQC in a VM and trying to view it in the VM (I could never get a VM solution working properly).

Tried from a salve and from the server itself.  Same error with VLC.  Two things with VLC.  It must be the 32bit version and you must add the install location into your system PATH.  

Even with that it did not fix the WebURL.  I don't know for sure if the WebUrl is supposed to support a HTTP camera feed either via a WebRTC or through a tradition mjpeg type URL.  It would seem odd to not support the standard mjpeg format that every NVR system provides.  I would think most people are running their cameras through Blue Iris or Xeoma or some other system which is then also providing a HTTP feed for those cameras.

After several tries with the WebURL not working I changed to using just the URL entry box and using a direct RTSP link to my cameras.  This works fine.  This is a more direct method of accessing the cameras anyways and does provide more advanced camera interaction as long as the cameras provide support for direct RTSP.  Most of mine do.  However my Unifi Cameras I have to send a sub channel RTSP for them which is ok and I do that today feeding them to Xeoma.

It would be nice not to have to guess and figure out what each URL is for each camera and just be able to go through either Blue Iris or Xeoma that has the camera feeds and then have CQC use the Web URL from Blue Iris.  I'm sure this is possible and it may be a problem with Xeoma which is what I'm using and was trying last night.  

I have Blue Iris so I'll start it up and see if the WebURL works with Blue Iris.  If it does I may switch back to BI from Xeoma.

[batwater]

Just looked at Xeoma, pricey for any quantity of cameras. Here I am running Blue Iris. I don't have it currently integrated with any of my user screens but have on the list to look at leveraging MQTT to trigger display of feeds on TV(s) in the house.

[simplextech]

Just looked at Xeoma, pricey for any quantity of cameras.  Here I am running Blue Iris.  I don't have it currently integrated with any of my user screens but have on the list to look at leveraging MQTT to trigger display of feeds on TV(s) in the house.

Xeoma is pricey if you go above 4 cameras.  The feature set included is nice and I like that it runs on Linux and currently I'm running it in a docker container on my UnRaid system which is nice.

In Xeoma I have it sending a HTTP event on motion start and motion end to CQC and I'm using the HTTP-Trigger driver to set a variable for motionStart and one for motionEnd so I can use those within events.  

The same can be done with Blue Iris with HTTP or MQTT.  I've put in a request to get MQTT support added to Xeoma as well.

[simplextech]

Update: Using the standard URL (NOT WebURL) in the Camera widget I've been able to access a RTSP feed via a rtsp:// url and a h.264 feed through a http:// url and a mjpeg feed with a http:// url. Seems the trick here is to just use the URL field in the widget and NOT the WebURL if looking to interface with cameras through Blue Iris, Xeoma, Anything, or going direct to the camera's RTSP feed.

[batwater]

Just looked at Xeoma, pricey for any quantity of cameras.  Here I am running Blue Iris.  I don't have it currently integrated with any of my user screens but have on the list to look at leveraging MQTT to trigger display of feeds on TV(s) in the house.

Xeoma is pricey if you go above 4 cameras.  The feature set included is nice and I like that it runs on Linux and currently I'm running it in a docker container on my UnRaid system which is nice.

In Xeoma I have it sending a HTTP event on motion start and motion end to CQC and I'm using the HTTP-Trigger driver to set a variable for motionStart and one for motionEnd so I can use those within events.  

The same can be done with Blue Iris with HTTP or MQTT.  I've put in a request to get MQTT support added to Xeoma as well.

Good background info, thanks!  I'm running 14 cameras.  Also running Unraid here to host 3 Win 10 PC instances, 2 with dedicated video and USB ports.