If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Want to remove the ads? Registered users do not see the ads.

I have received a bunch of PMs this past week about Supporting Memberships. Due to that I wanted to put a notice for all to see should they be interested.
You can learn more about Supporting Memberships by Clicking Here

Re: Since Nutcracker has become real, I want pixels!

The good news is that with a controller like the E681, you can wrap or fold your strings and the controller takes care of the details. Nutcracker or other software doesn't have to know about the specifics, just let it assume that they all go up the same direction.

Then you aren't limited to certain length strings, or having to choose 12V vs 5V pixels simply for string length.

Re: Since Nutcracker has become real, I want pixels!

Thank for the info on the string wrapping in nutcracker - I didn't know that.
Whith regard to the 50 pixel strings I would cut them down to 42 pixels each. The remaining will make up the extra strings.
So 27 x 50 pixels will make 32 x 42 pixel and a few
spare, plus you don't have to inject power half way down the string.
The number 42 (apart from being the answer to life the universe and everything) is derived from the fact that an E68x can only use 4 universes of data i.e. 512 x 4 = 2048 addresses / 3 colours per pixel = 680 pixels ( I know that's not quite right).
42 is a very efficient use of these channels 42 x 16 = 672.
When using nutcracker I will tell it I have 42 pixel strings with no wrap.

Re: Since Nutcracker has become real, I want pixels!

Originally Posted by Barnabybear

Thank for the info on the string wrapping in nutcracker - I didn't know that.
Whith regard to the 50 pixel strings I would cut them down to 42 pixels each. The remaining will make up the extra strings.
So 27 x 50 pixels will make 32 x 42 pixel and a few
spare, plus you don't have to inject power half way down the string.
The number 42 (apart from being the answer to life the universe and everything) is derived from the fact that an E68x can only use 4 universes of data i.e. 512 x 4 = 2048 addresses / 3 colours per pixel = 680 pixels ( I know that's not quite right).
42 is a very efficient use of these channels 42 x 16 = 672.
When using nutcracker I will tell it I have 42 pixel strings with no wrap.

Update: A new Nutcracker target generator is soon to be released. It WILL wrap strings like you first imagined. No need to order special pixel counts.

If you want 42 pixels on a strand out of your 50 pixel string , the code will wrap the extra 8 pixels down the next strand. You then start your next string right next to it and Nutcracker will assume you are at pixel 9 of the strand.

The new target generator will also allow any number of folds of the strings. Take a string and fold it 8 times. In your case 8x6=48 with 2 left over. Next string will start at 3 and go on.

The target generator is also going to support matrices(grids) and rays.