JDK-4932841 : asynchronous start/stop in Sequencer
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.sound
  • Affected Version: 1.4.1
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-10-06
  • Updated: 2004-03-12
  • Resolved: 2003-10-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
5.0 b26Fixed
Name: vtR10009			Date: 10/06/2003

Spec for method Sequencer.isRunning/isRecording() reads:
"Indicates whether the Sequencer is currently recording. The default is false.
The Sequencer begins recording when startRecording() is called, and then 
returns true until stop() or stopRecording() is called."

But RI (jdk1.5-b22) does not return true after invocation of 
Sequencer.startRecording(). May be it makes a sense to describe
that startRecoding() is asynchronous method and 
Sequencer.isRunning/isRecording() might return true after some 

This bug causes intermittent failure of JCK test:


CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b26 tiger-beta VERIFIED IN: tiger-b41

EVALUATION ###@###.### 2003-10-14: Recording never worked in Java Sound. In previous releases, startRecording would cause isRecording to return true, although recording really didn't take place. So the new sequencer is just consequent by returning false in isRecording. So this is not a spec bug, but missing implementation of the recording feature. Should be fixed for tiger. ###@###.### 2003-10-14