Description: h.264(verilog HDL)
这是基于流水线结构的H.264解码器源码-h.264 (verilog HDL) which is based on the pipeline structure of the H.264 decoder source code Platform: |
Size: 99328 |
Author:陈成 |
Hits:
Description: Designed and Optimized H264 Decoder on ARM9 and ARM11 (25 optimized).
Designed and Optimized H263/MPEG4 Decoder on Freescale SC3400 QuadCore platform (18 optimized).
Designed and Optimized MPEG4 Encoder and improved video quality by changing bitrate algorithm on Freescale StarCore QuadCore platform and ARM11 processors (25 optimized).
Designed and Optimized RealVideo Decoder for ARM11 processor (20 optimized).
Worked on porting of various codecs on ARM processors
- Designed and Optimized H264 Decoder on ARM9 and ARM11 (25 optimized).
Designed and Optimized H263/MPEG4 Decoder on Freescale SC3400 QuadCore platform (18 optimized).
Designed and Optimized MPEG4 Encoder and improved video quality by changing bitrate algorithm on Freescale StarCore QuadCore platform and ARM11 processors (25 optimized).
Designed and Optimized RealVideo Decoder for ARM11 processor (20 optimized).
Worked on porting of various codecs on ARM processors
Platform: |
Size: 22528 |
Author:satya |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到Android，深度删减优化，在模拟器(320x480)中验证通过。
程序的采用jni架构。界面部分，文件读取，视频显示都是用java做的，底层的视频解码用C来做满足速度的要求。
在这个版本中，从H264码流中分割出Nal是在java层做的，这样在java层直接调用解码时就知道是否有显示视频，缺点的就是耦合度/封装性差一点。
如果采用在底层做Nal分割的方法，可以封装得好看一些，但是每次送的数据有限制，如果送的数据太多，底层可能会一次解码出好几帧视频，但是通知到界面层只能显示一帧，造成丢帧的现象。 如果每次送的数据较少，就会有很多次底层调用没有进行实质解码，很小气的做法，比如有一压缩数据帧需要600字节，如果一次送100个字节给解码器，那么要送6次才会进行实质解码，因为每个数据帧有大有小，所以只能取极小值才不会导致丢帧。
不过所有的编码解码都是各种因素平衡折中的结果，具体用什么方法具体分析。
注意解码库写死了视频大小240x320,其他视频大小要简单修改一下底层的代码。-H264 decoder source code, porting ffmpeg s H264 decoding to Android, the depth of cut optimization, in the simulator (320x480) in the validation passed. Platform: |
Size: 650240 |
Author:caoliang |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到Symbian，深度删减优化，在N72和模拟器中验证通过。-H264 decoder source code, porting the H264 decoding in ffmpeg to Symbian, the depth of cut optimization, the N72 and the simulator is verified. Platform: |
Size: 71680 |
Author:caoliang |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到windows，深度删减优化，在VC6中验证通过。-H264 decoder source code, porting ffmpeg s H264 decoding to the windows, the depth of cut optimization, in VC6 verify pass. Platform: |
Size: 59392 |
Author:caoliang |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到Android，深度删减优化，在模拟器(320x480)中验证通过。
程序的采用jni架构。界面部分，文件读取，视频显示都是用java做的，底层的视频解码用C来做满足速度的要求。
在这个版本中，从H264码流中分割出Nal是在java层做的，这样在java层直接调用解码时就知道是否有显示视频，缺点的就是耦合度/封装性差一点。
如果采用在底层做Nal分割的方法，可以封装得好看一些，但是每次送的数据有限制，如果送的数据太多，底层可能会一次解码出好几帧视频，但是通知到界面层只能显示一帧，造成丢帧的现象。 如果每次送的数据较少，就会有很多次底层调用没有进行实质解码，很小气的做法，比如有一压缩数据帧需要600字节，如果一次送100个字节给解码器，那么要送6次才会进行实质解码，因为每个数据帧有大有小，所以只能取极小值才不会导致丢帧。
不过所有的编码解码都是各种因素平衡折中的结果，具体用什么方法具体分析。-H264 decoder source code, porting ffmpeg s H264 decoder part to Android, the depth of cut optimization, in the simulator (320x480) to verify through.
Program using jni architecture. Interface portion of the file to read, the video display is made with java, the underlying video decoding in C to do to meet the speed requirements.
In this version, the H264 stream from a separate layer of Nal is done in java, so call decoding in java layer directly whether there is to know when to display video, drawback is the coupling/packaging of almost.
If used at the bottom do Nal segmentation method can be encapsulated look good, but each time there is limited data to send, if you get too much data, the underlying may be a decoding of several frames of video, but the notice to the interface layer can only display one, resulting in dropped frames phenomenon. If you send less data each time, there will be many times not to call the underlying substance of decoding, a small gas practices, s Platform: |
Size: 230400 |
Author:wyc |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到Android，深度删减优化，此为测试码流-The H264 decoder source code, transplant ffmpeg' s H264 decoding part to Android, depth deletion optimization, this is a test stream Platform: |
Size: 351232 |
Author:葛伟 |
Hits:
Description: H264解码器源码，移植ffmpeg中的H264解码部分到Android，深度删减优化，在模拟器(320x480)中验证通过。
程序的采用jni架构。界面部分，文件读取，视频显示都是用java做的，底层的视频解码用C来做满足速度的要求。
在这个版本中，从H264码流中分割出Nal是在java层做的，这样在java层直接调用解码时就知道是否有显示视频，缺点的就是耦合度/封装性差一点。
如果采用在底层做Nal分割的方法，可以封装得好看一些，但是每次送的数据有限制，如果送的数据太多，底层可能会一次解码出好几帧视频，但是通知到界面层只能显示一帧，造成丢帧的现象。 如果每次送的数据较少，就会有很多次底层调用没有进行实质解码，很小气的做法，比如有一压缩数据帧需要600字节，如果一次送100个字节给解码器，那么要送6次才会进行实质解码，因为每个数据帧有大有小，所以只能取极小值才不会导致丢帧。
不过所有的编码解码都是各种因素平衡折中的结果，具体用什么方法具体分析。-H264 decoder source code, porting the H264 decoding ffmpeg to Android, depth of cut optimization, in the simulator (320x480) is verified.
Program using jni architecture. Part of the interface, file read, the video display is made with java, the underlying video decoding using C do meet the speed requirements.
In this version, from the H264 stream is segmented Nal java layer do so directly call the java layer decoding know whether displaying video, the disadvantage is that the degree of coupling/encapsulation almost.
If you do use the underlying Nal segmentation method, you can get some good-looking package, but every time there is limited data to send, if sending too much data, the underlying may decode several time-frame video, but can only display notifications to the UI layer one, resulting in dropped frames phenomenon. If you send less data each time, there will be many times the underlying call no substantial decoding, a small gas practice, such a frame requ Platform: |
Size: 243712 |
Author:caojin |
Hits:
Search - h264 decoder source code