Originally posted by Prescience500
View Post
Announcement
Collapse
No announcement yet.
Opus Codec 1.1.1 Brings Encoder/Decoder Optimizations
Collapse
X
-
Originally posted by caligula View Post
Ok. I just thought that you wouldn't appreciate optimizations.
I have even worked on a SIP project for a while, so I know how important a good codec is. So you see, this article struck a chord with me.
Comment
-
Originally posted by bug77 View PostThat's nice and everything, but what does it really mean? Can we get better sound now?
Because I doubt many end users will care that someone shove 10ms off their encoding process or that the decoding uses 1 less microwatt.
Let me rephrase the initial question: are these just routine improvements or do they enable something bigger?
- Likes 1
Comment
-
Originally posted by bug77 View Post
I'm a developer with a thing for sneaking in code cleanups whenever I can.
I have even worked on a SIP project for a while, so I know how important a good codec is. So you see, this article struck a chord with me.
Comment
-
Originally posted by bug77 View PostThat's nice and everything, but what does it really mean? Can we get better sound now?
Because I doubt many end users will care that someone shove 10ms off their encoding process or that the decoding uses 1 less microwatt.
Let me rephrase the initial question: are these just routine improvements or do they enable something bigger?
Comment
-
Originally posted by Namenlos View Post
Very unlikely, that there will be any significant improvements in the future. Maybe some metrics get added for a better vbr management, but even that is doubtful considering how close together all results are in this listening test: http://listening-test.coresv.net/results.htm 1.1 was done because of bad quality in harpsichord encoding.
Comment
Comment