Recherche avancée

Sur d’autres sites (10325)

• Revision 223bf29307 : libyuv : update to r1305 MIPS build fixes https://code.google.com/p/webm/issues

  3 mars 2015, par Johann

  Changed Paths :
   Modify /third_party/libyuv/README.libvpx

  
   Modify /third_party/libyuv/include/libyuv/compare.h

  
   Modify /third_party/libyuv/include/libyuv/convert.h

  
   Modify /third_party/libyuv/include/libyuv/convert_argb.h

  
   Modify /third_party/libyuv/include/libyuv/convert_from.h

  
   Modify /third_party/libyuv/include/libyuv/convert_from_argb.h

  
   Delete /third_party/libyuv/include/libyuv/format_conversion.h

  
   Modify /third_party/libyuv/include/libyuv/row.h

  
   Modify /third_party/libyuv/include/libyuv/scale.h

  
   Modify /third_party/libyuv/include/libyuv/scale_row.h

  
   Modify /third_party/libyuv/include/libyuv/version.h

  
   Modify /third_party/libyuv/include/libyuv/video_common.h

  
   Modify /third_party/libyuv/source/compare.cc

  
   Modify /third_party/libyuv/source/compare_neon.cc

  
   Add /third_party/libyuv/source/compare_neon64.cc

  
   Modify /third_party/libyuv/source/compare_posix.cc

  
   Modify /third_party/libyuv/source/compare_win.cc

  
   Modify /third_party/libyuv/source/convert.cc

  
   Modify /third_party/libyuv/source/convert_argb.cc

  
   Modify /third_party/libyuv/source/convert_from.cc

  
   Modify /third_party/libyuv/source/convert_from_argb.cc

  
   Modify /third_party/libyuv/source/convert_to_argb.cc

  
   Modify /third_party/libyuv/source/convert_to_i420.cc

  
   Modify /third_party/libyuv/source/cpu_id.cc

  
   Delete /third_party/libyuv/source/format_conversion.cc

  
   Modify /third_party/libyuv/source/mjpeg_validate.cc

  
   Modify /third_party/libyuv/source/planar_functions.cc

  
   Modify /third_party/libyuv/source/rotate.cc

  
   Modify /third_party/libyuv/source/rotate_argb.cc

  
   Modify /third_party/libyuv/source/rotate_neon.cc

  
   Add /third_party/libyuv/source/rotate_neon64.cc

  
   Modify /third_party/libyuv/source/row_any.cc

  
   Modify /third_party/libyuv/source/row_common.cc

  
   Modify /third_party/libyuv/source/row_mips.cc

  
   Modify /third_party/libyuv/source/row_neon.cc

  
   Modify /third_party/libyuv/source/row_neon64.cc

  
   Modify /third_party/libyuv/source/row_posix.cc

  
   Modify /third_party/libyuv/source/row_win.cc

  
   Modify /third_party/libyuv/source/scale.cc

  
   Modify /third_party/libyuv/source/scale_argb.cc

  
   Modify /third_party/libyuv/source/scale_common.cc

  
   Modify /third_party/libyuv/source/scale_neon.cc

  
   Modify /third_party/libyuv/source/scale_neon64.cc

  
   Modify /third_party/libyuv/source/scale_posix.cc

  
   Modify /third_party/libyuv/source/scale_win.cc

  
   Modify /third_party/libyuv/source/video_common.cc

  
  
  libyuv : update to r1305

  MIPS build fixes

  https://code.google.com/p/webm/issues/detail?id=957

  Change-Id : I9d53900af36d783c369b5dff27a7479cb94fd16b

• Why are rectangular boxes ([]) showing instead of text in burned subtitles when using ffmpeg/MoviePy on Google Colab ?

  14 mai, par Lavish

  I'm working on a Python script that adds subtitles to a video using MoviePy and burns/hardcodes them directly onto the video. The subtitles contain Hindi text, and I’ve specified a custom font that supports Devanagari (Hindi) script.

  


  The code works perfectly fine on my local machine, the subtitles appear correctly with Hindi characters. However, when I run the same code on Google Colab, the subtitles display as rectangular boxes (something like this -> [][][]) instead of proper characters.

  


  Things I've tried :

  


  

  • Ensured the font used supports Hindi (I'm using NotoSansDevanagari-Regular.ttf renamed as font.ttf).

  


  • Uploaded the font to Colab and specified the full path correctly.

  


  • Verified that the text is passed as a proper Unicode string.

  


  


  Here's the code snippet :

  


  def add_subtitles(video_path, subtitles_path, output_path):
    """Adds subtitles using FFmpeg with proper path escaping."""
    # Convert to absolute paths and normalize
    
    video_path = os.path.abspath(video_path)
    subtitles_path = os.path.abspath(subtitles_path)
    output_path = os.path.abspath(output_path)


    # Subtitle path
    font_path = "input_files/font.ttf"
    font_path = os.path.abspath(font_path).replace("\\", "\\\\")
    subtitles_path_escaped = os.path.abspath(subtitles_path).replace("\\", "\\\\")
    
    # Escape backslashes in paths
    subtitles_path = subtitles_path.replace("\\", "\\\\")
    # Remove all files in final_videos
    [os.remove(os.path.join(base_dir, "final_videos", f)) for f in os.listdir(os.path.join(base_dir, "final_videos")) if os.path.isfile(os.path.join(base_dir, "final_videos", f))]

    os.makedirs(os.path.dirname(output_path), exist_ok=True)
    escaped_path = subtitles_path.replace(':', '\\:').replace('\\', '\\\\')

    cmd = [
    "ffmpeg",
    "-i", video_path,
    "-vf", f"subtitles={escaped_path}:force_style='FontFile={font_path}'",
    "-c:v", "libx264",
    "-c:a", "copy",
    "-preset", "fast",
    "-crf", "22",
    output_path
]


    # Debug: Print the exact command being executed
    print("Executing:", " ".join(cmd))
    try:
        subprocess.run(cmd, check=True, capture_output=True, text=True)
        print(f"✅ Success! Output saved to: {output_path}")
    except subprocess.CalledProcessError as e:
        print(f"❌ FFmpeg failed with error:\n{e.stderr}")



  


  What could be causing this issue on Colab, and how can I get non-English subtitles (like Hindi) to render properly when burning subtitles using MoviePy/ffmpeg in a Colab environment ?

  


• Installing "ffmpeg" package from setup.py in Apache Beam pipeline running on Google Cloud Dataflow

  17 avril 2019, par John Allard

  I’m trying to run an Apache Beam pipeline on Google Cloud Dataflow that utilizes FFmpeg to perform transcoding operations. As I understand it, since ffmpeg is not a python package (available through PIP), I need to install it from setup.py using the following lines

  # The output of custom commands (including failures) will be logged in the
  
  # worker-startup log.
  
  CUSTOM_COMMANDS = [
  
      ['apt-get', 'update'],
  
      ['apt-get', 'install', '-y', 'ffmpeg']]

  Unfortunately, this is not working. My pipeline is stalling and when I go to examine the logs I’m seeing this

  

  RuntimeError: Command ['apt-get', 'install', '-y', 'ffmpeg'] failed: exit code: 100

  It appears to be unable to find the package ’ffmpeg’. I’m curious as to why this is - ffmpeg is a standard package that should be available under apt-get.