#Convert qlab 4 to qlab 3 full#
#Convert qlab 4 to qlab 3 software#

#Convert qlab 4 to qlab 3 full#

If you have full control over all devices on the network (including the sound computer), or the sound department also use the 10.101.x.x range, it is easiest to stick with these defaults, and ensure the IP address of the QLab computer is in the same range.Д«ut often, someone else is running sound, and they may have their own network, with their own IP address scheme.

Consoles with 2 network ports (Windows 7 consoles) use the .x range for their second port by default. Consoles with 1 network port (Windows XP consoles and ETCnomad Puck) use a default IP address in the 10.101.x.x range. This is all you need to know for a basic network setup between Eos and QLab - for more detail, see the et cetera blog post on IP addresses and subnets.Д®TC uses default IP addresses per product type, as detailed in this article. Another device with the IP address 192.168.1.55 could not talk to them. In the example above, the two Eos family consoles can talk to each other because they share the 10.101. Consequently, for 2 devices to be on the same subnet, their first 2 numbers must be the same (10.101.), but the remaining numbers can be different (and at least one of them must be).Set the Subnet Mask on every device to 255.255.0.0.Subnets are complex, but we can keep it simple for now: So with two Eos family consoles, one could have the address 10.101.100.20, and the other 10.101.90.101 - so far so simple.Д«ut the IP addresses of two devices must be in the same subnet, if those devices want to talk to each other. An IP address consists of 4 digits between 0 and 254 separated by decimal points. The trade-off is that OSC can be more time-consuming to set up.ДЇor an in-depth look at how OSC is implemented in Eos, see p47 of this document (PDF).Д®ach device on a network must have an IP address, which must be unique within that network. The advantage of OSC is that no additional MIDI hardware is required, as everything happens on the network, and that OSC is much more powerful. Luckily, both Eos and QLab are flexible enough to avoid this.ДЇormerly, the MIDI protocol was commonly used for this purpose.

#Convert qlab 4 to qlab 3 software#

If the sound software can only output in the format '/cue/1/go', but the lighting console can only understand in the format '/lights/cue/1/fire', we have a problem. Part of the trick in getting different devices to talk to each other is to have them speak each other's language. Other devices implement OSC in different ways for example, QLab would understand the incoming command '/cue/1/start'. For example, Eos can understand commands like '/eos/chan/1/out', which would turn off channel 1, or '/eos/cue/1/fire' to run Cue 1.

IвЂ™ve been fortunate to have worked on some amazing projects вЂ“ everything from establishing an international puppetry festival, to creating a high end studio ceramics exhibition, to delivering city-wide, site specific theatre projects, to helping artists and academics recreate the acoustics of a long ruined abbeyВ вЂ“ live in the footprint where the building stood.OSC is an open protocol which allows the sending and receiving of human-readable messages between sound, lighting and other entertainment technology systems. I work across disciplines in theatre, music, visual arts, festival, digital, community and education.ДЄs a cultural sector practitioner, my credits include major public events such as the Bradford Mela & Festival, Illuminating York, The York Mystery Plays and the PRSF New Music Biennale. If you have a lot of experience with the software this session is probably not for you.В Because this is a highly requested session and we can only accommodate 25 participants, places will be allocated on a first come first serve basis.ДЇor 20 years IвЂ™ve been providing comprehensive management infrastructure for projects, productions, festivals, and events in the creative and cultural industries. Qlab webinar is an additional session to our Production Management Training, and it works as an introduction to Qlab. Please bring along your questions and Ben will try to answer as many queries as possible. The session will conclude with a brief Q&A on Qlab. Ben will be creating cues, sequences, inputs and outputs and examples of working with both sound and video. We will be getting to grips with the interface, as well as, understanding the different cue types and where you might use them. This session is designed to help you find your feet and give you confidence to explore Qlab further.Д«en Pugh will demystify the idea behind Qlab breaking down what the app functionalities actually are and how you can use them effectively for work.