Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
That said, once there's a stable release, I see no reason for Valve not to change over to Opus, considering it's likely that people will use Steam Voice Chat for in-game realtime communication.
Thanks for requesting this.
VLC and Mumble now officially support Opus. Google Chrome and TeamSpeak has support in development. Skype will transition from SILK to Opus in the near future. Opus is also the required codec for the WebRTC internet standard which both Microsoft and Cisco Systems supports.
DOTA2 uses CELT 0.11 but should be moved to Opus obviously since Opus is CELT.
Wikipedia has a nice article about Opus and a growing list of support from software and hardware providers: http://en.wikipedia.org/wiki/Opus_codec
VLC does currently support Opus. Mumble 1.2.4 will implement Opus as its primary codec, but it is currently in the release candidate stage. Support for Opus in TeamSpeak is only available if the clients are all using 3.0.10 beta or later and the server is running 3.0.7 PreRelease 2 or later[forum.teamspeak.com].
Google Chrome stable release and Mozilla Firefox nightly releases[www.webrtc.org] both currently support WebRTC. Opera at least partially implements it currently, and I imagine that it will have a complete implementation when they switch over to WebKit. Microsoft hasn't implemented WebRTC in Internet Explorer, as far as I'm aware, as they're working on the competing CU-RTC-Web standard. Opus may be mandatory to implement, but I don't believe that means that it's mandatory to use Opus when communicating via WebRTC.
Opus isn't really CELT. It's a hybrid of SILK and CELT. The Hydrogenaudio Knowledgebase[wiki.hydrogenaudio.org] has a few nice tables that help to clarify when each is used. They also have a lot more information on how Opus works and how it compares to other codecs. (There's also examples of how Opus handles varying bitrates and packet loss[opus-codec.org] that are pretty interesting.)
- Firefox Nightlies has had WebRTC support in some fashion for a while. The problem was that Google and Mozilla had slightly different implementations that kept them from talking to each other until very recently. Opera will use Chromium which will already have that work done.
- Microsoft has supported Opus as the "Mandatory To Implement" or MIT codec for WebRTC. As in, it does not have to be used, but it has to be included in order to have spec compliance. They did have a proposal for changing the current WebRTC spec but it has fell on deaf ears since the proposal arrived late(That particularly irritated a Cisco rep). Its not known whether or not some of the spec will be changed at a later date to match CU-RTC-Web, but as it currently stands Microsoft has no issue with the codec being MIT and has approved of it in the WebRTC mailing list.
- Hybrid components aside, Opus is CELT as of version 1.0.1 and RFC 6716 IETF ratification. CELT in any other form is considered obsolete by Xiph and all parties involved. I've been aware of both Hydrogen Audio and the Opus samples for some time now. I'm also aware of its history and its hybrid nature with a heavily modified SILK.