Recherche avancée

Sur d’autres sites (9431)

• ffmpeg does not recognize used codec in any way

  26 janvier 2021, par Omid Ki

  I am using ffmpeg-python to combine video and audio in my program but for one video file I constantly get this error :

  


  ffmpeg version N-55702-g920046a Copyright (c) 2000-2013 the FFmpeg developers&#xA;built on Aug 21 2013 18:10:00 with gcc 4.7.3 (GCC)&#xA;configuration: --disable-static --enable-shared --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib&#xA;libavutil      52. 42.100 / 52. 42.100&#xA;libavcodec     55. 29.100 / 55. 29.100&#xA;libavformat    55. 14.101 / 55. 14.101&#xA;libavdevice    55.  3.100 / 55.  3.100&#xA;libavfilter     3. 82.100 /  3. 82.100&#xA;libswscale      2.  5.100 /  2.  5.100&#xA;libswresample   0. 17.103 /  0. 17.103&#xA;libpostproc    52.  3.100 / 52.  3.100&#xA;[mov,mp4,m4a,3gp,3g2,mj2 @ 000000000073cb40] Could not find codec parameters for stream 0 (Video: none (av01 / 0x31307661), 2560x1440, 5427 kb/s): unknown codec&#xA;Consider increasing the value for the &#x27;analyzeduration&#x27; and &#x27;probesize&#x27; options&#xA;temp/Above NYC - Filmed in 12K.mp4: could not find codec parameters&#xA;Traceback (most recent call last):&#xA;  File "C:/Users/Family/PycharmProjects/8-bit Downloader/class_8_bit.py", line 4, in <module>&#xA;    ffmpeg.output(v, "temp/hello.mp4").run()&#xA;  File "C:\Users\Family\PycharmProjects\8-bit Downloader\venv\lib\site-packages\ffmpeg\_run.py", line 325, in run&#xA;    raise Error(&#x27;ffmpeg&#x27;, out, err)&#xA;ffmpeg._run.Error: ffmpeg error (see stderr output for detail)&#xA;</module>

  


  It just doesn't recognize it. I know that the codec is av01 I have tried passing it in as the vcodec keyword but nothing would work. I tried going to cmd directly and adding to the 'analyzeduration' and 'probsize' but nothing seems to work. How can I fix this ? My code :

  


  import ffmpeg

# I have tried passing absolute paths instead of relative ones too, still not working
input_video = ffmpeg.input("temp/Above NYC - Filmed in 12K.mp4")
input_audio = ffmpeg.input("temp/audio_temp 1.webm")
full_path = "temp/New.mp4"
out = ffmpeg.output(input_video, input_audio, full_path, vcodec='copy', acodec='aac', strict='experimental')
out.run(overwrite_output=True)


  


• hwcontext_vulkan : allow using concurrent access images with more than 5 queues

  14 mars, par Lynne

  hwcontext_vulkan : allow using concurrent access images with more than 5 queues
  This limit was not bumped when the queue family rewrite happened.
  Fixes validation issues on nvidia.
  

  • [DH] libavutil/hwcontext_vulkan.c

• Resurrecting SCD

  6 août 2010, par Multimedia Mike — Reverse Engineering

  When I became interested in reverse engineering all the way back in 2000, the first Win32 disassembler I stumbled across was simply called "Win32 Program Disassembler" authored by one Sang Cho. I took to calling it ’scd’ for Sang Cho’s Disassembler. The original program versions and source code are still available for download. I remember being able to compile v0.23 of the source code with gcc under Unix ; 0.25 is no go due to extensive reliance on the Win32 development environment.

  I recently wanted to use scd again but had some trouble compiling. As was the case the first time I tried compiling the source code a decade ago, it’s necessary to transform line endings from DOS -> Unix using ’dos2unix’ (I see that this has been renamed to/replaced by ’fromdos’ on Ubuntu).

  Beyond this, it seems that there are some C constructs that used to be valid but are now rejected by gcc. The first looks like this :

  PLAIN TEXT

  C :

  1. return (int) c = *(PBYTE)((int)lpFile + vCodeOffset) ;

  Ahem, "error : lvalue required as left operand of assignment". Removing the "(int)" before the ’c’ makes the problem go away. It’s a strange way to write a return statement in general. However, ’c’ is a global variable that is apparently part of some YACC/BISON-type output.

  The second issue is when a case-switch block has a default label but with no code inside. Current gcc doesn’t like that. It’s necessary to at least provide a break statement after the default label.

  Finally, the program turns out to not be 64-bit safe. It is necessary to compile it in 32-bit mode (compile and link with the ’-m32’ flag or build on a 32-bit system). The static 32-bit binary should run fine under a 64-bit kernel.

  Alternatively : What are some other Win32 disassemblers that work under Linux ?