|
Quick Lists
|
|
Bug ID:
|
4932841
|
|
Votes
|
0
|
|
Synopsis
|
asynchronous start/stop in Sequencer
|
|
Category
|
java:classes_sound
|
|
Reported Against
|
hopper
|
|
Release Fixed
|
1.5(tiger-b26)
|
|
State
|
10-Fix Delivered,
Verified,
bug
|
|
Priority:
|
2-High
|
|
Related Bugs
|
|
|
Submit Date
|
06-OCT-2003
|
|
Description
|
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
latency.
This bug causes intermittent failure of JCK test:
api/javax_sound/midi/Sequencer/index.html#Record
======================================================================
|
|
Work Around
|
N/A
|
|
Evaluation
|
xxxxx@xxxxx 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.
xxxxx@xxxxx 2003-10-14
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |