Recherche avancée

Sur d’autres sites (5170)

• Create fragmented MP4 from MP3

  25 octobre 2020, par Stefan Falk

  I am trying to convert an MP3 file to a fragmented MP4 like this :

  


  ffmpeg -i input.mp3 -strict experimental -acodec aac -b:a 256k -f mp4 \
       -movflags faststart+frag_keyframe+empty_moov+separate_moof output.mp4 


  


  However, using Bento4 I can see that there is just one giant mdat object instead of a series of those :

  


  [ftyp] size=8+24
  major_brand = isom
  minor_version = 200
  compatible_brand = isom
  compatible_brand = iso2
  compatible_brand = iso6
  compatible_brand = mp41
[moov] size=8+701
  ...
[moof] size=8+62364
  ...
[mdat] size=8+5794679
[mfra] size=8+59
  [tfra] size=12+31, version=1
    track_ID = 1
    length_size_of_traf_num = 0
    length_size_of_trun_num = 0
    length_size_of_sample_num = 0
  [mfro] size=12+4
    mfra_size = 67


  


  I think what I want is this :

  


  

  


  (source)

  


  But I can't seem to be able to get this from ffmpeg.

  


  I found some other options here like

  


  $ ffmpeg -h muxer=ismv&#xA;...&#xA;-frag_duration     <int>   E.... Maximum fragment duration&#xA;-min_frag_duration <int>   E.... Minimum fragment duration&#xA;-frag_size         <int>   E.... Maximum fragment size&#xA;</int></int></int>

  


  but playing around with these didn't change the output.

  


  How can I create fragments of a specific sice e.g. 5 seconds each ?

  


• Mac terminal command to list files and sort by date to use in ffmpeg

  22 septembre 2020, par Jeff

  I am using a gopro to film a bunch of videos. I want to then take those videos directly from the SD card folder and concatenate them into a single video (bypass an editor) by using FFMPEG.

  


  I'm currently able to stitch together "chaptered" videos with the following example command on my Mac (10.13) :

  


  ffmpeg -f concat -safe 0 -i <(for f in /sdcardfolder/100GOPRO/GH*488.MP4; do echo "file '$f'"; done) -c copy /folder/video.mp4

  


  The reason for this is that the ffmpeg command requires a text file that looks like this :

  


  


  file '/folder/GH016992.MP4'

  
file '/folder/GH036990.MP4'

  
...

  


  


  The real command is this, which generates the list of files in the right format with file in front of each one and can be embedded into the ffmpeg command :

  


  for f in /Volumes/GoPro8/DCIM/100GOPRO/GH0*71*.MP4; do echo "file '$f'"; done

  


  I want to add 2 changes to this :

  


  


  1. List the files in date order (ascending) : I want the list of files to be in date order. But I can't figure out how to add a -sort or something to the for f in command.

     


  


  2. Allow a more robust set of file matching/filtering : Right now I can add basic regex like GH*488.MP4 or, with chapters which increments the first number, something like GH0[123]488.MP4 would work to just get the first few. But when I change it to be more flexible like GH0[0-9]71[0-9][0-9].MP4 - which would be necessary to match all files that were recorded yesterday, but nothing before then, the command doesn't like this regex. It seems to only accept a *.

     


  


  


  I looked at a few examples like https://opensource.com/article/19/6/how-write-loop-bash but there wasn't much more than just listing files.

  


  This boils down to a terminal command and isn't really related to FFMPEG but I hope it's helpful context.

  


  I imagined it would be something like this, but this definitely doesn't work :

  


  for f in (find /Volumes/GoPro8/DCIM/100GOPRO/GH0[0-9]71[0-9][0-9].MP4 -type f | sort); do echo "file '$f'"; done

  


  I'd appreciate any help ! Thanks !

  


  Update

  


  It looks like sorting isn't easy with Mac tools so I gave up and wrote a much simpler Ruby script that could execute everything for me. This is not really an answer to my question above but it is a solution.

  


  Here I can easily write the text file necessary for ffmpeg and I can also filter files with a regex on the name, filter for a particular date, and size. Then, via the script, simply execute the ffmpeg command with args to concat files. I can also have it immediately resample the file to compress it (gopro videos are giant and I'm ok with a much lower bitrate if I want to save raw footage).

  


  I got lucky with this Dir.entries in Ruby - it seems to automatically sort by date ? I don't know how to sort it otherwise.

  


  PATH = '/Volumes/GoPro8/DCIM/100GOPRO/'
NEW_FILENAME = '/folder/new-file.mp4'
video_list = '/folder/ffmpeg-list.txt'

# create the text file
File.delete(video_list) if File.exist?(video_list)
i = 1
Dir.entries(PATH).each do |f|
    d = File.mtime(PATH + f)
    size = File.size(PATH + f)
    if f.match(/GH0.*.MP4/) && d.to_s.match(/2020-07-30/) && size.to_i < 1000000000
        puts "#{i}\t#{f}\t#{d}\t#{size}"
        File.write(video_list, "file #{PATH + f}\n", mode: "a")
        i= i+1
    end
end

command = "ffmpeg -f concat -safe 0 -i #{video_list} -c copy #{NEW_FILENAME}"

puts "executing concatenate..."
puts command
system(command)


  


• Evolution #4468 : Unification des CSS pour les boutons et les icônes

  15 septembre 2020

  @b_b : Super, merci

  @jluc : Ah je pensais qu’on pouvait au moins éditer ses propres tickets sur trac, même sans être admin. Je viens de voir que j’aurais pu le faire moi-même d’ailleurs, mais je me suis encore fait avoir par l’UX : faut d’abord cliquer sur modifier, et ensuite sur la petite icône « changer la description ». Mon cerveau refuse de retenir ce truc.

  Alors en fin de compte j’ai fait en sorte de ranger un minimum, mais en essayant de pas toucher à trop de choses non plus :

  • Tout ce qui a trait aux boutons est dans un nouveau module boutons.css : les boutons de formulaires, les boutons d’action, et la nouvelle classe lambda .bouton.
  • Je n’ai pas touché au bando rapide, donc pour les nouveaux boutons le sélecteur CSS inclus le tag : a.bouton. Je disais que c’est sale parcequ’en dehors des règles de base (reset, typo…), la règle générale c’est d’éviter de cibler un tag en particulier.

  En parlant de rangement, le module icons.css contient aussi les onglets (barre + onglets simples). À mon avis le composant .icone.horizontale|verticale ça rentre dans la famille des boutons, donc à déplacer dans le module boutons.css, et le module icons pourrait ensuite être renommé en onglets.css.
  Mais bon, j’y touche pas, ça pourra faire l’objet d’un autre ticket spécifiquement pour le découpage et le rangement des modules.

  Je vais essayer de boucler ça demain, y a moyen de faire un PR pour tenter de squeezer ça dans l’alpha de la 3.3 amha.
  J’y mettrai un description complète de la prop incluant les derniers correctifs.