AudioRecord

Denotes a generic operation failure.

Denotes a failure due to the use of an invalid value.

Denotes a failure due to the improper use of a method.

indicates AudioRecord recording state is recording

indicates AudioRecord recording state is not recording

indicates AudioRecord state is ready to be used

indicates AudioRecord state is not successfully initialized.

Denotes a successful operation.

Class constructor.

Returns the configured audio data format. See ENCODING_PCM_16BIT and ENCODING_PCM_8BIT.

Returns the audio session ID.

Returns the audio recording source.

Returns the configured channel configuration. See CHANNEL_IN_MONO and CHANNEL_IN_STEREO.

Returns the configured number of channels.

Returns the minimum buffer size required for the successful creation of an AudioRecord object, in byte units. Note that this size doesn't guarantee a smooth recording under load, and higher values should be chosen according to the expected frequency at which the AudioRecord instance will be polled for new data. See AudioRecord(int, int, int, int, int) for more information on valid configuration values.

Returns the notification marker position expressed in frames.

Returns the notification update period expressed in frames.

Returns the recording state of the AudioRecord instance.

Returns the configured audio data sample rate in Hz

Returns the state of the AudioRecord instance. This is useful after the AudioRecord instance has been created to check if it was initialized properly. This ensures that the appropriate hardware resources have been acquired.

Reads audio data from the audio hardware for recording into a buffer.

Reads audio data from the audio hardware for recording into a buffer.

Reads audio data from the audio hardware for recording into a direct buffer. If this buffer is not a direct buffer, this method will always return 0. Note that the value returned by position() on this buffer is unchanged after a call to this method.

Releases the native AudioRecord resources. The object can no longer be used and the reference should be set to null after a call to release()

Sets the marker position at which the listener is called, if set with setRecordPositionUpdateListener(OnRecordPositionUpdateListener) or setRecordPositionUpdateListener(OnRecordPositionUpdateListener, Handler).

Sets the period at which the listener is called, if set with setRecordPositionUpdateListener(OnRecordPositionUpdateListener) or setRecordPositionUpdateListener(OnRecordPositionUpdateListener, Handler). It is possible for notifications to be lost if the period is too small.

Sets the listener the AudioRecord notifies when a previously set marker is reached or for each periodic record head position update. Use this method to receive AudioRecord events in the Handler associated with another thread than the one in which you created the AudioTrack instance.

Sets the listener the AudioRecord notifies when a previously set marker is reached or for each periodic record head position update.

Starts recording from the AudioRecord instance.

Starts recording from the AudioRecord instance when the specified synchronization event occurs on the specified audio session.

Stops recording.

Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.