
Recherche avancée
Médias (2)
-
Valkaama DVD Label
4 octobre 2011, par
Mis à jour : Février 2013
Langue : English
Type : Image
-
Podcasting Legal guide
16 mai 2011, par
Mis à jour : Mai 2011
Langue : English
Type : Texte
Autres articles (90)
-
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 ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
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
Sur d’autres sites (8551)
-
How to get a 7.1 PCMle encode in an MOV container to stay a single track while also rendering as 8 mono tracks in an NLE like an MXF container
26 février 2024, par varys_da_spidahI've been trying to convert Blu-Ray footage to the most efficient, yet least time consuming format for editing footage from them. For a while, I would make an MXF container and encode the h264 to DNxHD and the lossless compressed audio to pcm_s24le. I really liked how convenient it was to have my audio linked to my video, how it could be played as a single track in a media player, but then be inserted into my NLE as 6-8 separate mono tracks.


However, I found the DNxHD encodes to be unnecessary as they took up too much storage space and my NLE could perfectly handle the original h264 files in an MOV or MP4 container. But I noticed that switching from MXF to an MOV container meant that things that were jettisoned from the former were in the latter. Some of this was actually welcome, like the chapter markers, but I noticed that 7.1 audio (but not 5.1 for some reason) would now render in my NLE as a single 7.1 track.


I looked in MediaInfo and think I figured out that the issue is that the MOV container formats the channel layout while the MXF one doesn't. I'll paste the info to show what I mean


MOV FILE




- 

- ID : 2
- Format : PCM
- Format settings : Little / Signed
- Codec ID : in24
- Duration : 1 min 41 s
- Bit rate mode : Constant
- Bit rate : 9 216 kb/s
- Channel(s) : 8 channels
- Channel layout : L R C LFE Ls Rs Lb Rb
- Sampling rate : 48.0 kHz
- Bit depth : 24 bits
- Stream size : 111 MiB (34%)
- Title : English
- Language : English
- Default : Yes
- Alternate group : 1
- Menus : 3






































MXF FILE




- 

- ID : 3
- Format : PCM
- Format settings : Little
- Format settings, wrapping mode : Frame (AES)
- Codec ID : 0D01030102060300
- Duration : 1 min 13 s
- Bit rate mode : Constant
- Bit rate : 9 216 kb/s
- Channel(s) : 8 channels
- Sampling rate : 48.0 kHz
- Frame rate : 23.976 FPS (2002 SPF)
- Bit depth : 24 bits
- Stream size : 81.1 MiB (5%)
- Delay_SDTI : 0
- Locked : Yes


































Any ideas ?


I tried this code :


ffmpeg -i "INPUT.mkv" -c:v copy -r 23.976 -c:a pcm_s24le -filter_complex "[0:a:0]pan=mono|c0=c0[a0]; [0:a:1]pan=mono|c0=c0[a1]; [0:a:2]pan=mono|c0=c0[a2]; [0:a:3]pan=mono|c0=c0[a3]; [0:a:4]pan=mono|c0=c0[a4]; [0:a:5]pan=mono|c0=c0[a5]; [0:a:6]pan=mono|c0=c0[a6]; [0:a:7]pan=mono|c0=c0[a7]; [a0][a1][a2][a3][a4][a5][a6][a7]amerge=inputs=8" "OUTPUT.mov”


And got this error message :


Stream specifier ':a:4' in filtergraph description [0:a:0]pan=mono|c0=c0[a0]; [0:a:1]pan=mono|c0=c0[a1]; [0:a:2]pan=mono|c0=c0[a2]; [0:a:3]pan=mono|c0=c0[a3]; [0:a:4]pan=mono|c0=c0[a4]; [0:a:5]pan=mono|c0=c0[a5]; [0:a:6]pan=mono|c0=c0[a6]; [0:a:7]pan=mono|c0=c0[a7]; [a0][a1][a2][a3][a4][a5][a6][a7]amerge=inputs=8 matches no streams.


-
How can I add chapters to a mp4 file using bash script and ffmpeg
17 septembre 2023, par Rick TI'm trying to add chapters to an mp4 file using bash and ffmpeg. The chapters are located in a file called
chapters.txt
. When the bash script is run which is calledadd_chapters.sh
it reads thechapters.txt
file and creates a file calledchapters.ffmetadata
. The issue is that theSTART
andEND
times in the filechapters.ffmetadata
aren't being created correctly. How can I fix this ?

- 

-
I have a file called
chapters.txt
that has the chapters in it.

00:00:00=Intro
00:02:12=What are selections
00:03:19=Booleans



-
The bash file I run is
add_chapters.sh


The code in it is :


#!/bin/bash

input_file="chapters.txt"
output_file="chapters.ffmetadata"

# Create the FFmetadata chapter file
echo ";FFMETADATA1" > "$output_file"

previous_seconds=0

while IFS="=" read -r timestamp chapter_name; do
 # Convert start time to seconds
 seconds=$(date -u -d "1970-01-01 $timestamp" +"%s")

 # Calculate the end time (previous chapter's start time)
 end_seconds=$previous_seconds

 # Update previous_seconds for the next iteration
 previous_seconds=$seconds

 echo "[CHAPTER]" >> "$output_file"
 echo "TIMEBASE=1/1000" >> "$output_file"
 echo "START=${end_seconds}000" >> "$output_file"
 echo "END=${seconds}000" >> "$output_file"
 echo "title=$chapter_name" >> "$output_file"
done < "$input_file"

echo "Chapter file '$output_file' created successfully."

# Run FFmpeg to add chapters to the video
ffmpeg -i input_video.mp4 -i chapters.ffmetadata -map_metadata 1 -c:v copy -c:a copy -y output_video.mp4



-
It creates a file called
chapters.ffmetadata


;FFMETADATA1
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=0000
title=Intro
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=132000
title=What are selections
[CHAPTER]
TIMEBASE=1/1000
START=132000
END=199000
title=Booleans
[CHAPTER]
TIMEBASE=1/1000
START=199000
END=0000
title=



The
START
andEND
times aren't being calculated correctly. How can I fix this ?










UPDATE #1


I'm almost there thanks to @Freeman code / answer.


The issues in the generated

chapters.ffmetadata
file are just.

- 

-
The first
START=
andEND=
are0000


-
The Intro Chapter doesn't show up (most likely caused by the first
START=
andEND=
being0000
)

-
The Chapters seem to be shifted down by one timecode line (most likely caused by the first
START=
andEND=
being0000
)

;FFMETADATA1
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=0000
title=Intro
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=132000
title=What are selections ?
[CHAPTER]
TIMEBASE=1/1000
START=132000
END=199000
title=Booleans
[CHAPTER]
TIMEBASE=1/1000
START=199000
END=0000
title=
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=4459000
title=











UPDATE #2


Strange ; I tried the changes @Freeman suggested but an error comes up now.


Chapter end time 0 before start 199000
chapters.ffmetadata : Cannot allocate memory


;FFMETADATA1
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=0000
title=Intro
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=132000
title=What are selections?
[CHAPTER]
TIMEBASE=1/1000
START=132000
END=199000
title=Booleans
[CHAPTER]
TIMEBASE=1/1000
START=199000
END=0000
title=
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=4459000
title=




UPDATE #3 using his awk changes


;FFMETADATA1
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=0000
title=Intro
[CHAPTER]
TIMEBASE=1/1000
START=0000
END=132000
title=What are selections?
[CHAPTER]
TIMEBASE=1/1000
START=132000
END=199000
title=Booleans
[CHAPTER]
TIMEBASE=1/1000
START=199000
END=0000
title=



-
-
doc : Merge doc/dev_community/* and Code of Conduct into a seperate file
8 février 2023, par Thilo Borgmanndoc : Merge doc/dev_community/* and Code of Conduct into a seperate file
Remove doc/dev_communit markup files completely as they are at the wrong place.
Create a new community page, merging all of doc/dev_community and subsection Code of Conduct into a common place.
The corresponding patch to ffmpeg-web puts the Organisation & Code of Conduct into a seperate community chapter on the FFmpeg website.