
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (36)
-
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 -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)
Sur d’autres sites (3968)
-
ffmpeg : transcode over socket
19 septembre 2020, par user14258924I am consuming multiple streams of h264 video and aac audio data in my own RTMP server and I want to transcode these streams into different codecs so I want to send these tracks, in chunks, into ffmpeg and get the transcoded result back. But due to performance requirements I want to use some kind of streaming where I can just open up a socket to get files in/out instead of dumping the data into individual files and then reading transcoded files back.


Is it possible with ffmpeg ?


-
FFMPEG and libx264, WMP and QT playback at different res/aspect than specified
10 septembre 2013, par FoltzSo, for a little context. I'm trying to convert a JPEG2000 in .mxf video to an h264 in .mp4, maintaining its resolution/frame-size/aspect ratio. I'll say up front I'm not 100% sure on how all these ratios tie together.
So, my input file is 720x486. I have a sample h264 file with specs I'm trying to emulate (from an OpenCube video ingest machine) with ffmpeg. The OpenCube file plays back at 720x486 in both Quick Time 7 and Windows Media Player 12. It reports a PAR of 9:10 and DAR of 4:3 (Using VideoSpec to see these values).
When I make my derivative h264 using ffmpeg I can run the command :
ffmpeg -i lac-test.mxf -vcodec libx264 -s 720x486 -aspect 4:3 -b:v 2500000 -pix_fmt yuv420p -coder 0 -acodec libfaac -b:a 256000 lac-test.mp4
The output file reports the correct values in VideoSpec (720x486, DAR 4:3, PAR 9:10), but plays back in QT at 648x486. Weirder, the video plays back at the proper resolution (that is, same size as the sample OpenCube file).
Now, an alternative command creates yet another predicament :
ffmpeg -i lac-test.mxf -vcodec libx264 -s 720x486 -b:v 2500000 -pix_fmt yuv420p -coder 0 -acodec libfaac -b:a 256000 lac-test.mp4
So omitting the aspect ratio gives me an output file that plays at 720x486 in QT7 (good !) but reports a DAR of 1.481 and an Undefine PAR. Unfortunately, THIS file plays back slightly too wide in WMP12.
I've tried a slew of different strings to try and get something that plays back correctly. I've tried using various filters with the -fv flag such as :
ffmpeg -i lac-test.mxf -vcodec libx264 -vf "scale=720x486,setsar=9:10,setdar=4:3" -b:v 2500000 -pix_fmt yuv420p -coder 0 -acodec libfaac -b:a 256000 lac-test.mp4
This results in a video that shows all the correct specs in VideoSpec, and plays back correctly in WMP12 (same size as OpenCube file), but still plays back at 648x486 in QT7.
What gives ?
-
Anomalie #2647 : Logo/Forum : Appels Ajax qui n’aboutissent pas (FF v3.5.7)
12 avril 2012, par Julien -Une seule mise à jour vers la version 3.6.18 de FF suffit à régler le pb. Je ne connais pas les stats navigateur de la galaxie SPIP mais il n’est peut être pas utile de s’embêter pour si peu du coup...