
Recherche avancée
Autres articles (99)
-
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 (...) -
Les vidéos
21 avril 2011, parComme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...) -
(Dés)Activation de fonctionnalités (plugins)
18 février 2011, parPour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)
Sur d’autres sites (10134)
-
lavu/opt : Clarify the scope of AVOptions
24 avril 2024, par Andrew Sayerslavu/opt : Clarify the scope of AVOptions
See discussion on the mailing list :
https://ffmpeg.org/pipermail/ffmpeg-devel/2024-April/326054.htmlSigned-off-by : Michael Niedermayer <michael@niedermayer.cc>
-
React-Native FFmpeg-kit VideoCompress command not working
6 septembre 2024, par BrianI'm Using FFmpeg-kit's React-Native Kit


And I want to encode H264 to HEVC.
But the Videotoolbox in ios not working


I use "ffmpeg-kit-react-native" : "^6.0.2"
And here is my Code


// hevc_videotoolbox
 await FFmpegKit.execute(`-i ${videoUri} -c:v hevc_videotoolbox -c:a aac -tag:v hvc1 -movflags +faststart -y ${outputUri}`);
 } else {
 await FFmpegKit.execute(`-i ${videoUri} -c:v hevc_omx -c:a aac -tag:v hvc1 -movflags +faststart -y ${outputUri}`);
 }



But I got the error follwed like this


LOG libavutil 58. 2.100 / 58. 2.100
 LOG libavcodec 60. 3.100 / 60. 3.100
 LOG libavformat 60. 3.100 / 60. 3.100
 LOG libavdevice 60. 1.100 / 60. 1.100
 LOG libavfilter 9. 3.100 / 9. 3.100
 LOG libswscale 7. 1.100 / 7. 1.100
 LOG libswresample 4. 10.100 / 4. 10.100
 LOG Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 
 LOG Metadata:
 LOG major_brand :
 LOG mp42
 LOG 
 LOG minor_version :
 LOG 1
 LOG 
 LOG compatible_brands:
 LOG isommp41mp42
 LOG 
 LOG creation_time :
 LOG 2024-08-29T02:42:24.000000Z
 LOG 
 LOG Duration:
 LOG 00:00:23.10
 LOG , start:
 LOG 0.000000
 LOG , bitrate:
 LOG 1223 kb/s
 LOG 
 LOG Stream #0:0
 LOG [0x1]
 LOG (und)
 LOG : Video: h264 (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 640x360 [SAR 1:1 DAR 16:9], 1220 kb/s
 LOG ,
 LOG 30 fps,
 LOG 30 tbr,
 LOG 600 tbn
 LOG (default)
 LOG 
 LOG Metadata:
 LOG creation_time :
 LOG 2024-08-29T02:42:24.000000Z
 LOG 
 LOG handler_name :
 LOG Core Media Video
 LOG 
 LOG vendor_id :
 LOG [0][0][0][0]
 LOG 
 LOG Stream mapping:
 LOG Stream #0:0 -> #0:0
 LOG (h264 (native) -> hevc (hevc_videotoolbox))
 LOG 
 LOG Press [q] to stop, [?] for help
 LOG [hevc_videotoolbox @ 0x11af89120] Error encoding frame: -12905
 LOG [hevc_videotoolbox @ 0x11af89120] popping: -542398533
 LOG [vost#0:0/hevc_videotoolbox @ 0x11af88e50] Error initializing output stream: Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
 LOG Conversion failed!



How can I fix this error ?


I read the
stack overflow






But that links doesn't work for me
I want to compress video's compressing with react-native on ios and android for reducing server cost


-
Nginx RTMP "Server Error : No Such Stream"
7 août 2024, par Tony RuthI am trying to capture and stream video within my network 10.100.64.1/24 using libnginx-mod-rtmp. I followed a tutorial. I used the same URL for publishing and playing : rtmp ://10.100.64.4/lab/test But the player does not find the stream.


My nginx settings :


rtmp {

 server {

 listen 1935;
 chunk_size 4096;
 allow publish 127.0.0.1;
 allow publish 10.100.64.4/24;
 deny publish all;
 allow play 127.0.0.1;
 allow play 10.100.64.4/24;
 deny play all;

 application lab {

 live on;
 idle_streams off;
 record all;
 record_path /media/HLEV/GoPro/Raw;
 record_unique on;
 } 
 }
} 



The server lives on 10.100.64.4, so I published a video using ffmpeg :


ffmpeg -stream_loop -1 -re -i MyVideo.flv -c:v copy -c:a aac -ar 44100 -ac 1 -f flv -flvflags no_duration_filesize rtmp://10.100.64.4/lab/test



The publishing looks good. Last line of the above command :


frame=54030 fps= 60 q=-1.0 size= 119584kB time=00:15:01.00 bitrate=1087.3kbits/s speed= 1x 



And I can see that the video is being saved locally from the record block of the nginx settings.


Then I try to play the stream using ffplay :


ffplay -i rtmp://10.100.64.4/lab/test
ffplay version 5.1.5-0+deb12u1 Copyright (c) 2003-2024 the FFmpeg developers
 built with gcc 12 (Debian 12.2.0-14)
 configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared
 libavutil 57. 28.100 / 57. 28.100
 libavcodec 59. 37.100 / 59. 37.100
 libavformat 59. 27.100 / 59. 27.100
 libavdevice 59. 7.100 / 59. 7.100
 libavfilter 8. 44.100 / 8. 44.100
 libswscale 6. 7.100 / 6. 7.100
 libswresample 4. 7.100 / 4. 7.100
 libpostproc 56. 6.100 / 56. 6.100
[rtmp @ 0x7fe7940015c0] Server error: No such stream= 0B f=0/0 
rtmp://127.0.0.1/lab/test: Operation not permitted
 nan : 0.000 fd= 0 aq= 0KB vq= 0KB sq= 0B f=0/0 



ffplay does not find the stream.


I can observe both the publish and play commands by examine the access log of nginx :


sudo tail -2 /var/log/nginx/access.log 
10.100.64.4 [07/Aug/2024:12:24:56 -0500] PUBLISH "lab" "test" "" - 45365243 529 "" "FMLE/3.0 (compatible; Lavf59.27" (5m 36s)
10.100.64.4 [07/Aug/2024:12:25:03 -0500] PLAY "lab" "test" "" - 368 412 "" "LNX 9,0,124,2" (0s)



I have tried using different video streams (directly from a webcam instead of from ffmpeg). I have also tried using different players (VLC instead of ffplay).


How do I connect to the stream ?
Do you need different URLs for publishing versus playing ? The way I understood it, publishing is on port 1395 and playing is on port 80, so there is no conflict with using the same URL.
Is there a way to list the currently active streams on my server ?