Why use Virtual Strings?

[TomL8345]

I am new to both XLights and Falcon controllers.  I had set up my XLights layout making my models and custom models for another controller, but I have since ordered a Falcon F4V.  In reading and watching videos on this controller system I came across the videos on Virtual String.  What is the benefit of setting up a model in the hardware using Virtual Strings vs. defining the model in software using sub-models.  To my limited knowledge base both should accomplish the same end result.  Am I missing something?

Also while I am asking this question, what is the advantage of setting the pixel color order in the hardware vs software(RGB, BRG, GBR, etc)

[jnealand]

I have not used virtual strings yet so I am not going to attempt to answer that but on the color order.  If you have the color order correct in the hardware you can do hardware testing with the correct colors, otherwise they may not show up as what you think they should be.  I like everything to match.  I create an all red seq with every prop in my layout reg.  It is just 30 sec, but I can do a repeat when testing.  I go to each controller and fix the colors while using the seq to see if I get the correct color there as well.  Also have an all blue and all green sequence.

Again I have no experinece on virtual strings, but I understand that you can have a string of pixels that are say RGB and then connect to another prop where the pixels are GRB or something non RGB.  A virtual string lets you correct the color for the different contiguous sections of lights.  Virtual strings are controller based, sub models are software based.

[keithsw1111]

Virtual strings have their uses but if you can avoid them I would do so. They make your configuration more difficult.

[deplanche]

Virtual strings are great if you are grouping pixels that you always want to act the same.  For example, if you have a prop that you need 3 pixels in to get bright enough for your liking, and you have 5 of those in a row.  Rather than trying to set up a custom model in xlights that will always work the way you want it to, you can set up groups in the virtual strings, and then just make a 5 node string in xlights.   There is an example of this in the F16 v3 Manual in Section 4.2.4.21, Example 3 at: https://docs.google.com/document/d/1S67ZVLgQRYsdqPhgfPkQucnFXvu1FmQAME9qnK5RixU/edit?usp=sharing

Many of the other features can be done in either xlights or on the falcon, but as keith said, it's generally easier and better to do that in xlights.

[algerdes]

Where we use virtual strings is when we need to combine different types of pixels, or even different props on the same data line.

For example, a 'ground tree' we have contains 12 'legs' of 70 pixels each.  At the end of each leg is a mini-tree of 70 more pixels and a 20 pixel 'star'.  To make matters a bit more interesting, the trees have a different color pattern to the pixels (BRG instead of RGB.)  The stars are standard RGB.  The F16's virtual strings make it possible to make all of this work together.

[mararunr]

The number one thing I use it for is grouping strobe pixels to make a brighter strobe than just the one pixel by itself (I've never been able to figure out how to do this with xLights).  So I can bundle 7 strobe pixels together and then treat them as one pixel in xLights by having a virtual string with grouping 7.
https://youtu.be/ldeJVM35s1Q

[pixelpuppy]

another thing that Virtual Strings provides is the ability to put null pixels in the middle of a long string, not just the start.  When stringing multiple props together on the same controller port the distance between props might require a null pixel between them.   Virtual strings makes this every easy.