#6681 closed defect (invalid)
iOS hardware H264+AAC
| Reported by: | skryv | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | git-master | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
One famous company want to switch to hardware support of RTSP with H264+AAC on iOS devices.
It would be nice to know plans of FFmpeg on switching to its HW support.
Here is some relevant answer on SO https://stackoverflow.com/a/10336035/525578
It is also considerable to know price of such services.
Up on answer the client would decide whether to go with implementing it in FFmpeg by FFmpeg forces, by outsourcing, by own or implement own simple solution with outsourcing.
Change History (3)
comment:1 by , 7 years ago
| Keywords: | ios hw h264 aac removed |
|---|---|
| Priority: | important → normal |
| Resolution: | → invalid |
| Status: | new → closed |
| Type: | enhancement → defect |
comment:2 by , 7 years ago
comment:3 by , 7 years ago
why keywords removed?
why resolution is set to invalid?
why status is changed to closed?
why type changed from enchancement to defect?
It seems this understood wrong. It is about performance and power consumption enhancement of iOS-specific implementation. Whom should I contact to?
why keywords removed?
why resolution is set to invalid?
why status is changed to closed?
why type changed from enchancement to defect?
It seems this understood wrong. It is about performance and power consumption enhancement of iOS-specific implementation. Whom should I contact to?