Recherche avancée

Sur d’autres sites (7359)

• ffmpeg waits to close the pipe in order to start processing data

  15 juin 2022, par Mahmoud Ferig

  I'm struggling with this issue.
Here I am trying to stream video using ffmpeg from images and audio file this code below works fine but it is start streaming after stdin closed, I would expect ffmpeg to start processing the pipe input as it is received, and immediately output the result.

  


  p = subprocess.Popen(
    [
        'ffmpeg',
        '-y',
        '-re',
        '-f', 'image2pipe',
        '-vcodec', 'mjpeg',
        '-framerate', '15',
        '-analyzeduration', '2147483647',
        '-probesize', '2147483647',
        '-i', '-',
        '-vn', '-i', audio_path,
        '-c:v', 'libx264',
        '-pix_fmt', 'yuv420p',
        '-preset', 'ultrafast',
        '-c:a', 'aac',
        '-f', 'flv',
        rtmp_url
    ],
    stdin=subprocess.PIPE,
    stdout=subprocess.PIPE
)

time.sleep(2)

i = 0
while True:
    current_images = [name for name in os.listdir(img_dir) if os.path.isfile(os.path.join(img_dir, name))]
    current_images = sorted(current_images)
    if i > fnum-1:
        print("frame read failed")
        break
    try:
        img = cv2.imread(os.path.join(img_dir, current_images[i]))
        success, buffer = cv2.imencode('.jpg', img)
        frame = buffer.tobytes()
        p.stdin.write(frame)
        i += 1
    except:
        time.sleep(2)
        pass

p.stdin.close()
p.wait()


  


  Why is ffmpeg waiting to close the pipe to start processing ? Can it be configured to start a live transcoding of the received stream ?

  


  Do you know how can I convince ffmpeg to start producing output immediately ?

  


  Thank you !

  


• avformat/mov : Non overflowing ambisonic order check

  25 mars 2022, par Michael Niedermayer

  avformat/mov : Non overflowing ambisonic order check
  Fixes : signed integer overflow : 536870913 * 536870913 cannot be represented in type 'int'
  
  Fixes : 45862/clusterfuzz-testcase-minimized-ffmpeg_dem_MOV_fuzzer-4730373768085504
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/mov.c

• Location of the amd64 compiler in Visual Studio 2022 | Compiling FFmpeg with NVENC

  6 juin 2022, par Gal Grünfeld

  I'm trying to follow Nvidia's guide to compile FFmpeg with nvenc support on Windows and it has a stage to export the path of Visual Studio's 2013 SP2 amd64 compiler to the global path variable of the compilation dev environment :

  


  


  export PATH="/c/Program Files (x86)/Microsoft Visual Studio 12.0/VC/BIN/amd64/" :$PATH

  


  


  They say earlier in the guide that for different versions of Visual Studio different path might be required. I'm trying to use Visual Studio 2022 Community, but don't know where its amd64 compiler directory is.
I also don't know what that VC stands for ("Visual C", maybe, whatever that "Visual" might mean ?).

  


  I found in the installation directory of Visual Studio 2022 a few directories named amd64 but none of them were under one with VC or something similar in its name.
The one I think is the most likely candidate to be the updated compiler is at /MSBuild\Current\Bin\amd64.

  


  If anyone knows, please tell me if if this is the right path, and if not, what is the right path.

  


  Microsoft does offer a version of Visual Studio 2013 Update 2, though (I assume they changed their naming scheme from "service packs" to "updates, which would make it the same software), but it doesn't offer a 64-bit version of it, and I want to compile a 64-bit software - so I assume it doesn't come with one. Please do correct me if I'm wrong, it'd save me needing to use a version of Visual Studio that is different than the one in the guide.