Recherche avancée

Sur d’autres sites (5191)

• what codec to specify to accessing my HDMI-to-USB adaptor, under Linux ? [closed]

  14 mai 2022, par David

  A week or so ago,I bought a HDMI-to-USB adapter, to use to capture video
TV content from my TV's set-top box. (Xfinity, if it matters. Box generically is :
"XiD X1"...I have both the Pace and the Cisco models available here in this house.)

  


  Specifically, here's the adapter I bought,from Amazon :
https://www.amazon.com/gp/product/B09FLN63B3

  


  So, I'm fluent in both Windows (Win-11) and Linux (Debian 'Bullseye', on my chromebook).

  


  The adapter does not come with any recommendations for what software/drivers to (try to) use, but I was prepared for that.
After some google searches, I decided to first try using the cmd-line
'ffmpeg' program, because I'm
quite familiar with that (excellent !) piece of open-source software !

  


  So, after a day or two of (mostly) success recordings under Win-11, using
ffmpeg's Microsoft-based 'dshow' (aka 'DirectShow'), I decided to attempt to get
up to the same level of accomplishment on my Chromebook, under Linux, also
using 'ffmpeg'.

  


  [Ok...a very brief explanation of 'mostly' successful. I'll
post another separate question here, about the specifics of my glitches,
using 'dshow' on Windows. But, essentially, when I try to record to a MP4
file, I get 2 scenarios of glitch : #1 : Suddenly, dropped packets surges up,
and I get "1000 dropped' yellow msg #2 : On other trials, I get '...contains
no image...'.) So, I figured I should first give a Linux a chance,
before spending more effort trying to resolve the glitches on Windows.]

  


  My first snag, was learning that 'dshow' seems to be specific to 'Windows',
and thus ffmpeg is getting 'unknown' for my reference to 'dshow'. After more hours of 'guessing', I've finally learned/concluded that there are other things
(something call "DeckLink" is one such alternative ?) for Linux, but I'm unclear
what extra Linux packages might exist for ffmpeg support, or whether I will need to built a more complete 'ffmpeg' (e.g. from source code), to get things going under Linux ?

  


  Is my device able to be accessed from some tools other than 'ffmpeg' ?
(e.g. VLC or Handbrake or whatever ?) more easily, on the Linux platform ?

  


  [If I had to, I'd probably invest another $20-$50 in some other hardware
device that goes from HDMI-to-USB (USB-A/B), if it were ]

  


  All ideas are welcome...(TIA)

  


  — Dave

  


• AWS Lambda and Fluent FFMPEG error "cannot read property "isStream" of undefined"

  29 mai 2021, par Travis Lee

  so here's the goal : convert a .webm file hosted in an S3 into a gif and upload that to a new bucket. This all works fine when run locally, but when trying to translate it into a lambda, fluent-ffmpeg throws errors when it runs the command.

  


  Here's the code snippet :

  


  ffmpeg(new URL(vid))
  .outputOptions("-vf", "scale=320:-1:flags=lanczos,fps=14")
  .on('progress', () => {
      console.log('progress');
  })
  .on('end', () => {
     //Do stuff with the result when it is done
  })
  .output(newKey)
  .run(newKey);


  


  in this snippet, "vid" is a presigned GET url for an S3 bucket containing the .webm video file, and "newKey" is the name of the new bucket (and a temporary writeStream/File that is created in the lambda to store the new .gif file until we upload it to S3 - not super relevant to this issue).

  


  What should happen (and does locally) is that a new output is created containing the converted .gif file

  


  What happens when it is deployed in a lambda is that it reaches the .outputOptions call and throws a type error saying that it cannot read property isStream of undefined.

  


  At first glance, this seems like I simply don't have FFMPEG installed in the lambda, but I do. I have tried with the prebuilt layer using NodeJS 10 found here : https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/ffmpeg-lambda-layer ,
with a NodeJS 12 layer that was built by some engineers here previously, and tried building a NodeJS 14 FFMPEG layer myself and using that. I tried for all three using no configuration and letting it call the PATH ffmpeg, using the FFMPEG_PATH and FFPROBE_PATH environment variables set to either what was specified in the previous layers, or what I made it in the newly built one, and even manually setting the path to the executables using the setFfmpegPath and setFfprobePath functions found on the fluent-ffmpeg object.

  


  Lastly, I even tried bundling the executables in with the actual lambda code itself and uploading it through an S3, trying all three above methods of getting it to point to the correct paths once again to no avail.

  


  I'm seriously in need of help if anyone else has encountered something similar or just might know what is going on. I'm at wit's end here trying to figure this out.

  


• How to send ffmpeg based HTTP stream to CloudFront [on hold]

  5 octobre 2017, par Tarun Maheshwari

  I have a live streaming server, where media is available as HTTP / RTMP / HLS format.
  I am able to access it and play from my desktop using following links.

   rtmp://52.xx.xx.192/live/tarun1 (RTMP)
  
   http://52.xx.xx.192:8080/hls/movie.m3u8 (HLS)
  
   http://52.xx.xx.190:7090/stream (HTTP)

  I want to forward any of the above streams to CloudFront with these steps.