Ravelights Giveaway!
Thanks for being here! We are going to do a giveaway when we launch version 2 right here, in this channel! We plan to launch late summer! Stay tuned, we are working our butts off.
Thank you for supporting our pipe dream of making everyone unreasonably shiny. Love you lots ❤️ We're gonna post some cool stuff in here in the meantime!
Give our Twitter a follow:
https://twitter.com/Ravelights
Join the Discord and chat with the nerds making this happen:
https://discord.gg/GgWGvHyVBX
Browse our website:
https://ravelights.ca/
Thanks for being here! We are going to do a giveaway when we launch version 2 right here, in this channel! We plan to launch late summer! Stay tuned, we are working our butts off.
Thank you for supporting our pipe dream of making everyone unreasonably shiny. Love you lots ❤️ We're gonna post some cool stuff in here in the meantime!
Give our Twitter a follow:
https://twitter.com/Ravelights
Join the Discord and chat with the nerds making this happen:
https://discord.gg/GgWGvHyVBX
Browse our website:
https://ravelights.ca/
Hi everyone! DDR (the Ravelights software bat) here, figured it was about time for an update from us. :)
Thanks to everyone who stopped by our booth at VF! It was wonderful to meet you all, and your enthusiasm for our project really buoyed me and Cornflakes' spirits. ❤️
The week after the con, we took a small vacation. We are firm believers in self-care at Flake Technologies.
After that, we got to work fixing an issue we'd noticed while testing the Ravelight at the con - the darn thing would go deaf and stop listening to beats when the music got loud. This was exactly the thing we didn't want happening! It worked everywhere but raves!
The issue was traced back, after two weeks of software detective work, to a number in a software library used by another software library we were using for our beat detection logic. The original authors hadn't allocated enough space to store the number in, so when the microphone recorded enough loud noises, it lost the most significant digit. This caused our analysis to loop back around to "quiet" from "loud". After allocating some more space for the number, everything started working at loud volumes. In our testing, which we probably owe our neighbours an apology for, the Ravelight now works up to 94-ish decibels. At this point, we think our microphone physically stops working, which should be fine because that's also past the point where our ears stop working.
(Also, mad shout out to Cornflakes for helping me throughout this process. Although the issue was in software, at various points I was dead convinced it was a hardware issue. We're both really glad it turned out not to be! Getting the mic running properly in the first place was hard. 😅)
After this was fixed, I moved on to making the Ravelight remember what it was doing when you powered it off. As of about half an hour ago, this now works! The library providing the underlying functionality for this on our chip has a few unstated assumptions. If I use it too early in the program, the Ravelight just reboots. This is a little hard to debug, to say the least, but it's working and understood now.
On hardware, Cornflakes has been working getting the next revision of our custom circuit board to fab. We identified an unexpectedly high battery drain when the Ravelight was powered off, which took a week or so to fix and blew up our remaining supply of dev boards, less the one Cornflakes gave me which I won't let him touch now. Cornflakes has managed to get powered-off mode down to taking, I think, like 5-10% of the electricity it used to? It's looking pretty good now.
Anyhow, that's about it for now I think. Catch y'all again soon!
—DDR
Thanks to everyone who stopped by our booth at VF! It was wonderful to meet you all, and your enthusiasm for our project really buoyed me and Cornflakes' spirits. ❤️
The week after the con, we took a small vacation. We are firm believers in self-care at Flake Technologies.
After that, we got to work fixing an issue we'd noticed while testing the Ravelight at the con - the darn thing would go deaf and stop listening to beats when the music got loud. This was exactly the thing we didn't want happening! It worked everywhere but raves!
The issue was traced back, after two weeks of software detective work, to a number in a software library used by another software library we were using for our beat detection logic. The original authors hadn't allocated enough space to store the number in, so when the microphone recorded enough loud noises, it lost the most significant digit. This caused our analysis to loop back around to "quiet" from "loud". After allocating some more space for the number, everything started working at loud volumes. In our testing, which we probably owe our neighbours an apology for, the Ravelight now works up to 94-ish decibels. At this point, we think our microphone physically stops working, which should be fine because that's also past the point where our ears stop working.
(Also, mad shout out to Cornflakes for helping me throughout this process. Although the issue was in software, at various points I was dead convinced it was a hardware issue. We're both really glad it turned out not to be! Getting the mic running properly in the first place was hard. 😅)
After this was fixed, I moved on to making the Ravelight remember what it was doing when you powered it off. As of about half an hour ago, this now works! The library providing the underlying functionality for this on our chip has a few unstated assumptions. If I use it too early in the program, the Ravelight just reboots. This is a little hard to debug, to say the least, but it's working and understood now.
On hardware, Cornflakes has been working getting the next revision of our custom circuit board to fab. We identified an unexpectedly high battery drain when the Ravelight was powered off, which took a week or so to fix and blew up our remaining supply of dev boards, less the one Cornflakes gave me which I won't let him touch now. Cornflakes has managed to get powered-off mode down to taking, I think, like 5-10% of the electricity it used to? It's looking pretty good now.
Anyhow, that's about it for now I think. Catch y'all again soon!
—DDR
❤12
Hi all! Cornflakes here, I wanna share a quick update on what’s new with the progress on Ravelights Gen 2.
We’ve been going very hard, getting things ready so we can share some really cool LED tech with you, and the world. The enthusiasm y'all have for us has been so rewarding and motivating, you even just being here genuinely means a lot to us.
The update:
Gen 2 Ravelights use custom, dedicated hardware that we’ve kinda over engineered, mostly for fun and we were bored, but also because it allows us to do some really cool new stuff that does not really exist yet in this capacity.
We just sent our final prototype hardware to be built. We made a lot of improvements this round and fixed all the weird bugs from version 1 that you might be familiar with lol. We think the hardware is going to be incredibly stable and robust this time.
We decided to do circuit boards in purple! It costs a bit more to make them purple, but honestly we think it will look pretty cool, so worth it haha. You can look through the vents on your Ravelights and see purple circuit boards, which is pretty neat.
Designing everything ourselves has been really exciting. It gives us unlimited freedom and makes it easy to add features you all keep requesting.
A couple things we are building:
-Software Updates: Your Ravelights will get more features, even after you bought them. Like, if we figure out how to make your battery last longer or create new modes, we’ll send you those upgrades for free.
-Tons of easter eggs hidden around the UI, like games. HEY - got any games on your Ravelight? Actually, yes, I do XD
-Got more than one Ravelight? They will sync and integrate with each other
-Very smart battery management software
-And a ton more I can’t list right now.
That's all for now! Thanks for reading! Chat more soon ❤️
Discord: https://discord.gg/GgWGvHyVBX
Twitter: https://twitter.com/Ravelights
We’ve been going very hard, getting things ready so we can share some really cool LED tech with you, and the world. The enthusiasm y'all have for us has been so rewarding and motivating, you even just being here genuinely means a lot to us.
The update:
Gen 2 Ravelights use custom, dedicated hardware that we’ve kinda over engineered, mostly for fun and we were bored, but also because it allows us to do some really cool new stuff that does not really exist yet in this capacity.
We just sent our final prototype hardware to be built. We made a lot of improvements this round and fixed all the weird bugs from version 1 that you might be familiar with lol. We think the hardware is going to be incredibly stable and robust this time.
We decided to do circuit boards in purple! It costs a bit more to make them purple, but honestly we think it will look pretty cool, so worth it haha. You can look through the vents on your Ravelights and see purple circuit boards, which is pretty neat.
Designing everything ourselves has been really exciting. It gives us unlimited freedom and makes it easy to add features you all keep requesting.
A couple things we are building:
-Software Updates: Your Ravelights will get more features, even after you bought them. Like, if we figure out how to make your battery last longer or create new modes, we’ll send you those upgrades for free.
-Tons of easter eggs hidden around the UI, like games. HEY - got any games on your Ravelight? Actually, yes, I do XD
-Got more than one Ravelight? They will sync and integrate with each other
-Very smart battery management software
-And a ton more I can’t list right now.
That's all for now! Thanks for reading! Chat more soon ❤️
Discord: https://discord.gg/GgWGvHyVBX
Twitter: https://twitter.com/Ravelights
❤4👍2🔥2
This media is not supported in your browser
VIEW IN TELEGRAM
Ravelights have wall mounts so you can hang them up when you’re back from con
🔥12❤2❤🔥1👍1