Tutorial for import...
 
Notifications
Clear all

Tutorial for importing Singing Tree and 12CCR sequences...

13 Posts
6 Users
0 Reactions
4,822 Views
Posts: 1049
(@phrog30)
Noble Member
Joined: 12 years ago

That's probably the issue. Try S4 beta, there are new options that Brian incorporated that aren't in S3, so the row and column forcing will not be translated. I'm actually surprised it worked at all. I tried opening the S4 visualizer in S3 and nothing happened. S4 added a dmx tool, which I used.


Reply
Posts: 1015
(@gilrock)
Noble Member
Joined: 14 years ago

I took a closer look at the visualization type SuperStar sequences. Seeing that we really only want to import to a single display element a visualization sequence will only work if it contains data for one display element in xLights. For a visualization sequence the .sup file does not define the size so what I've done is instead of trying to have you point me to a visualization file I've added X and Y size and offset fields that you can use to tell me the size of the display element. If its not a visualization sequence then I look at the number of CCR's attribute and whether they are full or half to calculate the sizes. The offsets will work for either sequence type so if you forced your sequence to row 16 then you need to put in a Y offset of 16 because he is storing all the position values with that offset added in.


Reply
Posts: 1049
(@phrog30)
Noble Member
Joined: 12 years ago
CopperCreekLights wrote:I took a closer look at the visualization type SuperStar sequences. Seeing that we really only want to import to a single display element a visualization sequence will only work if it contains data for one display element in xLights. For a visualization sequence the .sup file does not define the size so what I've done is instead of trying to have you point me to a visualization file I've added X and Y size and offset fields that you can use to tell me the size of the display element. If its not a visualization sequence then I look at the number of CCR's attribute and whether they are full or half to calculate the sizes. The offsets will work for either sequence type so if you forced your sequence to row 16 then you need to put in a Y offset of 16 because he is storing all the position values with that offset added in.

That works for me.

Thanks!

James


Reply
Page 2 / 2
Share: