Recherche avancée

Sur d’autres sites (10346)

• Problems using Cuda for video transcoding [closed]

  19 août 2022, par Jay Adlard

  I just bought a new pc as my faithful old windows 7 i7 laptop died. Now the laptop had both intel and nvidea gtx660m chips. When I transcoded video with handbrake the intel graphics managed 8fps when I changed over to the nvidia it managed 80fps and the graphics card got nice and hot so was obviously working.

  


  The new machine i bought is a i9 with an nvidea gtx780 running windows 10. When I tried to transcode some video hoping for it to use the cpu and Gpu but no joy,the card stays cool power usage is only a handful of watts higher than it running something simple.I had been using handbrake but I read it doesn’t support Cuda so why the laptop speeded up I don’t know. A friend of mine that is into ffmpeg came round found that ffmpeg reports no Cuda yet the card works fine in every other respect. Unlike the rest of the machine the graphics card wasn’t new but it looked like new…

  


  One thing to note I am not talking about nvenc as the quality is rather poor, no point in capturing uncompressed files cleaning them up and not using an encoder that will do 2 pass and an exhaustive search.
Can anyone recommend a reasonably priced encoder that will use the Cuda cores ?

  


  Has anyone got any idea what the problem is ?

  


• FFMPEG and HTTPS

  14 juin 2012, par Joel

  ffmpeg lists http as a protocol when I ask : ffmpeg -protocols

  Does this also mean support for a https url ? Do I need to encode this url somehow for the command line. I get "No such file or directory", but with http urls (at least some) it does work.

  A url (created for a Amazon S3 bucket) similar to this one does not seem to work :
  https://mycompany-video-test.s3.amazonaws.com/client/btr/video/xyz0011-x403-snap-n-go-ex/1/video/baby-laugh-ripping-paper.mp4?AWSAccessKeyId=AVIAZL9J6SIRPAA&Expires=1323709667&Signature=pTvS9F2do2t8%3D

  I suspect the format of the url is problematic, I've also tried enclosing in quotes... Yes, this URL does not currently work as it has expired, but even while its valid, its a problem.

  In short :
  1) Should https work ?
  2) Do I need to format the url somehow ?

• ffmpeg not working with filenames that have whitespace

  1er avril 2017, par cmw

  I’m using FFMPEG to measure the duration of videos stored in an Amazon S3 Bucket.

  I’ve read the FFMPEG docs, and they explicitly state that all whitespace and special characters need to be escaped, in order for FFMPEG to handle them properly :

  See docs 2.1 and 2.1.1 : https://ffmpeg.org/ffmpeg-utils.html

  However, when dealing with files whose filenames contain whitespace, ffmpeg fails to render a result.

  I’ve tried the following, with no success

  ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
  
  ffmpeg -i "http://s3.mybucketname.com/videos/my video file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
  
  ffmpeg -i "http://s3.mybucketname.com/videos/my'\' video'\' file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d
  
  ffmpeg -i "http://s3.mybucketname.com/videos/my\ video\ file.mov" 2>&1 | grep Duration | awk '{print $2}' | tr -d

  However, if I strip out the whitespace in the filename – all is well, and the duration of the video is returned.

  Any help is appreciated !