Recherche avancée
Autres articles (110)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)
Sur d’autres sites (15396)
-
MAINTAINERS : remove myself as mailing list maintainer
21 mars 2019, par Lou Logan -
doc/developer : revise mailing list section
4 décembre 2017, par Jim DeLaHuntdoc/developer : revise mailing list section
The Developer Documentation had instructions to
subscribe to the ffmpeg-cvslog email list. But that is
no longer accurate. For the purposes in this section —
review of patches, discussion of development issues —
ffmpeg_devel is the appropriate email list. Some developers
may want to monitor ffmpeg-cvslog, but it is not mandatory.This is v3 of this doc, based on discussion in thread
<https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220528.html> ;
and in response to docs Maintainer comments in
<https://ffmpeg.org/pipermail/ffmpeg-devel/2017-December/221596.html>.1. In doc/developer.texi, add a new section about
ffmpeg-devel, based on existing text from ffmpeg-cvslog
section regarding discussion of patches and of
development issues. Reflect wording from discussion at
<https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/221199.html> ;
but with copy-editing to make wording more concise.2. In doc/developer.texi, rewrite the ffmpeg-cvslog section
to match the current usage of ffmpeg-cvslog. Some
developers choose to follow this list, but it is not
mandatory.There are a lot of improvements possible to the
Developer Documentation page, beyond this refactoring.
However, making those improvements is a much bigger
and more difficult task. This change is "low hanging
fruit".Signed-off-by : Jim DeLaHunt <from.ffmpeg-dev@jdlh.com>
Signed-off-by : Timothy Gu <timothygu99@gmail.com> -
Trying to find a way to limit the number of List that can run at one time
14 mars 2024, par JakeMy application has a List of Tasks. Each Task launches a FFMPEG process that requires a lot of resources on my machine. At times, this list can contain 200+ processes to FFMPEG. While processing, my memory is at 99% and everything freezes up.


I need to limit the amount of processes that can run at one time. I have read a little about SemaphoreSlim ; however, I cannot wrap my mind around it's implementation.


Is this a solution for this particular problem and if so, any ideas on how to implement it in my code ?


Below is my code :


public async System.Threading.Tasks.Task GetVideoFiles()
{ 
 OpenFileDialog openFileDialog = new OpenFileDialog();
 openFileDialog.Multiselect = true;
 
 if (openFileDialog.ShowDialog() == true)
 {
 AllSplices.Clear();
 AllSplices = new ObservableCollection<splicemodel>();
 IsBusy = true;
 IsBusyMessage = "Extracting Metadata";
 IsBusyBackgroundVisible = "Visible";
 NotifyPropertyChanged(nameof(IsBusy));
 NotifyPropertyChanged(nameof(IsBusyMessage));
 NotifyPropertyChanged(nameof(IsBusyBackgroundVisible));
 metaTasks = new List>(); 
 extractFramesTask = new List();
 
 foreach (string file in openFileDialog.FileNames)
 {
 FileInfo fileInfo = new FileInfo(file);
 bool canAdd = true;
 var tempFileName = fileInfo.Name;
 
 foreach (var video in AllVideos)
 {
 if (file == video.VideoPath)
 {
 canAdd = false;
 break;
 }

 if (video.VideoName.Contains(tempFileName))
 {
 video.VideoName = "_" + video.VideoName; 
 } 
 }
 if (canAdd)
 { 
 metaTasks.Add(System.Threading.Tasks.Task.Run(() => ProcessMetaData(file))); 
 } 
 }
 var metaDataResults = await System.Threading.Tasks.Task.WhenAll(metaTasks); 
 
 foreach (var vid in metaDataResults)
 { 
 if(vid == null)
 {
 continue;
 }
 
 vid.IsNewVideo = true; 
 AllVideos.Add(vid);
 
 // This list of task launches up to 200 video processing processes to FFMPEG
 extractFramesTask.Add(System.Threading.Tasks.Task.Run(() => ExtractFrames(vid)));
 
 vid.IsProgressVisible = "Visible";
 TotalDuration += vid.VideoDuration;
 vid.NumberOfFrames = Convert.ToInt32(vid.VideoDuration.TotalSeconds * 30);
 _ = ReportProgress(vid);
 }
 
 IsBusyMessage = "Importing Frames";
 NotifyPropertyChanged(nameof(IsBusyMessage)); 
 await System.Threading.Tasks.Task.WhenAll(extractFramesTask); 
 }
</splicemodel>

Syndiquer tout le site
