Recherche avancée

Sur d’autres sites (9420)

• how to stop the FFmpeg process programmatically without using Ctrl + C ?

  30 septembre 2024, par bee

  const shell = require("shelljs");

const processShell = shell.exec(
  `ffmpeg -i "https://pull-hls-f16-va01.tiktokcdn.com/game/stream-2998228870023348312_or4/index.m3u8?expire=1728629296&session_id=000-2024092706481532076B1319E1100113F8&sign=1016b521d08053bc0ae8eddb0881b029" -movflags use_metadata_tags -map_metadata 0 -metadata title="Chill chill kiß║┐m k├¿o Warthunder" -metadata artist="bacgaucam" -metadata year="2024" -c copy "downloads/bacgaucam-927202491939.mp4" -n -stats -hide_banner -loglevel error`,
  { async: true }
);

setTimeout(() => {
  // processShell.kill();
  process.exit();
}, 20000);


  


  my video only works when I use Ctrl+C to stop it. I’ve tried using process.exit(), .kill(pid, "SIGINT"), and the .kill() method from the shell.exec() ffmpeg() of fluent-ffmpeg or spawn() of child_process reference, but none of them work

  


  If you want to test it directly, please message me to get a new live url in case it expires (https://t.me/ppnam15) or clone this :
https://github.com/loo-kuhs/tiktok-live-downloader

  


  can anyone help ? Thanks !

  


• get error ffmpeg when running wdio-video-reporter in jenkins and centos

  31 janvier 2024, par Ferawati Hartanti Pratiwi

  i got this error when i run wdio-video-reporter on jenkins and the OS is centos 8

  


  


  2024-01-31T17:54:56.047Z ERROR @wdio/config:ConfigParser: Failed loading configuration file:


  


  file :///var/data/jenkins-slave/workspace/QE_Playground/web-testing-pr-only/test/support/wdio.conf.chrome.js :
undefined
Could not find ffmpeg executable, tried "/var/data/jenkins-slave/workspace/QE_Playground/web-testing-pr-only/node_modules/@ffmpeg-installer/linux-x64/ffmpeg",
"/var/data/jenkins-slave/workspace/QE_Playground/web-testing-pr-only/node_modules/@ffmpeg-installer/ffmpeg/node_modules/@ffmpeg-installer/linux-x64/ffmpeg"
and
"/var/data/jenkins-slave/workspace/QE_Playground/web-testing-pr-only/node_modules/@ffmpeg-installer/linux-x64/ffmpeg"

  


  


  this is my jenkins env

  


    environment {
    PATH = "/usr/bin/ffmpeg:$PATH"
  }


  


  this is my wdio config

  


    ffmpegPath: '/usr/bin/ffmpeg',
  capabilities: [
    {
      maxInstances: parseInt(process.env.MAX_INSTANCES, 10) || 3,
      specs: [
        `${process.cwd()}/test/**_${folder}/features/**/*.feature`,
      ],
      browserName: 'chrome',
      'goog:chromeOptions': browserOptions,
      acceptInsecureCerts: true,
    },
  ],


  


• avutil : Fix linking x86 asm constants with Clang in MSVC mode

  12 juin, par Martin Storsjö

  avutil : Fix linking x86 asm constants with Clang in MSVC mode
  This fixes building with Clang in MSVC mode, for x86, which was
  
  broken in 6e49b8699657b808b7dc80033f2c3f2d0e029fa3 (in Nov 2024) ;
  
  previously it failed with undefined symbols for the constants
  
  defined with DECLARE_ASM_CONST, accessed via inline assembly.
  Before 57861911a34e1c33796be97f2b2f44e05fffd647, there was an
  
      #elif defined(__GNUC__) || defined(__clang__)
  
  case before the
  
      #elif defined(_MSC_VER)
  
  case for defining DECLARE_ASM_CONST, which included av_used.
  
  (This case included the explicit "defined(__clang__)" since
  
  f637046d3134a331e4b5a7243ac3dfb92735b8a5.)
  After 57861911a34e1c33796be97f2b2f44e05fffd647, it used the
  
  generic definition of DECLARE_ASM_CONST that also included
  
  av_used - which also worked for Clang in MSVC mode. But after
  
  6e49b8699657b808b7dc80033f2c3f2d0e029fa3, Clang in MSVC mode
  
  ended up using the MSVC specific variant which lacked the
  
  av_used declaration, causing linker errors due to undefined
  
  symbols.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavutil/mem_internal.h