
Recherche avancée
Autres articles (53)
-
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP Player : problèmes potentiels
22 février 2011, parLe lecteur ne fonctionne pas sur Internet Explorer
Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...) -
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 (5721)
-
x86 : Faster high bit-depth intra_sad_x3_4x4
1er mai 2013, par Henrik Gramner -
RTMP stream and bandwidth usage
5 mai 2015, par Mike SanchezAs of now, I have an RTMP live stream going. FFMPEG transcodes the video files on my server, and then I direct it to LiveStream.com’s RTMP service. I use this method because my server just doesn’t have enough bandwidth to support numerous users watching the same stream all at once.
Livestream currently acts as a middle-man for me. So my question is, are there other opensource options wherein I can put Livestream to rest ? Can video.js handle this ? Maybe even Castamp ? Or do I risk losing the ability to keep bandwidth under control without an option like the one I’m currently using ?
-
Re-packetize h264 bytestream to Matroska output
10 février 2021, par Adam SzmydI have an app that's capturing multiple video streams from users and put them into one mkv output file.



Data are from RTP packets. I use h264.



I'm creating mkv using ffmpeg and
bytedeco/javacpp-presets
bridge for Java.


For some reason my output mkv, after changed container to mp4 (
ffmpeg -i input.mkv -c copy output.mp4
) is not playable by QuickTime Player. It opens the file but shows nothing but black frame for whole duration.


I'm trying to avoid re-coding of the streams.



One of my attempts to fix this was to somehow pack up raw h264 bytestream and use ffmpeg to put it in mkv again :

ffmpeg -i input.mkv -c copy -f h264 - | ffmpeg -i - -c copy output.mkv



But because raw h264 bytestream has no timing information (ffmpeg warns about lack of timestamps here) it packs it with some constant frame rate which results in different video duration than original. So i.e. from 27min video i get 30min with constant frame rate.



I'm looking for a way to re-pack my h264 video data into mkv container without re-coding.



I also tried
NUT
container for raw data as it persists some timing informations but result was the same as original mkv - black frame in QuickTime.


Maybe there is some other way to debug why QT shows nothing for my file ? Is there any verbosity mode i can enable, some logs to see if it complains for something ?