Recherche avancée
Autres articles (111)
-
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
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 -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (16551)
-
Writing to two standard input pipes from C#
3 janvier 2021, par Den DelimarskyI am using FFMPEG from my C# application to build out the video stream from raw unencoded frames. For just one input stream this is fairly straightforward :


var argumentBuilder = new List<string>();
argumentBuilder.Add("-loglevel panic");
argumentBuilder.Add("-f h264");
argumentBuilder.Add("-i pipe:");
argumentBuilder.Add("-c:v libx264");
argumentBuilder.Add("-bf 0");
argumentBuilder.Add("-pix_fmt yuv420p");
argumentBuilder.Add("-an");
argumentBuilder.Add(filename);

startInfo.Arguments = string.Join(" ", argumentBuilder.ToArray());

var _ffMpegProcess = new Process();
_ffMpegProcess.EnableRaisingEvents = true;
_ffMpegProcess.OutputDataReceived += (s, e) => { Debug.WriteLine(e.Data); };
_ffMpegProcess.ErrorDataReceived += (s, e) => { Debug.WriteLine(e.Data); };

_ffMpegProcess.StartInfo = startInfo;

Console.WriteLine($"[log] Starting write to {filename}...");

_ffMpegProcess.Start();
_ffMpegProcess.BeginOutputReadLine();
_ffMpegProcess.BeginErrorReadLine();

for (int i = 0; i < videoBuffer.Count; i++)
{
 _ffMpegProcess.StandardInput.BaseStream.Write(videoBuffer[i], 0, videoBuffer[i].Length);
}

_ffMpegProcess.StandardInput.BaseStream.Close();
</string>

One of the challenges that I am trying to address is writing to two input pipes, similar to how I could do that from, say, Node.js, by referring to
pipe:4orpipe:5. It seems that I can only write to standard input directly but not split it into "channels".

What's the approach to do this in C# ?


-
fate : Change the probe-format refs to match the final text format committed.
7 mai 2012, par Alex Conversefate : Change the probe-format refs to match the final text format committed.
-
checkasm : Use standard multiple inclusion guards
16 février 2016, par Diego Biurrun
Syndiquer tout le site
