Recherche avancée

Sur d’autres sites (3345)

• Révision 116184 : Mise a jour de la lib CSSTidy an v1.7.0 : support de @support et @media imbriques

  31 juillet 2019, par cedric@yterium.com

• How to correctly specify the path to a file in -vf media ?

  15 juillet 2024, par Wintreist

  Good afternoon, please, I really need help.
I'm putting a watermark on the video :

  


  with tempfile.TemporaryFile("wb", delete=False, suffix=".png") as watermark_file:
    watermark_file.write(buff.read())
(
    ffmpeg
    .input(str(path))
    .output(
        os.environ.get("TEMP")+f"\\{uuid.hex}_{path.name}",
        vf=f"movie='{watermark_file.name}' [watermark]; [in][watermark] overlay='{overlay}' [out]"
    )
    .global_args('-copyts')
    .run()
)


  


  In a temporary folder, I create a file in which I write a watermark from io.BytesIO
using the ffmpeg-python library, I do not work directly with the console.

  


  The problem is that when running .run() to the console outputs the following :

  


  [Parsed_movie_0 @ 0000011b21b3e300] Failed to avformat_open_input 'C'
[AVFilterGraph @ 0000011b21b4d4c0] Error initializing filters
[vost#0:0/libvpx-vp9 @ 0000011b23a07500] Error initializing a simple filtergraph
Error opening output file C:\Users\smeta\AppData\Local\Temp\5e5a695966cf4d728edbd7f39c509d0e_000.webm.
Error opening output files: No such file or directory


  


  But if I copy a watermarked file from temp and upload it to the workspace :
vf=f"movie='{'test.png'}' [watermark]; [in][watermark] overlay='{overlay}' [out]"
then everything works as it should. I.e. apparently there is a problem with the path to the watermark, and I do not understand what to do.
I ask for help

  


• Media conversion on AWS

  27 juin 2022, par Gurmeet Singh

  I have an API written in nodeJS (/api/uploadS3) which is a PUT request and accepts a video file and a URL (AWS s3 URL in this case). Once called its task is to upload the file on the s3 URL.

  


  Now, users are uploading files to this node API in different formats (thanks to the different browsers recording videos in different formats) and I want to convert all these videos to mp4 and then store them in s3.

  


  I wanted to know what is the best approach to do this ?

  


  I have 2 solutions till now

  


  1. Convert on node server using ffmpeg -

  


  The issue with this is that ffmpeg can only execute a single operation at a time. And since I have only one server I will have to implement a queue for multiple requests which can lead to longer waiting times for users who are at the end of the queue. Apart from that, I am worried that during any ongoing video conversion if my node's traffic handling capability will be affected.

  


  Can someone help me understand what will be the effect of other requests coming to my server while video conversion is going on ? How will it impact the RAM, CPU usage and speed of processing other requests ?

  


  2. Using AWS lambda function -

  


  To avoid load on my node server I was thinking of using an AWS lambda server where my node API will upload the file to S3 in the format provided by the user. Once, done s3 will trigger a lambda function which can then take that s3 file and convert it into .mp4 using ffmpeg or AWS MediaConvert and once done it uploads the mp4 file to a new s3 path. Now I don't want the output path to be any s3 path but the path that was received by the node API in the first place.

  


  Moreover, I want the user to wait while all this happens as I have to enable other UI features based on the success or error of this upload.

  


  The query here is that, is it possible to do this using just a single API like /api/uploadS3 which —> uploads to s3 —> triggers lambda —> converts file —> uploads the mp4 version —> returns success or error.

  


  Currently, if I upload to s3 the request ends then and there. So is there a way to defer the API response until and unless all the operations have been completed ?

  


  Also, how will the lambda function access the path of the output s3 bucket which was passed to the node API ?

  


  Any other better approach will be welcomed.

  


  PS - the s3 path received by the node API is different for each user.