At this point the only ATtiny-based boards that we support at the Adafruit Trinket and Gemma. Are you using one of those, or something else? They are both ATtiny85. What board are you using?
Righty, so. I’d like to work out why the 2.1 beta gives me two dead lines while the older 2.1 branch was/is fine. Mostly because some of my visualisations could really do with the nice dithering. Any suggestions?
@Mark_Kriegsman
I am using the chip itself. As there should be no difference in using the chip itself or the board.
I loaded 2.1 bata fastled. Still getting a lot of message but different ones:
D:\Documents\Arduino\libraries\FastLED2.1/FastLED.h:132: undefined reference to __cxa_guard_acquire' D:\Documents\Arduino\libraries\FastLED2.1/FastLED.h:132: undefined reference to__cxa_guard_release’
./fastSPITest.cpp.o: In function L_1491': D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: undefined reference totimer0_millis’
D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: undefined reference to timer0_millis' D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: undefined reference totimer0_millis’
D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: undefined reference to timer0_millis' D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: undefined reference totimer0_millis’
./fastSPITest.cpp.o:D:\Documents\Arduino\libraries\FastLED2.1/clockless_trinket.h:101: more undefined references to `timer0_millis’ follow
@nico_verduin except the build environment t, compiler used absolutely makes a difference
@Mat_Bettinson have you pulled the latest code since I fixed the 24 and 48mhz timings?
For both of you (and others) - can you please start new threads for getting help - it makes it more likely that other people will see your posts and hopefully chime in (especially on building on unsupported platforms)
@nico_verduin as for the compile errors that you are getting - look at the discussion in https://github.com/FastLED/FastLED/issues/46 - though I don’t know if that will help with the impossible constraint issues you were talking about in the trinket ticket.
Reinstalled everything. Now I have the same problems as issue 46. I am running with 1.5.2. Maybe that is the cause?
@Daniel_Garcia I’m thinking about using 12 parallel output for my future project. Are there any limitations ? Do you have an example using FastLED ?
It’s not ready for use yet - it still needs a lot of cleaning up. The biggest problem that I’m running into is it seems to slide the data rate down from 800khz down to about 550khz - which the WS2812’s are still ok with, but I’m trying to do some tweaking to improve that. (Granted, with 12-way output, the aggregate data rate is still far higher than with single line out at a time rates, but still…)
What platform are you going to be using for this? Teensy 3.1 or due, or something else?
Thanks for that work 
My project is planned for July, do you think you will be able to have a working version before june ?
I think i’m going to use teensy 3.1, but still wondering if that wouldn’t be better to be able to set effects or speed of the lights using Digix’s wifi
Funny you should say that - i’m using both the teensy 3.1 and the digix. I have a project that I’m working on that relies on n-way output (most likely going to use the digix) - that is getting installed on july 4th weekend, so I kind of need to have it wrapped up well before then
I can probably get a branch up before june, it may not be in the 2.1 tree, but i’ll definitely announce it when it’s up.
I’m torn on the teensy 3.1 and the digix. The teensy 3.1 compiler generates much better code, and I feel like the arm chip in the teensy is a bit more efficient per/clock than the digix (though that may be a product of the compiler being better).
However, with the digix I can get up to 30 lines out in parallel. (Er, maybe - I may realistically be limited to 16 or 24 because of the aforementioned fuckery with compilers). Also, the digix has built in wifi (which I now have working with OSC so I can use TouchOSC on an ipad as a controller).
The teensy 3.1 is capped at 12 lines out, just because of exposed pins, but in reality, 4 of those 12 are pads on the bottom of the teensy, a bit of a pain to get at 
I’ll have to trust you on overtechnical details, i’m just beginning with boards programming
So a bad thing that digix doesn’t seem to be efficient, but isn’t it a young product ? Maybe future updates will improve efficiency… I really like the fact that it could be controlled by wifi, and furthermore OSC, this could pretty easily enable pieces of led to be controlled with a kinect 
I can’t see which pins of the teensy on the site’s photography wouldn’t be easy to get at… Would it be hard to solder them ?
There’s two candidates for parallel output on the teensy 3/3.1 - there’s the 8 pins used by OctoWS2811 (2,14,7,8,6,20,21,15) on Port D - then there’s 12 pins on Port C - the first 8 of them are 15,22,23,9,10,13,11,12. The remaining four on the backside are 27,28,29, and 30
If you look at the pinout on here - http://www.pjrc.com/teensy/pinout.html - under “Pin Assignments, Back Side” - you can see that pins 27-30 are pads on the bottom.
Oh, that bottom! Okay I didn’t understand what you were meaning. Indeed, that would be hard to use them 
Then I’ll definitely go with the Digix !
Hi @Daniel_Garcia !
I’ve finally received my LED setup for my project. Now thinking about which platform buying. Did you try multiple outputs on teensy and DigiX ? Which one would you recommand ?
I don’t have a final recommendation between the two - I’m still working on refining the code - but at the moment i’m focused on some specific needs for an installation piece i’m working on, and will revisit a more general version of the parallel code when it is done.
Ok, so maybe I should go for 2 teensy to be able to use the octo library if the update isn’t ready for next month…?
That might be safer for your project timeline. Right now I’m putting all my spare time/resources into the project that I’m trying to get finished - and I have an immovable deadline for it, so any parallel code work that I do until it’s finished will be tuning for that, vs something more generic that people can use (and it’s possible I will actually have to flip over to a beaglebone black, we’ll see).
Okay, thanks for your answers Good luck with your project !
Hi @Daniel_Garcia , did you manage to get parallel driving work for your project ? Mine is in good road for this weekend, but if I could get a little more speed it would be awesome
@Pierrick_Letos : Dan is off taking some much deserved R&R; he’ll be back next week.