...rather than trying both modes for each frame and using the lower distortion one?
Quote from: Banned on 18 July, 2017, 02:17:56 AM...rather than trying both modes for each frame and using the lower distortion one?My guess is that it is fairly inefficient to switch modes, so you want to pick one and stick with it for more than a frame. Usually MDCT codecs work like this at least. Probably it gets pretty complex to try the brute force solution over a long enough time interval to be worthwhile.
One question is if OPUS_SET_SIGNAL is meant to be deprecated in future builds, or it still has some particular use cases. (on top of the setting the application option)For one, I know opusenc.exe has it disabled (or very well hidden).=
Am I correct in assuming that voip + voice is ideal for, well erm. voice chat.And that audio + music is best suited for music and live streaming?In particular I'm thinking of a internet radio DJ that plays music and then talk between songs (sometimes with background music).
The detection is mostly used in a relatively narrow range of bitrate and it's generally reliable (and in version 1.3 it's going to be near-perfect).
Sorry for off-topic. What are features in development plan for 1.3 in general terms?
I'm aiming to release 1.3 before the end of 2017, so there's going to be much less than in 1.2. The main thing of interest will likely be a much better speech/music detector based on recurrent neural networks, and which makes very very few errors. There's also going to be improvements to stereo music around 24-48 kb/s.
Looking back, are there any big mistakes in the codec itself or any easy gains you wish you could implement now into the finished specification? Or is Opus pretty much still perfect both in design/architecture as well as the possible features that are built in, leaving only the encoder with possible refinements? Just curious here.
Opus is by no means perfect, but there is also nothing I would consider as a "big mistake" either. There's a few details I might have done differently, but the encoder can reasonably work around most of those.