When we started Firefox didn't have the level of functionality that we needed; it wasn't even possible to capture stereo audio, for example. Even today we're reliant on Chrome functionality that either isn't in the standards, or is undocumented.
That has been changing over time, and periodically we go through the codebase and re-align it with what's going on in Firefox or the standards as best as possible. You may even find you can close the warning and try and use it anyway. I'm also a long term Firefox user, and a proponent of a multi-browser world (I only started using Chrome to develop and use Cleanfeed!)
Cleanfeed began as a tool used to produce live radio; focusing on Chrome is a practical way to keep the bug footprint lower. That's important when things like the audio handling can be 'within spec' but just not performing very well. Things get more interesting with the peer-to-peer nature too, everything blows up in possibilities when you start trying to get Chrome to peer with Firefox and so on -- not just supporting each browser version, but combinations of them.
So I think we're justified as we sit on the bleeding edge a little, but also try and keep an eye on browser developments too, especially important if Cleanfeed finds uses in other areas. I'm happy when I hear people do care about Firefox (and other browsers) so the right thing is to let us know.
Yeah, the audio input world isn’t at all great on the web. Nor is the output world, for that matter. I wish Mozilla’s Audio Data API had won, it’s so much more sensible as a foundation than the Web Audio API.
When we started Firefox didn't have the level of functionality that we needed; it wasn't even possible to capture stereo audio, for example. Even today we're reliant on Chrome functionality that either isn't in the standards, or is undocumented.
That has been changing over time, and periodically we go through the codebase and re-align it with what's going on in Firefox or the standards as best as possible. You may even find you can close the warning and try and use it anyway. I'm also a long term Firefox user, and a proponent of a multi-browser world (I only started using Chrome to develop and use Cleanfeed!)
Cleanfeed began as a tool used to produce live radio; focusing on Chrome is a practical way to keep the bug footprint lower. That's important when things like the audio handling can be 'within spec' but just not performing very well. Things get more interesting with the peer-to-peer nature too, everything blows up in possibilities when you start trying to get Chrome to peer with Firefox and so on -- not just supporting each browser version, but combinations of them.
So I think we're justified as we sit on the bleeding edge a little, but also try and keep an eye on browser developments too, especially important if Cleanfeed finds uses in other areas. I'm happy when I hear people do care about Firefox (and other browsers) so the right thing is to let us know.