*Sorry Folks Its working fine. It works fine . The problem was in the application Implementation .*
On Tue, Dec 22, 2009 at 6:32 PM, vishal bhoj <vishalb...@gmail.com> wrote: > these are the xecution logs > when I start the playback. > > > ideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = 1 > E/CameraInput( 1021): postWriteAsync > E/CameraInput( 1021): postWriteAsync: ID = 23, base = 0x40dff000, offset = > 0x0, size = 202752 pointer 0x40dff000 > E/CameraInput( 1021): Run > E/CameraInput( 1021): Ln 733 Run writeAsync mFrameRefCount 1 writeAsyncID > 175 > > E/CameraInput( 1021): writeComplete > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/PVMediaRecorder( 1021): reset > E/AuthorDriver( 1021): handleReset > E/AuthorDriver( 1021): removeConfigRefs > E/CameraInput( 1021): deleteMediaTransfer > E/CameraInput( 1021): setPeer iPeer 0x2415c aPeer 0x0 > E/CameraInput( 1021): Reset > E/CameraInput( 1021): AddCmdToQueue > D/OMX_AACDEC( 1021): AACDEC_LCML_Callback():2716 out ts-13230 > E/CameraInput( 1021): Run > E/CameraInput( 1021): DoReset > > D/CameraService( 1021): stopRecording (pid 1021) > D/CameraService( 1021): stopRecording(), hardware stopped OK > E/CameraInput( 1021): ReleaseQueuedFrames > E/CameraInput( 1021): DoRequestCompleted > E/CameraInput( 1021): ThreadLogoff > E/CameraInput( 1021): disconnect > E/AuthorDriver( 1021): Command (16) completed with status(1) > E/AuthorDriver( 1021): handleRemoveVideoSource > E/AuthorDriver( 1021): Command (18) completed with status(1) > E/AuthorDriver( 1021): handleRemoveAudioSource > E/PVMediaRecorder( 1021): close > E/AuthorDriver( 1021): handleClose > E/AuthorDriver( 1021): Command (17) completed with status(1) > E/AuthorDriver( 1021): doCleanUp > E/CameraInput( 1021): destructor > E/CameraInput( 1021): ReleaseQueuedFrames > E/CameraInput( 1021): camera was cold when we started, stopping preview > D/CameraService( 1021): stopPreview (pid 1021) > > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold = > 1 > E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, num > > On Tue, Dec 22, 2009 at 6:21 PM, vishal bhoj <vishalb...@gmail.com> wrote: > >> I am using donut + opencore 2.02 >> >> >> On Tue, Dec 22, 2009 at 6:20 PM, vishal bhoj <vishalb...@gmail.com>wrote: >> >>> >>> I see that when I have video playback and recording object , >>> as soon as I start my video playback the recording gets stopped.Someone >>> is calling a writecomplete on the camera input. >>> I am unable to find any reference in the mediaserver implementation.Can >>> anyone clarify my doubts, >>> Is opencore internally calling this complete when I start videoplayback ? >>> Here is the log . I have just change LOGV to LOGE so that I can see the >>> logs >>> >>> /CameraInput( 1021): postWriteAsync >>> E/CameraInput( 1021): postWriteAsync: ID = 24, base = 0x40e33000, offset >>> = 0x0, size = 202752 pointer 0x40e33000 >>> E/CameraInput( 1021): Run >>> E/CameraInput( 1021): Ln 733 Run writeAsync mFrameRefCount 2 writeAsyncID >>> 42 >>> E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold >>> = 1 >>> E/CameraInput( 1021): writeComplete >>> E/CameraInput( 1021): writeComplete >>> E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold >>> = 1 >>> E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold >>> = 1 >>> E/VideoMIO( 1021): processWriteResponseQueue: queued = 2, numFramesToHold >>> = 1 >>> E/CameraInput( 1021): postWriteAsync >>> E/CameraInput( 1021): postWriteAsync: ID = 24, base = 0x40e33000, offset >>> = 0x0, size = 202752 pointer 0x40e33000 >>> E/CameraInput( 1021): Run >>> E/CameraInput( 1021): Ln 733 Run writeAsync mFrameRefCount 1 writeAsyncID >>> 43 >>> E/CameraInput( 1021): writeComplete >>> E/CameraInput( 1021): Stop >>> E/CameraInput( 1021): AddCmdToQueue >>> E/CameraInput( 1021): Run >>> E/CameraInput( 1021): DoStop >>> D/CameraService( 1021): stopRecording (pid 1021) >>> D/CameraService( 1021): stopRecording(), hardware stopped OK >>> E/CameraInput( 1021): ReleaseQueuedFrames >>> E/CameraInput( 1021): DoRequestCompleted >>> E/AuthorDriver( 1021): HandleInformationalEvent(2049) >>> >>> >>> ---------- Forwarded message ---------- >>> From: vishal bhoj <vishalb...@gmail.com> >>> Date: Tue, Dec 22, 2009 at 2:56 PM >>> Subject: simultaneous video playback and camera record >>> To: android-porting@googlegroups.com, android-platf...@googlegroups.com >>> >>> >>> Hi, >>> >>> I created an application with videoview and mediarecorder from camera on >>> omap3 platform. >>> The hardware codecs work fine for seperate video playback and recording. >>> Is there any restriction inside opencore causing a blocking when I try to >>> run both simultaneously . >>> Through command prompt the same codecs are able to encode and decode >>> simultaneously. >>> >>> Is there any kind of scheduler setting inside opencore (OSCL) ? >>> >>> -- >>> with regards vishal >>> >>> >>> >>> -- >>> with regards vishal >>> >> >> >> >> -- >> with regards vishal >> > > > > -- > with regards vishal > -- with regards vishal -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
