約 5,307,461 件
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/nwnnwn/pages/9.html
OnConversationに入るスクリプト。 メッセージを聞いた時に発動する。 NWNデフォルト（翻訳付き） NWNデフォルト（翻訳付き） #include "nw_i0_generic" void main() { // 石になってる時は飛ばす if (GetHasEffect(EFFECT_TYPE_PETRIFY, OBJECT_SELF) == TRUE) { return; } // 死んでる時も飛ばす if (GetIsDead(OBJECT_SELF) == TRUE) { return; } // 特定のパターンを数値に変換して習得する // 話者を習得する int nMatch = GetListenPatternNumber(); object oShouter = GetLastSpeaker(); if (nMatch == -1) { // どのパターンの会話でも無い場合は普通にカンバセーションを始める if (GetCommandable(OBJECT_SELF)) { ClearActions(CLEAR_NW_C2_DEFAULT4_29); BeginConversation(); } else //チャーム状態ならカンバセーションを開始する if (GetHasEffect(EFFECT_TYPE_CHARMED) == TRUE) { ClearActions(CLEAR_NW_C2_DEFAULT4_29); BeginConversation(); } } // PC以外の仲間からの呼びかけに答える else if (GetIsObjectValid(oShouter) !GetIsPC(oShouter) GetIsFriend(oShouter)) { object oIntruder = OBJECT_INVALID; // もしあるなら侵入者を決定してください if(nMatch == 4) { //叫んだ仲間が持っている"NW_BLOCKER_INTRUDER"関数をoIntruderとして習得 oIntruder = GetLocalObject(oShouter, "NW_BLOCKER_INTRUDER"); } else if (nMatch == 5) { //叫んだ仲間に最後に敵対行動をした相手をoIntruderとして習得 oIntruder = GetLastHostileActor(oShouter); if(!GetIsObjectValid(oIntruder)) { //見つからなかったら、自分が攻撃していた相手を習得します oIntruder = GetAttemptedAttackTarget(); if(!GetIsObjectValid(oIntruder)) { //それも駄目なら、呪文を唱えようとした相手を習得します oIntruder = GetAttemptedSpellTarget(); if(!GetIsObjectValid(oIntruder)) { oIntruder = OBJECT_INVALID; } } } } // oIntruderに警戒するように返事をします。 // 最初の敵を見失った仲間に戻って来いと言う。 RespondToShout(oShouter, nMatch, oIntruder); } // Send the user-defined event if appropriate if(GetSpawnInCondition(NW_FLAG_ON_DIALOGUE_EVENT)) { SignalEvent(OBJECT_SELF, EventUserDefined(EVENT_DIALOGUE)); } }
https://w.atwiki.jp/taimemachine2200/pages/11.html
article2 Why we need cryonics？ (Title) (Article) ●●● (未完成) (Title) クライオニクスは詐欺か？ Is Cryonics a Scam? (Article) 人々は、クライオニクスを、詐欺だと主張します。 People claim cryonics as a scam. 私はこれはとても奇妙な事実だと思います。 I feel this fact very strange. 例えば、私は将来、クライオニクスを希望します。 For example, I hope for cryonics in the future. 私が生きている間に、私の体をロボットにすることはできません。 I can t make my body a robot while I m alive. 私は現実的に、問題を解決したい。 I want to solve the problem, realistically. 私は自ら望んでクライオニクスをします。 I do cryonics myself. つまり、詐欺は成立しません。 In other words, fraud does not hold. むしろ、クライオニクスを疑う人は、クライオニクスを使用するべきでない。 Rather, those who suspect cryonics should not use them. クライオニクスは未完成だ。 Cryonics is incomplete. 私は、そのリスクを理解したが、利用したい。 I understand the risk, but I want to use it. しかし、明日死ぬ人はどうすればいい？助かる手段は他にありません。 やりたい人だけが、やればいい。もし、あなたが詐欺だと思うのならクライオニクスをしてはいけない。 疑問に思うのなら、クライオニクスをしてはいけない。 だから、詐欺は成立しない。 可能性を残すことは間違いでしょうか？ 人の意思はは自由。これを妨害している。 それは、自由意思の侵害です。 私がもし明日死ぬなら、今の未完成な技術でクライオニクスをすることは最善だと思っいます ●●● (完成・未提出） (Title) 私たちは歴史上、とても珍しい時代に生きています。 We live in a very rare time in history. 私たちは未来に私たちの命を繋ぐことができるのか？ Can we connect our lifes in the future? 私は、ある男の人の可能性を、その男性の子孫とご先祖様の番号を使ってここに表します。 I represent a man s potential here using his offspring and ancestor numbers. 私が使うナンバーはおおよその数字です。 The numbers I use are about numbers. (Article) 私は彼の1000人の祖先と子孫の存在を使って、彼が持っている可能性を表現します。 I use the presence of his 1000 ancestors and descendants to express the possibilities he has. 彼は、人類が誕生して以来898人目の子孫です。 He is the 898th person since the birth of mankind. 彼は898番目だ。 He is the 898th. 彼の息子は899番目です。 His son is 899th. 彼の父は897番目です。 His father is 897th. つまり、 898th→He 899th→His son 897th→His father 私は彼の子孫、ナンバー1000は宇宙を脱出していると予想します。 I expect his descendants, number 1000th, have escaped the universe. 彼の2500年後に生まれる子孫は、もう地球には住んでいません。 His offspring, born 2500 years later, no longer live on earth. 彼には897人の先祖がいます。 He has 897 ancestors. もちろん、彼には父、祖父、100年前、1000年前の沢山の先祖がいます。 Of course he has a father, a grandfather, and hundreds of years ago, many ancestors a thousand years ago. 彼のご先祖様、ナンバーワンは、原始人です。 His first ancestor, number one, is a primitive man. さらに遡ると、細胞や微生物も私たちの先祖です。 Going back, cells and microorganisms are also our ancestors. 私たちがこの時代に生きていることは奇跡です。 It is a miracle that we live in this age. もし、彼の孫が2050年以降に生まれるならば、孫は将来、不老不死かもしれません。 If his grandchild is born after 2050, the grandchild may be immortal in the future. 彼の孫が老人になる頃には、人類の医療は完成しているでしょう。 When his grandson becomes an old man, the medical care of mankind will be complete. その頃、人類は簡単に体を作ることができる。 At that time, human beings can easily make bodies. 彼の907番目の孫は絶対に不老不死です。それは、2300年頃です。 His 907th grandchild is absolutely immortal. It s about 2300 years. 少し先の未来では、不老不死は常識になっています。 In the future, immortality is common sense. 彼の920番目の子孫は宇宙に住んでいます。 His 920th descendant lives in space. 未来の人類は食事や酸素を必要しないだろう。 Future humans will not need food or oxygen. 私たちの先祖の体は機械になっています。 The body of our ancestors is a machine. 逆に、彼の祖父、すなわち896番目は必ず死にます。 Conversely, his grandfather 896th will die. 現実に、彼の祖父が200歳まで生き続けることは不可能です。 In reality, it is impossible for his grandfather to stay alive until the age of 200. 現在の医療技術は祖父の寿命には間に合いません。 Current medical technology is not enough for my grandfather s life. 今の技術では、彼の体をロボットや電気信号の体にすることもできません。 Right now, the only technology that connects my grandfather s life to the future is cryonics. 私たちには時間が足りません。 We do not have enough time. 夢と現実は異なります。 Dreams and reality are different. これは実現できない夢です。 This is an unrealizable dream. では、私たちが死を回避するために、私たちは現実に何をすることができるでしょうか？ So what can we actually do to avoid death? 今、私の祖父の命を未来へ繋ぐテクノロジーはクライオニクスしかありません。 Right now, the only technology that connects my grandfather s life to the future is cryonics. 例えば、1400年に生まれた農民は確実に死にました。 For example, a farmer born in 1400 has certainly died. 彼の時代にはレントゲンはありませんでした。 There were no radiographs in his time. 1800年に生まれた騎士も不老不死にはなりませんでした。 Knights born in 1800 did not become immortal. 彼の時代に内視鏡はありませんでした。 There were no endoscopes in his time. その時代には技術が存在しなかった。 There was no technology at that time. 彼らが生きることは不可能でした。 They could not live. では、2200年に生まれた人々はどうでしょうか？ So what about people born in 2200? 私たちの番号は、898番～900番です。 Our numbers are 898-900. 私たちは人類の歴史上、珍しい位置にいます。 We are in an unusual position in human history. 私たちの運命は不死身なのか死ぬか、どちらかがまだ決まっていません。 Whether our destiny is immortal or dying has yet to be determined. これは人類の歴史上、極めて珍しいことなのです。 This is extremely rare in human history. それは、とても珍しいのです。 It is very rare. 私はそれを番号で表現します。 I express it using numbers. No, 886→人類は100％死にます。 (人類誕生～2050年) No, 1～886→Humanity dies 100% (Mankind is born on earth～2050year) No, 897?900→私たちはどちらか分からない。これはとても珍しい時間です。 (2051年～2120年) No, 897～900→？？？ We don t know either．This is a very rare time. (2051year～2120year) No, 901～→確実に不老不死 (2151year～宇宙の寿命が終わる時) No, 901～ Humanity grants immortality (2151year～At the end of the life of the universe) もし私たちが50年後に生まれていれば、私たちは100％不老不死でした。私たちは死について完全に悩むことはなかった。 If we were born late 50 years, we were 100% immortal. We were not completely worried about death. 私は2051year～2120yearを、人類の歴史上、最も奇妙な時間と呼んでいます。 I call 2051year-2120year the strangest time in human history. しかし、私たちはあと少しでそこに到達します。 But we will get there shortly. 歴史上、私たちは非常に珍しい瞬間に生まれました。医療の発展は、私たちの寿命に間に合わないかもしれない。しかし、間に合う可能性もある。 In history we were born at a very unusual moment. Medical development may not be in time for our lifespan. But we may be in time. 私は悔しい。私たちの生存率は不明です。 I am very frustrated.Our survival rate is unknown. 私たちの多くの先祖は死にました。彼らが死ぬまでに、不老不死の技術が完成しなかった。 Many of our ancestors have died.By the time they died, the technology of immortality had not been completed. 私たちは、生まれた時代によって、生きることを諦めるか、挑戦するかのどちらかを決断しなければいけない。 We have to decide whether to give up or to challenge, depending on the age at which we were born. しかし、私たちは間に合うかもしれない。私たちは、なぜこの不思議な時間に生まれたのかは分からないが、自分の可能性を信じるべきだ。私たちはベストを尽くす。 But we may be in time. We don t know why we were born at this mysterious time, but we should believe in our potential. We do our best. しかし、私たちは現実を見なければいけません。 But we must see the reality. だから、クライオニクスには意義がある。私たちが挑戦することには意義がある。 Therefore, cryonics is significant.It is significant that we take on the challenge. 人事を尽くして天命を待つ。 Do the best you can and leave the rest to God. 私たちにできる現実の最高の手段はクライオニクスだ。 The best real thing we can do is cryonics. 私たちがベストを尽くせば奇跡は起きる。 Miracles happen if we do our best. 私たちはクライオニクスだけでなく、すべてのことの可能性を維持することは重要です。仕事、人生、夢、維持した可能性の全てが未来へ繋がります。 It is important that we maintain the potential of everything, not just cryonics. Your work, your life, your dreams, and the possibilities you have maintained will all lead to the future. 私たちは可能性が最も高くなるように行動するべきだ。 We should act to be most likely. 私たちは夢を忘れてはいけない。 We must not forget our dreams. ●●● (未完成) (Title) 犯罪者に殺された犠牲者をクライオニクスで救う Save victims killed by criminals with cryonics (Article) 私たちのクライオニクスは、将来、殺された被害者を救います。 Our cryonics will save the killed victims in the future. 私たちの目的は、被害者を蘇生するためと、公正な裁判をするためです。私たちは彼の脳を冷凍保存します。 Our purpose is to revive the victims and to make a fair trial.We cryopreserve his brain. 私たちは100年後、犠牲者の脳を未来の技術でスキャンし、モニターに事件を映像化で表示します。 100 years later, we scan the victim s brain with future technology and visualize the incident on a monitor. この映像は、犯罪者と犯罪の真実を証明します。 公正な裁判をするためです。 This video proves the truth of the criminal and the crime. To make a fair trial. 彼の脳は犯罪の事実と犯人の顔を記憶しています。 His brain remembers the facts of the crime and the culprit s face. 被害者の脳は犯罪者を思い出した。 The victim s brain remembered the criminal. 脳をクライオニクスして、真実を明らかにする可能性と犠牲者が生き返る可能性を維持します。 Cryonics the brain to maintain the possibility of revealing the truth and the possibility of the victim being revived. もし彼の遺体を処分してしまえば、全ての可能性が消えてしまいます。 If you dispose of his body, all possibilities will disappear. 国家は犠牲者を救う。国民の命を尊重する。こんな社会は素晴らしい。 The nation saves the victim. Respect the lives of the people. Such a society is wonderful ●●● (提出済み） (Title) 私の思い クリオルスファンより My thoughts. by Japanese KrioRus Fan (Article) 私は日本人です。私は10年前、インターネットでKrioRusを偶然知り、クライオニクスが好きになりました。 I am Japanese. I happened to know KrioRus on the Internet 10 years ago and came to like cryonics. KrioRusの仕事は、人々に夢と生きるための希望を与えます。 The work of KrioRus gives people dreams and hope to live. 日本の癌の患者様は毎日痛みに苦しんでいます。彼らの体は一年後、二年後、さらに悪化します。彼らは未来に希望を持つことができません。 Japanese cancer patients suffer from pain every day. Their bodies get worse after a year or two. They cannot have hope for the future. クライオニクスは、難病の患者様が明日を生きる理由となることができます。クライオニクスは飾り物ではなく本物です。 Cryonics can be the reason why patients with intractable diseases live tomorrow. Cryonics is real, not decorative. 人間は、未来に夢や希望があると、今、この瞬間が輝きだします。どんなに小さくても！ This moment is shining when humans have dreams and possibilities in the future.No matter how small! ところで、全てのクライオニクスの責任はKrioRusですか？ By the way, is KrioRus responsible for all cryonics? 私はそれは間違っている考え方だと思います。 I think it is the wrong way of thinking. KrioRusは、私たちの代理で仕事をしてくれています。 KrioRus works on our behalf. 私たちはこれを忘れてはいけません。 We must not forget this. 私たちには技術がなく、クライオニクスをすることができません。 We have no technology and cannot do cryonics. クライオニクスは大衆の人々に恐れられます。しかし、KrioRusは私たちの夢を叶えてくれました。彼らには勇気がある。彼らには太陽よりも暑い情熱がある。 Cryonics is feared by the masses. But KrioRus has fulfilled our dream. They have courage. They have a passion that is hotter than the sun. また、私たちはクライオニクスを進化させることができません。KrioRusだけでも進化することはできません。クライオニクスを完成させるためにはみんなの愛とパワーが必要です。 Also, we cannot evolve cryonics. KrioRus alone cannot evolve. Everyone needs love and power to complete cryonics. もしKrioRusが消えたら、私たちは困ります。私たちはクライオニクスができない。 If KrioRus disappears, we are in trouble. We cannot do cryonics. だから、私はクリオルスを応援します。私はクリオルスの発展を望みます。 That s why I support KrioRus. I hope the development of KrioRus. The only thing that connects my life is cryonics. KrioRus supports cryonics. So KrioRus is a benefactor for us. 私はKrioRusにクライオニクスを使い保存されている患者様に未来で会いたい。同じ夢を持つ人は全て家族です。 I would like to see KrioRus in the future with patients stored using cryonics.Everyone who has the same dream is a family. クライオニクスが成功できるか、失敗するか、それは私たちみんなの責任でもあります。 Whether cryonics can succeed or fail is the responsibility of all of us. 私たちは傍観者ではいけません。 We must not be bystanders. 残念ながら、ほとんどの人が協力してくれません。人々は見ているだけで、動きません。 Unfortunately, most people don t cooperate. People are just watching, not moving. これは私たちみんなの挑戦でもあり、責任でもあります。 This is both our challenge and our responsibility. みんなでクリオルスを支えましょう。みんなのパワーでクライオニクスを発展させ、歴史を変えましょう。 Let s support KrioRus together. Let s develop cryonics and change history with the power of everyone. 私たちは国境と時代を超えて助け合いましょう。 Let us help each other across borders and times. みんなで、クリオルスの魅力を世界中に伝えませんか？ Let s all share the significance of KrioRus around the world. 私たちに何ができますか？ What can we do? もし、音楽が得意な人はKrioRusの音楽を作ればいい。小説が好きな人はKrioRusの小説を書けばいい。 If you are good at music, just make KrioRus music. If you like novels, write a KrioRus novel. あなたが得意なこと、好きなことであなたなりに、クライオニクスの発展に試みませんか？ Would you like to develop cryonics for yourself with what you are good at or what you like. みんなでKrioRusに貢献しましょう。 Let s all contribute to KrioRus. 私は思います。あなたにしかできないことがきっとある。あなたがすべきことがきっとある。 I think so. There is surely something you can do. There is definitely something you need to do. 小さな力が集まればとても巨大になります。歴史は動きます。 If a small power gathers, it will be very huge. History moves. 一人は万人のために、万人は一人のために。 One for all, one for one. 命と情熱の火を消してはいけない。 Do not extinguish the fire of life and passion. クライオニクスは100年先も200年先も私たちの先祖に継承されます。 Cryonics will be inherited to our ancestors for 100 years and 200 years. 私たちの先祖は愛の力によって、200年後に私たちを生き返らします。 Our ancestors will resurrect us 200 years later by the power of love. クライオニクスは壮大なプロジェクトです。 Cryonics is a grand project.
https://w.atwiki.jp/elvis/pages/1889.html
Salad William Sonoma Collection (Williams-Sonoma Collection (New York, N.Y.).) Free Pr?Georgeanne BrennanChuck Williams?Noel Barnhurst? Little Herb Gardens Simple Secrets for Glorious Gardens--Indoors and Out Chronicle BooksGeorgeanne BrennanMimi LuebbermannFaith Echtermeyer Cocktail Parties (Williams-Sonoma Entertaining) Free Pr?Steve Siegelman?Georgeanne BrennanBen Masters?Chuck Williams?David Matheson? Williams-Sonoma Christmas Entertaining (Williams-Sonoma Entertaining) Free Pr?Georgeanne BrennanChuck Williams?Quentin Bacon? Food Made Fast Soups (Food Made Fast) Oxmoor House?Georgeanne BrennanChuck Williams?Bill Bettencourt? The Mediterranean Herb Cookbook Fresh and Savory Recipes from the Mediterranean Garden Chronicle BooksGeorgeanne BrennanGrey Crawford? Green Eggs and Ham Cookbook Random House Childrens Books?Georgeanne BrennanFrankie Frankeny Aperitif Kaleidoskop Verlag?Georgeanne Brennan Mein Provence-Kochbuch. Die schoensten Erinnerungen an Suedfrankreich. Mit 125 Rezepten Kaleidoskop Verlag?Georgeanne Brennan Williams-Sonoma Entradas La Nueva Cocina Saludable (Colección Williams-Sonoma) Degustis?Georgeanne BrennanDanny Goldberg?Chuck Williams?Ben Dearnly? Williams-Sonoma Platos Principales La Nueva Cocina Saludable (Colección Williams-Sonoma) Degustis?Georgeanne BrennanChuck Williams?Dan Goldberg?Ben Dearnly? Ensaladas (Coleccion Williams-Sonoma) Degustis?Georgeanne BrennanChuck Williams? Little Herb Gardens Boxtree?Georgeanne BrennanMimi Luebbermann Fragrant Flowers Boxtree?Georgeanne Brennan Beautiful Bulbs (Garden Style) Boxtree?Georgeanne BrennanMimi Luebbermann Savoring France Recipes and Reflections on French Cooking (Savoring ...) Leisure Arts?Georgeanne Brennan Starters (New Healthy Kitchen) Bonnier Books Ltd?Georgeanne Brennan Main Dishes (New Healthy Kitchen) Bonnier Books Ltd?Georgeanne Brennan Les Immortelles Everlasting Blooms-The Beauty of Dried Flowers Todtri Book Pub?Georgeanne BrennanKathryn Kleinman Casual Outdoor Dining (Williams-Sonoma Lifestyles) Leisure Arts?Georgeanne Brennan Savoring Meat Poultry Oxmoor House?Georgeanne BrennanKerri Conan?Lori De Mori?Abigail Johnson Dodge?Chuck Williams? Savoring Pasta Rice Best Recipes from the Award-Winning International Cookbooks (Savoring ...) Oxmoor House?Georgeanne BrennanKerri Conan?Lori De Mori?Chuck Williams? Flowerkeeping Ten Speed Pr?Georgeanne BrennanKathryn Kleinman Holiday Eggs Ten Speed Pr?Georgeanne Brennan Salad Apple Press?Georgeanne Brennan Holiday Eggs (Holiday Series) Smithmark Pub?Georgeanne BrennanRichard Jung? The Children's Kitchen Garden A Book of Gardening, Cooking, and Learning Ten Speed Pr?Georgeanne BrennanEthel Breanan?Marcel Barchechat?Ann Arnold? Savoring Soups Salads Best Recipes from the Award-Winning International Cookbooks (Savoring ...) Oxmoor House?Georgeanne BrennanKerri Conan?Lori De Mori?Abigail Johnson Dodge?Chuck Williams? Savoring Appetizers Best Recipes from the Award-Winning International Cookbooks (Savoring ...) Oxmoor House?Georgeanne BrennanKerri Conan?Lori De Mori?Johnson Abigail Dodge?Williams Sonoma? Savoring France Recipes and Reflections on French Cooking (The Savoring Series) Time Life Education?Georgeanne BrennanChuck Williams? The New American Vegetable Cookbook The Definitive Guide to America's Exotic and Traditional Vegetables Simon & Schuster (Paper)?Georgeanne BrennanIsaac Cronin?Charlotte Glenn? Cooking from the Farmers Market (Williams-Sonoma Lifestyles , Vol 10, No 20) Time Life Education?Georgeanne BrennanChuck Williams?Richard Eskite? Potager Fresh Garden Cooking in the French Style Chronicle BooksGeorgeanne BrennanJohn Vaughan? Geniesser unterwegs. Frankreich. Rezepte und kulinarische Notizen Christian Verlag GmbH?Georgeanne Brennan Holiday Pumpkins (Holiday) Smithmark Pub?Georgeanne Brennan Holiday Fruit A Collection of Inspired Recipes, Gifts, and Decorations (Holiday Series) Smithmark Pub?Georgeanne BrennanRichard Jung? Holiday Sweets A Collection of Inspired Recipes, Gifts, and Decorations (Holiday Series) Smithmark Pub?Georgeanne BrennanRichard Jung? Casual Outdoor Dining (Williams-Sonoma Lifestyles , Vol 9, No 20) Time Life Education?Georgeanne BrennanGeorganne Brennan?Chuck Williams?Richard Eskite? Potager Fresh Garden Cooking in the French Style Chronicle BooksGeorgeanne BrennanJohn Vaughan? Fragrant Flowers Simple Secrets for Glorious Gardens-Indoors and Out (A Garden Style Book) Chronicle BooksGeorgeanne BrennanFaith Echtermeyer Little Herb Gardens Simple Secrets for Glorious Gardens--Indoors and Out (A Garden Style Book) Chronicle BooksGeorgeanne BrennanMimi Luebbermann Beautiful Bulbs Simple Secrets for Glorious Gardens-Indoors and Out (A Garden Style Book) Chronicle BooksGeorgeanne BrennanMimi LuebbermannFaith Echtermeyer The Glass Pantry Preserving Seasonal Flavors Chronicle BooksGeorgeanne BrennanKathryn Kleinman The Glass Pantry The Pleasures of Simple Preserves Chronicle BooksGeorgeanne BrennanKathryn Kleinman Aperitif Recipes for Simple Pleasures in the French Style Chronicle BooksGeorgeanne BrennanKathryn Kleinman France The Vegetarian Table (Vegetarian Table) Chronicle BooksGeorgeanne Brennan Down to Earth Great Recipes for Root Vegetables Chronicle BooksGeorgeanne Brennan Les Immortelles Everlasting Blooms - The Beauty of Dried Flowers Chronicle BooksGeorgeanne BrennanKathryn Kleinman Easy Roses Simple Secrets for Glorious Gardens, Indoors and Out (The Garden Style Book) Chronicle BooksGeorgeanne BrennanFaith Echtermeyer Backyard Bouquets Growing Great Flowers for Simple Arrangements Chronicle BooksGeorgeanne BrennanKleinman? The Food and Flavours of Haute Provence Chronicle BooksGeorgeanne BrennanJeffrey Fisher Garden Dreams A Scrapbook for Gardeners Chronicle BooksGeorgeanne BrennanLeigh Wells? Goat Cheese {Delectable Recipes for All Occasions} (Artful Kitchen) Chronicle BooksEthel Brennan?Georgeanne BrennanPhilippe Weisbecker? Potager Fresh Garden Cooking in the French Style Chronicle BooksAlice WatersGeorgeanne BrennanJohn Vaughan? In the French Kitchen Garden The Joys of Cultivating a Potager Chronicle BooksGeorgeanne BrennanMelissa Sweet? The Family Table A Journal for Recipes and Memories Chronicle BooksGeorgeanne Brennan France The Vegetarian Table (The Vegetarian Table Series) Chronicle BooksGeorgeanne BrennanJohn Vaughan? Olives, Anchovies and Capers The Secret Ingredients of Mediterranean Table Chronicle BooksGeorgeanne BrennanLeigh Beisch Aperitif Recipes for Simple Pleasures in the French Style Chronicle BooksGeorgeanne BrennanKathryn Kleinman Beautiful Bulbs Simple Secrets For Glorious Gardens Indoors And Out Chronicle BooksMimi LuebbermannGeorgeanne BrennanFaith Echtermeyer The Art of the Bar Cocktails Inspired by the Classics Chronicle BooksGeorgeanne BrennanJeff Hollinger?Rob Schwartz?Frankie Frankeny A Pig in Provence Good Food and Simple Pleasures in the South of France Chronicle BooksGeorgeanne Brennan Little Herb Gardens Deck 50 Simple Secrets for Glorious Gardens Indoors And Out Chronicle BooksGeorgeanne BrennanMimi Luebbermann Great Greens Fresh, Flavorful, and Innovative Recipes Chronicle BooksTodd Koons?Georgeanne BrennanFrankie Frankeny The New American Vegetable Cookbook The Definitive Guide to America's Exotic Traditional Vegetables Addison-Wesley?Georgeanne Brennan Peppers Hot and Chili Addison-Wesley?Georgeanne BrennanCharlotte Glenn? Village Walks Provence and Cote D'azur. 50 Adventures on Foot (Village Walks) Chronicle BooksGeorgeanne Brennan Holiday Sweets Chronicle BooksChroniclestaff?Georgeanne Brennan Holiday Pumpkins A Collection of Recipes, Gifts, and Decorations Ten Speed Pr?Georgeanne BrennanJennifer Barry?Penina? Beautiful Bulbs Chronicle BooksGeorgeanne BrennanMimi LuebbermannFaith Echtermeyer Cooking from the Farmers Market (Williams-Sonoma Lifestyles) Leisure Arts?Georgeanne Brennan Die neue Einmachkunst. Rezepte nicht nur fuer den Hausgebrauch Carlsen Verlag GmbH?Georgeanne BrennanKathryn Kleinman The New American Vegetable Cookbook The Definitive Guide to America's Exotic and Traditional Vegetables Addison-Wesley Pub (T)?Georgeanne BrennanIsaac Cronin?Charlotte Glenn? Mein kulinarisches Tagebuch aus der Haute Provence. Mit 125 Rezepten Christian Verlag GmbH?Georgeanne BrennanJeffrey. Fisher? Unvergaengliche Bluetentraeume. Die Schoenheit getrockneter Pflanzen Ars Edition GmbH?Georgeanne BrennanKathryn KleinmanMichaele Thunen?Jacqueline Jones? Savouring France Time Life UK?Georgeanne Brennan Potager Ebury Press?Geraldine Holt?Georgeanne Brennan Aus dem Kuechengarten der Provence. Rezepte der vier Jahreszeiten Hugendubel Heinrich GmbH?Georgeanne Brennan Einladung zum Aperitif. Mit 50 Rezepten fuer Drinks und kleine Leckerbissen Christian Verlag GmbH?Georgeanne BrennanKathryn Kleinman
https://w.atwiki.jp/wicjp/pages/13.html
myErrors.HeaderFailed to start World in Conflict myErrors.InitCheckFailedCRITICAL ERROR DirectX9.0b or higher must be installed to run World in Conflict. myErrors.UnsupportedWinVersionERROR This version of Windows is not supported by World in Conflict. myErrors.MoreRamRequiredERROR Minimum 128Mb RAM memory is required to play World in Conflict. myErrors.MoreRamDesiredWarning Minimum 128Mb RAM memory is required to play World in Conflict. myErrors.TooMuchMemoryOnWin95Warning Windows 98 and Windows ME does not properly support 1Gb (or more) of memory. The system can be very unstable. myErrors.NotEnoughMemoryERROR There is not enough free RAM memory to run World in Conflict. Please close all other applications or restart Windows. myErrors.LowOnMemoryWarning Low on memory. Game performance may suffer. myErrors.DX9BRequiredERROR DirectX9.0b or higher is required to run World in Conflict. myErrors.DebugDXUsedWarning A debug version of DirectX is currently in use. Game performance may suffer. myErrors.MustUpdateDriverERROR You must update your graphics card drivers to run World in Conflict. myErrors.ShouldUpdateDriverWarning It is highly recommended that you update your graphics card driver to play World in Conflict. myErrors.No3DCardThatCanRunWicERROR No appropriate 3D graphics card detected. Unable to run World in Conflict. myErrors.AGPDisabledWarning AGP acceleration is not enabled. It is highly recommended that you update your motherboard drivers or game performance may suffer. myErrors.NotEnoughGFXMemoryERROR Your graphics card does not have enough memory to run World in Conflict. Minimum 32Mb is required. myErrors.CPUTooSlowWarning A slow CPU is detected. Game performance may suffer. myErrors.FailedToAccessProfilesERROR An error occurred while accessing the profiles directory. No write access. myErrors.WicAlreadyRunningWorld in Conflict is already running. myErrors.WicAlreadyRunningExclusiveWorld in Conflict is already running on this computer. myErrors.RemoteSessionNotSupportedWorld in Conflict can not be played using Remote Desktop Connection. myErrors.FailedGeneralInitGeneral initialization error. myErrors.FailedInitDebugFailed to initialize debug system. myErrors.FailedLoadDirectoryFailed to load directory file. myErrors.CDKeyNotFoundCD Key not found. myErrors.CDKeyInvalidInvalid CD Key. myErrors.FailedInitInputFailed to initialize input system. myErrors.FailedLoadProfilesFailed to load user profile. myErrors.FailedLoadMPMissionsFailed to load multiplayer missions. myErrors.FailedInitMassGateFailed to initialize Massgate(TM). myErrors.FailedLoadInitGuiFailed to load or initialize GUI. myErrors.FailedStartStateFailed to initialize game state. myErrors.DX9NotInstalledDirectX9.0b not installed. myErrors.DX9NotWorkingDirectX9.0b does not work properly. Please try reinstalling DirectX. myErrors.NoWorking3dCardThe detected graphics card is not working with World in Conflict. myErrors.DX9FailedInitFailed to initialize DirectX9.0b. myErrors.NotEnoughGfxMemoryThe detected graphics card does not have enough memory (mimimum 32Mb required). myErrors.Unknown3dEngineErrorUnspecified error when trying to initialize the 3D engine. myErrors.FailedToStartGameFailed to start game. myErrors.ErrorHeaderSerious problems found when starting World in Conflict myErrors.ErrorBodyIt is highly recommended that you try to fix these problems before running the game.\nPress OK to quit or press Cancel to try to start the game anyway. myErrors.WarningHeaderPotential problems found when starting World in Conflict myErrors.WarningBody empty myErrors.WrongDesktopBppERROR World in Conflict must be run on a desktop with 32bit color quality. Please adjust your Windows display properties and restart the game.
https://w.atwiki.jp/meet-artproject/pages/24.html
Meet! 2014 Made out of thin air The recipe of becoming / the reception of becoming See almost a nothing unfounded, untenable up in the air / don t hold back, the Emergence / envision it, grasp it. Maybe it is a process, beginning in a next-to-nothingness or ending there | delicate | fragile | invisible | light | or diff erent; soft-footed, unfolding a strong impact... Meet! 2014 makes room for the art, which draws its force from beyond the big, obvious, spectacular and piercing – out of the small, the plain, the elusive. Quiet in its form or in the subject matter itself – we are looking for art works, which do not present themselves to the consuming spectator too readily but expect a deep, close gaze. In short This art wants to be discovered. Works from any art genre are permitted. Date Meet! 2014 takes place from April 6th to Mai 4th in the urban gallery KUBUS, Hanover, Germany. General requirements please transfer a processing fee in the amount of 5 € to Meet! 2014; Sparkasse Hannover; IBAN DE55 2505 0180 1911 5463 92, BIC SPKHDE2HXXX personal data and all relevant contact data (address, E-Mail, phone numbers) vita or info about artistic development a piece of art work or a series three pictures (max.) of the art works in digital form or on one DVD. Submissions via E-Mail pdf, jpg, tiff or giff or text fi les are possible– the size of the fi le will be less then 5 MB, for data transfer (for example www.wetransfer.com) less then 1 GB. A statement (one page max.) for performances documentation and description of the project, info about the length of the time interval. For performances which have been presented before, we accept a report (one page max.) we will choose only one piece or series per artist (space is limited) We will not accept incomplete applications. However, we will be happy to answer any questions, do not hesitate to contact us meet.artproject@googlemail.com Postal applications are also possible (Please note that it is unfortunately not possible to return unrequested submissions of originals) Address konnektor – Forum für Künste Stichwort Meet! 2014 Kötnerholzweg 11 D-30451 Hannover Germany We will return the application, if desired, only in case an addressed and suffi ciently stamped envelope is attached to the application. Closing date for the application will be January 14th 2014 February 15th. 2014. (extended until 15.02.2014) By submitting an application, artists automatically give their consent to the terms and conditions of the organiser. Terms and conditions of the organizer the works selected have to be accessible to the organizer at least two weeks before and one week after the exhibition. No expenses of the artists are refundable. The exhibiting artists are solely responsible for the delivery and collection of their own works (no refunds either). The works are ensured during the time of the exhibition (but not during the construction- and the deconstruction-phase). They may be send to us by post or delivery. The artists accepted will be notifi ed about further details concerning the exhibition and the dates for delivery and collection of the pieces. Meet!2014Aplicationform.pdf Meet!2014Aplicationform-jan.pdf Copyright (c) Meet! 2014 All Right Reserved
https://w.atwiki.jp/voice2012/pages/293.html
Thank you for your message We are very sorry to hear that the item was not playable. Please understand that all of our items are second hand. They have some wears and scratches, moreover we do not guarantee playback operation. However we might have overlooked when listed. Please forgive us for this matter. We would like to make two options for you to select. 1) Send back the items for full refund with shipping cost. However refund will be made after we received back the item safely. 2) Receive partial refund of the item price only and keep the item. We will await for your reply. マニュアル： 【送料の返金に関して（追加送料返金）】 【返金方法】
https://w.atwiki.jp/codecenter/pages/14.html
このスニペットについて ユーザーコントロールにプロパティを追加します。 サンプル Const DefaultProp As Integer = 0 Private _Prop As Integer = DefaultProp summary プロパティの説明をここに記述します /summary value /value returns /returns remarks /remarks System.ComponentModel.DesignerSerializationVisibility( _ System.ComponentModel.DesignerSerializationVisibility.Visible) _ System.ComponentModel.DefaultValue(DefaultProp) _ System.ComponentModel.Browsable(True) _ System.ComponentModel.Description("プロパティの説明をここに記述します") _ Public Overridable Property Prop() As Integer Get Return _Prop End Get Set(ByVal value As Integer) _Prop = value End Set End Property ダウンロード ControlProperty.snippet
https://w.atwiki.jp/nicoratch/pages/919.html
概要 ハンピン製"Super OEM"タンテの先駆けとなったモデル。33/45/78回転可能、±10%（Pro TT-1+から20%）のピッチ・コントロール搭載。またピッチが表示されるLCDディスプレイが搭載された初のタンテ。しかし不正確であまり役に立たないらしい。 Pro TT-1 Pro TT-1+ ※画像なし Pro TT-1+（クローム仕上げの限定版） +スペック表・TT-1 Features feature ± 10% pitch adjustment feature Start/Stop Button feature 33/45/78 RPM speeds feature Forward and Reverse Platter Direction feature Unique Top Plate LCD Display feature Pitch Change Percentage feature Platter Speed feature Quartz Lock Mode feature Rotating 12 segment circular display indicating the spinning actions of the platter at all times feature Pop-up Stylus Target Light feature Quartz Lock of 0% speed position feature 45RPM adapter and holder feature S-Shaped Tone arm assembly with feature Counterweight feature Height Adjustment feature Skating Adjustment feature Height Lock feature Lever lift with height adjustment feature Tone arm holder with locking mechanism feature Output for feature External START/STOP control feature Easily removable smoked plastic lid feature Extra Stylus Holder Specifications feature Type 3-speed, full manual feature Driving method Direct drive feature Motor 12 Pole, 3 Phase, Brushless DC Motor feature Turntable platter Aluminum diecast 330mm dia. feature Starting Torque more than 2.2kgf.cm feature Braking Electronic feature Wow and flutter 0.13% feature S/N ratio 50dB (DIN-B) feature Output Difference 2.3dB feature Channel Separation 16dB feature Power consumption 15 Watts feature Dimension (W x D x H) 450 x 352 x 148.5 mm feature Weight 10,8kg 価格 499ドル（PRO TT-1 / PRO TT-1 +） PRO TT-1（取扱説明書・英語・PDF） https //www.numark.com/images/product_downloads/prott_1_referencemanual_00.pdf Pro TT-2 Pro TT-2（クローム仕上げの限定版。ストロボライトが青色LED仕様もある） Pro TT-2 MX edition（ブラック仕上げの限定版。希少らしい） +スペック表・TT-2 Features feature ± 20% pitch adjustment feature Start/Stop Button feature 33/45/78 RPM speeds feature Forward and Reverse Platter Direction feature Unique Top Plate LCD Display feature Pitch Change Percentage feature Platter Speed feature Quartz Lock Mode feature Rotating 12 segment circular display indicating the spinning actions of the platter at all times feature Pop-up Stylus Target Light feature Quartz Lock of 0% speed position feature 45RPM adapter and holder feature S-Shaped Tone arm assembly with feature Counterweight feature Height Adjustment feature Skating Adjustment feature Height Lock feature Lever lift with height adjustment feature Tone arm holder with locking mechanism feature Output for feature External START/STOP control feature Easily removable smoked plastic lid feature Extra Stylus Holder Specifications feature Type 3-speed, full manual feature Driving method Direct drive feature Motor 12 Pole, 3 Phase, Brushless DC Motor feature Turntable platter Aluminum diecast 330mm dia. feature Starting Torque more than 2.2kgf.cm feature Braking Electronic feature Wow and flutter 0.13% feature S/N ratio 50dB (DIN-B) feature Output Difference 2.3dB feature Channel Separation 16dB feature Power consumption 15 Watts feature Dimension (W x D x H) 450 x 352 x 148.5 mm feature Weight 10,8kg 価格 599ドル（PRO TT-2）
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 ここを編集