
Recherche avancée
Autres articles (46)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Soumettre améliorations et plugins supplémentaires
10 avril 2011Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...) -
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 (7998)
-
MP4 cut with ffmpeg doesn't play nicely in VLC but does in Browser
21 février, par AlexI cut a video with ffmpeg :


ffmpeg -ss 2 -to 10 -i src.mp4 -c copy out.mp4



But the playback in VLC is choppy for the first few seconds. Strangely it does play in my browser fine.


I saw this post :
https://superuser.com/questions/1167958/video-cut-with-missing-frames-in-ffmpeg?newreg=1502e1698e0344acb214aa8d7e6048bd where the suggestion is to use
-avoid_negative_ts make_zero
. That does fix the playback in VLC. I think that shifts the whole stream, and results in the video being longer than I want it to be.

For my use case I need the video to be precisely the correct length and I can't incur the cost of a (full) re-encode. I think the addition of
-avoid_negative_ts
is effectively snapping the cut to the nearest keyframe.

So I think the negative timestamps are upsetting VLC ? I can see they exist.


$ ffprobe -v error -select_streams v:0 -of default=noprint_wrappers=1 out.mp4 -show_entries packet=pts | head
pts=-30720
pts=-30464
pts=-30208
pts=-29952



I also tried with a few other media players (Films & TV in Windows) and had similar issues. Is there a better way to handle this, in a way that will allow the output video to be played normally ?


I saw the approach in this question : Cut a video in between key frames without re-encoding the full video using ffpmeg ?. But had issues with "Non-monotonous DTS" that also seemed to manifest in choppy playback.


-
FFMPEG libx264 mp4 file does not play in firefox Windows
2 mai 2020, par BehelSome of my ffmpeg converted videos in mp4 format, using libx264 encoder, aren't playable with Firefox browser on Windows.



Here is my ffmpeg command : 

ffmpeg -i file_tmp.mp4 -c:v libx264 -profile:v baseline -level 3.0 -crf 15 -preset slow -pix_fmt yuv420p -c:a aac -movflags faststart -strict -2 -vf scale=1024:576 file.mp4



The video can be played with every browsers on Mac, and works well with Webkit based browers on Windows.



The problem not occur with every video converted, only a few, like this one for instance : https://attentionphilippelepara.pet/testcard/m6-29_04_2020-mire.mp4



Here is what I see when i try to play this media, on Firefow Windows then on Chrome Windows.






I really don't see where is the problem. Can someone could help me ?


-
Wowza : Live stream detected but does not play
2 septembre 2016, par searcot jabaliThis is the command I use to being the stream on my hardware device
ffmpeg -i /dev/video0 -f rtsp rtsp ://[user] :[password]@52.66.64.136:1935/test/myStreamI can see that there is an input coming in from the Incoming Streams section of the Wowza Engine Manager.
The IP, Stream name & Application name are correct.
However when I try to play the stream using the Test Players, I dont see anything. Just a black screen.
An error message at the bottom of Adobe HDS says Source stream or file could not be found or access was denied.When I try to use the RTSP wowza link on VLC I get an error stating that the "Input Cannot Be opened"
Source security for RTSP has been set to open.
When I stream through the GoCoder App there are no issues.
This leads me to believe the server is functioning correctly.When I use the same command but change the output to write to file (ffmpeg -i /dev/video0 out.mp4) it works perfectly fine !!
So even the base command is correct.Am I missing some arguments from the FFMPEG command ?
Do I need to provide the username & password even though RTSP Source Security has been set to open ?