• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /netgear-R7000-V1.0.7.12_1.2.5/ap/gpl/amule/wxWidgets-2.8.12/contrib/docs/latex/mmedia/

Lines Matching refs:sound

13 Base class for sound streams
36 \twocolitem{{\bf wxSOUND\_INVFRMT}}{The sound format passed to the function is
38 stream or you don't pass the right sound format object to the right sound codec
41 sound stream didn't manage to open the device driver due to an invalid parameter
42 or to the fact that sound is not supported on this computer.}
43 \twocolitem{{\bf wxSOUND\_NOEXACT}}{No exact matching sound codec has been found for
44 this sound format. It means that the sound driver didn't manage to setup the sound
57 When a sound event is generated, it may either call the internal sound event
67 The {\bf evt} parameter represents the sound event which is the cause of the calling. (See \helpref{wxSound events}{wxsoundstream}).
72 {\it Note:} There are two other ways to catch sound events: you can inherit the
73 sound stream and redefine \helpref{wxSoundStream::OnSoundEvent}{wxsoundstreamonsoundevent}, or you can reroute the events to another sound stream using \helpref{wxSoundStream::SetEventHandler}{wxsoundstreamseteventhandler}.
103 The sound events are generated when the sound driver (or the sound stream) completes
104 a previous sound buffer. There are two possible sound events and two meanings.
106 The {\bf wxSOUND\_INPUT} event is generated when the sound stream has a new input
110 The {\bf wxSOUND\_OUTPUT} event is generated when the sound stream has completed a
111 previous buffer. This buffer has been sent to the sound driver and it is ready to
140 Reads {\it len} bytes from the sound stream. This call may block the user so
142 interested by sound events: see \helpref{wxSoundStream::OnSoundEvent}{wxsoundstreamonsoundevent}.
145 sound event system.
153 \docparam{data}{Data in \it{buffer} are coded using the sound format attached to this sound
165 Writes \it{len} bytes to the sound stream. This call may block the user so
166 use it carefully. You may be interested by sound events: see
170 sound event system.
178 \docparam{buffer}{Data in \it{buffer} are coded using the sound format attached to this sound
191 a good alignment for data to be written (or read) to (or from) the sound stream.
192 So, when, for example, a sound event is sent, you are sure the sound stream
204 It specifies the sound format the user needs. SetSoundFormat tries to
205 apply the format to the current sound stream (it can be a sound file or a
206 sound driver). Then, either it manages to apply it and it returns {\bf TRUE},
228 It returns a reference to the current sound format of the stream represented by a
250 StartProduction starts the sound streaming. {\it evt} may be one of
254 recording). Actually this may happen the sound IO queue is too short.
255 It is also advised that you fill quickly enough the sound IO queue when the
262 I stops the async notifier and the sound streaming straightly.
280 It returns the number of bytes which were effectively written to/read from the sound stream.
286 It returns whether the sound IO queue is full. When it is full, the next IO call will block
293 It is called by the wxSoundStream when a new sound event occurred.