
Recherche avancée
Médias (1)
-
Publier une image simplement
13 avril 2011, par ,
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (40)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
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 -
Demande de création d’un canal
12 mars 2010, parEn fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...)
Sur d’autres sites (6499)
-
mp4 video loading forever and does not open of Samsung TV
16 août 2020, par Amira Elsayed IsmailI have two mp4 files one is working on Samsung TV and the second one is not working, it keep loading forever


I have checked the codec of both and the are the same , the only change is the bitrate is different, could that be the reason of not being able to play the video on TV


and if yes how to solve t using vlc program or any ffmpeg code that convert it








-
FFmpeg export codec not supported by Samsung
21 juillet 2021, par CoskiI am using FFmpeg to render videos (concatenating image files with audio and then applying speed and volume filters) to export videos to upload to TikTok. As a result, I must first move the videos to my phone.


I do not understand why my phone (S20) will happily play one of the videos (codec information pictured first), but presents an error "Codec not supported" when playing the other (information second).






The codec information is from VLC, and as you can see, both videos have identical Codecs (H264-MPEG4).


From analysing the information, the only conclusion I come to is that it has something to do with the fact that the "Decoded Format" differs across the videos. How can I change my export command on the latter so my phone supports the codec ?


CONCATENATION CODE

ffmpeg -f concat -safe 0 -i {path_temp}\\clips.txt -c copy -y "{path_temp}\\{title}_a.mp4


FILTER CODE

ffmpeg -i input.mp4 -filter:a "volume={volume}" -y temp.mp4"


SECOND FILTER

ffmpeg -i temp.mp4 -filter_complex "[0:v]setpts={1/speed}*PTS[v];[0:a]atempo={speed}[a]" -map "[v]" -map "[a]" -y output.mp4


-
Android Exoplayer garbled mp4 video output on imagereader surface while playing fine on SurfaceView (Samsung galaxy tab s7)
29 mars 2023, par OrcunProblem :


I am trying to play an mp4 video file on Samsung Galaxy Tab S7 for video processing purposes. For the purpose, I use Exoplayer(v2.18.4) library to be able to play the video onto an ImageReader surface so that I can grab the frames in
ImageReader.OnImageAvailableListener
.

I do not have any problems in getting the frames. However, the frames I acquire are garbled/corrupted like :




When I saw this frame, it made me think that it is some sort of color format or codec issue for the mp4 file or device I use. In logcat, there are no errors reported.
Device uses
[OMX.qcom.video.decoder.avc]
decoder. Also, same video plays nicely on some other devices that use exactly the same decoder.

What I tried so far :


I tried a lot of things to understand the root cause and also find a solution, so my brain currently is free flowing stream. I will try to summarise, please bear with me.


I use a
CustomMediaCodecVideoRenderer
in my app which overridesMediaCodecVideoRenderer.getMediaFormat
of Exoplayer to set color format like :

setInteger(MediaFormat.KEY_COLOR_FORMAT, MediaCodecInfo.CodecCapabilities.COLOR_FormatYUV420Flexible)



This step proved itself necessary. Without it I get a crash simply because I cannot access the image planes of an image frame in expected YUV image format.
This unfortunately was not enough for the Samsung Galaxy Tab 7 although it was already enough for another device like Xiaomi to render the image correctly.


Then I decided to use a library like
ffmpeg
to modify the mp4 file itself to maybe use a different profile, color format, resolution that is widely compatible in android devices. No luck so far.
a quickffprobe
on my mp4 file shows :

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'outputyuv169.mp4':
Metadata:
 major_brand : isom
 minor_version : 512
 compatible_brands: isomiso2avc1mp41
 encoder : Lavf59.16.100
Duration: 00:03:00.02, start: 0.000000, bitrate: 4823 kb/s
Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(progressive), 
1280x720 [SAR 1:1 DAR 16:9], 4820 kb/s, 30 fps, 30 tbr, 360k tbn (default)



I tried even recording a simple video on the tablet itself and using that as my input file. Nevertheless, still getting similarly garbled frames.


One thing I keep noticing in logcat is this line :


[OMX.qcom.video.decoder.avc] using color format 0x7fa30c04 in place of 0x7f420888


and


[OMX.qcom.video.decoder.avc] Requested output format 0x7f420888 and got 0x7fa30c04


where
0x7fa30c04
refers toYCbCr_420_SP_VENUS_UBWC
. Not really sure If this has anything to do with it. I did not dive too deep into that because same log is present also on other device that renders the mp4 correctly.

I would be grateful for any clue.