[NickKovach]

hello

i want to make permanent recording from MIC and permanent sending of recorded samples over network.

But i do not see way for that..
Is it ever possible? Maybe someone meet this problem?

I made my class based on StreamOutput and overrided all "write" functions.

But i see that "write" functions are not called until i do RecordControl.commit()

So i cannot get samples data until i stop recording?

I am trying in J2ME Wireless Toolkit emulator.
Anyway it behaves strange.

Is any emulator which correctly executes audio recording and playback?

[hartti]

You have to record the audio in pieces and send those pieces separately in another thread.

Hartti

[Keyin]

Originally Posted by hartti

You have to record the audio in pieces and send those pieces separately in another thread.

Hartti

Ya.I agree what Hartti say:)

[NickKovach]

hey!! it's me again with my question!!
i cannot agree with You!!!

i can imagine i create 2 players for recording and when 1st recorder stops i can start 2nd recorder - but between these stop and start events time elapsed and i can expect that i miss some samples - and for sure in this time noise will be hearable.

Sound recorder in this way will be choppy.
It is very bad solution.

Is any other and better solutions?

I cannot understand why API has no some cyclic buffers - it is very simple and solves all problems :-(

Or solution could be if API could have function similar to "commit" but which does not stops recorder.
In this case i could call "commit" by timer and get portions of ready samples.

[Symbian_Neil]

Originally Posted by NickKovach

hey!! it's me again with my question!!
i cannot agree with You!!!

i can imagine i create 2 players for recording and when 1st recorder stops i can start 2nd recorder - but between these stop and start events time elapsed and i can expect that i miss some samples - and for sure in this time noise will be hearable.

Sound recorder in this way will be choppy.
It is very bad solution.

Is any other and better solutions?

I cannot understand why API has no some cyclic buffers - it is very simple and solves all problems :-(

Or solution could be if API could have function similar to "commit" but which does not stops recorder.
In this case i could call "commit" by timer and get portions of ready samples.

I believe that what hartti meant was not two recorders, but one single recorder, but the recording and buffering takes place in one thread, while another thread takes care of sending the buffered packet and clearing the buffer which is sent.

Logically this seems fine to me. And as far as the time between threads when the second thread is running, I guess thats the overhead that you might have to live with ;)