約 2,995,132 件
https://w.atwiki.jp/animesongs/pages/4386.html
SOUL EATER リピートショー 牧野由依 碧の香り 牧野由依「碧の香り」(Amazon) 発売元・販売元 Epic Records 発売日 2010.11.10 価格 1500円（税抜き） 内容 CD 碧の香り 歌：牧野由依 碧の香り（TV Size） 歌：牧野由依 碧の香り（without Yui） Cluster 歌：牧野由依 Cluster（without Yui） DVD 碧の香り［Music Video］ 碧の香り メイキング映像 TVアニメ「ソウルイーター リピートショー」エンディング映像 備考
https://w.atwiki.jp/gunvolt2ch/
“蒼き雷霆”が導く新たなる神話 このページは、PS4/Switch/3DS/PC/G-cluster用ソフト「蒼き雷霆(アームドブルー)ガンヴォルト」・「蒼き雷霆ガンヴォルト ストライカーパック」の攻略ページです。 閲覧の際はネタバレにご注意ください。 Switch版の変更点については、こちらを参照してください。 Steam版についても、2018年5月12日より一部内容がSwitch版に準拠して変更されております。変更点はこちら。 次作「蒼き雷霆ガンヴォルト 爪」の攻略wikiはこちら。 次々作「蒼き雷霆ガンヴォルト 鎖環」の攻略wikiはこちら。 次作の外伝編「マイティガンヴォルト バースト」の攻略wikiはこちら。 ガンヴォルトも出演する「ブラスターマスター ゼロ」の攻略wikiはこちら。 アキュラくんが主役のスピンアウト作品「白き鋼鉄のX」の攻略wikiはこちら。 サントラ・グッズ販売・イベントチケットはインティ・ダイレクトへ ゲーム情報 蒼き雷霆ガンヴォルト(3DS/PC/G-cluster) タイトル名 蒼き雷霆(アームドブルー)ガンヴォルト ハードウェア ニンテンドー3DSPC（Steam）PC（DMM）G-cluster/LEONET（レオパレス21） 販売方法 ダウンロード ジャンル ライトノベル2Dアクション レーティング CERO B（12歳以上対象） 配信日 3DS 2014年8月20日Steam 2015年8月29日DMM 2017年3月10日G-cluster 2018年2月21日 プレイ人数 1人 価格 1960円（税込）（G-cluster月額プランの対象外） セーブデータ 最大4つ 容量 3150ブロック（マイティガンヴォルトは71ブロック） 公式サイト http //gunvolt.com 公式ツイッター https //twitter.com/GunvoltOfficial 公式ラジオ（毎週日曜更新） 「INTERACTIVE WAVE」 Steamストアページ こちら DMMストアページ http //dlsoft.dmm.com/detail/inti_0033 G-cluster紹介ページ http //gcluster.jp/games/gunvolt.html https //gcluster.jp/leonet/games/gunvolt.html ストライカーパック(Switch/PS4) 今作ガンヴォルトと次作ガンヴォルト爪がセットになったパッケージです。 Switch/PS4では今作ガンヴォルトが単体で発売されていないため、必然的にこのストライカーパックを買うことになります。 タイトル名 蒼き雷霆(アームドブルー)ガンヴォルト ストライカーパック 収録作品 蒼き雷霆ガンヴォルト蒼き雷霆ガンヴォルト爪 ハードウェア Nintendo SwitchPlayStation4 販売方法 ダウンロード・パッケージ ジャンル ライトノベル2Dアクション レーティング CERO B 発売日 Seitch：2017年8月31日PS4：2020年4月23日 プレイ人数 1人 価格 Switchダウンロード版：4900円（税込）Switchパッケージ通常版：5000円+税Switchパッケージ限定版：8000円+税PS4デジタル版：4900円（税込）PS4パッケージ版：5000円（税込） 容量 2.8GB～ 公式サイト Switch：http //gunvolt.com/SP_NS/PS4：http //gunvolt.com/SP_PS4/ アニメガンヴォルト タイトル名 アニメ 蒼き雷霆(アームドブルー)ガンヴォルト ハードウェア ニンテンドー3DSDVDBlu-ray ジャンル アニメーション 収録時間 21分44秒 発売日 3DS 2017年2月9日DVD 2017年8月31日Blu-ray 未定 価格 3DS 600円（税込）DVD Switch版ストライカーパック限定版に同梱Blu-ray 未定 容量 3DS 1149ブロック 公式サイト http //gunvolt.com/anime/ eショップ https //www.nintendo.co.jp/titles/50010000042097 兄弟作 ロックマンゼロ攻略wiki http //www18.atwiki.jp/rockmanzero2ch/ ロックマンゼクス攻略wiki http //www14.atwiki.jp/rockmanzx2ch/
https://w.atwiki.jp/usb_audio/pages/39.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 51 Offset Field Size Value Description 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant 3D-STEREO_EXTENDER_PROCESS process type. 6 bNrInPins 1 Number Number of Input Pins of this Unit 1 7 bSourceID 1 Number ID of the Unit or Terminal to which the Input Pin of this Processing Unit is connected. 8 bNrChannels 1 Number Number of logical output channels in the Processing Unit’s output channel cluster. 9 wChannelConfig 2 Bitmap Describes the spatial location of the logical channels in the output channel cluster of the Processing Unit. At least Left and Right must be set. 11 iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel in the Processing Unit’s output channel cluster. 12 bControlSize 1 Number Size, in bytes, of the bmControls field n 13 bmControls n Bitmap A bit set to 1 indicates that the mentioned Control is supported D0 Enable Processing. D1 Spaciousness. D2..(n*8-1) Reserved 13+n iProcessing 1 Index Index of a string descriptor, describing this Processing Unit. 4.3.2.6.4 Reverberation Processing Unit Descriptor The wProcessType field of the common Processing Unit descriptor contains the value REVERBERATION_PROCESS. (See Section A.7, “Processing Unit Process Types”) The Reverberation Processing Unit has a single Input Pin. Therefore, the bNrInputs field must contain the value 1. The bNrChannels, wChannelConfig and iChannelNames fields together constitute the output cluster descriptor of the Reverberation Processing Unit. It describes which logical channels are physically present at the output of the Processing Unit. In most cases, this will be identical to the configuration of the input channel cluster. The bmControls field indicates which reverberation-related Controls are effectively implemented in the Reverberation Processing Unit. The following table outlines the Reverberation Processing Unit descriptor. It is identical to the common Processing Unit descriptor, except for some field values. It is repeated here for clarity. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 52 Table 4-12 Reverberation Processing Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 14+n 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant PROCESSING_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant REVERBERATION_PROCESS process type. 6 bNrInPins 1 Number Number of Input Pins of this Unit 1 7 bSourceID 1 Number ID of the Unit or Terminal to which the Input Pin of this Processing Unit is connected. 8 bNrChannels 1 Number Number of logical output channels in the output channel cluster of the Processing Unit. 9 wChannelConfig 2 Bitmap Describes the spatial location of the logical channels in the output channel cluster of the Processing Unit. 11 iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel in the output channel cluster Processing Unit. 12 bControlSize 1 Number Size, in bytes, of the bmControls field n 13 bmControls n Bitmap A bit set to 1 indicates that the mentioned Control is supported D0 Enable Processing. D1 Reverb Type. D2 Reverb Level. D3 Reverb Time. D4 Reverb Delay Feedback. D5..(n*8-1) Reserved. 13+n iProcessing 1 Index Index of a string descriptor, describing this Processing Unit. 4.3.2.6.5 Chorus Processing Unit Descriptor The wProcessType field of the common Processing Unit descriptor contains the value CHORUS_PROCESS. (See Section A.7, “Processing Unit Process Types”) The Chorus Processing Unit has a single Input Pin. Therefore, the bNrInputs field must contain the value 1. The bNrChannels, wChannelConfig, and iChannelNames fields together constitute the output cluster USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 53 descriptor of the Chorus Processing Unit. It describes which logical channels are physically present at the output of the Processing Unit. In most cases, this will be identical to the configuration of the input channel cluster. The bmControls field indicates which chorus-related Controls are effectively implemented in the Chorus Processing Unit. The following table outlines the Chorus Processing Unit descriptor. It is identical to the common Processing Unit descriptor, except for some field values. It is repeated here for clarity. Table 4-13 Chorus Processing Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 14+n 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant PROCESSING_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant CHORUS_PROCESS process type. 6 bNrInPins 1 Number Number of Input Pins of this Unit 1 7 bSourceID 1 Number ID of the Unit or Terminal to which the Input Pin of this Processing Unit is connected. 8 bNrChannels 1 Number Number of logical output channels in the output channel cluster of the Processing Unit. 9 wChannelConfig 2 Bitmap Describes the spatial location of the logical channels in the output channel cluster of the Processing Unit. 11 iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel in the output channel cluster of the Processing Unit. 12 bControlSize 1 Number Size, in bytes, of the bmControls field n 13 bmControls n Bitmap A bit set to 1 indicates that the mentioned Control is supported D0 Enable Processing. D1 Chorus Level. D2 Chorus Modulation Rate. D3 Chorus Modulation Depth. D4..(n*8-1) Reserved USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 54 Offset Field Size Value Description 13+n iProcessing 1 Index Index of a string descriptor, describing this Processing Unit. 4.3.2.6.6 Dynamic Range Compressor Processing Unit Descriptor The wProcessType field of the common Processing Unit descriptor contains the value DYN_RANGE_COMP_PROCESS. (See Section A.7, “Processing Unit Process Types”) The Dynamic Range Compressor Processing Unit has a single Input Pin. Therefore, the bNrInputs field must contain the value 1. The bNrChannels, wChannelConfig, and iChannelNames fields together constitute the output cluster descriptor of the Dynamic Range Compressor Processing Unit. It describes which logical channels are physically present at the output of the Processing Unit. In most cases, this will be identical to the configuration of the input channel cluster. The bmControls field indicates which Controls are effectively implemented in the Dynamic Range Compressor Processing Unit. The following table outlines the Dynamic Range Compressor Processing Unit descriptor. It is identical to the common Processing Unit descriptor, except for some field values. It is repeated here for clarity. Table 4-14 Dynamic Range Compressor Processing Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 14+n 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant PROCESSING_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant DYN_RANGE_COMP_PROCESS process type. 6 bNrInPins 1 Number Number of Input Pins of this Unit 1 7 bSourceID 1 Number ID of the Unit or Terminal to which the Input Pin of this Processing Unit is connected. 8 bNrChannels 1 Number Number of logical output channels in the output channel cluster of the Processing Unit. 9 wChannelConfig 2 Bitmap Describes the spatial location of the logical channels in the output channel cluster of the Processing Unit. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 55 Offset Field Size Value Description 11 iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel in the output channel cluster of the Processing Unit. 12 bControlSize 1 Number Size, in bytes, of the bmControls field n 13 bmControls n Bitmap A bit set to 1 indicates that the mentioned Control is supported D0 Enable Processing. D1 Compression Ratio. D2 MaxAmpl. D3 Threshold. D4 Attack time. D5 Release time. D6..(n*8-1) Reserved 13+n iProcessing 1 Index Index of a string descriptor, describing this Processing Unit. 4.3.2.7 Extension Unit Descriptor The Extension Unit is uniquely identified by the value in the bUnitID field of the Extension Unit descriptor (XUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Extension Unit. The Extension Unit descriptor provides minimal information about the Extension Unit for a generic driver at least to notice the presence of vendor-specific components within the audio function. The wExtensionCode field may contain a vendor-specific code that further identifies the Extension Unit. If it is not used, it should be set to zero. The bNrInPins field contains the number of Input Pins (p) of the Extension Unit. The connectivity of the Input Pins is described via the baSourceID() array that contains p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or Terminal to which Input Pin i is connected. The cluster descriptors that describe the logical channels that enter the Extension Unit are not repeated here. It is up to the Host software to trace the connections ‘upstream’ to locate the cluster descriptors pertaining to the audio channel clusters. Because an Extension Unit can freely redefine the spatial locations of the logical output channels that are contained in its output cluster, there is a need for an output cluster descriptor. The bNrChannels, wChannelConfig, and iChannelNames fields characterize the cluster that leaves the Extension Unit over its single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” The bmControls field is a bitmap, indicating the availability of certain audio Controls in the Extension Unit. For future expandability, the number of bytes occupied by the bmControls field is indicated in the bControlSize field. In general, all Controls are optional, except for the Enable Processing Control. This Control must be supported by every Extension Unit. The Enable Processing Control is used to bypass the entire functionality of the Extension Unit. This Control is mandatory for it allows a generic driver to operate the audio function without further knowledge of the internals of the Extension Unit. (Of course, the additional functionality provided by the 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/bfgmatome/pages/596.html
ゲーム情報（登録されているタグ） ジャンル＞アイテム探し 製作会社＞不明 言語＞英語 コメント欄へ移動 ゲーム配布ページ 英語 http //www.bigfishgames.com/download-games/11096/clutter/index.html 日本語 紹介文 Clean up the Clutter in this amazing Hidden Object game! Take on minigames and put everything in order again! Progress through countless levels as you dash through each stage and try different modes of play. Randomly created levels and puzzles give you hours upon hours of fun! Can you take on the Clutter? Tons of levels Gripping gameplay Clean up the Clutter! 画像 « » var ppvArray_0_3b0e726e505675c49612412e292ae48e = new Array(); ppvArray_0_3b0e726e505675c49612412e292ae48e[0] = http //w.atwiki.jp/bfgmatome/?cmd=upload&act=open&page=Clutter&file=en_clutter-screen1.jpg ; window.onload=function(){ ppvShow_0_3b0e726e505675c49612412e292ae48e(0); }; function ppvShow_0_3b0e726e505675c49612412e292ae48e(n){ if(!ppvArray_0_3b0e726e505675c49612412e292ae48e[n]){ alert( 画像がありません ); return; } ppv_0_3b0e726e505675c49612412e292ae48e$( ppv_img_0_3b0e726e505675c49612412e292ae48e ).src=ppvArray_0_3b0e726e505675c49612412e292ae48e[n]; ppv_0_3b0e726e505675c49612412e292ae48e$( ppv_link_0_3b0e726e505675c49612412e292ae48e ).href=ppvArray_0_3b0e726e505675c49612412e292ae48e[n]; ppv_0_3b0e726e505675c49612412e292ae48e$( ppv_prev_0_3b0e726e505675c49612412e292ae48e ).href= javascript ppvShow_0_3b0e726e505675c49612412e292ae48e( +(n-1)+ ) ; ppv_0_3b0e726e505675c49612412e292ae48e$( ppv_next_0_3b0e726e505675c49612412e292ae48e ).href= javascript ppvShow_0_3b0e726e505675c49612412e292ae48e( +(n+1)+ ) ; } function ppv_0_3b0e726e505675c49612412e292ae48e$(){ var elements = new Array(); for (var i = 0; i arguments.length; i++){ var element = arguments[i]; if (typeof element == string ) element = document.getElementById(element); if (arguments.length == 1) return element; elements.push(element); } return elements; } 備考 レス一覧 コメント コメント すべてのコメントを見る トップページに戻る
https://w.atwiki.jp/clickeridle/pages/110.html
URL https //demonin.com/games/hyperGame/ 作者名 Demonin プラットフォーム HTML オフライン進行 有 数学において巨大な数を表すための記法「ハイパーE表記」を題材としたゲーム。 Ordinal Markupにインスパイアされたゲーム、「Ordinal Pringles」の影響を強く受けているとのこと。 ※ハイパーE表記自体については、Wikipediaの解説記事を参照。 ゲームの流れ Hyper-ENumber Factors Clusters Challenges Vectors Base Points CascadeCascade Recent Milestones Post-cascade Flavours Shadow crystals DeutericDeuteric Recent Deuteric Milestones Deuteric Challenges Achievements コメント ゲームの流れ Hyper-E Number 「Increase your number」を押すことで、上の数字がどんどん大きくなっていく。 あなたはいつでも数字をリセットして1E1に戻すことができる。 リセットを行った場合、上部にある、ハイパーE表記で書かれた数の大きさに応じて、「hyper-point」を獲得する。 Factors 集めたhyper-pointでアップグレードを購入することができる。 base shiftを行うと、ハイパーE表記で書かれた数の底(≒繰り上がりのタイミング)が1減る。4以下にはならない。 数の底を5に減らした上で、数を一定以上の大きさにすると「Cluster your number」ができるようになる。 Cluster your numberを行うとNumber・Factorsタブの進行がリセットされるが、「Cluster」というリソースを獲得できる。 Factorは、プレイヤーの代わりに「Increase your number」を自動で押してくれる「Auto Clicker」を生産する。 1st factorはAuto Clickerを直接生産し、2番目以降のfactorは1つ下の番号のfactorを生産する。 種類 効果 解禁条件 価格 1st factor Auto Clickerを生産 - 1e(購入回数+1) 2nd factor 1st factorを生産 base shiftを1回行うと出現 1e((購入回数+1)×2) 3rd factor 2nd factorを生産 base shiftを2回行うと出現 1e((購入回数+1)×3) 4th factor 3rd factorを生産 base shiftを3回行うと出現 1e((購入回数+1)×4) 5th factor 4th factorを生産 base shiftを4回行うと出現 1e((購入回数+1)×5) 6th factor 5th factorを生産 base shiftを5回行うと出現 1e((購入回数+1)×6) Clusters 集めたClusterでアップグレードを購入することができる。 アップグレードは上から下へと取っていくのが原則であり、 2行目以降のアップグレードを購入したいなら、直上のアップグレードを先に購入しておく必要がある。 「Respec cluster」を押すことで、購入したアップグレードを全て手放してclusterに還元できる。 ただし、この際、「Cluster your number」を押した時と同等のリセットが行われる。 一番右はアップグレードではなく実績。 一定以上のClusterを所持することで達成となり、何らかの要素が解禁される。 アップグレードの効果 価格 左1 手動で購入したFactorが、そのFactorの効果を増加させる 1 左2 「Increase your number」を手動で押した時の効果 ×10 4 左3 3rd factorを1個持った状態で始まる 40 左4 Vector所持量に応じて、Vectorの入手量が増加 50 中1 倍率をかける効果の倍率が2乗される 1 中2 未使用のclusterに応じて、Factorの生産量が増加 3 中3 チャレンジ中、底が8になる 24 中4 Base pointに応じて、Vectorの入手量が増加 175 右1 手動で購入したFactorが、そのFactorの効果を増加させる 2 右2 Base shiftを行った回数に応じて、Factorの生産力が増加 12 右3 Hyper-pointが毎秒100ずつ自動増加 15 右4 チャレンジの達成回数に応じて、Autoclickerのクリック速度が増加 25 MS1 Challengeを解禁 (10) MS2 Vectorを解禁 (55) MS3 Base Pointを解禁 (153) MS4 Cascadeを解禁 (496) Challenges Clusterを10以上獲得することで解禁される。 受領時に「Cluster your number」相当のリセットを行った上で、画面上部の数を一定以上まで上げればクリア。 ただし、チャレンジの種類ごとに特定の条件が課せられる。 チャレンジは1回クリアするごとに、各Factorの生産速度が100倍になる。クリアボーナスは3回が上限。 No. 制約 目標 1 2nd以降のFactorを購入できない 1回目： 1Ex##x##22回目： 1Ex##x##x#x#x#23回目： 1Ex###x##x##2 2 Base shiftを行うごとに、各Factorの生産力÷10 1回目： 1Ex##x##x#22回目： 1Ex###x##x##x##23回目： 1Ex###x###x##x##2 3 底が20になるBase Shiftを行えない 1回目： 1Ex##x#x#x#22回目： 1Ex##x##x##x##x##23回目： 1Ex###x##2 4 Cluster Upgradeを購入するごとに、Autoclickerの速度が1/10000になる 1回目： 1Ex####22回目： 1Ex####x###x##23回目： 1Ex####x####2 5 常にVectorの獲得がオンになる(速度上限10k/s)Base ShiftでVectorがリセットされる 1回目： 1Ex####x###22回目： 1Ex####x###x###x###23回目： 1Ex####x####x##x##2 6 Cluster Upgradeを購入できないAutoclicker multiplierを購入できない5th以降のFactorを購入できない 1回目： 1Ex####22回目： 1Ex####x###x##23回目： 1Ex####x###x###2 Vectors Clusterを55以上獲得することで解禁される。 Vector Gainをオンにしている間、上の数の大きさに応じてVectorを獲得できる。 ただし、その所持数に応じてFactorの生産力が劇的に減少してしまう。 「Reset vectors to 0」ボタンでVector所持量が0になるので必要に応じて活用したい。 また、Vectorの生産量は1e100/秒を超えるとSoftcapがかかるようになる。 Vectorアップグレード 名前 効果 価格 Double vector gain Vector獲得量×2 200×(10^購入回数) Increase vector gainbased on total clusters Cluster所持量に応じて、Vector獲得量が増加 1000×(5^購入回数) Multiply factor production Factor生産量が増加 1000×(4^購入回数) Multiplier autoclicker speedin challenges Challenge内のみ、Autoclickerの速度が増加13回購入すると上限に達する(x1.00e15) 100000×(10^購入回数) Decrease basedverse base Basedverseの底-1(5回まで購入可能) 1e12×(100^購入回数) Multiply up-base anddown-base effect Base pointの効果が向上 1e15×(20^購入回数) Base Points Clusterを153以上獲得することで解禁される。 Basedverseというチャレンジに似たようなものが用意される。 Basedverseに入っている間は底が20に固定される。Base shiftやClustersのアップグレードでは底が減らない。 Basedverse中の上の数の大きさに応じて、Basedverseから抜けた際にBase Pointを獲得する。 Base Pointはupとdownのいずれかに振り分けることができ、upは各Factorの生産力を、DownはVectorの獲得量を増加させる。 1000 Base Pointで上限に達し、それ以上Base pointを入手することはできない。 Cascade Clusterを496以上獲得することで解禁されるタブ。 上の数字が1Ex#^#xを超えた時、新たなソフトリセットを行うことができる。 ソフトリセットを行うとHyper-Eの進捗（Clusterタブのマイルストーンを除く）が全て失われてしまう代わりに、Cascadeというリソースを入手できる。 Clusterを496獲得するためには1Ex#^#xが必要なので、初回のみ1Ex#^#x以上に二度到達しなければならない。 Cascade このタブではPower Producerを購入できる。 Power Producerは「Cascade power」を産み出すことができる施設。 Cascade powerの所持量に応じて、Factorの生産力が上昇する。 種類 効果 価格 Power producer Cascade Powerを生産 1×2^(購入回数) 1st layer Power producerを生産 1×2^(購入回数) 2nd layer 1st layerを生産 2×2^(購入回数) 3rd layer 2nd layerを生産 4×4^(購入回数) 4th layer 3rd layerを生産 8×8^(購入回数) 5th layer 4th layerを生産 16×16^(購入回数) 6th layer 5th layerを生産 32×32^(購入回数) Recent 過去10回のCascadeソフトリセットに要した時間と、獲得したCascade、そして1秒あたりのCascade獲得量を確認できる。 Milestones Cascadeリセットに関する実績。 所持しているClusterが一定以下の状態でCascadeリセットを行うことで達成となり、ボーナスを得られる。 実績一覧 Cluster ボーナス 496 Factorを自動購入できるようになる 435 Vectorを所持していてもFactorの生産力が低下しなくなる（Challenge 5を除く） 378 Challenge報酬の効果が×100→×1000に増加Layerを解禁 325 Cascadeリセットを行っても、Base Pointがリセットされなくなる 276 購入したLayerが、その種類のLayerの生産力を増加させる 231 Cascade Powerの効果が向上 171 Cascadeリセットを行っても、Challengeの達成状況がリセットされなくなる 120 Cascadeリセットを行っても、Vectorアップグレードがリセットされなくなる 21 毎秒100のhyper-pointを自動獲得 0 Post-cascadeを解禁 Shadow milestones 後に登場する「Shadow Crystal」の所持数が一定以上になるとボーナスを得られる。 Shadow Crystal ボーナス 1 Vector Upgradeの3番目の効果を強化 3 Alpha-flavourの所持量に応じて、Shadow Power獲得量が増加 10 Clusterリセットを行わずにClusterを獲得可能になる 50 Alpha-flavourの所持量に応じて、Cascade獲得量が増加 100 Vector Upgradeの3番目の効果を強化 1,500 Blood Crystalの所持数に応じて、Shadow Power獲得量が増加 15,000 Shadow Crystalの所持数に応じて、Divine Power獲得量が増加 100,000 Post-cascadeeアップグレードを自動購入 10,000,000 Cascadeを自動獲得（獲得ペースは現在値の100%/秒） 1e15 Deutericを解禁 Post-cascade 10番目のMilestoneを達成（Clusterを一切持たずにCascadeリセットを行う）することで解禁される。 Surpass Cascadeのボタンを押すことで数字の上限(1Ex#^#x)が撤廃され、数字に応じて一度に2以上のCascadeを入手することが出来るようになる。 ここではCascadeを使用してアップグレードを購入できる。 アップグレード名 効果 価格 Increase cascade gain Cascadeの獲得量×2（何度でも購入可能） 20×5^(購入回数) Increase up/down-base effectbased on time spent in this cascade 最後のCascadeリセットからの経過時間に応じて、Up/Downの効果が向上 30 Unlock auto-base shift Base shiftを自動化 50 Multiply cascade gainbased on unspent clusters 未使用のClusterに応じて、Cascadeの獲得量が増加 120 Cluster upgrades arenot always bought at no cost Clusterアップグレードを自動購入 300 Gain 100% of potentialhyper-point per second 現在リセットで獲得可能なHyper pointの100%を毎秒得る 750 Gain 10% of best cascadeper second Cascadeを自動獲得（獲得ペースは最高効率時の10%） 1000 Improve post-cascadeupgrade 1 cost 「Increase cascade gain」のコストを85%減少させる 5,000,000 Layer production is multipliedby (layers bought)^3 instead of ^1 各Layerの生産力が、そのLayerの購入回数の3乗に比例するようになる 250,000,000 Unlock Shadow crystalsand shadow milestones Shadow Crystalを解禁Shadow Milestonesを解禁 1e12 Flavours Post-Cascadeアップグレードの7番目を購入することで解禁される。 各Flavourをアンロックしたのち、一定の量のCascadeを消費することによって各Flavourを入手することが出来る。 各Flavourには様々なブースト効果がある。 これらのFlavourを入手するためにはまず、Cascadeを使用してアンロックする必要がある。 Flavour名 解禁コスト Alpha-Flavour 500 Beta-Flavour 100,000 Gamma-Flavour 1,000,000 Delta-Flavour 100,000,000 Epsilon-Flavour 1e10 各Flavourの1つあたりのコストと効果は下表のとおり。 Flavour名 コスト 効果 Alpha-Flavour 1,000 Cascade Factorの生産量を累乗で強化し、さらにCascade入手量も乗算で強化する Beta-Flavour 1,000 Alpha-Flavour Alpha-FlavourとCascadeの入手量を乗算で強化する Gamma-Flavour 1,000 Beta-Flavour Beta-FlavourとCascadeの入手量を乗算で強化する Delta-Flavour 1,000 Gamma-Flavour Gamma-FlavourとCascadeの入手量を乗算で強化する Epsilon-Flavour 1,000 Delta-Flavour Delta-FlavourとCascadeの入手量を乗算で強化する Shadow crystals Post-Cascadeアップグレードの9番目を購入すると解禁される。 ここでは現在のHyper-Point, Shadow Power, Blood Powerに応じて、Shadow Power, Blood Power, Divine Powerがたまっていく。そして一定のPowerに到達すると(デフォルトでは1,000,000 Power)Shadow Crystalなどのリソースを入手することが出来る。Shadow CrystalはCascadeの入手量を乗算で強化し、Blood CrystalとDivine Crystalはそれぞれ1つ下のPower入手量とCascade入手量を乗算で強化する。 また、Shadow PowerなどのPowerはアップグレードにも使用される。 アップグレード名 効果 コスト Double shadow power/s Shadow Power入手量を倍加する 100,000×10^(購入回数) Decrease shadowcrystal requirement Shadow Crystalを入手するために必要なShadow Powerの要求量を減少させる 5,000,000×4^(購入回数) Unlock blood crystals Blood Crystalを解禁する 25,000,000 Double blood power/s Blood Power入手量を倍加する 100,000×10^(購入回数) Decrease bloodcrystal requirement Blood Crystalを入手するために必要なBlood Powerの要求量を減少させる 5,000,000×4^(購入回数) Unlock divine crystals Divine Crystalを解禁する 25,000,000 Double divine power/s Divine Power入手量を倍加する 100,000×10^(購入回数) Decrease divinecrystal requirement Divine Crystalを入手するために必要なDivine Powerの要求量を減少させる 5,000,000×4^(購入回数) Deuteric v1.4.2で追加。現在編集中。 Shadow Crystalが1e15まで到達し、上の数字を1Ex##*##xまで貯めると実行できる。 Cascadeタブまでのすべての進行状況（Deuteric Milestonesによる例外あり）をリセットする。 Deuteric このタブではDeuterium Producerを購入できる。 Deuterium Producerは「Deuterium」を産み出すことができる施設。 Deuteriumの所持量に応じて、Cascadeの入手量が上昇する。 1st～6thのcombinatorはDeutericを2回行うと解禁される。 種類 効果 価格 Deuterium producer Deuteriumを生産 1×2^(購入回数) 1st combinator Deuterium producerを生産 1×2^(購入回数)? 2nd combinator 1st layerを生産 2×2^(購入回数)? 3rd combinator 2nd layerを生産 4×4^(購入回数)? 4th combinator 3rd layerを生産 8×8^(購入回数)? 5th combinator 4th layerを生産 16×16^(購入回数)? 6th combinator 5th layerを生産 32×32^(購入回数)? Recent 過去10回のDeutericソフトリセットに要した時間と、獲得したDeuteric、そして1秒あたりのDeuteric獲得量を確認できる。 Deuteric Milestones Deutericリセットに関する実績。 一定量のDeutericを獲得(トータルの所持量)することで達成となり、様々なボーナスを得られる。 実績一覧 Deuteric ボーナス 1 リセット時にFactorの自動購入とHyper-pointの自動入手を保持する 2 リセット時にChallangeの達成状況を保持するCombinatorを解禁する 3 Shadow powerの入手量を増加し、その効果の上限を引き上げる 4 リセット時にpost-Cascadeアップグレード1の自動購入を保持するCrystalアップグレードの自動購入を解禁する 6 Blood powerの入手量を増加し、その効果の上限を引き上げる 8 リセット時にpost-Cascadeアップグレードを保持する(アップグレード1を除く) 12 Divine powerの入手量を増加し、その効果の上限を引き上げる 16 購入したCombinatorが、その種類のCombinatorの生産力を増加させる 25 Base Pointの上限を2500まで引き上げる 40 Deuteric Challengeを解禁する 50 up/down baseが、base pointの所持数と等しくなる 60 Vector生産が生産力低下なしで常に有効になるVectorアップグレードの自動最大購入を解禁する 75 Combinatorの生産力が10倍になり、さらにDeuteriumの効果が2乗される 100 Deuteric Challengeの達成数に応じて、Shadow/Blood/Divine Power獲得量増加 150 Beta以降のFlavour所持数がAlpha-Flavourの所持数と常に等しくなる 250 リセット時にShadow Milestone 3とCascade Milestoneを保持する 350 Layerの自動購入を解禁する 500 Layerの生産力が2乗される 650 Flavour所持数が、Cascadeの最大所持数と常に等しくなる 1000 未実装 Deuteric Challenges Deutericを40以上獲得することで解禁される。 受領時にDeuteric相当のリセットを行った上で、Deutericリセットを行えばクリア。 ただし、チャレンジの種類ごとに特定の条件が課せられる。 各チャレンジは1回クリアするごとに、それぞれのクリアボーナスが得られ、さらに制約が厳しくなる。 その分、クリア回数に応じて報酬も強化される。 No. 制約 制約の上昇 ボーナス 1 Post-Cascadeアップグレード2-8を購入できないアップグレード1の購入回数が制限される 1回目：20回2回目：5回3回目：0回(購入不可) Shadow Crystalの効果上限増加(1回につき1e8倍) 2 Shadow/Blood/Divine Powerの所持数が制限される 1回目：1e162回目：1e143回目：999,999 Blood Crystalの効果上限増加(1回につき1e8倍) 3 Cascade Milestoneを獲得できないCascadeの獲得量が大幅減少 1回目：(獲得量)^0.92回目：(獲得量)^0.53回目：(獲得量)^0.3 Divine Crystalの効果上限増加(1回につき1e8倍) 4 Cascadeを実行すると、slogsが指数関数的に増加するslogsがCascade保有量を上回ると、Challengeがリセットされる slogsの増加がさらに加速 Base Pointの所持数上限が2500からさらに増加(1回につき+1倍) Achievements 実績。取得しても特に効果があるわけではないが自分のゲームの進捗状況の目安として活用できる。 ここでは上から2段目,左から3番目ならIDは23などのようにする ID Achievement名 達成条件 11 Achieve 1Ex##2 任意のBaseで1Ex##2に到達する 12 Achieve 1Ex###2 任意のBaseで1Ex###2に到達する 13 Achieve 1Ex###x###2 任意のBaseで1Ex###x###2に到達する 14 Achieve 1Ex####2 任意のBaseで1Ex####2に到達する 15 Achieve 1Ex####x####2 任意のBaseで1Ex####x####2に到達する 16 Achieve 1Ex#^#x 任意のBaseで1Ex#^#xに到達する(Cascade到達) 21 Beat Challange1 once Challange1を1回クリアする 22 Beat Challange2 once Challange2を1回クリアする 23 Beat Challange3 once Challange3を1回クリアする 24 Beat Challange4 once Challange4を1回クリアする 25 Beat Challange5 once Challange5を1回クリアする 26 Beat Challange6 once Challange6を1回クリアする 31 Beat Challange1 3times Challange1を3回クリアする 32 Beat Challange2 3times Challange2を3回クリアする 33 Beat Challange3 3times Challange3を3回クリアする 34 Beat Challange4 3times Challange4を3回クリアする 35 Beat Challange5 3times Challange5を3回クリアする 36 Beat Challange6 3times Challange6を3回クリアする 41 Achieve 1 cascade milestone Cascade Milestoneを1つ達成する 42 Achieve 2 cascade milestones Cascade Milestoneを2つ達成する 43 Achieve 4 cascade milestones Cascade Milestoneを4つ達成する 44 Achieve 6 cascade milestones Cascade Milestoneを6つ達成する 45 Achieve 8 cascade milestones Cascade Milestoneを8つ達成する 46 Achieve 10 cascade milestones Cascade Milestoneを10個達成する 51 Have 1 alpha-flavour Alpha-Flavorを1つ獲得する 52 Have 1 beta-flavour Beta-Flavorを1つ獲得する 53 Have 1 gamma-flavour Gamma-Flavorを1つ獲得する 54 Have 1 delta-flavour Delta-Flavorを1つ獲得する 55 Have 1 epsilon-flavour Epsilon-Flavorを1つ獲得する 56 Have 1,000 epsilon-flavour Epsilon-Flavorを1,000個獲得する 61 Achieve 1 deuteric milestone Deuteric Milestoneを1つ達成する 62 Achieve 2 deuteric milestones Deuteric Milestoneを2つ達成する 63 Achieve 4 deuteric milestones Deuteric Milestoneを4つ達成する 64 Achieve 6 deuteric milestones Deuteric Milestoneを6つ達成する 65 Achieve 8 deuteric milestones Deuteric Milestoneを8つ達成する 66 Achieve 10 deuteric milestones Deuteric Milestoneを10個達成する コメント 今は更に上位のDeutericレイヤーが実装されました (2023-12-04 15 17 38) コメント
https://w.atwiki.jp/clan-sorz/pages/41.html
Counter-Strike Valveの「Half-life」のMODとして登場した作品。 後に製品化された作品。通称「1.6」 当時のエンジンを使用しているため、癖の強い操作やエイムの仕方などに癖のある作品である。 特に走り撃ちでは余り当たらない。 しかし今もなお、世界中で愛されているPCゲームでのFPSである。 また、シングルプレイなどが導入された「Condition Zero」などバージョンアップタイプが続々リリースされた。
https://w.atwiki.jp/usb_audio/pages/37.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 41 The bNrInPins field contains the number of Input Pins (p) of the Mixer Unit. This evidently equals the number of audio channel clusters that enter the Mixer Unit. The connectivity of the Input Pins is described via the baSourceID() array, containing p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels entering the Mixer Unit are not repeated here. It is up to the Host software to trace the connections ‘upstream’ to locate the cluster descriptors pertaining to the audio channel clusters. As mentioned before, every input channel can virtually be mixed into all of the output channels. If n is thetotal number of logical input channels, contained in all the audio channel clusters that are entering the Mixer Unit ここに式 and m is the number of logical output channels, then there are n x m mixing Controls in the Mixer Unit, some of which may not be programmable. cite(Note) Both n and m must be limited to 254. Because a Mixer Unit can redefine the spatial locations of the logical output channels, contained in its output cluster, there is a need for a Mixer output cluster descriptor. The bNrChannels, wChannelConfig and iChannelNames characterize the cluster that leaves the Mixer Unit over the single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” The Mixer Unit Descriptor reports which Controls are programmable in the bmControls bitmap field. This bitmap must be interpreted as a two-dimensional bit array that has a row for each logical input channel and a column for each logical output channel. If a bit at position [u, v] is set, this means that the Mixer Unit contains a programmable mixing Control that connects input channel u to output channel v. If bit [u, v] is clear, this indicates that the connection between input channel u and output channel v is non-programmable. Its fixed value can be retrieved through the appropriate request. The valid range for u is from one to n. The valid range for v is from one to m. The bmControls field stores the bit array row after row where the MSb of the first byte corresponds to the connection between input channel 1 and output channel 1. If (n x m) is not an integer multiple of 8, the bit array is padded with zeros until an integer number of bytes is occupied. The number of bytes used to store the bit array, N, can be calculated as follows IF ((n x m) MOD 8) 0 THEN N = ((n x m) DIV 8) + 1 ELSE N = ((n x m) DIV 8) An index to a string descriptor is provided to further describe the Mixer Unit. The following table details the structure of the Mixer Unit descriptor. Table 4-5 Mixer Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 10+p+N 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant MIXER_UNIT descriptor subtype. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 42 Offset Field Size Value Description 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bNrInPins 1 Number Number of Input Pins of this Unit p 5 baSourceID(1) 1 Number ID of the Unit or Terminal to which the first Input Pin of this Mixer Unit is connected. … … … … … 5+(p-1) baSourceID (p) 1 Number ID of the Unit or Terminal to which the last Input Pin of this Mixer Unit is connected. 5+p bNrChannels 1 Number Number of logical output channels in the Mixer’s output audio channel cluster. 6+p wChannelConfig 2 Bitmap Describes the spatial location of the logical channels. 8+p iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel. 9+p bmControls N Number Bit map indicating which mixing Controls are programmable. 9+p+N iMixer 1 Index Index of a string descriptor, describing the Mixer Unit. 4.3.2.4 Selector Unit Descriptor The Selector Unit is uniquely identified by the value in the bUnitID field of the Selector Unit descriptor (SUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Selector Unit. The bNrInPins field contains the number of Input Pins (p) of the Selector Unit. The connectivity of the Input Pins is described via the baSourceID() array that contains p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels that enter the Selector Unit are not repeated here. In order for a Selector Unit to be legally connected, all of the audio channel clusters that enter the Selector Unit must have the same number of channels. However, the spatial locations of these channels may vary from cluster to cluster. Therefore, the Host software should trace all Input Pins to find their ‘upstream’ connection to locate the cluster descriptors for all the Input Pins that enter the Selector Unit. This further implies that the cluster descriptor, associated with the Output Pin of the Selector Unit can change dynamically, depending on the currently selected position of the Selector Unit. An index to a string descriptor is provided to further describe the Selector Unit. The following table details the structure of the Selector Unit descriptor. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 43 Table 4-6 Selector Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 6+p 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant SELECTOR_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bNrInPins 1 Number Number of Input Pins of this Unit p 5 baSourceID(1) 1 Number ID of the Unit or Terminal to which the first Input Pin of this Selector Unit is connected. … … … … … 5+(p-1) baSourceID (p) 1 Number ID of the Unit or Terminal to which the last Input Pin of this Selector Unit is connected. 5+p iSelector 1 Index Index of a string descriptor, describing the Selector Unit. 4.3.2.5 Feature Unit Descriptor The Feature Unit is uniquely identified by the value in the bUnitID field of the Feature Unit descriptor (FUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Feature Unit. The bSourceID field is used to describe the connectivity for this Feature Unit. It contains the ID of the Unit or Terminal to which this Feature Unit is connected via its Input Pin. The cluster descriptor, describing the logical channels entering the Feature Unit is not repeated here. It is up to the Host software to trace the connection ‘upstream’ to locate the cluster descriptor pertaining to this audio channel cluster. The bmaControls() array is an array of bit-maps, each indicating the availability of certain audio Controls for a specific logical channel or for the master channel 0. For future expandability, the number of bytes occupied by each element (n) of the bmaControls() array is indicated in the bControlSize field. The number of logical channels in the cluster is denoted by ch. An index to a string descriptor is provided to further describe the Feature Unit. The layout of the Feature Unit descriptor is detailed in the following table. Table 4-7 Feature Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 7+(ch+1)*n USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 44 Offset Field Size Value Description 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant FEATURE_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 bSourceID 1 Constant ID of the Unit or Terminal to which this Feature Unit is connected. 5 bControlSize 1 Number Size in bytes of an element of the bmaControls() array n 6 bmaControls(0) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for master channel 0 D0 MuteD1 VolumeD2 BassD3 MidD4 TrebleD5 Graphic EqualizerD6 Automatic GainD7 DelayD8 Bass BoostD9 LoudnessD10..(n*8-1) Reserved 6+n bmaControls(1) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for logical channel 1. … … … … … 6+(ch*n) bmaControls(ch) n Bitmap A bit set to 1 indicates that the mentioned Control is supported for logical channel ch. 6+(ch+1)*n iFeature 1 Index Index of a string descriptor, describing this Feature Unit. 4.3.2.6 Processing Unit Descriptor The Processing Unit is uniquely identified by the value in the bUnitID field of the Processing Unit descriptor (PUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Processing Unit. The wProcessType field contains a value that fully identifies the Processing Unit. For a list of all supported Processing Unit Types, see Section A.7, “Processing Unit Process Types.” The bNrInPins field contains the number of Input Pins (p) of the Processing Unit. The connectivity of the Input Pins is described via the baSourceID() array that contains p elements. The index i into the array is one-based and directly related to the Input Pin numbers. BaSourceID(i) contains the ID of the Unit or USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 45 Terminal to which Input Pin i is connected. The cluster descriptors, describing the logical channels entering the Processing Unit are not repeated here. It is up to the Host software to trace the connections ‘upstream’ to locate the cluster descriptors pertaining to the audio channel clusters. Because a Processing Unit can freely redefine the spatial locations of the logical output channels, contained in its output cluster, there is a need for an output cluster descriptor. The bNrChannels, wChannelConfig, and iChannelNames fields characterize the cluster that leaves the Processing Unit over the single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” The bmControls field is a bitmap, indicating the availability of certain audio Controls in the Processing Unit. For future expandability, the number of bytes occupied by the bmControls field is indicated in the bControlSize field. In general, all Controls are optional. However, some Processing Types may define certain Controls as mandatory. In such a case, the appropriate bit in the bmControls field must be set to one. The meaning of the bits in the bmControls field is qualified by the wProcessType field. However, bit D0 always represents the Enable Processing Control for all Processing Unit Types. The Enable Processing Control is used to bypass the entire functionality of the Processing Unit. Default behavior is assumed when set to off. In case of a single Input Pin, logical channels entering the Unit are passed unaltered for those channels that are also present in the output cluster. Logical channels not available in the output cluster are absorbed by the Processing Unit. Logical channels present in the output cluster but unavailable in the input cluster are muted. In case of multiple Input Pins, corresponding logical input channels are equally mixed together before being passed to the output. If the Enable Processing Control is present in a Processing Unit, bit D0 must be set to one. Otherwise, it is set to zero, indicating that the Processing Unit cannot be bypassed. An index to a string descriptor is provided to further describe the Processing Unit. The previous fields are common to all Processing Units. However, depending on the value in the wProcessType field, a process-specific part is added to the descriptor. The following paragraphs describe these process-specific parts. The following table outlines the common part of the Processing Unit descriptor. Table 4-8 Common Part of the Processing Unit Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 13+p+n+x 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant PROCESSING_UNIT descriptor subtype. 3 bUnitID 1 Number Constant uniquely identifying the Unit within the audio function. This value is used in all requests to address this Unit. 4 wProcessType 2 Constant Constant identifying the type of processing this Unit is performing. 6 bNrInPins 1 Number Number of Input Pins of this Unit p 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/usb_audio/pages/34.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 31 Table 3-1 Status Word Format Offset Field Size Value Description 0 bStatusType 1 Bitmap D7 Interrupt PendingD6 Memory Contents ChangedD5..4 ReservedD3..0 Originator0 = AudioControl interface1 = AudioStreaming interface2 = AudioStreaming endpoint3..15 = Reserved 1 bOriginator 1 Number ID of the Terminal, Unit, interface, orendpoint that reports the interrupt. 3.7.2 AudioStreaming Interface AudioStreaming interfaces are used to interchange digital audio data streams between the Host and the audio function. They are optional. An audio function can have zero or more AudioStreaming interfaces associated with it, each possibly carrying data of a different nature and format. Each AudioStreaming interface can have at most one isochronous data endpoint. This construction guarantees a one-to-one relationship between the AudioStreaming interface and the single audio data stream, related to the endpoint. In some cases, the isochronous data endpoint is accompanied by an associated isochronous synch endpoint for synchronization purposes. The isochronous data endpoint is required to be the first endpoint in the AudioStreaming interface. The synch endpoint always follows its associated data endpoint. An AudioStreaming interface can have alternate settings that can be used to change certain characteristics of the interface and underlying endpoint. A typical use of alternate settings is to provide a way to change the bandwidth requirements an active AudioStreaming interface imposes on the USB. By incorporating a low-bandwidth or even zero-bandwidth alternate setting for each AudioStreaming interface, a device offers to the Host software the option to temporarily relinquish USB bandwidth by switching to this lowbandwidth alternate setting. If such an alternate setting is implemented, it must be the default alternate setting (alternate setting zero). A zero-bandwidth alternate setting can be implemented by specifying zero endpoints in the standard AudioStreaming interface descriptor. All other interface and endpoint descriptors (both standard and class-specific) need not be specified in this case. The AudioStreaming interface is essentially used to provide an access point for the Host software (drivers) to manipulate the behavior of the physical interface it represents. Therefore, even external connections to the audio function (S/PDIF interface, analog input, etc.) can be represented by an AudioStreaming interface so that the Host software can control certain aspects of those connections. This type of AudioStreaming interface has no associated USB endpoints. The related audio data stream is not using USB as a transport medium. In addition, the concepts of dynamic interfaces as described in the Universal Serial Bus Class Specification can be used to notify the Host software that changes have occurred on the external connection. This is analogous to switching alternate settings on an AudioStreaming interface with USB endpoints, except that the switch is now device-initiated instead of Host-initiated. As an example, consider an S/PDIF connection to an audio function. If nothing is connected to this external S/PDIF interface, the AudioStreaming interface is idle and reports itself as being dynamic and non-configured (bInterfaceClass=0x00). If the user connects a standard IEC958 signal to the audio function, the S/PDIF receiver inside the audio function detects this and notifies the Host that the AudioStreaming interface has switched to its IEC958 mode (alternate setting x). If, on the other hand, an USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 32 IEC1937 signal, carrying MPEG-encoded audio is connected, the AudioStreaming interface switches to the appropriate setting (alternate setting y) to handle the MPEG decoding process. For every isochronous OUT or IN endpoint defined in any of the AudioStreaming interfaces, there must be a corresponding Input or Output Terminal defined in the audio function. For the Host to fully understand the nature and behavior of the connection, it must take into account the interface- and endpoint-related descriptors as well as the Terminal-related descriptor. 3.7.2.1 Isochronous Audio Data Stream Endpoint In general, the data streams that are handled by an isochronous audio data endpoint do not necessarily map directly to the logical channels that exist within the audio function. As an example, consider a “stereo” audio data stream that contains audio data, encoded in Dolby Prologic format. Although there is only one data stream, carrying interleaved samples for Left and Right (or more precisely LT and RT), these two channels carry information for four logical channels (Left, Right, Center, and Surround). Other examples include cases in which multiple logical audio channels are compressed into a single data stream. The format of such a data stream can be entirely different from the native format of the logical channels (for example, 256 Kbits/s MPEG1 stereo audio as opposed to 176.4 Kbytes/s 16 bit stereo 44.1 kHz audio). Therefore, to describe the data transfer at the endpoint level correctly, the notion of logical channel is replaced by the notion of audio data stream. It is the responsibility of the AudioStreaming interface which contains the OUT endpoint to convert between the audio data stream and the embedded logical channels before handing the data over to the Input Terminal. In many cases, this conversion process involves some form of decoding. Likewise, the AudioStreaming interface which contains the IN endpoint must convert logical channels from the Output Terminal into an audio data stream, often using some form of encoding. Consequently, requests to control properties that exist within an audio function, such as volume or mute cannot be sent to the endpoint in an AudioStreaming interface. An AudioStreaming interface operates on audio data streams and is unaware of the number of logical channels it eventually serves. Instead, these requests must be directed to the proper audio function’s Units or Terminals via the AudioControl interface. As already mentioned, an AudioStreaming interface can have zero or one isochronous audio data endpoint. If multiple synchronous audio channels must be communicated between Host and audio function, they must be clustered into one audio channel cluster by interleaving the individual audio data, and the result can be directed to the single endpoint. Furthermore, a single synch endpoint, if needed, can service the entire cluster. In this way, a minimum number of endpoints are consumed to transport related data streams. If an audio function needs more than one cluster to operate, each cluster is directed to the endpoint of a separate AudioStreaming interface, belonging to the same Audio Interface Collection (all servicing the same audio function). If there is a need to manipulate a number of AudioStreaming interfaces as a whole, these interfaces can be tied together. The techniques for associating interfaces, described in the Universal Serial Bus Class Specification should be used to create the binding. 3.7.2.2 Isochronous Synch Endpoint For adaptive audio source endpoints and asynchronous audio sink endpoints, an explicit synch mechanism is needed to maintain synchronization during transfers. For details about synchronization, see Section 5, “USB Data Flow Model,” in the USB Specification and the relevant parts of the Universal Serial Bus Class Specification. The information carried over the synch path consists of a 3-byte data packet. These three bytes contain the Ff value in a 10.14 format as described in Section 5.10.4.2, “Feedback” of the USB Specification. Ff represents the average number of samples the endpoint must produce or consume per frame to match the desired sampling frequency Fs exactly. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 33 A new Ff value is available every 2(10 – P) ms (frames) where P can range from 1 to 9, inclusive. The sample clock Fs is always derived from a master clock Fm in the device. P is related to the ratio between those clocks through the following relationship 数式 In worst case conditions, only Fs is available and Fm = Fs, giving P = 1 because one can always use phase information to resolve the estimation of Fs within half a clock cycle. An adaptive audio source IN endpoint is accompanied by an associated isochronous synch OUT endpoint that carries Ff. An asynchronous audio sink OUT endpoint is accompanied by an associated isochronous synch IN endpoint. For adaptive IN endpoints and asynchronous OUT endpoints, the standard endpoint descriptor provides the bSynchAddress field to establish a link to the associated synch endpoint. It contains the address of the synch endpoint. The bSynchAddress field of the synch standard endpoint descriptor must be set to zero. As indicated earlier, a new Ff value is available every 2(10 – P) frames with P ranging from 1 to 9. The bRefresh field of the synch standard endpoint descriptor is used to report the exponent (10-P) to the Host. It can range from 9 down to 1. (512 ms down to 2 ms) 3.7.2.3 Audio Channel Cluster Format An audio channel cluster is a grouping of logical audio channels that share the same characteristics like sampling frequency, bit resolution, etc. Channel numbering in the cluster starts with channel one up to the number of channels in the cluster. The virtual channel zero is used to address a master Control in a Unit, effectively influencing all the channels at once. The maximum number of independent channels in an audio channel cluster is limited to 254. Indeed, Channel zero is used to reference the master channel and code 0xFF (255) is used in requests to indicate that the request parameter block holds values for all available addressed Controls. For further details, refer to Section 5.2.2, “AudioControl Requests” and the sections that follow, describing the second form of requests. In many cases, each channel in the audio cluster is also tied to a certain location in the listening space. A trivial example of this is a cluster that contains Left and Right logical audio channels. To be able to describe more complex cases in a manageable fashion, this specification imposes some limitations and restrictions on the ordering of logical channels in an audio channel cluster. There are twelve predefined spatial locations · Left Front (L) · Right Front (R) · Center Front (C) · Low Frequency Enhancement (LFE) [Super woofer] · Left Surround (LS) · Right Surround (RS) · Left of Center (LC) [in front] · Right of Center (RC) [in front] · Surround (S) [rear] · Side Left (SL) [left wall] · Side Right (SR) [right wall] · Top (T) [overhead] If there are logical channels present in the audio channel cluster that correspond to some of the previously defined spatial positions, then they must appear in the order specified in the above list. For instance, if a USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 34 cluster contains logical channels Left, Right and LFE, then channel 1 is Left, channel 2 is Right, and channel 3 is LFE. To characterize an audio channel cluster, a cluster descriptor is introduced. This descriptor is embedded within one of the following descriptors · Input Terminal descriptor · Mixer Unit descriptor · Processing Unit descriptor · Extension Unit descriptor The cluster descriptor contains the following fields · bNrChannels a number that specifies how many logical audio channels are present in the cluster. · wChannelConfig a bit field that indicates which spatial locations are present in the cluster. The bit allocations are as follows § D0 Left Front (L) § D1 Right Front (R) § D2 Center Front (C) § D3 Low Frequency Enhancement (LFE) § D4 Left Surround (LS) § D5 Right Surround (RS) § D6 Left of Center (LC) § D7 Right of Center (RC) § D8 Surround (S) § D9 Side Left (SL) § D10 Side Right (SR) § D11 Top (T) § D15..12 Reserved · Each bit set in this bit map indicates there is a logical channel in the cluster that carries audio information, destined for the indicated spatial location. The channel ordering in the cluster must correspond to the ordering, imposed by the above list of predefined spatial locations. If there are more channels in the cluster than there are bits set in the wChannelConfig field, (i.e. bNrChannels [Number_Of_Bits_Set]), then the first [Number_Of_Bits_Set] channels take the spatial positions, indicated in wChannelConfig. The remaining channels have ‘non-predefined’ spatial positions (positions that do not appear in the predefined list). If none of the bits in wChannelConfig are set, then all channels have non-predefined spatial positions. If one or more channels have non-predefined spatial positions, their spatial location description can optionally be derived from the iChannelNames field. · iChannelNames index to a string descriptor that describes the spatial location of the first nonpredefined logical channel in the cluster. The spatial locations of all remaining logical channels must be described by string descriptors with indices that immediately follow the index of the descriptor of the first non-predefined channel. Therefore, iChannelNames inherently describes an array of string descriptor indices, ranging from iChannelNames to (iChannelNames + (bNrChannels- [Number_Of_Bits_Set]) - 1) Example 1 An audio channel cluster that carries Dolby Prologic logical channels has the following cluster descriptor Table 3-2 Dolby Prologic Cluster Descriptor Offset Field Size Value Description USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 35 Offset Field Size Value Description 0 bNrChannels 1 4 There are 4 logical channels in the cluster. 1 wChannelConfig 2 0x0107 Left, Right, Center and Surround are present. 3 iChannelNames 1 Index Because there are no non-predefined logical channels, this index must be set to 0. Example 2 A hypothetical audio channel cluster inside an audio function could carry Left, Left Surround, Left of Center, and two auxiliary channels that contain each a different weighted mix of the Left, Left Surround and Left of Center channels. The corresponding cluster descriptor would be Table 3-3 Left Group Cluster Descriptor Offset Field Size Value Description 0 bNrChannels 1 5 There are 5 logical channels in the cluster 1 wChannelConfig 2 0x0051 Left, Left Surround, Left of Center and two undefined channels are present. (bNrChannels [Number_Of_Bits_Set]) 3 iChannelNames 1 Index Optional index of the first non-predefined string descriptor Optional string descriptors String (Index) = ‘Left Down Mix 1’ String (Index+1) = ‘Left Down Mix 2’ 3.7.2.4 Audio Data Format The format used to transport audio data over the USB is entirely determined by the code, located in the wFormatTag field of the class-specific interface descriptor. Therefore, each defined Format Tag must document in detail the audio data format it uses. Consequently, format-specific descriptors are needed to fully describe the format. For details about the predefined Format Tags and associated data formats and descriptors, see the separate document, USB Audio Data Formats, that is considered part of this specification. Vendor-specific protocols must be fully documented by the manufacturer. 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/ktonegaw/pages/28.html
PCクラスタコンソーシアム http //www.pccluster.org/index.html.ja クラスタ・システム構築 http //www.senryu.biz/linux/cluster/cluster1.htm 並列プログラミング例 http //www.senryu.biz/linux/cluster/cluster2.htm PCクラスタ超入門 http //mikilab.doshisha.ac.jp/dia/smpp/cluster2000/index.html 「Linux で PCクラスタを組む」記 http //atlas.riken.go.jp/~shinkai/cactus/LinuxPCcluster.html PCクラスタを利用した解析例 http //www.terrabyte.co.jp/TI_Cluster/Cluster.htm 超並列計算研究会 http //www.is.doshisha.ac.jp/SMPP/ 普通のパソコンをスパコン並みに――ある高校生たちの挑戦 http //www.itmedia.co.jp/enterprise/articles/0411/08/news016.html PCクラスタを用いた並列プログラミング講義実施報告 http //www.hucc.hokudai.ac.jp/center_news/pdf/center_news35_1_3.pdf PCクラスタ/グリッドシステムの使い方 http //staff.media.hiroshima-u.ac.jp/hpc/HPC_wiki/wiki.cgi?PC%A5%AF%A5%E9%A5%B9%A5%BF%2F%A5%B0%A5%EA%A5%C3%A5%C9%A5%B7%A5%B9%A5%C6%A5%E0%A4%CE%BB%C8%A4%A4%CA%FD
https://w.atwiki.jp/diablo3_2ch/pages/84.html
効果 Unlocked at level 26 Reduces the Hatred cost of your Grenades and Cluster Arrow abilities by 15. Upon death, you drop a giant grenade that explodes for 213 - 320 fire damage.GrenadesとCluster Arrowのコストを15低減する。死んだ時に巨大なグレネードを落とし、爆発して213 - 320の火ダメージを与える。 評価 使い方 その他 コメント 名前 コメント Demon Hunter Skills Active Skills Offensive Hungering Arrow、Entangling Shot、Evasive Fire、Fan of Knives、Bola Shot、Grenades、Chakram、Impale、Spike Trap、Elemental Arrow、Multishot、Cluster Arrow、Rapid Fire、Strafe、Rain of Vengeance Descipline Caltrops、Vault、Marked for Death、Smoke Screen、Companion、Shadow Power、Sentry Utility Preparation Passive Skills Brooding、Thrill of the Hunt、Vengeance、Steady Aim、Cull the Weak、Fundamentals、Hot Pursuit、Archery、Perfectionist、Custom Engineering、Grenadier、Sharpshooter、Ballistics