A glimpse of fw3.00’s visualizer on 2.71 SE-C

If you guys have been following the goings on in the homebrew community, then you’ve probably heard the news that LordSturm and kando are currently working on having fw 3.00’s Visualizer in 2.71SE-C.

When Dark_Alex released his 2.71 SE-C Custom Firmware, you didn’t really expect that other coders wouldn’t get to work on improving it and adding more features right? A perfect example for this is LordSturm and kando, who are hard at work in devising a method to use 3.00 visualizer features safely from 2.71 SE-C.

And to update us on what’s been going on so far and how much progress they’ve achieved on their work, kando (or kandowontu on YouTube) has posted this video on YouTube which shows the visualizer at work…via Kanye West. Again, they remind us that this is a work in progress so if you don’t like what you see, don’t complain just yet, alright? LordSturm has also informed us that we can expect a release or hack soon, probably early December. Great work you guys!

If you guys have been following the goings on in the homebrew community, then you’ve probably heard the news that LordSturm and kando are currently working on having fw 3.00’s Visualizer in 2.71SE-C.

When Dark_Alex released his 2.71 SE-C Custom Firmware, you didn’t really expect that other coders wouldn’t get to work on improving it and adding more features right? A perfect example for this is LordSturm and kando, who are hard at work in devising a method to use 3.00 visualizer features safely from 2.71 SE-C.

And to update us on what’s been going on so far and how much progress they’ve achieved on their work, kando (or kandowontu on YouTube) has posted this video on YouTube which shows the visualizer at work…via Kanye West. Again, they remind us that this is a work in progress so if you don’t like what you see, don’t complain just yet, alright? LordSturm has also informed us that we can expect a release or hack soon, probably early December. Great work you guys!

Add a Comment

Your email address will not be published. Required fields are marked *