# WLED pattern porting? **URL:** \ **Category:** Patterns and Code\ **Created:** [June 9, 2021, 3:34pm UTC](https://forum.electromage.com/t/wled-pattern-porting/1295 "2021-06-09T15:34:35Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![wizard](https://forum.electromage.com/user_avatar/forum.electromage.com/wizard/32/4_2.png) [@wizard](https://forum.electromage.com/u/wizard)\ **Post date:** [June 24, 2021, 6:44pm UTC](https://forum.electromage.com/t/wled-pattern-porting/1295/10 "2021-06-24T18:44:38Z")
Right, BTW I didn’t see it linked, but there’s some more thoughts in this post that are relevant: > [@FastLED syntax compatability on PB](https://forum.electromage.com/t/fastled-syntax-compatability-on-pb/588/2): > > Hi @devoh, This is a good idea, and something I’ve been considering. There’s a number of tools that could be ported/supported, and some commonality with slightly different inputs/names. Much of the fastLED AP is fixed in 8 bit or 16 bit math, and as such has name variants (like beat8 and beat16) and takes integer arguments and return integer values where they usually mean some ratio between 0.0 and 1.0. I could add a strictly compatible API so that code could work as-is (with a few exception… --- _[View the full topic](https://forum.electromage.com/t/wled-pattern-porting/1295)._