jerry72 Posted September 13, 2015 Share Posted September 13, 2015 I am not sure if this is a bug or not, but when i open my viz file for my mega tree, i get the message that two of my strings are sharing the same address, Viz would not use the same address. Fixture [MegaTree- DMX Pixels 04] and Fixture [MegaTree- DMX Pixels 05] both use channel 2.0.1 I checked, 04 uses Universe 2 starting pixel 151 and 05 uses Universe 3 starting pixel 1. I ma unable to load the VIZ file because it is to big, but i can send it to you. Link to comment Share on other sites More sharing options...
BrianBruderer Posted September 13, 2015 Share Posted September 13, 2015 email the visualization file to brian@superstarlights.com and I will take a look at it. What version of superstar are you running? Link to comment Share on other sites More sharing options...
jerry72 Posted September 13, 2015 Author Share Posted September 13, 2015 email the visualization file to brian@superstarlights.com and I will take a look at it. What version of superstar are you running?I just downloaded the latest 4.2.0 onto a new computer, i saved all my viz files on an external hard drive. when i opened the viz file i get that error message. I tried creating a new viz file but still got the same message. Email on its way. Link to comment Share on other sites More sharing options...
roverdish Posted September 13, 2015 Share Posted September 13, 2015 Jerry,I had a similar issue. I had a non active prop in my prop file that shared some channels with one of the props in my active visualizer. I changed the channels in the non active prop and the problem went away. Link to comment Share on other sites More sharing options...
BrianBruderer Posted September 13, 2015 Share Posted September 13, 2015 I looked at the visualization. The root of the problem is that the Channel Wizard in the Visualizer does not always assign valid settings if you accept all the offered values. In your case, you have 16 strings and each string is 50 pixels in length. There are 170 pixels in a Universe. As you use the channel wizard to set the channels for your strings it will end up assigning the following Universe and Channel settings: String 1 - Universe 1, Pixel 1String 2 - Universe 1, Pixel 51String 3 - Universe 1, Pixel 101String 4 - Universe 1, Pixel 151String 5 - Universe 2, Pixel 1String 6 - Universe 2, Pixel 51String 7 - Universe 2, Pixel 101String 8 - Universe 2, Pixel 151String 9 - Universe 3, Pixel 1String 10 - Universe 3, Pixel 51String 11 - Universe 3, Pixel 101String 12 - Universe 3, Pixel 151String 13 - Universe 4, Pixel 1String 14 - Universe 4, Pixel 51String 15 - Universe 4, Pixel 101String 16 - Universe 4, Pixel 151 The problem is that String 4 starts at Universe 1, Pixel 151, but since there are only 170 pixels in a Universe, there are only 20 pixels left if you start at Pixel 151. When superstar sees this it assigns the first 20 pixels of string 4 to the end of Universe 1, then it bumps to Universe 2 and starts using pixels from Universe 2. So String 4 and 5 end up overlapping. So what you need to do is manually enter in some of the values in the Channel Wizard so that you end up with: String 1 - Universe 1, Pixel 1String 2 - Universe 1, Pixel 51String 3 - Universe 1, Pixel 101String 4 - Universe 2, Pixel 1String 5 - Universe 2, Pixel 51String 6 - Universe 2, Pixel 101String 7 - Universe 3, Pixel 1String 8 - Universe 3, Pixel 51String 9 - Universe 3, Pixel 101String 10 - Universe 4, Pixel 1String 11 - Universe 4, Pixel 51String 12 - Universe 4, Pixel 101String 13 - Universe 5, Pixel 1String 14 - Universe 5, Pixel 51String 15 - Universe 5, Pixel 101String 16 - Universe 6, Pixel 1String 17 - Universe 6, Pixel 51String 18 - Universe 6, Pixel 101 Link to comment Share on other sites More sharing options...
jerry72 Posted September 13, 2015 Author Share Posted September 13, 2015 I looked at the visualization. The root of the problem is that the Channel Wizard in the Visualizer does not always assign valid settings if you accept all the offered values. In your case, you have 16 strings and each string is 50 pixels in length. There are 170 pixels in a Universe. As you use the channel wizard to set the channels for your strings it will end up assigning the following Universe and Channel settings: String 1 - Universe 1, Pixel 1String 2 - Universe 1, Pixel 51String 3 - Universe 1, Pixel 101String 4 - Universe 1, Pixel 151String 5 - Universe 2, Pixel 1String 6 - Universe 2, Pixel 51String 7 - Universe 2, Pixel 101String 8 - Universe 2, Pixel 151String 9 - Universe 3, Pixel 1String 10 - Universe 3, Pixel 51String 11 - Universe 3, Pixel 101String 12 - Universe 3, Pixel 151String 13 - Universe 4, Pixel 1String 14 - Universe 4, Pixel 51String 15 - Universe 4, Pixel 101String 16 - Universe 4, Pixel 151 The problem is that String 4 starts at Universe 1, Pixel 151, but since there are only 170 pixels in a Universe, there are only 20 pixels left if you start at Pixel 151. When superstar sees this it assigns the first 20 pixels of string 4 to the end of Universe 1, then it bumps to Universe 2 and starts using pixels from Universe 2. So String 4 and 5 end up overlapping. So what you need to do is manually enter in some of the values in the Channel Wizard so that you end up with: String 1 - Universe 1, Pixel 1String 2 - Universe 1, Pixel 51String 3 - Universe 1, Pixel 101String 4 - Universe 2, Pixel 1String 5 - Universe 2, Pixel 51String 6 - Universe 2, Pixel 101String 7 - Universe 3, Pixel 1String 8 - Universe 3, Pixel 51String 9 - Universe 3, Pixel 101String 10 - Universe 4, Pixel 1String 11 - Universe 4, Pixel 51String 12 - Universe 4, Pixel 101String 13 - Universe 5, Pixel 1String 14 - Universe 5, Pixel 51String 15 - Universe 5, Pixel 101String 16 - Universe 6, Pixel 1String 17 - Universe 6, Pixel 51String 18 - Universe 6, Pixel 101 Ok, i will change it around then. Thanks Brian. Link to comment Share on other sites More sharing options...
jerry72 Posted September 14, 2015 Author Share Posted September 14, 2015 Perfect, worked great Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now