
Recherche avancée
Médias (2)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (73)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (6993)
-
ffmepg why error :Failed to write core dump
9 juillet 2021, par dmouseI wang to implement a feature that allows me to save RTSP stram as a file,
use javacv implement a demo,but there's an error.
i debug the demo , execute 'recorder.record(frame) ;' error, "ulimit -c unlimited" is useless,the program still reports an error.
review of the source code did note find the problem principle.pleace give me a hand.


import org.bytedeco.javacpp.avcodec;
import org.bytedeco.javacv.FFmpegFrameGrabber;
import org.bytedeco.javacv.FFmpegFrameRecorder;
import org.bytedeco.javacv.Frame;

import java.io.File;
import java.io.IOException;

/**
 * @ClassName video
 * @Description TODO
 * @Author mouse
 * @Date 2021/7/9 11:13
 * @Version 1.0
 **/
public class Video {
 public static void main(String[] args) {
 String streamUrl = "rtsp://admin:12345678.@192.168.20.180:554/h265/ch1/main/av_stream";
 String filePath = "./video/hello.mp3";
 File outFile = new File(filePath);
 FFmpegFrameGrabber grabber = new FFmpegFrameGrabber(streamUrl);
 if (!outFile.getParentFile().exists()) {
 outFile.getParentFile().mkdirs();
 }
 FFmpegFrameRecorder recorder = new FFmpegFrameRecorder(filePath,1080,1440, 1);
 recorder.setVideoCodec(avcodec.AV_CODEC_ID_H265);
 recorder.setFormat("flv");
 recorder.setVideoBitrate(4000);
 try {
 grabber.start();
 recorder.start();
 Frame frame = grabber.grabFrame();
 while (frame!=null){
 recorder.record(frame);
 frame = grabber.grabFrame();
 }
 recorder.record(frame);
 recorder.stop();
 grabber.stop();

 } catch (FFmpegFrameGrabber.Exception e) {
 e.printStackTrace();
 } catch (IOException e) {
 e.printStackTrace();
 } finally {
 try {
 if (recorder != null) {
 recorder.stop();
 }
 if (grabber != null) {
 grabber.stop();
 }
 } catch (FFmpegFrameRecorder.Exception | FFmpegFrameGrabber.Exception e) {
 e.printStackTrace();
 }
 }
 }
}




log error


#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000131fef233, pid=50498, tid=0x0000000000001003
#
# JRE version: Java(TM) SE Runtime Environment (8.0_281-b09) (build 1.8.0_281-b09)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.281-b09 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C [libavformat.57.dylib+0xbf233] av_write_frame+0x993
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#



pom :


<dependency>
 <groupid>org.bytedeco</groupid>
 <artifactid>javacv</artifactid>
 <version>1.4.3</version>
 </dependency>
 <dependency>
 <groupid>org.bytedeco.javacpp-presets</groupid>
 <artifactid>ffmpeg-platform</artifactid>
 <version>4.0.2-1.4.3</version>
 </dependency>



My os : macOS Bgi Sur 11.4 ;

JDK : 1.8.0_281

execute 'recorder.record(frame) ;' error,
"ulimit -c unlimited" is useless,the program still reports an error .

-
electron ffmpeg mas build "Illegal instruction : 4"
8 mars 2021, par MartinI am trying to release an electron app on the Mac Apple Store (mas), my electron app uses ffmpeg to render videos. In order to release my app on the mac apple store, It needs to be sandboxed, and by default ffmpeg makes calls to external libraries so I need to statically build ffmpeg and package it with my app. My code is on the 'mas-ffmpeg-fix' branch : https://github.com/MartinBarker/digify/tree/mas-ffmpeg-fix


My static ffmpeg build works before I build my app, but after running
electron-builder build --mac
, the ffmpeg executable now fails withIllegal instruction: 4


This is the full timeline of building/packaging/submitting my app to the mac apple store and where the error first appears :


- 

-
In Digify repo :


-
clone, configure, and build static ffpmeg : “sudo rm -rf ffmpeg-mac/ && npm run download-ffmpeg”


-
download-ffmpeg command is inside package.json and runs this :

git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac && cd ffmpeg-mac && ./configure pkg_config='pkg-config --static' --pkg-config-flags='--static' --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect && make && cd ..


-
Check if any dylibb files in the static ffmpeg build with command : “otool -L ffmpeg-mac/ffmpeg | grep /usr/local”


-
If there are any, move them to folder in desktop, run ‘otool’ again to ensure there are no dynamic libraries, rebuild static ffmpeg.


-
there will now be a folder 'ffmpeg-mac' which contains static versions of ffmpeg and ffprobe
















Using ffmpeg with electron UI : works
Using Ffmpeg with command-line command :

/Users/martinbarker/Documents/projects/digify-new/ffmpeg-mac/ffmpeg -h

Works

- 

- Build mac mass app with “npm run build-mas“
- When this command finishes it will output two files inside the /dist/mas/ folder : Digify.app and Digify-01.20.pkg (or whatever version number it is)
Ffmpeg command-line check :
/Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg -h
Illegal instruction : 4






This is the first place the error appears, after building my mac mac-apple-store app, ffmpeg fails with this err.


- 

- Sign built app with .sh file : “sh mas-sign-script.sh”
view .sh file here

- 

- the .sh file will output Digify-mac.pkg




- Easier command to both build & sign : “sudo rm -rf dist/mas/ && npm run build-mas && sh mas-sign-script.sh”
- Upload the outputted “Digify-mac.pkg” file & submit to apple for review








Once this app gets published in the store, if you download it and try to run an ffmpeg command with the electron UI, it fails with this error :


/Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/lib/error.js:59 Uncaught (in promise) Error: Command failed with exit code 1: /Applications/Digify.app/Contents/Resources/ffmpeg -i /Users/martinbarker/Downloads/Felix Lebarty - Bobo/01. Bobo.mp3 -y -filter_complex concat=n=1:v=0:a=1 -c:a libmp3lame -b:a 320k /Users/martinbarker/Downloads/Felix Lebarty - Bobo/output-064237.mp3
ffmpeg version N-101191-g51a9f487ae-ntd_20150128 Copyright (c) 2000-2021 the FFmpeg developers
 built with Apple LLVM version 10.0.1 (clang-1001.0.46.4)
 configuration: pkg_config='pkg-config --static' --pkg-config-flags=--static --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --disable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect
 libavutil 56. 65.100 / 56. 65.100
 libavcodec 58.125.100 / 58.125.100
 libavformat 58. 68.100 / 58. 68.100
 libavdevice 58. 12.100 / 58. 12.100
 libavfilter 7.107.100 / 7.107.100
 libswscale 5. 8.100 / 5. 8.100
 libswresample 3. 8.100 / 3. 8.100
 libpostproc 55. 8.100 / 55. 8.100
[mp3 @ 0x7feeae809c00] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from '/Users/martinbarker/Downloads/Felix Lebarty - Bobo/01. Bobo.mp3':
 Metadata:
 comment : 
 album : Bobo
 artist : Felix Lebarty
 title : Funkytown Eklablog
 genre : Boogie
 date : 1984
 Duration: 00:05:19.53, start: 0.000000, bitrate: 320 kb/s
 Stream #0:0: Audio: mp3, 44100 Hz, stereo, fltp, 320 kb/s
/Users/martinbarker/Downloads/Felix Lebarty - Bobo/output-064237.mp3: Operation not permitted
 at makeError (/Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/lib/error.js:59)
 at handlePromise (/Applications/Digify.app/Contents/Resources/app.asar/node_modules/execa/index.js:114)
 at async file:/Applications/Digify.app/Contents/Resources/app.asar/src/js/newindex.js:1162



Command failed with exit code 1: Operation not permitted


-
-
h274 : remove optimization pragma
25 août 2021, par Lynneh274 : remove optimization pragma
This results in warnings on compilers which don't support it,
objections were raised during the review process about it but went unnoticed,
and the speed benefit is highly compiler and version specific, and
also not very critical.We generally hand-write assembly to optimize loops like that, rather
than use compiler magic, and for 40% best case scenario, it's simply
not worth it.Plus, tree vectorization is still problematic with GCC and disabled by default
for a good reason, so enabling it locally is sketchy.