fyhertz / libstreaming-examples

Some examples of how to use libstreaming
283 stars 231 forks source link

Does the libstreaming can send rtsp Stream to remote wowza server ? #3

Closed alfredcc closed 8 years ago

alfredcc commented 10 years ago

Hi, In example 3 , when i did the following steps

  1. set url is rtsp://my_remote_addr:1935/live/test.stream 2.push the start button in example 3
  2. use VLC to play rtsp://my_remote_addr:1935/live/test.stream i can only get the audio but no video.
fyhertz commented 10 years ago

Hi,

Well, if wowza is accepting the audio, it means that the RTSP client of libstreaming and the RTSP server of wowza have properly communicated.

The problem here is video streaming, could you paste the logs from logcat here and tell me what phone you have with what android version ?

Video streaming is buggy on some phones right now, I am working on a fix for Android 4.1 and up using the MediaCodec API...

alfredcc commented 10 years ago

before it ,our test phone is running with the 4.04 android version. then ,we change it to Android 4.1 version and 4.2, everything is ok now... well,thanks for your help :)

alfredcc commented 10 years ago

Hi,fyhertz Unfortunately, in the 4.1 version, we again encounter some problems Now, we can not see the video again here is my log:

10-31 15:08:31.690: E/Trace(3502): error opening trace file: No such file or directory (2) 10-31 15:08:31.710: W/dalvikvm(3502): Refusing to reopen boot DEX '/system/framework/hwframework.jar' 10-31 15:08:32.009: I/MediaStream(3502): Phone supports the MediaCoded API 10-31 15:08:32.259: I/Adreno200-EGL(3502): : EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_REL_2.0.3.04.01.01.21.010_msm8625_JB_REL_2.0.3_Merge_release_AU (Merge) 10-31 15:08:32.259: I/Adreno200-EGL(3502): Build Date: 10/26/12 Fri 10-31 15:08:32.259: I/Adreno200-EGL(3502): Local Branch: 10-31 15:08:32.259: I/Adreno200-EGL(3502): Remote Branch: quic/jb_rel_2.0.3 10-31 15:08:32.259: I/Adreno200-EGL(3502): Local Patches: NONE 10-31 15:08:32.259: I/Adreno200-EGL(3502): Reconstruct Branch: AU_LINUX_ANDROID_JB_REL_2.0.3.04.01.01.21.010 + NOTHING 10-31 15:08:33.489: I/Choreographer(3502): Skipped 75 frames! The application may be doing too much work on its main thread. 10-31 15:08:38.229: I/RtspClient(3502): ANNOUNCE rtsp://119.97.235.185:1935/live/test.stream RTSP/1.0 10-31 15:08:38.269: I/RtspClient(3502): ANNOUNCE rtsp://119.97.235.185:1935/live/test.stream RTSP/1.0 10-31 15:08:38.289: I/RtspClient(3502): SETUP rtsp://119.97.235.185:1935/live/test.stream/trackID=0 RTSP/1.0 10-31 15:08:38.339: I/RtspClient(3502): SETUP rtsp://119.97.235.185:1935/live/test.stream/trackID=1 RTSP/1.0 10-31 15:08:38.409: I/RtspClient(3502): RECORD rtsp://119.97.235.185:1935/live/test.stream RTSP/1.0 10-31 15:08:38.449: E/OMXNodeInstance(3502): OMX_GetExtensionIndex failed 10-31 15:08:39.029: E/H264Packetizer(3502): Packetizer out of sync ! Let's try to fix that... 10-31 15:08:40.219: E/H264Packetizer(3502): A NAL unit may have been found in the bit stream ! 10-31 15:08:49.059: I/RtspClient(3502): TEARDOWN rtsp://119.97.235.185:1935/live/test.stream RTSP/1.0 10-31 15:08:49.109: W/IInputConnectionWrapper(3502): showStatusIcon on inactive InputConnection 10-31 15:08:49.169: W/MediaRecorder(3502): mediarecorder went away with unhandled events 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x516badf0 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516c7000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x5157d388 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516c6000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x5157d270 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516c5000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x5157d090 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516c4000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x516bbaf0 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516ce000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x516bb9f0 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516cc000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x516bb8d8 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516ca000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint 10-31 15:08:49.219: E/OMXNodeInstance(3502): OMX_FreeBuffer for buffer header 0x516bb708 successful 10-31 15:08:49.219: W/MemoryDealer(3502): madvise(0x516c8000, 8192, MADV_REMOVE) returned Operation not supported on transport endpoint