Roof Line Model

[gadgetsmith]

I'd like to request a roof line model.  This would be similar to the window model, but take into account the ridge string.  Options may include rotation by 90° to account for ridge direction, and also direction of a "chase"; CW or CCW.

Picture of what I suggest

https://onedrive.live.com/redir?resid=C25AE91809212A09!520&authkey=!AA0p1NozQJSNAjY&v=3&ithint=photo%2cjpg

Thank you all for this great software!
Happy Thanksgiving!

[jnealand]

A roof line is a single strand for sequencing purposes.  You just need to use a multimodel approach.  Create a single line for each unique straight part of your roof line with the appropriate start channels and pixel counts.  Use one or two long single strand models that are not marked as part of my display for sequencing that have the same channel numbers and total pixel counts as your individual "displayed" models.

[gadgetsmith]

Thanks for that info.  I will be working on sequencing over the holiday weekend, and think I understand what you're saying.  "Part of my display" button is what is displayed in the preview window, correct?

[sean]

Thanks for that info.  I will be working on sequencing over the holiday weekend, and think I understand what you're saying.  "Part of my display" button is what is displayed in the preview window, correct?

basically "Part of my Display" would be closer to say "Part of the Preview Screen"
Having this checked does NOT mean that it being sequenced by xlights. Only models added into the NUTCRACKER grid are generating effects. This is why you would add whole hous emodel into the grid, but not into the profile.
If you build models for your single channel LOR AC lights, you would check "Part of my Display" so they would show up in the preview, you would NOT add them into the NUTCRACKER grid (unless you want to try some nutcracker effects on your LOR AC items)

[gadgetsmith]

A roof line is a single strand for sequencing purposes.  You just need to use a multimodel approach.  Create a single line for each unique straight part of your roof line with the appropriate start channels and pixel counts.  Use one or two long single strand models that are not marked as part of my display for sequencing that have the same channel numbers and total pixel counts as your individual "displayed" models.

In creating the roofline models, i've run into a bit of a snag.  I'm using the SanDevices 682 controller, which uses blocks of 4 for defining string length.  When I get to block 2, I have string length's of 40, 29, 37 and 36, which means I need to define block 2 string length as 40 (2-1), which means I have extra channels not being used on 2-2, 2-3 and 2-4.  I can easily set the start channel of each individual string as part of my roof line model, but in creating the single strand models to use in sequencing the entire roofline, there is no option to skip channels.
So i'm thinking I can create a "whole roofline" model and sequence using that, individually sequence each segment (PITA), or is there a way to skip non-used channels when doing the setup in xlights, such that my xLights/FPP mapping channels would be contiguous?  For example, can I add Universe 10 up to channel 270 (xLights mapping 1-270) then skip to Universe 10 channel 390-490 (xLights mapping 271-370).

Thanks,
Charlie

[jnealand]

You can also use another model in the multimodel approach by making a horizontal matrix that is as long as the longest string.  Then use excel to create a custom model.  Consider the sum of all the channels including skipped channels as the total string length.  Each line in excel will have the first channel number of each string in the first cell of that row of the matrix.  The last used channel number for each string will go in the column that represents the longest total individual string length.  Then highlight the total row and use Fill, series, linear to fill in the values between the first and last column.  That will give you some decimal numbers, but then you just format the row with zero decimal points.  Now copy the rows that represent your actual eave sections and paste it into the custom model are of the nutcracker model section.  It is okay if there are duplicate node numbers.

I am attaching the excel file I did for my gutter line which has 4 distinct sections of different lengths.  that should give you something to work with.
This will let you program matching effects on your eaves, but will not let you take some effects like a chase from one section to the other, just have the same chase type on all section.  You don't have to use this model for the whole sequence, but only in the time slots where you want it and then put none, none in the time slots where you are using other models for effects on the same physical elements.

[attachment deleted by admin]

[gadgetsmith]

I see what you did there.  Very clever.

What I had not learned how to do, was to create custom models.  After seeing your example, then watching one of Seans video's, I went to the spreadsheets and created a map of my roofline pixels.  Being able to set the start channel, and skipping channel numbers not used on the shorter strings, I got exactly the type of thing I was looking for when requesting the roofline model.

This is what I came up with for my 5 different roofline elements.



[attachment deleted by admin]

[jnealand]

Glad you got it working