Recherche avancée

Médias (0)

Mot : - Tags -/content

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (83)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

Sur d’autres sites (14468)

  • FFmpeg - Past Duration Too Large

    14 avril 2018, par Nimble

    I’m having an issue with the warning "Past Duration Too Large" being spammed in my console. There has been quite a bit of discussion about this "warning" online but I have yet to find an actual solution to get rid of it.

    Many just say silence your console, but then I can’t see my segments and other things like warnings, it’s really not a good solution. Another suggests using the fps filter but I have found it creates stutter in the end files...

    Very strangely for reasons completely unknown to me if I double the input framerate and then specify the actual framerate for the output file the warning disappears. Example :

    ffmpeg - y -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -video_size 3440x1440 -rtbufsize 2147.48M ^
    
-framerate 200 -pixel_format nv12 -i video="Video (00 Pro Capture HDMI 4K+)":audio="SPDIF/ADAT (1+2) (RME Fireface UC)" ^
    
-map 0:0,0:1 -map 0:1 -flags +cgop -force_key_frames expr:gte(t,n_forced*2) -c:v h264_nvenc -preset: llhp -pix_fmt nv12 ^
    
-b:v 250M -minrate 250M -maxrate 250M -bufsize 250M -c:a aac -ar 44100 -b:a 384k -ac 2 -r 100 ^
    
-af "atrim=0.038, asetpts=PTS-STARTPTS, aresample=async=250" -vsync 1 -ss 00:00:01.096 -max_muxing_queue_size 9999 ^
    
-f segment -segment_time 600 -segment_wrap 9 -reset_timestamps 1 C:\Users\djcim\Videos\PC\PC\PC%02d.ts

    As you can see I have -framerate on the input at 200 and -r on the output at 100, believe it or not this gets rid of the warning completely and the resulting file has no issues. However... this is not something you can pull off with any capture card, the only reason I can do this with the Magewell is because under certain resolutions it can record 200fps. Therefore FFmpeg allows me to set it, even though it is double what the card actually allows at the resolution I’m recording. So when I record my camera with a card from Elgato I can’t pull that off :

    ffmpeg -y -thread_queue_size 9999 -indexmem 9999 -guess_layout_max 0 -f dshow -video_size 1920x1080 -rtbufsize 2147.48M ^
    
-framerate 60 -pixel_format yuyv422 -i video="Game Capture HD60 Pro (Video) (#01)":audio="ADAT (5+6) (RME Fireface UC)" ^
    
-map 3:0,3:1 -map 3:1 -flags +cgop -r 60 -force_key_frames expr:gte(t,n_forced*2) -c:v h264_nvenc -preset: llhp ^
    
-pix_fmt yuv420p -b:v 40M -minrate 40M -maxrate 40M -bufsize 40M -c:a aac -ar 44100 -b:a 384k -ac 2 ^
    
-af "pan=mono|c0=c0, adelay=112|112, aresample=async=250" -vsync 1 -max_muxing_queue_size 9999 -f segment ^
    
-segment_time 600 -segment_wrap 9 -reset_timestamps 1 C:\Users\djcim\Videos\PC\Camera\CPC%02d.ts

    When I try to set the -framerate to 120 is just throws an error and wont start recording. Also, while I really wish I could just double the framerate and be done with it, it is pretty clear that that is not a conventional or "actual" solution. That really shouldn’t get rid of the message... The only solution I have come up with besides buying another Magewell is to modify the if statement in the code and compile FFmpeg myself.

    Also I’d like to mention that at times the message is spammed so much that it actually crashes the console, so it’s a real issue not just a warning...

    Any help would be appreciated.

  • ffmpeg rotate and trim video 4k horizontal -> 2k vertical

    19 juillet 2015, par Flash Thunder

    I was looking for solution, but seems that the ones that google finds are not valid anymore... I think that you have to use mapping for that, but not sure how...

    I need to rotate horizontal 4K video and trim it (leaving center part), so the output would be vertical 1080p. Could anybody give me a hand with that ?

    Of course I need to keep the best possible quality.

    PS. ffmpeg compiled from git-8250943 (2015-07-17)

  • hevc_filter : run vertical and horizontal together

    26 juillet 2014, par Christophe Gisquet
    hevc_filter : run vertical and horizontal together

    This should help cache locality. On win64 :
    
Before : 1397x cycles, 16216 bytes
    
After :  1369x cycles, 16040 bytes
    

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavcodec/hevc_filter.c

Navigation