Recherche avancée

Sur d’autres sites (10028)

• Introducing WebM, an open web media project

  20 mai 2010, par noreply@blogger.com (christosap)

  A key factor in the web’s success is that its core technologies such as HTML, HTTP, TCP/IP, etc. are open and freely implementable. Though video is also now core to the web experience, there is unfortunately no open and free video format that is on par with the leading commercial choices. To that end, we are excited to introduce WebM, a broadly-backed community effort to develop a world-class media format for the open web.

  WebM includes :
  

  • VP8, a high-quality video codec we are releasing today under a BSD-style, royalty-free license
  • Vorbis, an already open source and broadly implemented audio codec
  • a container format based on a subset of the Matroska media container

  The team that created VP8 have been pioneers in video codec development for over a decade. VP8 delivers high quality video while efficiently adapting to the varying processing and bandwidth conditions found on today’s broad range of web-connected devices. VP8’s efficient bandwidth usage will mean lower serving costs for content publishers and high quality video for end-users. The codec’s relative simplicity makes it easy to integrate into existing environments and requires less manual tuning to produce high quality results. These existing attributes and the rapid innovation we expect through the open-development process make VP8 well suited for the unique requirements of video on the web.

  A developer preview of WebM and VP8, including source code, specs, and encoding tools is available today at www.webmproject.org.

  We want to thank the many industry leaders and web community members who are collaborating on the development of WebM and integrating it into their products. Check out what Mozilla, Opera, Google Chrome, Adobe, and many others below have to say about the importance of WebM to the future of web video.

  
  

  AMD

  ARM

  Brightcove

  Broadcom

  Collabora

  Digital Rapids

  Encoding.com

  Grab Networks

  iLinc

  INLET

  Kaltura

  Logitech

  MIPS

  Nvidia

  Ooyala

  Qualcomm

  Skype

  Sorenson

  Telestream
  

  Texas Instruments

  Verisilicon

  ViewCast

  Wildform

  
  

  Posted by Jeremy Doig, Engineering Director of video and Mike Jazayeri, Group Product Manager, Google

  

• FFmpeg-kit : Unknown encoder 'libx264' / 'mediacodec' and Gradle dependency issues in Android Studio

  15 mai, par Izzet dönertaş

  I'm working on a video editor app in Android Studio using ffmpeg-kit. My goal is to export video segments with fade transitions and audio using FFmpeg.

  


  This implementation line works fine :

  


  implementation("com.arthenica:ffmpeg-kit-full:6.0-2")


  


  What doesn't work (Encoding) :
When I try to export a video segment using :

  


  -c:v libx264 -c:a aac


  


  I get this error in the logs :

  


  [vost#0:0 @ ...] Unknown encoder 'libx264'


  


  After checking the build configuration, it turns out libx264 is not enabled in the current FFmpeg-kit build :

  


  --disable-libx264 (or rather: --enable-libx264 is missing)


  


  Tried replacing libx264 with mediacodec :
Then I tried using :

  


  -c:v mediacodec -c:a aac


  


  But again I got :

  


  Unknown encoder 'mediacodec'


  


  Apparently, mediacodec is supported for decoding, but not as an encoder in FFmpeg-kit.

  


  Tried to compile my own FFmpeg binary :
I attempted building FFmpeg manually using the following flags :

  


  --enable-libx264 --enable-gpl --enable-shared ...


  


  My plan was to access it via JNI or ProcessBuilder.

  


  But the process is extremely frustrating :

  


  

  • Missing file errors

  


  • Configuration conflicts

  


  • Dependency hell (especially on macOS/Linux NDK toolchains)

  


  


  Tried other ffmpeg-kit variants :
I also tried switching to :

  


  implementation 'com.arthenica:ffmpeg-kit-full-gpl:6.0'


  


  and other variants like ffmpeg-kit-min-gpl, etc.
But in all of them I got the same Gradle error :

  


  Caused by: org.gradle.api.internal.artifacts.ivyservice.TypedResolveException:  Could not resolve all files for configuration ':app:debugRuntimeClasspath'.

  


  My build.gradle setup (yes, mavenCentral + google are already included) :

  


  pluginManagement {
    repositories {
        google()
        mavenCentral()
    }
}

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
    }
}



  


  I also tried enabling offline mode, clearing cache, adding jetpack.io, nothing helped.

  


  I asked ChatGPT-4o, Gemini 2.5 Pro. None could provide a working solution for this combination of :

  


  

  • Working implementation

  


  • Proper video encoding (with libx264 or mediacodec)

  


  • Without breaking Gradle dependency resolution

  


  


  I just want one of the following :

  


  


  1. A working FFmpeg-kit implementation (that supports libx264) and doesn’t crash Gradle

     


  


  2. A reliable guide or build.gradle snippet that lets me use GPL version (with libx264) without resolve errors

     


  


  3. (Ideally) A prebuilt safe LGPL-compatible alternative that allows encoding and is Google Play compliant

     


  


  


  Any help or suggestions would be highly appreciated.
Thanks in advance

  


• lavc/vvc : Ensure subpictures don't overlap

  22 février, par Frank Plowman

  lavc/vvc : Ensure subpictures don't overlap
  This is essentially a re-implementation of
  
  https://patchwork.ffmpeg.org/project/ffmpeg/patch/20241005223955.54158-1-post@frankplowman.com/
  That patch was not applied last time.  Instead we opted to identify
  
  issues which could be caused by invalid subpicture layouts and remedy
  
  those issues where they manifest, either through error detection or code
  
  hardening.  This was primarily implemented in the set
  
  https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=13381.
  This has worked to some degree, however issues with subpicture layouts
  
  continue to crop up from the fuzzer and I've fixed a number of bugs
  
  related to subpicture layouts since then.  I think it's best to return
  
  to the initial plan and simply check if the subpicture layout is valid
  
  initially.
  This implementation is also lighter than the first time — by doing a
  
  bit more logic in pps_subpic_less_than_one_tile_slice, we are able to
  
  store a tile_in_subpic map rather than a ctu_in_subpic map.  This
  
  reduces the size of the map to the point it becomes possible to allocate
  
  it on the stack.  Similar to 8bd66a8c9587af61c7b46558be3c4ee317c1af5a,
  
  the layout is also validated in the slice map construction code, rather
  
  than in the CBS, which avoids duplicating some logic.
  Signed-off-by : Frank Plowman <post@frankplowman.com>
  

  • [DH] libavcodec/vvc/ps.c