
Recherche avancée
Autres articles (75)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
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 (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (11266)
-
Revision 533470c998 : add unit test for datarate control Adds some basic datarate control tests.. Ch
30 octobre 2012, par Jim BankoskiChanged Paths : Add /test/datarate_test.cc Modify /test/test.mk add unit test for datarate control Adds some basic datarate control tests.. Change-Id : I6eff18aa58ef7cfd14886c6b1e048247cd1ad247
-
Why is the external executable I bundled with my azure function not being found at runtime, despite it being present in the expected location ?
6 septembre 2023, par Cristian Camilo Garcia BarreraI have a group of Azure functions that I publish to a functions app. One of these is a blob triggered function, meant to extract thumbnails from videos uploaded to Azure storage, and to do so, uses
ffmpeg.exe
.

I have published the project via Visual Studio, adding the executable in a directory in the root of the project. The relative path is
exe/ffmpeg.exe
. To include the executable in the published bundle I followed the instructions in this Microsoft Developer instructional video.

After publication, If I enter the Kudu debug console for this function app, I can find the file under
C:\home\site\wwwroot\exe\ffmpeg.exe
, as expected. I can even use that absolute path to execute ffmpeg inside the Kudu console.

This is the code I use to call the ffmpeg executable in the blob function :


using (var process = new Process())
{
 process.StartInfo = new ProcessStartInfo
 {
 FileName = @"C:\home\site\wwwroot\exe\ffmpeg.exe",
 Arguments = $"-hide_banner -loglevel error -i {videoTempPath} -frames:v 1 {thumbTempPath}",
 UseShellExecute = false,
 RedirectStandardOutput = true,
 RedirectStandardError = true,
 CreateNoWindow = true
 };

 process.Start();
 await process.WaitForExitAsync();
}



However, this does not work. I get the following error in the logs :




An error occurred trying to start process 'C :\home\site\wwwroot\exe\ffmpeg.exe' with working directory 'C :\Program Files (x86)\SiteExtensions\Functions 4.25.2132bit. The system cannot find the file specified.




And indeed my thumbnails are never created. How can I solve this, or why does it happen ?


-
Revision a4fd58a761 : Refactor tx_block_rd_b() to compute per block rd cost This commit makes the tx_
12 juin 2015, par Jingning HanChanged Paths :
Modify /vp9/encoder/vp9_rdopt.c
Refactor tx_block_rd_b() to compute per block rd costThis commit makes the tx_block_rd_b() compute the rate and
distortion cost per transform block, instead of accumulating these
costs.Change-Id : Iff5adc4c27cc54f8e6eb3abd95f8d88ba00f462c