
Recherche avancée
Autres articles (105)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
Sur d’autres sites (11524)
-
Clion is configured with FFMPEG under MAC. Missing LC_ID_DYLIB load command file
1er juin 2022, par QingGisHancmake_minimum_required(VERSION 3.21)
project(DemoExample)

set(CMAKE_CXX_STANDARD 14)

include_directories(/Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/include)
link_directories(/Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/lib)

add_executable(DemoExample main.cpp)


target_link_libraries(
 DemoExample
 swscale swresample avcodec avutil avdevice avfilter avformat
)



====================[ Build | DemoExample | Debug ]=============================
/Applications/CLion.app/Contents/bin/cmake/mac/bin/cmake --build /Users/windy/devlop/code/CLionProjects/DemoExample/cmake-build-debug --target DemoExample
[1/1] Linking CXX executable DemoExample
FAILED: DemoExample 
: && /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -g -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk -mmacosx-version-min=10.15 -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/DemoExample.dir/main.cpp.o -o DemoExample -L/Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/lib -Wl,-rpath,/Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/lib -lswscale -lswresample -lavcodec -lavutil -lavdevice -lavfilter -lavformat && :
ld: dylib /Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/lib/libswscale.dylib missing LC_ID_DYLIB load command file '/Users/windy/devlop/ffmpeg/mac_ffmpeg_lib/lib/libswscale.dylib' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.



-
FFmpeg 5 C api codec end of stream situation
11 mars 2023, par Guanyuming HeI'm new to FFmpeg api programming (I'm using version 5.1) and am learning from the documentation and official examples.


In the documentation page about send/receive encoding and decoding API overview, end of stream situation is discussed briefly :




End of stream situations. These require "flushing" (aka draining) the codec, as the codec might buffer multiple frames or packets internally for performance or out of necessity (consider B-frames). This is handled as follows :






Instead of valid input, send
NULL
to theavcodec_send_packet()
(decoding) oravcodec_send_frame()
(encoding) functions. This will enter draining mode.
Callavcodec_receive_frame()
(decoding)
oravcodec_receive_packet()
(encoding) in a loop untilAVERROR_EOF
is returned. The functions will not returnAVERROR(EAGAIN)
, unless you forgot to enter draining mode.
Before decoding can be resumed again, the codec has to be reset withavcodec_flush_buffers()
.



As I understand it, when I get
AVERROR_EOF
, I have reached a special point where I need to drain buffered data from the codec and finally reset the codec withavcodec_flush_buffers()
. Without doing it, I cannot continue decoding/encoding.

Then I have some questions :


- 

- If I received EOF when I already finished sending data (e.g. when after EOF is returned by
av_read_frame()
), how should I tell if it's really finished ? - The data returned from the
receive_...
functions during draining, should I take them as valid ?






I might have found answers to those in the official examples, but I'm not sure if the answer is universally true. I noticed that in some official examples, like in transcode_aac.c, draining is only done for the first EOF reached, and then after the second one is received, it is regarded that there are really nothing left. Any data received during draining is also written to the final output.


I just wonder, Is it true for all multimedia files in ffmpeg ?


I appreciate your response and time in advance. :)


- If I received EOF when I already finished sending data (e.g. when after EOF is returned by
-
How should one start with ffmpeg's API ?
20 mai 2018, par JoeDoughI’d like to make a real time streaming program that takes input from a webcamera, ffmpeg looks like a good library for encoding a stream of images but there is no documentation or community tutorials (there is just a doxygen API reference).Where should I start if there’s no official documentation ?