
Recherche avancée
Autres articles (63)
-
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...) -
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 -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (11306)
-
Node Media Server not stream when i try to pass the argument "transpose=1" to ffmpeg
28 mai 2020, par joao.jlf4I'm using node-media-server to stream to instagram, and i need to rotate the original vídeo, to be portrait. I know that there is a flag on ffmpeg called transpose (there is rotate too), but when i pass it on node_relay_session.js on 24 line at the argv array, it returns me a "[Relay end]" on console, and it does'nt stream. When I remove the transpose flag from argv array it backs to stream normaly. Here is my config to nms :



import NodeMediaServer from 'node-media-server';
import removeBarOfRtmpUrl from './utils/removeBarRtmpUrl';
import path from 'path';
import { remote } from 'electron';

export default function(data) {

const streams = data.map(stream => ({
endpoint: removeBarOfRtmpUrl(stream.endpoint),
key: stream.key,
}))

const config = {
rtmp: {
port: 1935,
chunk_size: 60000,
gop_cache: true,
ping: 30,
ping_timeout: 60
},
http: {
port: 8000,
allow_origin: '*'
},
relay: {
// C:\Users\Usuario\Desktop\multistream\node_modules.bin\ffmpeg.exe
ffmpeg: path.join(remote.app.getPath('appData'), '..', 'Local', 'Programs', 'multistream', 'app', 'ffmpeg', 'bin', 'ffmpeg.exe'),
tasks: streams.map(stream => ({
app: 'live',
mode: 'push',
edge: ${stream.endpoint}/${stream.key},

 }))
},
};

const nms = new NodeMediaServer(config);
return nms;
}

// {
// app: 'live',
// mode: 'push',
// edge: 'rtmp://a.rtmp.youtube.com/live2/keyyoutube',
// },```



-
converting a "gif" to video using swift
3 décembre 2019, par James WoodrowI’ve looked around and found a few things here and there, mainly that I should be using AVAssetWriter to do this but I have 0 experience with this and video editing/creation so it doesn’t help me much since I can’t seem to find anything that does something I can modify easily (or not at my level of knowledge at least) so that it works as I intend it to.
I have an app which takes
n
photos everycft
(capture frame time which I get from a backend server) seconds (it’s a double for obvious reasons) I then display these frames using a UIImageView and the frames change everydft
(display frame time which I also get from a backend server and can be different fromcft
). Up until this point nothing complicated.now what is currently the workflow is that these frames are sent back to a server with any relevant information I want and then the server would use imagemagick to create a real gif file and ffmpeg to create a 15 seconds video using said gif.
the issue is this makes it so that my heroku server bills aren’t as low as I would like because of the limited memory on the dynos and the time it takes to generate these videos is of about 5-10 seconds I believe (not sure but it’s longer than I’d like)
So the idea I had was to make the app create the video since he already has all the information he needs for this, and then simply upload it with the rest of the frames and relevant data. Using bandwidth nowadays is much cheaper than buying extra processing power on a server.
- he has
n
frames to loop over - he has a float value representing how long each frame should last
dft
- he has a gpu or at least a much better cpu than the dynos heroku have to offer
I’ve also looked around to see if anyone made an extensive tutorial on how to use ffmpeg in swift but I still didn’t find anything at my level and I didn’t even find a tutorial per se, only some GitHub projects which were partially completed and/or without the original tutorial linked to understand the thought process.
I would appreciate any tips/code sample/tutorials on the subject.
I’m adding the ffmpeg command line equivalent to what I would love to be able to do (if I could use ffmpeg directly with iOS this could be nice too)
ffmpeg -framerate 100/13 -loop 1 -i frame%02d.png -c:v libx264 -r 100/13 -pix_fmt yuv420p -t 0:15 instagram.mp4
where basically I did
100 / (dft * 100)
for the input frame rate and just output at the same fps for 15 seconds. by the way if there are any ways to optimise this command to make it run faster without losing quality I might be able to keep the current way of functioning with heroku although I would still prefer some iOS solution. - he has
-
FFmpeg "no frame !" encoding error
9 juillet 2015, par oleg.semenI’m trying to compress video by scaling it. Here is how
But I’m getting this error :D/FFMpeg﹕ progress[h264 @ 0x42124970] no frame!
D/FFMpeg﹕ progress[aac @ 0x42122fe0] Input buffer exhausted before END element foundhere is whole log :
Loading FFmpeg for armv7-neon CPU
start
Running publishing updates method
progressWARNING: linker: /data/data/com.example.ffmpeg/files/ffmpeg has text relocations. This is wasting memory and is a security risk. Please fix.
progressffmpeg version n2.4.2 Copyright (c) 2000-2014 the FFmpeg developers
progress built on Oct 7 2014 15:08:46 with gcc 4.8 (GCC)
progress configuration: --target-os=linux --cross-prefix=/home/sb/Source-Code/ffmpeg-android/toolchain-android/bin/arm-linux-androideabi- --arch=arm --cpu=cortex-a8 --enable-runtime-cpudetect --sysroot=/home/sb/Source-Code/ffmpeg-android/toolchain-android/sysroot --enable-pic --enable-libx264 --enable-libass --enable-libfreetype --enable-libfribidi --enable-fontconfig --enable-pthreads --disable-debug --disable-ffserver --enable-version3 --enable-hardcoded-tables --disable-ffplay --disable-ffprobe --enable-gpl --enable-yasm --disable-doc --disable-shared --enable-static --pkg-config=/home/sb/Source-Code/ffmpeg-android/ffmpeg-pkg-config --prefix=/home/sb/Source-Code/ffmpeg-android/build/armeabi-v7a-neon --extra-cflags='-I/home/sb/Source-Code/ffmpeg-android/toolchain-android/include -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-strict-overflow -fstack-protector-all -mfpu=neon' --extra-ldflags='-L/home/sb/Source-Code/ffmpeg-android/toolchain-android/lib -Wl,-z,relro -Wl,-z,now -pie' --extra-libs='-lpng -lexpat -lm' --extra-cxxflags=
progress libavutil 54. 7.100 / 54. 7.100
progress libavcodec 56. 1.100 / 56. 1.100
progress libavformat 56. 4.101 / 56. 4.101
progress libavdevice 56. 0.100 / 56. 0.100
progress libavfilter 5. 1.100 / 5. 1.100
progress libswscale 3. 0.100 / 3. 0.100
progress libswresample 1. 1.100 / 1. 1.100
progress libpostproc 53. 0.100 / 53. 0.100
progress[h264 @ 0x42124970] no frame!
progress[aac @ 0x42122fe0] Input buffer exhausted before END element found
progressInput #0, mov,mp4,m4a,3gp,3g2,mj2, from '/storage/emulated/0/Movies/Instagram/VID_37551017_035953.mp4':
progress Metadata:
progress major_brand : isom
progress minor_version : 0
progress compatible_brands: isom3gp4
progress creation_time : 2015-06-19 09:03:19
progress Duration: 00:00:03.20, start: 0.000000, bitrate: 2975 kb/s
progress Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x640, 2911 kb/s, 15.22 fps, 14.92 tbr, 90k tbn, 180k tbc (default)
progress Metadata:
progress creation_time : 2015-06-19 09:03:19
progress handler_name : VideoHandle
progress Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 101 kb/s (default)
progress Metadata:
progress creation_time : 2015-06-19 09:03:19
progress handler_name : SoundHandleDid I miss something in config ?
Thanks.