Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (96)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains 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, par

    Pré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 2013

    Puis-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 (4996)

  • Rotating gyro data in gopro footage with ffpmeg

    2 juillet 2023, par FPV Shenanigans

    I believe orientation of gyro data in some of my gopro clips is wrong. Reelsteady runs stabilization ok but it results in even worse than initial video shaky effect. I have filmed with gopro in 90 degree with orientation locked .

    


    Is it possible to amend metadata if ffmpeg to fix this ?

    


    the below is an example clip

    


    Metadata :
major_brand : isom
minor_version : 512
compatible_brands : isomiso2mp41
encoder : Lavf60.10.100
Duration : 00:04:30.22, start : 0.000000, bitrate : 119132 kb/s
Stream #0:00x1 : Video : hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(pc, bt709), 3840x3360 [SAR 1:1 DAR 8:7], 118934 kb/s, 59.94 fps, 59.94 tbr, 60k tbn (default)
Metadata :
handler_name : GoPro H.265
vendor_id : [0][0][0][0]
encoder : GoPro H.265 encoder
timecode : 13:27:43:05
Side data :
displaymatrix : rotation of -90.00 degrees
Stream #0:10x2 : Audio : aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
Metadata :
handler_name : GoPro AAC
vendor_id : [0][0][0][0]
Stream #0:20x3 : Data : none (tmcd / 0x64636D74)
Metadata :
handler_name : GoPro H.265
timecode : 13:27:43:05

    


    tried this

    


    ffmpeg.exe -i "F :\2023 THE ONLY COPY\Chasing surfers\GX010223.MP4" -c copy -metadata:s:v rotate=90 "F :\2023 THE ONLY COPY\Chasing surfers\GX010223_test.mp4"

    


    but reelsteady can't read metadata from a new video

    


  • Issue with repairing 3GP video using untrunc - Error : bad track : 's263'

    2 juillet 2023, par sifirib

    I am trying to repair a corrupted 3GP video using the untrunc program, but I'm facing an issue due to an error.

    


    The command I ran :

    


    ./untrunc -v ~/Desktop/logic/Video0086.3gp ~/Desktop/logic/Video0035.3gp


    


    I am running Ubuntu 20.04 LTS and using the 'v308-d72ec32' version of the untrunc. The error message I encounter is as follows :

    


    Info: version 'v308-d72ec32' using ffmpeg '4.4.2-0ubuntu0.22.04.1'
Info: reading /home/hsrv/Desktop/logic/Video0086.3gp
Info: parsing healthy moov atom ... 
ftyp_ = 'mp42'
[amrnb @ 0x56075d7656c0] Multiple frames in a packet.
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/hsrv/Desktop/logic/Video0086.3gp':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2014-04-26T21:38:29.000000Z
    com.android.version: 12
  Duration: 00:02:22.80, start: 0.000000, bitrate: 154 kb/s
  Stream #0:0(eng): Video: h263 (s263 / 0x33363273), yuv420p, 176x144 [SAR 12:11 DAR 4:3], 140 kb/s, 10.74 fps, 11 tbr, 90k tbn, 29.97 tbc (default)
    Metadata:
      creation_time   : 2023-07-02T15:34:22.000000Z
      handler_name    : VideoHandle
      vendor_id       : [0][0][0][0]
  Stream #0:1(eng): Audio: amr_nb (samr / 0x726D6173), 8000 Hz, mono, flt, 12 kb/s (default)
    Metadata:
      creation_time   : 2023-07-02T15:34:22.000000Z
      handler_name    : SoundHandle
      vendor_id       : [0][0][0][0]
ss: s263 is_stable: 0
ss: using f=7 span
assuming constant duration of 640 for 'samr' (x1785)

Info: unknown track 's263' found -> fallback to dynamic stats
created dummy track 'free'
removed dummy track 'free'
first_failed: 0 of 101
simpleOrder: 0 
order ( 101): (0, 14) (0, 11) (0, 11) (0, 12) (0, 11) (0, 12) (0, 11) (0, 12) (0, 11) (0, 11) (0, 11) (0, 11) (0, 12) (0, 12) (0, 11) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 11) (0, 11) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 11) (0, 11) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 11) (0, 11) (0, 12) (0, 11) (0, 11) (0, 12) (0, 12) (0, 11) (0, 12) (0, 12) (0, 11) (0, 10) (0, 12) (0, 12) (0, 12) (0, 11) (0, 12) (0, 11) (0, 10) (0, 12) (0, 11) (0, 11) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 12) (0, 10) (0, 12) (0, 11) (0, 11) (0, 12) (0, 12) (0, 12) (0, 12) 
isTrackOrderEnough: 0  (sz=0)
genPatternPerm of: s263
0 s263 0.918296 3
1 samr 1 2
genPatternPerm of: samr
0 s263 4.8125 32
1 samr 0 1
has_zero_transitions_: 0
**Error: bad track: 's263'**


    


    This error message indicates that the untrunc program is having trouble with a track named 's263'. This track could be a track or codec within the video file.

    


    How can I resolve this error and successfully repair the corrupted 3GP video ? What steps should I follow or can you suggest an alternative approach ?

    


    Thank you in advance !

    


    I was expecting trunc tool to fix the corrupted/trunced video. But it gave me this error and no matter how much I searched for a solution, I couldn't find anything.

    


  • ffprobe not showing language tag for ASS files in Ubuntu

    9 juillet 2023, par Efraín

    This is something that has me totally lost, because I'm not sure what could I have done, but from one week to another, "language" stopped appearing in the tags of an ASS track on a MKV. I know this just started to appear, because just last week I ended working on an script to detect the language of tracks, and today that I decided to test it again, I noted that it started to fail, and from my debug it's because ffprobe is now printing this

    


    {
    "index": 2,
    "codec_name": "ass",
    "codec_long_name": "ASS (Advanced SSA) subtitle",
    "codec_type": "subtitle",
    "codec_tag_string": "[0][0][0][0]",
    "codec_tag": "0x0000",
    "r_frame_rate": "0/0",
    "avg_frame_rate": "0/0",
    "time_base": "1/1000",
    "start_pts": 0,
    "start_time": "0.000000",
    "duration_ts": 1430816,
    "duration": "1430.816000",
    "disposition": {
        "default": 1,
        "dub": 0,
        "original": 0,
        "comment": 0,
        "lyrics": 0,
        "karaoke": 0,
        "forced": 0,
        "hearing_impaired": 0,
        "visual_impaired": 0,
        "clean_effects": 0,
        "attached_pic": 0,
        "timed_thumbnails": 0
    },
    "tags": {
        "BPS-eng": "85",
        "DURATION-eng": "00:23:34.830000000",
        "NUMBER_OF_FRAMES-eng": "262",
        "NUMBER_OF_BYTES-eng": "15128",
        "_STATISTICS_WRITING_APP-eng": "mkvmerge v40.0.0 ('Old Town Road + Pony') 32-bit",
        "_STATISTICS_WRITING_DATE_UTC-eng": "2023-07-02 11:29:54",
        "_STATISTICS_TAGS-eng": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES"
    }
}


    


    Where it should be a field called "language" in the "tags", like this(Note that other file types, like SRT, or audio tracks show it correctly)

    


    "tags": {
    "language": "eng",
    "BPS-eng": "128000",
    "DURATION-eng": "00:23:50.813000000",
    "NUMBER_OF_FRAMES-eng": "61620",
    "NUMBER_OF_BYTES-eng": "22893018",
    "_STATISTICS_WRITING_APP-eng": "mkvmerge v40.0.0 ('Old Town Road + Pony') 32-bit",
    "_STATISTICS_WRITING_DATE_UTC-eng": "2023-07-02 11:29:54",
    "_STATISTICS_TAGS-eng": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES"
}


    


    The weird part is that is the same file I used for testing(And it worked), and I haven't edited it, so I'm not sure why is this happening, Does someone knows if I might have messed up something installing a library for another thing that might have caused it ?

    


    Just in case is necessary, this is the command I use : ffprobe -v quiet -print_format json -show_streams <file></file>

    &#xA;