
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 (101)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 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 v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, 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 (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 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 (...)
Sur d’autres sites (11595)
-
checkasm : Serialize read_time() calls on x86
8 octobre 2014, par Henrik Gramnercheckasm : Serialize read_time() calls on x86
Improves the accuracy of benchmarks, especially in short functions.
To quote the Intel 64 and IA-32 Architectures Software Developer’s Manual :
"The RDTSC instruction is not a serializing instruction. It does not necessarily
wait until all previous instructions have been executed before reading the counter.
Similarly, subsequent instructions may begin execution before the read operation
is performed. If software requires RDTSC to be executed only after all previous
instructions have completed locally, it can either use RDTSCP (if the processor
supports that instruction) or execute the sequence LFENCE ;RDTSC."RDTSCP would accomplish the same task, but it’s only available since Nehalem.
This change makes SSE2 a requirement to run checkasm.
-
ffmpeg randomly stops recording rtmp stream
14 novembre 2022, par M9AI am trying to record a rtmp stream using ffmpeg. On the whole it records the stream fine but every so often it stops recording the stream and when I then go to record it again, it will only record around a second or 2 before it stops again. This usually goes on for like 10-15mins. In this time if I want to record the stream, I would have to manually record 1-2 seconds each time. This sounds like it is a server issue - perhaps there is a mechanism that cuts off the stream every few seconds.


In the case where the stream cuts off, is there a way to keep trying and recording all of these 1-2 second segments rather than me doing it manually ? Doing it manually creates gaps in the recording due to the time taken to connect and record the stream. I even tried running the command in a loop but even with that there are gaps in the video.


The code I am using to record the stream is as follows :


ffmpeg -i "rtmp://example.com/stream?id=12345" -vcodec copy -acoded copy "output.mp4"



When it is recording fine and cuts off the first time, there is no error given. It's like the stream came to an end so it stops recording. The subsequent times where I can only record 1-2 seconds are the same - there is no error


As there are no error messages such as timeout or connection errors, I cannot even run flags on the command to retry recording.


-
How to detetc hardware acceleration in ffmpeg
19 décembre 2020, par Ali RazmkhahI am writing c++ program to screen record by ffmpeg 4.3 ! I need to detect hardware acceleration support such as h264_qsv or h264_nvenc without running ffmpeg.exe !


I explored ffmpeg.exe source code and found no results ! some solutions are deprecated or dose not work on 4.3 !
As instance,


avcodec_find_encoder_by_name("h264_qsv")



returns null even it is exist and works properly !