However for our internal purposes we used Vimeo. The below written tutorial is built using Youtube as an example video host – we have attempted to make this first tutorial as accessible and open source as possible. We hope that we can contribute in some small way to help move the world forward, help industries and techies continue to exchange information in innovative, simulated conferency ways. We will be posting more tutorials and hopefully helpful videos on this topic in the coming days and weeks at our blog for anyone who may be interested in following along.
We hope that you may like to join us in our journey as we explore what conferences may look like in the, “virtual,” space as opposed to merely the physical space. In short – we’ve seen it all, we have built extremely innovative and wacky things and connected to them to the internet under extremely tight timeframes and this is no different.
Each year we have run and participated in both the IoTFuse conference and workshop series in April, which you can read about more on this website – as well as the IoTHackDay in October, which you can read more about here, here, here, here and here. Is this a daunting challenge? Yes, absolutely – but we have run multiple massive scale workshops, conferences and hackathons before going back since at least 2015 – using all sorts of connected devices, operating systems, networking challenges and hardware. We’re talking about having up to 10 speakers simultaneously, with a total of up to 60 speakers, and including the capability for those speakers to interact with the audience – all while the speakers and workshop administrators stream from their homes and apartments from multiple locations and different varieties of machines. Have virtual conferences been done in the past? Yeah, sure – but not on the scale and magnitude that we’re going for here.
Rather than not go forward with the conference – we thought to ourselves – well, as engineers – what can we do to move humanity forward in the face of this great challenge? We thought that rather than delaying and postponing a conference indefinitely to a date that may never come in the age of social distancing, we should, “make lemonade out of lemons,” and put all of the, “Internet of Things” skills that we have been working on over the past several years to good use and build a completely new form of conference.
Sadly, as everyone not living under a rock right now knows – all events worldwide have been cancelled, for very good reasons. Paul and greater midwest tech region, the IoTFuse Conference has been the go-to place to get together and network with others living at the intersection of the digital and physical space. Fire up your favorite web browser and visit the following URL (replacing with.For many in the Minneapolis-St.
When you're done, you may want to come back here and read on to find out how to access the frontend or how to update your motionEye.Īfter having successfully followed the installation instructions, the motionEye server should be running on your system and listening on port 8765. no locally connected cameras and no IP cameras), you can skip installing motion, ffmpeg and v4l-utils.Ĭhoose one of the following specific install instructions. Note 3: If you are configuring a motionEye system that will only act as a hub for other motionEye-based cameras (i.e. Note 2: On systems where Python3 is the default Python interpreter, you should use the pip2 command instead of pip. Note 1: The given commands normally need to be run as root type them in a root shell or use sudo before each command. Following are detailed instructions for some common distributions. MotionEye releases are uploaded to PyPI, so you can use the pip (or pip2) command to install it as well as (some of) its dependencies. Install it (along with ffmpeg and v4l-utils) unless you configure a machine that will only act as a hub for other motionEye-based cameras. The motion daemon itself is optional, but needed in most cases. a machine running a recent Linux distro.