Complete Help Docs

Laser Show Technology for Lighting Professionals

User Tools

Site Tools

You are here: The Pangolin Wiki » Lasershow Designer QuickShow Manual » Networking for Lasershows, QuickShow, and Entertainment
quickshow:system_and_networks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
quickshow:system_and_networks [2024/01/10 15:13]
Bob Varkevisser created 		quickshow:system_and_networks [2024/01/10 15:19] (current)
Bob Varkevisser
Line 1: Line 1:
-====== Networking for Lasershows, BEYOND, and Entertainment ======+====== Networking for Lasershows, QuickShow, and Entertainment ======
  
 ===== Introduction ===== ===== Introduction =====
  
-A somehow “brief” overview of networking for laser shows and the entertainment industry. As well as understanding how BEYOND (and QS) Utilize your PC and your network to achieve a show. And finally how to tune your system to best handle those specific needs of our protocols and entertainment technology in general. Buckle up and have a coffee ready. +A somehow “brief” overview of networking for laser shows and the entertainment industry. As well as understanding how QuickShow Utilize your PC and your network to achieve a show. And finally how to tune your system to best handle those specific needs of our protocols and entertainment technology in general. Buckle up and have a coffee ready. 
  
 This guide assumes a completely unmanaged network, one where all your switches are unmanaged and there is no “network engineer” on site to make it all pretty and clean, and instead that you are just trying to make your shows more reliable utilizing basic networking equipment.  Because of this we may skip over some things for sake of simplicity.   This guide assumes a completely unmanaged network, one where all your switches are unmanaged and there is no “network engineer” on site to make it all pretty and clean, and instead that you are just trying to make your shows more reliable utilizing basic networking equipment.  Because of this we may skip over some things for sake of simplicity.  
Line 118: Line 118:
 ==== Basic IP Schedule Example and network layout ==== ==== Basic IP Schedule Example and network layout ====
  
-{{:beyond:networkingforlasershows1.png?800|}} +{{:quickshow:networkingforlasershows1.png?800|}} 
-{{:beyond:networkingforlasershows2.png?800|}}+{{:quickshow:networkingforlasershows2.png?800|}}
  
 ==== Setting IP’s on your devices. ==== ==== Setting IP’s on your devices. ====
Line 131: Line 131:
    - Enter IP Settings    - Enter IP Settings
  
-{{:beyond:networkingforlasershows3.png?800|}}+{{:quickshow:networkingforlasershows3.png?800|}}
  
 ==== Or in your control panel ==== ==== Or in your control panel ====
Line 141: Line 141:
    - Select “use following IP Address” and enter in your IP.    - Select “use following IP Address” and enter in your IP.
  
-{{:beyond:networkingforlasershows4.png?800|}}+{{:quickshow:networkingforlasershows4.png?800|}}
  
 ==== On FB4 ==== ==== On FB4 ====
Line 147: Line 147:
 Go to the “Network Setup” Dropdown while within a mode that uses network (Like BEYOND Mode). Turn auto IP off until you have a red x. Then enter in the address in the fields below for IP, Mask and gateway. This can also be done in FB4 Settings window. Go to the “Network Setup” Dropdown while within a mode that uses network (Like BEYOND Mode). Turn auto IP off until you have a red x. Then enter in the address in the fields below for IP, Mask and gateway. This can also be done in FB4 Settings window.
  
-{{:beyond:networkingforlasershows5.jpg?200|}}+{{:quickshow:networkingforlasershows5.jpg?200|}}
  
 Check the [[hardware:fb4:quickstart|FB4 QuickStart Guide]] For more information regarding FB4. Check the [[hardware:fb4:quickstart|FB4 QuickStart Guide]] For more information regarding FB4.
Line 169: Line 169:
 There are a couple caveats. You will often find protocols that are “Broadcast, Multicast, or unicast” These three options basically mean whether the protocol will be sent out to every single Ip, to multiple specific Ip’s, or one individual Ip. Broadcast usually allows data to get to where it needs to go, but is very wasteful and inefficient, that’s where multi and unicast come into play, allowing the user to decide specific Ip’s and devices to transmit the data to. Most protocols decide the option for you as part of the protocol, while others give you the option. This is part of why people may choose one protocol over another.  There are a couple caveats. You will often find protocols that are “Broadcast, Multicast, or unicast” These three options basically mean whether the protocol will be sent out to every single Ip, to multiple specific Ip’s, or one individual Ip. Broadcast usually allows data to get to where it needs to go, but is very wasteful and inefficient, that’s where multi and unicast come into play, allowing the user to decide specific Ip’s and devices to transmit the data to. Most protocols decide the option for you as part of the protocol, while others give you the option. This is part of why people may choose one protocol over another. 
  
-==== BEYOND’s laser Protocol ====+==== QuickShow’s laser Protocol ====
  
-Now that we know how networks work and how to set them up, lets talk about the peculiarities of our laser control protocol we use in BEYOND and why it leaves us with some unique challenges. +Now that we know how networks work and how to set them up, lets talk about the peculiarities of our laser control protocol we use in QuickShow and why it leaves us with some unique challenges. 
  
 There main problem we are concerned with when it comes to the laser protocol over network is speed and timing. There main problem we are concerned with when it comes to the laser protocol over network is speed and timing.
Line 179: Line 179:
 Synchronization is also very important, every single laser in your rig needs to be perfectly timed as well, as if they are all slightly off, you may not necessarily “see” it, but you will “feel” it.  Synchronization is also very important, every single laser in your rig needs to be perfectly timed as well, as if they are all slightly off, you may not necessarily “see” it, but you will “feel” it. 
  
-To achieve this synchronization, first, all FB4’s on the network sync with the PC and each other to have the exact same “clock time” with each other. On the BEYOND side, the software calculates every lasers next frame, caches these frames, and when they are all finished they are given a “display time” for a few milliseconds in the future and sent off down your network port, to your switches and to each laser. Over the next couple milliseconds every laser controller in the rig receives their frame, and waits for that “display time” to come to output. When that time comes, they all display the frame they got for that moment in time. +To achieve this synchronization, first, all FB4’s on the network sync with the PC and each other to have the exact same “clock time” with each other. On the QuickShow side, the software calculates every lasers next frame, caches these frames, and when they are all finished they are given a “display time” for a few milliseconds in the future and sent off down your network port, to your switches and to each laser. Over the next couple milliseconds every laser controller in the rig receives their frame, and waits for that “display time” to come to output. When that time comes, they all display the frame they got for that moment in time. 
  
-This is how BEYOND keeps every single laser in time with each other, enabling smooth output and things like distributed scanning. The controllers just get a heartbeat signal that keeps all their clocks matched up and things are synced.+This is how QuickShow keeps every single laser in time with each other, enabling smooth output and things like distributed scanning. The controllers just get a heartbeat signal that keeps all their clocks matched up and things are synced.
  
 When networks are slow, or data is getting damaged by overloaded switches, or bad cables, the TPC process can be slowed down immensely, causing tons of rebroadcasted frames, and frames will “miss” their “display time” and you get “lag” or no output. Often, waiting for a rebroadcasted frame can take tens of milliseconds, which lead to extremely late frames.  When networks are slow, or data is getting damaged by overloaded switches, or bad cables, the TPC process can be slowed down immensely, causing tons of rebroadcasted frames, and frames will “miss” their “display time” and you get “lag” or no output. Often, waiting for a rebroadcasted frame can take tens of milliseconds, which lead to extremely late frames. 
  
-//**So, wait, are you using TCP or UDP for BEYOND?**//+//**So, wait, are you using TCP or UDP for QuickShow?**//
  
-Historically, we have utilized TCP for its delivery guarantee, and while there were a few builds that did make it to the public in early 5.0 days to try and utilize UDP we did revert back to TCP and BEYOND has used TCP for the majority of its life. This has many benefits and drawbacks as you see from the next section of this document. This choice is not final however, and we have continued to do testing and experimentation with UDP instead. And it may very well make it into future versions if deemed more reliable. For the average user. Of course, if the rest of your network is solid, it wont really matter, but those nuances are for when things go wrong. +Historically, we have utilized TCP for its delivery guarantee, and while there were a few builds that did make it to the public in early 5.0 days to try and utilize UDP we did revert back to TCP and QuickShow has used TCP for the majority of its life. This has many benefits and drawbacks as you see from the next section of this document. This choice is not final however, and we have continued to do testing and experimentation with UDP instead. And it may very well make it into future versions if deemed more reliable. For the average user. Of course, if the rest of your network is solid, it wont really matter, but those nuances are for when things go wrong. 
  
 ==== Why fames get “delayed” and the cause of "Purple FB4" ==== ==== Why fames get “delayed” and the cause of "Purple FB4" ====
Line 197: Line 197:
   * Network induced delay.   * Network induced delay.
  
-**First lets discuss CPU**. When BEYOND calculates all the frames for all the projectors in your setup, it live calculates everything, and the process looks something like this:+**First lets discuss CPU**. When QuickShow calculates all the frames for all the projectors in your setup, it live calculates everything, and the process looks something like this:
  
 Cue Frame> Cue effects> Cue Timing> Live FX> Routing> Projection Zone reshape> Projector settings application> Packaging> Delivery Cue Frame> Cue effects> Cue Timing> Live FX> Routing> Projection Zone reshape> Projector settings application> Packaging> Delivery
  
-BEYOND does repeat similar frames, and does some optimization, however when lots of effects, different routings, (or the real challenge), offsetting effects are introduced, this drastically increases the calculation time for output. This leads cheaper and lower performing computers to not be able to actually calculate every single frame before the cycle time expires and BEYOND needs to start over. This cycle time is important for speed and timing and safety reasons like the previous chapter describes. +QuickShow does repeat similar frames, and does some optimization, however when lots of effects, different routings, (or the real challenge), offsetting effects are introduced, this drastically increases the calculation time for output. This leads cheaper and lower performing computers to not be able to actually calculate every single frame before the cycle time expires and QuickShow needs to start over. This cycle time is important for speed and timing and safety reasons like the previous chapter describes. 
  
 CPU induced delay will often appear in real life in dropout or lag in order of zones. Where the first few lasers in your setup may be running fine but you may not even get any output out of your last few lasers, where it degrades more and more between each end. This is an example of very obvious CPU delay.  CPU induced delay will often appear in real life in dropout or lag in order of zones. Where the first few lasers in your setup may be running fine but you may not even get any output out of your last few lasers, where it degrades more and more between each end. This is an example of very obvious CPU delay. 
  
-**Secondly, network induced delay.** This is when data makes it out of BEYOND, but doesn’t make it to the laser controllers before the “display time” they are expecting the frame by. This could mean it failed the TCp-IP check, it could mean it never received anything, or it could mean it was receiving the data when the time elapsed. Either way the data didn’t make it in time, and the fame it was expecting (or if it got it late) has expired. Of course, frames need to expire for the speed and timing and safety concerns from before. +**Secondly, network induced delay.** This is when data makes it out of QuickShow, but doesn’t make it to the laser controllers before the “display time” they are expecting the frame by. This could mean it failed the TCp-IP check, it could mean it never received anything, or it could mean it was receiving the data when the time elapsed. Either way the data didn’t make it in time, and the fame it was expecting (or if it got it late) has expired. Of course, frames need to expire for the speed and timing and safety concerns from before. 
  
 Network induced delay is a little more complicated because it can be many factors at play, but lets talk about the general steps data has to make it through, and the common reasons that part can cause issues. Network induced delay is a little more complicated because it can be many factors at play, but lets talk about the general steps data has to make it through, and the common reasons that part can cause issues.
Line 232: Line 232:
 How do you determine if it’s CPU or Network? Utilize the updated in 5.2 FB4 Data Transmission monitor located under System>Monitoring> FB4 Data Transmission Monitor, under the “Overview/ NetStat” Tab. If you are having issues, icons will appear in the top rows next to your projectors. Use the Key below to determine what kind of issue is happening.  How do you determine if it’s CPU or Network? Utilize the updated in 5.2 FB4 Data Transmission monitor located under System>Monitoring> FB4 Data Transmission Monitor, under the “Overview/ NetStat” Tab. If you are having issues, icons will appear in the top rows next to your projectors. Use the Key below to determine what kind of issue is happening. 
  
-{{:beyond:networkingforlasershows6.png?800|}}+{{:quickshow:networkingforlasershows6.png?800|}}
  
  
Line 243: Line 243:
   * i7 or i9 intel CPU, Modern   * i7 or i9 intel CPU, Modern
   * 16GB of ram is fine for most laser shows, 32 GB of ram if you intend to run multimedia.   * 16GB of ram is fine for most laser shows, 32 GB of ram if you intend to run multimedia.
-  * Get some sort of GPU, just make it a discrete GPU not integrated, Nvidia 3060 class (or generational equivalent) is fine, just to offload the GUI to the VGA. Some things in BEYOND may be calculated on the GPU in the future, so best to be prepared. +  * Get some sort of GPU, just make it a discrete GPU not integrated, Nvidia 3060 class (or generational equivalent) is fine, just to offload the GUI to the VGA. Some things in QuickShow may be calculated on the GPU in the future, so best to be prepared. 
-  * Get an NVME based Hard drive, they are fast and more durable than spinning drives, or even run beyond on portable SSD’s so the install can travel with you to any pc, but that’s another topic for another day. +  * Get an NVME based Hard drive, they are fast and more durable than spinning drives, or even run QuickShow on portable SSD’s so the install can travel with you to any pc, but that’s another topic for another day. 
   * Intel based Networking port.   * Intel based Networking port.
   * Lots of USB IO, lots of our accessories we use are USB, you will need the ports.   * Lots of USB IO, lots of our accessories we use are USB, you will need the ports.
Line 257: Line 257:
 The first thing you should do for a show computer is install windows from scratch, this computer is not your personal gaming computer anymore, it’s a dedicated show computer and a completely fresh instillation of windows allows you to get rid of any bloat and give you a good baseline to start with. The first thing you should do for a show computer is install windows from scratch, this computer is not your personal gaming computer anymore, it’s a dedicated show computer and a completely fresh instillation of windows allows you to get rid of any bloat and give you a good baseline to start with.
  
-Use as little security as possible. This may seem counterintuitive, however the less things interacting with your network the better. Just use your show computer as a show computer and utilize internet for work and you should be fine. Turn off firewalls, don’t use 3rd party security software etc. Windows defender on its own usually is fine and you don’t need to turn that off. BEYOND when first started, will run a small app that will disable the firewall functions that inhibit BEYOND data, so you probably won’t have to worry about firewall.+Use as little security as possible. This may seem counterintuitive, however the less things interacting with your network the better. Just use your show computer as a show computer and utilize internet for work and you should be fine. Turn off firewalls, don’t use 3rd party security software etc. Windows defender on its own usually is fine and you don’t need to turn that off. QuickShow when first started, will run a small app that will disable the firewall functions that inhibit QuickShow data, so you probably won’t have to worry about firewall.
  
 Disable Windows Updates, if you are on windows pro versions, you can do this through the UI pretty easily, however if you are on a Home version, you need to disable windows update through the “Services.msc” application. [[https://www.tomsguide.com/how-to/how-to-turn-off-automatic-updates-in-windows-10|Here is a good guide on Toms Guide]] Disable Windows Updates, if you are on windows pro versions, you can do this through the UI pretty easily, however if you are on a Home version, you need to disable windows update through the “Services.msc” application. [[https://www.tomsguide.com/how-to/how-to-turn-off-automatic-updates-in-windows-10|Here is a good guide on Toms Guide]]
Line 267: Line 267:
 Sometimes, you may need to do driver-based adjustments, including disabling “Jumbo Frames”, “Energy Efficient Ethernet” and other driver level features. Found in this chain: Sometimes, you may need to do driver-based adjustments, including disabling “Jumbo Frames”, “Energy Efficient Ethernet” and other driver level features. Found in this chain:
  
-{{:beyond:how_to_configure_network_adapters_in_windows.png?800}}+{{:quickshow:how_to_configure_network_adapters_in_windows.png?800}}
  
-{{:beyond:networkingforlasershows8.png?400|}}+{{:quickshow:networkingforlasershows8.png?400|}}
  
  
Line 323: Line 323:
   * If you have found yourself with a laptop with a killer ethernet port, you will need to not only utilize a USB ethernet device to not use the killer port, you will also need to format your windows computer to remove all pieces of the software, as it will try and manage other non-killer ports you attach to your pc.   * If you have found yourself with a laptop with a killer ethernet port, you will need to not only utilize a USB ethernet device to not use the killer port, you will also need to format your windows computer to remove all pieces of the software, as it will try and manage other non-killer ports you attach to your pc.
       * It is possible to massage killer ports into functioning fine, but to be honest its not worth the trouble and its just easier and cheaper to purchase a separate device.       * It is possible to massage killer ports into functioning fine, but to be honest its not worth the trouble and its just easier and cheaper to purchase a separate device.
-      * If BEYOND stream changes to UDP, Killer ports will actually become the best ports to use, so it’s not necessarily a bad thing, but important to understand. +      * If QuickShow stream changes to UDP, Killer ports will actually become the best ports to use, so it’s not necessarily a bad thing, but important to understand. 
   * USB 3.2 Gen1 USB to ethernet adaptors. It seems a large number of these devices are utilizing a chip from ASIX named AX88179A. These adaptors are causing issues due to the devices’ inability to be stable at cable lengths over 10M.    * USB 3.2 Gen1 USB to ethernet adaptors. It seems a large number of these devices are utilizing a chip from ASIX named AX88179A. These adaptors are causing issues due to the devices’ inability to be stable at cable lengths over 10M. 
       * If you already have one of these devices or are experiencing issues with your USB to ethernet device, use a switch and a short cable at FOH before your homerun to stage, this should clean things up.        * If you already have one of these devices or are experiencing issues with your USB to ethernet device, use a switch and a short cable at FOH before your homerun to stage, this should clean things up. 
quickshow/system_and_networks.1704896009.txt · Last modified: 2024/01/10 15:13 by Bob Varkevisser

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki