Controller Patching...
 
Notifications
Clear all

Controller Patching Question

2 Posts
2 Users
0 Reactions
1,172 Views
gassy
Posts: 548
Topic starter
(@gassy)
Honorable Member
Joined: 17 years ago
[#39980]

I'm switching to Vixen for '16 - I've finished my sequencing and would like to test it out on this year's display and if all goes well finish this season with it. My issue - I'm planning on making my pixel tree slightly taller next year by adding 10 pixels to each of the 16 strings. My display setup and sequencing includes these 160 extra pixels. Would I be safe going to the controller setup and unpatching the corresponding channels before exporting for FPP? Is there a better way? Or, should I just wait until next year? Thanks.


1 Reply
jchuchla
Posts: 8698
(@jchuchla)
Illustrious Member
Joined: 15 years ago

If you've got them in there already, and they're already patched, I don't see any point in unpatching them. They simply don't exist in your display and obviously won't light. But it's not a problem for them to be in the file. On the FPP side, you can choose to not output those channels. Or you might even be able to output them anyhow and since nothing is there, nothing will light. That depends on how picky your controller is about receiving data it's not configured to be listening for. And it also depends on your channel plan in the controller. If those channels are already allocated as spare, you should be fine, if they're not included and would cause overlap, you wouldn't want to output for them.

You could even delete those extra pixels in vixen altogether and then add them in next year. Any work you've done on the groups will self adjust to the then current group size every time the sequence opens.


Reply
Share: