Profile cover photo
Profile photo
François Simond (supercurio)
Product & Software development, Analyst
Product & Software development, Analyst


Post has shared content
Hurray to that 😀

All my Android & Android Things development is in Kotlin nowadays: it'll be nice to be know what's nullable or not from the SDK directly.
Android Pie SDK is now more Kotlin-friendly

Learn more on the blog →

The Android Pie SDK now contains nullability annotations to make it tastier for developers using #Kotlin.
Add a comment...

Post has attachment
What about speaker "break-in"?

+clavinetjunkie tested that on a JBL Xtreme 2 bluetooth speaker and came up with a blind test for your to judge, and measurements to confirm.

I really like +clavinetjunkie's channel by the way, he does an awesome job with everything.
Add a comment...

Post has attachment
Awesome video from +Linus Tech Tips where +OnePlus shares their current production and QA process for the OnePlus 6.
Add a comment...

Post has attachment
Thank you all for the help with the name yesterday :)
It was pretty funny to follow as the race was so tight, but the name MultiDSP won your vote in the end :)

So I'm please to announce #MultiDSP as a project.
Here's the full description.
Please tell if you have any comment or question!

I've started work on it but there's nothing usable at the moment.

A first step was to port zita-resampler to Rust programming language.
After some research and a lot of data gathering, I'm now gonna prototype the Asynchronous Sample Rate Converter (ASRC) at the core of this project.

Synchronizing in a stable way different clocks and sample rates between input and output hardware, with high sound quality and the lowest latency possible is a good challenge and I wanted to try that for 1.5 years after reading about it.

I'm driven by the use cases tho, both for speakers and headphones.
Simply put I need this, and it doesn't exist - or it kinda does but at price points which makes the existing products simply impractical.
So here you go :)
Add a comment...

Post has attachment
The vote is completed now, thank you all!
MultiDSP was chosen.

I'd like your help to choose the name for an open source project I'm working on.

It is a real-time software DSP running on single board computers for headphones/speaker tuning and room correction.
- Inputs: USB, analog, digital, network.
- Outputs: analog, digital, HDMI
I/O capabilities: stereo, digital crossover and multichannel audio

That's the two last names which are fitting and seem available, please vote :)
votes visible to Public
Poll option image
Add a comment...

Post has attachment
Thanks Michael from +Vsauce , I'll try that next time I can't fall asleep!

It's so soothing 😁
Add a comment...

I thought my Nexus 5X might have been immune to the bootloop defect..
But nope.
He's dead, Jim.

Today was kinda tough, and it didn't really help.
Add a comment...

Awesome display measurement methodology by as described in this video.

There's so much good stuff there. They set the bar very high, which is impressive: it also means a lot more work, and time spent for each review

I'm a big fan of the fact they measure all 1024 values for RGB channels (which correspond to 10 bits colors).
Taking all these points is the only way to measure the actual response curve and identify banding at the same time.
Some measurement software still propose only to measure 10 IRE values instead, which doesn't say much and ends up being misleading.

In my own software I've been measuring all 256 values for 8 bit mobile displays, but it'll be time to upgrade to 10 bits for HDR 😊
Another difference is that I've been measuring all three channels simultaneously from grayscale, which works well and also illustrates grayscale linearity. I'm curious about why chose plain Red / Green / Blue separate colors instead, there must be a reason.

Always happy to see color rendition and displays in general being measured better! is likely doing the bed job in the business now 👍
Add a comment...

Post has shared content

Post has shared content
Yes and yes.
Excellente idée!

Source: I'm working with an IoT company.

I'll guess than often, inside hardware companies which turned into hardware+software+services there are multiple influences which promote both openness and locked-in proprietary approaches.

Even discussing this type or regulation will encourage companies to design their systems with long term support and/or open source requirements.
It sometimes seems as though barely a week can go by without yet another major software-related hardware vulnerability story. As manufacturers grapple with the demands of no longer building simple appliances but instead supplying them containing software…
Add a comment...
Wait while more posts are being loaded