falkTX
/
FFmpeg
mirror of https://github.com/falkTX/FFmpeg.git
1
0
Fork 0
Code Issues 0 Releases 338 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
31707 Commits
32 Branches
959MB
Tree: 014f8d8106
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '014f8d8106'
${ noResults }
FFmpeg/doc/RELEASE_NOTES

54 lines
2.1KB
Raw Blame History 

  1. Release Notes

  2. =============

  3. 

  4. * 0.8 "Forbidden Fruit"

  5. 

  6. General notes

  7. -------------

  8. 

  9. This release continues the API cleanups that have begun with the

  10. previous release. While it is binary compatible with 0.7, many parts of

  11. the public API were deprecated and will be removed in the git master and

  12. later releases. Note that a couple of header includes have been cleaned

  13. up, which may require code changes in your applications. In particular,

  14. the header "libavutil/mathematics.h" is no longer included from

  15. "libavcodec/avcodec.h". Please consult the doc/APIchanges file to see

  16. intended replacements for the deprecated APIs.

  17. 

  18. Furthermore, our work on the 'ffmpeg' command-line tool has resulted in

  19. major revisions to its interface. In order to not break existing scripts

  20. and applications, we have chosen to introduce a new tool called

  21. 'avconv', and keep the traditional 'ffmpeg' frontend for end-user's

  22. convenience. Please see the Changelog file for details how 'avconv'

  23. differs from 'ffmpeg'.

  24. 

  25. Additionally, this release introduces a number of new interesting codecs

  26. such as the Apple Prores, Flash Screen Video 2 and Windows Media Image,

  27. and muxers such as LATM or CELT in Ogg, among many others. Moreover, our

  28. H.264 decoder has been improved to decode 4:2:2 material and our libx264

  29. wrapper now allows to produce 4:2:2 and 4:4:4 video.

  30. 

  31. See the Changelog file for a list of significant changes.

  32. 

  33. Please note that our policy on bug reports has not changed. We still only accept

  34. bug reports against HEAD of the Libav trunk repository. If you are experiencing

  35. issues with any formally released version of Libav, please try a current version

  36. of the development code to check if the issue still exists. If it does, make your

  37. report against the development code following the usual bug reporting guidelines.

  38. 

  39. 

  40. API changes

  41. -----------

  42. 

  43. A number of additional APIs have been introduced and some existing

  44. functions have been deprecated and are scheduled for removal in the next

  45. release. Please see the file doc/APIchanges for details along with

  46. similar programmer-centric information.

  47. 

  48. 

  49. 

  50. Other notable changes

  51. ---------------------

  52. 

  53. Please see the Changelog file for a more detailed list of changes.