Recherche avancée

Sur d’autres sites (12243)

• How to reinsert edited metadata stream information from the FFMETADATAFILE file ? [closed]

  6 septembre 2024, par SENYCH

  I'm working on simplifying and speeding up the process of editing video metadata for user convenience. I've successfully edited metadata streams using console commands, such as :

  


  ffmpeg -i INPUT.mp4 -map 0 -metadata:s:0 "handler_name=An other video" -metadata:s:1 "handler_name=An other audio recording in russian" -metadata:s:2 "handler_name=An other audio recording in english" -metadata:s:3 "handler_name=An other audio recording in japanese" -c copy OUTPUT.mp4


  


  However, I'd like to accomplish this through a ffmetadata file. Here's the approach I've taken :

  


  ffmpeg -t 0 -i INPUT.mp4 -map 0 -c copy -f ffmetadata ffmetadata.txt -hide_banner


  


  Original ffmetadata.txt is :

  


  ;FFMETADATA1
major_brand=isom
minor_version=512
compatible_brands=isomiso2avc1mp41
encoder=Lavf61.5.101
[STREAM]
language=und
handler_name=The best video
vendor_id=[0][0][0][0]
[STREAM]
language=rus
handler_name=The best russian language
vendor_id=[0][0][0][0]
[STREAM]
language=eng
handler_name=The best english language
vendor_id=[0][0][0][0]
[STREAM]
language=jpn
handler_name=The best japanese language
vendor_id=[0][0][0][0]


  


  Edit the ffmetadata.txt file to update the handler_name values :

  


  ;FFMETADATA1
major_brand=isom
minor_version=512
compatible_brands=isomiso2avc1mp41
encoder=Lavf61.5.101
[STREAM]
language=und
handler_name=An other video
vendor_id=[0][0][0][0]
[STREAM]
language=rus
handler_name=An other audio recording in russian
vendor_id=[0][0][0][0]
[STREAM]
language=eng
handler_name=An other audio recording in english
vendor_id=[0][0][0][0]
[STREAM]
language=jpn
handler_name=An other audio recording in japanese
vendor_id=[0][0][0][0]


  


  Attempt to apply the updated metadata from ffmetadata2.txt :

  


  C:\Users\Alexander\Videos>ffmpeg -i INPUT.mp4 -i ffmetadata2.txt -map 0:v -map 0:a -map_metadata 1 -c copy OUTPUT2.mp4 -hide_banner


  


  Despite these steps, I've noticed that only the global metadata is updated, while the metadata for each stream remains unchanged. The console output shows that metadata for each stream is not updated as expected.

  


  What am I missing ? How can I ensure that the stream-specific metadata is also updated correctly when using a ffmetadata file ?

  


  Additional Information :

  


  

  • FFmpeg version : 2024-08-26-git-98610fe95f-full_build

  


  • The ffmetadata file format and the approach I've used should be correct according to the FFmpeg documentation.

  


  


  I would greatly appreciate any recommendations or suggestions on how to solve this problem !

  


  I found a bad solution for my problem, but it still isn't ideal as it requires specifying -map_metadata:s:N 1:s:N for each stream individually, which is quite cumbersome. Is there a way to simplify this process and avoid having to set metadata for each stream separately ?

  


  The command I’m using is :

  


  C:\Users\Alexander\Videos>ffmpeg -i INPUT.mp4 -i ffmetadata2.txt -map 0 -map_metadata:s:0 1:s:0 -map_metadata:s:1 1:s:1 -map_metadata:s:2 1:s:2 -map_metadata:s:3 1:s:3 -c copy OUTPUT2.mp4 -hide_banner


  


  This works, but having to specify -map_metadata:s:N for each stream creates extra work, especially as the number of streams increases. Is there a more efficient way to handle this ?

  


• ffmpeg convert mkv to mp4 with subtitles

  18 février 2021, par Frederik

  i try to convert a mkv file to mp4. but I having trouble getting the subtitles copied.Thats the command I used : ffmpeg -i input.mkv -c copy -c:s mov_text output.mp4. The problem is the subtitles r in two different languages. The original has just one language. After copying the subtitles look like this : engoriginal language. Does anyone know how to fix that

  


• Piwik 3 Release Candidate

  14 décembre 2016, par Piwik Core Team — Development

  The release candidate for Piwik 3 is now available.

  RC means we think we’re done, but it’s possible we’ve missed something. We hope to ship Piwik 3 on Sunday, December 18th (updated). If you haven’t tested Piwik 3 yet, now is the time ! To test Piwik 3, you can use the beta release channel or you can download the release candidate here (zip).

  Piwik 3 is a jam-packed release, with a number of features focused on security, performance, and more advanced analytics capabilities. Highlights include new UI design, responsive experience on mobile, better email reports, secure password storage, better tracking of downloads and outlinks, and more.

  Not sure where to start with testing ? Try setting up a new installation and taking notes on what you enjoyed and what got you stuck. For more details about what’s new in version 3.0, check out the beta 1, beta 2, beta 3, beta 4 changelogs as well as these blog posts : Piwik 3 overview, and Important notes and API breaking changes in Piwik 3.

  Think you’ve found a bug ? Please post to our Issues tracker. If any known issues come up, you’ll be able to search and find them there.

  Developers, please test your plugins and themes against Piwik 3 and update your plugin.json to require Piwik 3. An in-depth field guide to developer-focused changes and plugin migration is published on the Developer website.

  Do you speak a language other than English ? Help us translate Piwik into more than 50 languages !

  Happy testing !