
Recherche avancée
Autres articles (59)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, 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 (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (8584)
-
How to manually reset the offset of an mp4 video created from m4s files ?
12 août 2020, par natdevI'm building a service that combine
.m4s
files (from a dash stream) to amp4
video.

I have some samplem4s
files from a random point in time of a stream,

usingffmpeg
on those file + the init file does the job.

cat init.mp4 032.m4s 033.m4s 034.m4s > output.mp4



I have tried concating the
m4s
files to themp4
init file and I manage to play the video,

but there is an offset from the encoded video segments.

I guess
ffmpeg
does reset that somehow, and I was wondering how can I reset that offset as well ?

Having a little bit of experience withdash
, I know that there is a field namepresentationTimeOffset
that is responsible to set the offset.

-
Ffmpeg in docker-compose could not be started
27 mai 2021, par indexlin





I have the following
docker-compose
file but myffmpeg
container does not seem to start for some reason. It outputs a code of0
and does not give any other info.


version: '3'

networks:
 b2c:
 driver: bridge

services:
 ffmpeg:
 container_name: b2c-ffmpeg
 image: jrottenberg/ffmpeg

 nginx:
 container_name: b2c-nginx
 image: nginx:1.17.0
 depends_on:
 - "php"
 volumes:
 - ../server/public:/server/public
 - ./config/nginx/conf.d:/etc/nginx/conf.d
 - ./config/nginx/nginx.conf:/etc/nginx/nginx.conf
 - ../data/nginx/logs:/logs
 networks:
 - b2c
 ports:
 - "20001:80"

 php:
 container_name: b2c-php
 image: indexlin/gzyx-php7.2.4:1.1
 working_dir: /server
 volumes:
 - ../server:/server
 #- ./php/docker-php-ext-xdebug.ini:/usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini
 networks:
 - b2c
 ports:
 - "23001:9000"
 #user: "1000:1000"

 mysql:
 container_name: b2c-mysql
 image: mysql:5.7.21
 environment:
 MYSQL_ROOT_PASSWORD: root
 volumes:
 - ../data/mysql/lib:/var/lib/mysql
 #- ../data/mysql/log:/var/log/mysql
 - ./config/mysql/mysqld.cnf:/etc/mysql/mysql.conf.d/mysqld.cnf
 networks:
 - b2c
 ports:
 - "25001:3306"

 redis:
 container_name: b2c-redis
 image: redis:5.0.5
 volumes:
 - ../data/redis:/data
 - ./config/redis/redis.conf:/usr/local/etc/redis/redis.conf
 networks:
 - b2c
 ports:
 - "27001:6379"

 node:
 container_name: b2c-node
 volumes:
 - ../server:/server
 - ../web:/web
 image: node:10.15.3
 networks:
 - b2c
 tty: true
 working_dir: /web
 ports:
 - "29001:29000"



-
Forwarding rtsp feed from one local port to another
11 août 2021, par Thabet Sabhaso let's say I have an rtsp server running on port 554, and when a certain command is received, i want the rtsp server to start forwarding the feed (using rtsp+tcp) to a service running on the same machine but on port 553 (Linux OS), is that possible via a CL command, or do I have to use something like ffmpeg ?


currently this is what is being used, but I feel like this is redundant since all we're doing is just forwarding the feed to another port on the same machine.


const ffmpegOptions = [
"-rtsp_transport", "tcp",
"-i", "rtsp://127.0.0.1:554",
"-codec", "copy",
"-f", "rtsp",
"-rtsp_transport", "tcp",
"rtsp://127.0.0.1:553"
]

const myProcess = spawn('ffmpeg', ffmpegOptions);



Thanks.