
Recherche avancée
Autres articles (61)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
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 ;
-
Dépôt de média et thèmes par FTP
31 mai 2013, parL’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)
Sur d’autres sites (10914)
-
Making colour of MP4 video consistent in Chrome
21 septembre 2021, par OneWorldI see a difference in the colour of a video between different machines using different browsers. I was wondering what the cause of the difference is ?


I use FFMPEG to create the video. I sent the video to three different people with slightly different machines, and slightly different Chrome versions, to try and see where the differences are.


The FFMPEG output from the video is as follows :-


ffmpeg version 3.2.2-static http://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2016 the FFmpeg developers
 built with gcc 5.4.1 (Debian 5.4.1-4) 20161202
 configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-5 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gray --enable-libass --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg
 libavutil 55. 34.100 / 55. 34.100
 libavcodec 57. 64.101 / 57. 64.101
 libavformat 57. 56.100 / 57. 56.100
 libavdevice 57. 1.100 / 57. 1.100
 libavfilter 6. 65.100 / 6. 65.100
 libswscale 4. 2.100 / 4. 2.100
 libswresample 2. 3.100 / 2. 3.100
 libpostproc 54. 1.100 / 54. 1.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'red_and_yellow_uat.mp4':
 Metadata:
 major_brand : isom
 minor_version : 512
 compatible_brands: isomiso2avc1mp41
 encoder : Lavf57.56.100
 Duration: 00:00:03.00, start: 0.000000, bitrate: 84 kb/s
 Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p(tv, unknown/bt709/bt709), 1080x1080, 81 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
 Metadata:
 handler_name : VideoHandler



From the same UAT rendered Video, with screenshots taken in Chrome from person 1, person 2, person 3, and person 4, and using GIMP colour picker on my machine from the screenshots, the results for red, and yellow are as follows.


Person 1:- #A83833 and #FFCB2E Chrome Version 92.0.4515.131 (Official Build) (64-bit)
Person 2:- #AB3334 and #FFCA38 Chrome Version 92.0.4515.107



(Note : these colours Match / are very close to the original).


Both these machines above are 64 bit Ubuntu machines, using Ubuntu 18.04.5 LTS
We both use the gnome screenshot tool in Ubuntu to take the screenshot, which creates an 8bit PNG.


Person 3:- #B14039 and #FED303 Chrome Version 93.0.4577.63 (Official Build) (x86_64)
Person 4:- #B2403A and #FFD201 Chrome Version 92.0.4515.159 (Official Build) (x86_64)



Mac screenshots are taken using cmd shift 4, and generate an 8bit PNG file.


Person 3 Machine Spec :-
Machine :- Macbook Pro (2019)
OS : macOS Big Sur Version 11.5.2
Processor :- 2.6Ghz Intel Core i7 processor. 32bit architecture (typing arch in her tty terminal returns i386).
Graphics :- Intel UHD Graphics 630 1536


Person 4 Machine Spec :-
Machine :- Macbook Pro (Retina, 2015)
OS :- MacOS Mojave, Version 10.14.6
Processor :- 2.5GHz, Intel Core i7
Graphics :- AMD Radeon R9, M370X 2 GB Intel Iris Pro 1536 MB


Person 1 screenshot




Person 2 screenshot




Person 3 screenshot




Person 4 screenshot




Any suggestions anyone has to make these colours consistent would be much appreciated. Would love to know why it happens also ? If anyone can explain ?


-
How to build FFmpeg with Apple Symbols ?
22 septembre 2021, par Meh.MOVED FROM : https://superuser.com/questions/1676856/how-to-build-ffmpeg-with-apple-symbols?noredirect=1#comment2572799_1676856


I'm trying to build
FFmpeg 3.2.4
withOpenSSL >= 2.0.7
(3.0.0) from source so I can use it's binaries to build Dolphin-Emu.

I just do this :
./configure --enable-gnutls
and when I build withmake -j5
(-j5 speeds up the process) thenmake install
. When I use it in compiling Dolphin , I get an error somewhat like this :

Undefined symbols for architecture x86_64:
 "_kCVImageBufferColorPrimaries_ITU_R_709_2", referenced from:
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 "_kVDADecoderConfiguration_SourceFormat", referenced from:
 "_kCVImageBufferTransferFunction_ITU_R_2020", referenced from:
 _ff_vda_create_decoder in libavcodec.a(vda_h264.o)
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 "_kVDADecoderConfiguration_avcCData", referenced from:
 "_CMBlockBufferCopyDataBytes", referenced from:
 _ff_vda_create_decoder in libavcodec.a(vda_h264.o)
 _vtenc_frame in libavcodec.a(videotoolboxenc.o)
 "_kCVImageBufferYCbCrMatrixKey", referenced from:
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 _vtenc_send_frame in libavcodec.a(videotoolboxenc.o)
 "_SSLSetCertificate", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_CMTimeMake", referenced from:
 _vtenc_send_frame in libavcodec.a(videotoolboxenc.o)
 "_kCVPixelBufferWidthKey", referenced from:
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 "_VDADecoderCreate", referenced from:
 _ff_vda_create_decoder in libavcodec.a(vda_h264.o)
 "_kVTProfileLevel_H264_High_4_2", referenced from:
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
 "_kCVPixelBufferIOSurfacePropertiesKey", referenced from:
 _ff_vda_create_decoder in libavcodec.a(vda_h264.o)
 "_kVTProfileLevel_H264_Baseline_1_3", referenced from:
 _vtenc_init in libavcodec.a(videotoolboxenc.o)
(example)



These
_kV(blahblahblah)
symbols are provided by Apple... under<coremedia></coremedia>CoreMedia.h>
so my mac should DEFINITELY have this. OpenSSL version is 3.0.0 as there's an error about_SSLSetCertificate
not existing.

Does anyone have any ideas why this is throwing undefined symbols for existing symbols ? (My FFmpeg is compiled by
clang
whenever I use make, and I use gnutls(installed by brew) which should rely on openssl3.0)

Xcode version : 11.3.1 (Only has macos 10.15 SDK)


Linker command to link Dolphin and FFmpeg w/ OpenSSL binaries/libs


/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk -mmacosx-version-min=10.14.0 -Wl,-search_paths_first -Wl,-headerpad_max_install_names -L/usr/local/lib -Wl,-dead_strip,-dead_strip_dylibs CMakeFiles/dolphin-nogui.dir/Platform.cpp.o CMakeFiles/dolphin-nogui.dir/PlatformHeadless.cpp.o CMakeFiles/dolphin-nogui.dir/MainNoGUI.cpp.o -o ../../../Binaries/dolphin-emu-nogui ../Core/libcore.a ../UICommon/libuicommon.a ../../../Externals/cpp-optparse/libcpp-optparse.a ../VideoBackends/Null/libvideonull.a ../VideoBackends/OGL/libvideoogl.a ../VideoBackends/Software/libvideosoftware.a ../VideoBackends/Vulkan/libvideovulkan.a ../VideoCommon/libvideocommon.a ../Core/libcore.a ../VideoBackends/Null/libvideonull.a ../VideoBackends/OGL/libvideoogl.a ../VideoBackends/Software/libvideosoftware.a ../VideoBackends/Vulkan/libvideovulkan.a ../VideoCommon/libvideocommon.a ../AudioCommon/libaudiocommon.a /usr/local/lib/libpulse.dylib ../../../Externals/soundtouch/libSoundTouch.a ../../../Externals/FreeSurround/libFreeSurround.a ../../../Externals/cubeb/libcubeb.a -framework AudioUnit -framework CoreAudio -framework CoreServices ../DiscIO/libdiscio.a /usr/lib/libbz2.dylib ../../../Externals/liblzma/liblzma.a ../../../Externals/zstd/libzstd.a ../InputCommon/libinputcommon.a -framework Carbon -framework ForceFeedback /usr/local/lib/libSDL2.dylib -framework Cocoa ../../../Externals/SFML/libsfml-network.a ../../../Externals/SFML/libsfml-system.a ../../../Externals/LZO/liblzo2.a -framework CoreServices -framework IOBluetooth ../../../Externals/mGBA/mgba/libmgba.a -framework Foundation -lm ../../../Externals/hidapi/libhidapi.a ../../../Externals/glslang/libglslang.a ../../../Externals/xxhash/libxxhash.a ../../../Externals/imgui/libimgui.a /usr/local/lib/libavformat.a /usr/local/lib/libavcodec.a /usr/local/lib/libswscale.a /usr/local/lib/libavutil.a ../Common/libcommon.a ../../../Externals/enet/libenet.a ../../../Externals/mbedtls/library/libmbedtls.a ../../../Externals/mbedtls/library/libmbedx509.a ../../../Externals/mbedtls/library/libmbedcrypto.a /usr/lib/libcurl.dylib /usr/lib/libiconv.dylib ../../../Externals/libpng/libpng.a -framework AppKit ../../../Externals/miniupnpc/libminiupnpc.a ../../../Externals/pugixml/libpugixml.a ../../../Externals/fmt/libfmt.a ../../../Externals/Bochs_disasm/libbdisasm.a ../../../Externals/libusb/libusb.a -framework CoreFoundation -framework IOKit /usr/lib/libobjc.dylib ../../../Externals/minizip/libminizip.a /usr/lib/libz.dylib ../../../Externals/discord-rpc/src/libdiscord-rpc.a -lpthread -framework AppKit 



-
x86/tx_float : do not build tx_float_init.c if x86 assembly is disabled
26 janvier 2022, par Lynnex86/tx_float : do not build tx_float_init.c if x86 assembly is disabled
This broke builds with —disable-mmx, which also disabled assembly
entirely, but ARCH_X86 was still true, so the init file tried to find
assembly that didn't exist.
Instead of checking for architecture, check if external x86 assembly
is enabled.