Recherche avancée

Sur d’autres sites (10806)

• Revision 65614 : Notification des forums : c’est du contenu html mis en forme par des ...

  6 septembre 2012, par cedric@… — Log

  Notification des forums : c’est du contenu html mis en forme par des raccourcis spip, le conserver intact pour l’envoyer dans un mail html plutot que le transformer en texte pour faire un mail texte puis re formater le mail en html par un wrapper qui perd des mises en forme.
  On utilise le wrapper pour formater le mail directement en html, et on le fournit a la fonction notifications_envoyer_mails avec les bons arguments.
  Si pas de plugin facteur, c’est le mail texte qui est utilisé, comme avant.

• Translating a multiple line terminal command into a single line terminal command

  5 décembre 2019, par andy stumpf

  Does anyone have any direction or suggestion on how to translate this command into a single line command ? I need to keep this in a terminal command and no use a shell. Thank you so much for any help and direction.

      for event in */; do
  
      (
  
      echo "$event"
  
      cd "$event"
  
      for segment in */; do          
  
          (                       
  
              cd "$segment"
  
              echo "$segment"           
  
              for f in *-0.ts; do
  
                  (
  
                      echo $f
  
                  )
  
              done
  
              (printf "file '$PWD/%s'\n" *.ts | sort -n -k1.$(($(printf "file '$PWD/$f'" | wc -c) - 4))) > fraglist.txt
  
              ../../ffmpeg -f concat -i fraglist.txt -c copy ../../"${segment[@]%.hls/}.ts"
  
          )
  
      done
  
      )
  
  done

  I’ve tried something like the following but the outcome is not the same

  for s in *.*; do ffmpeg -f concat -i <(for f in $s/*.ts; do echo 'file '$PWD/$f''; done) -c copy ${s[@]%.hls/}.ts; done 

• How to resolve the issue of FFmpeg.wasm not working about SharedArrayBuffer error properly when using Nginx as a server and use Vite no error ?

  18 décembre 2023, par bully

  I am using FFmpeg.wasm for some frontend transcoding work. I know that due to certain browser policies, I need to configure some response headers in the Vite server options :
 server: { headers: { 'Cross-Origin-Opener-Policy': 'same-origin', 'Cross-Origin-Embedder-Policy': 'require-corp' } },

  


  This works fine and doesn't throw the SharedArrayBuffer error.

  


  Then, I ran yarn run build to generate the dist directory and copied it to my Nginx proxy server. I also configured similar response headers in Nginx as follows :

  


    server {
    listen 80;
    server_name ...My IP;
    add_header 'Cross-Origin-Embedder-Policy' 'require-corp';
    add_header 'Cross-Origin-Opener-Policy' 'same-origin';
    add_header 'Cross-Origin-Resource-Policy' "cross-origin";
    add_header 'Access-Control-Allow-Origin' '*';
  
    location / {
        add_header 'Cross-Origin-Embedder-Policy' 'require-corp';
        add_header 'Cross-Origin-Opener-Policy' 'same-origin';
    }

    root /www/audioserver/dist;
    ...
    }


  


  However, it doesn't work in this setup. I have been trying for a while but haven't been able to solve it.

  


  Here is my code for loading ffmpeg.wasm. It works fine in the development environment. The blob is the cached file of the wasm saved in IndexedDB :

  


  `const blob = await getWasmCoreWasm();
await this.ffmpegInstance.load({
    coreURL: await toBlobURL(`${baseURL}/ffmpeg-core.js`, 'text/javascript'),
    wasmURL: await toBlobURL(URL.createObjectURL(blob), 'application/wasm'),
    workerURL: await toBlobURL(`${baseURL}/ffmpeg-core.worker.js`, 'text/javascript'),
});
`


  


  I have tried checking the response headers of the links, updating Nginx, and even modifying the version of FFmpeg. They all seem to be fine, but I don't know how to resolve this issue. I would really appreciate it if someone could help me out. Thank you very much !