Is 'native' gapless support (like in Vorbis) planned for Opus?
EDIT2: I tried quickly enconding to Opus with the last opus-tools CLI (opusenc) and it's always glitching, at 44.1k and at 48k. But I'm also using different settings than with LameXP.If I decode the LameXP Opus with opusdec CLI, then again, the 44.1k doesn't glitch, while the 48k does.
Where is the current "Transparent" settings right now, if there is any:)?
Quote from: zerowalker on 28 July, 2012, 07:50:39 PMWhere is the current "Transparent" settings right now, if there is any:)?Transparency is subjective. Furthermore Opus is on intensive development. So quality is improving constantly.To have an idea, the last experimental build is reaching the quality of MP3 130 kbps (LAME -V 5) at 80 kbps.
Is there any software that´s using Opus for speech transfer (skype like)?
Mumble will undoubtedly support Opus soon. Mumble upcoming features
Yes, you may use Murmur as server, and can tell friends about your IP address (or maybe DynDNS name) and other connection details to talk freely with each other via Mumble clients. But there are also public servers with voice chat channels, similar to IRC with text chat channels.The quality of the service depends on the (mainly upload) bandwidth from the server and each client, you can configure bitrate and latency / packet size.
It is a SourceForge project. So someone will probably be able to build an Opus DLL for it... But I would not recommend to rush it. It might be buggy. And it might be incompatible to other users not using exactly the same files.Patience, young Padawan.
One thing I've noticed is that Opus (the exp version of course) is pushing a lot of bits into pieces at higher bitrates for which other encoders like Vorbis or even Lame are using way less. Since Opus should be at least better than Vorbis at anything there could be probably a lot of average bitrate decrease done while still keeping the same quality overall.
I believe Gainless refers to something I would call "bitrate dynamics".If one reduces the overall bitrate target, it does not only reduce the bitrate for the complex scenes which consume a lot of bitrate, but also for the simple scenes which are satisfied with less bitrate already. Gainless is probably interested in "compressing" only the high bitrate scenes, which he feels seem to get out of control.
There might be situations where extreme bitrate fluctuations may lead to technical issues, e.g. regarding decoding buffers filled from slow sources like optical drives or network transfers.
Do you know the Xvid video codec and the parameters for "Overflow treatment" and "Curve compression"?