Basically what i am doing is i gotI basically have 3 processes which iI loop through.
The first process is encoding Video, it's. It's actually 2 processes but they are connected, so iI don't need to worry about how it handles the other one.
The second and third are connected by me, however. One reads and the other writes, So iso I have to manually feed the Stdinstdin/out.
And here iI am a bit skeptical, if i. If I do it the "normal" way, which basically is having one callback thread which get'sgets the data, and then writes it immediatly, the Performanceimmediately. The performance will be locked to one thread.
With that iI mean that both processes will share Thread, so both will pretty much run at 50%.
To solve this i iI am letting the Callback run and just feed the Data to a BlockingCollectionBlockingCollection, which the other process then reads from (That'sthat's being done on another Thread). I am not, however, sure this is truly an efficient way to do things, but it works.
And well, theThe last is simply a process which takes 2 files and putputs them ininto a container.
3 of these processes are run on the same Variable "cmdProcesses", thevariable cmdProcesses. The exception is the one that is a separate cause of the piping.
Here is how the Mainmain part of this code runs:
private void Encoding(string[] GetFile)
{
using(AutoResetEvent OpusCheck = new AutoResetEvent(false))
using (QU = new BlockingCollection<byte[]>())
using (OpusEncoder = new Process())
for (int i = 0; i < GetFile.Length; i++)
{
try
{
ReadBuffer = new byte[4096];
string filename = Path.GetDirectoryName(GetFile[i]) + "\\" + Path.GetFileNameWithoutExtension(GetFile[i]);
using (cmdCommands = new Process())
{
cmdCommands.StartInfo.UseShellExecute = false;
cmdCommands.StartInfo.CreateNoWindow = false;
cmdCommands.StartInfo.FileName = SC.GetAVS4x264Path();
cmdCommands.StartInfo.Arguments = string.Format("\"{0}\" --x264-binary \"{1}\" --colormatrix=bt709 {2} --output=\"{3}\" -", filename + ".avs", SC.Getx264Path(), SC.Getx264Settings(true), filename + ".mkv");
cmdCommands.Start();
cmdCommands.WaitForExit();
if (EncodingStopped)
break;
cmdCommands.StartInfo.UseShellExecute = false;
cmdCommands.StartInfo.CreateNoWindow = true;
cmdCommands.StartInfo.RedirectStandardOutput = true;
cmdCommands.StartInfo.FileName = SC.GetAVS2PipeModPath();
cmdCommands.StartInfo.Arguments = string.Format("{0} \"{1}\" -wav", SC.GetAVS2PipeModPath(), filename + ".avs");
cmdCommands.Start();
Thread OpusThread = new Thread(() => OpusEncode(filename, OpusCheck));
OpusThread.Start();
cmdCommands.StandardOutput.BaseStream.BeginRead(ReadBuffer, 0, ReadBuffer.Length, PipeWrite, null);
cmdCommands.WaitForExit();
OpusCheck.WaitOne();
if (EncodingStopped)
break;
cmdCommands = new Process();
cmdCommands.StartInfo.UseShellExecute = false;
cmdCommands.StartInfo.RedirectStandardError = true;
cmdCommands.StartInfo.FileName = SC.GetMKVMergePath();
cmdCommands.StartInfo.Arguments = (" -o \"" + filename + "-muxed.mkv\" \"" + filename + ".mkv\" " + "\"" + filename + ".opus\"");
cmdCommands.Start();
cmdCommands.WaitForExit();
File.Delete(filename + ".mkv");
File.Delete(filename + ".opus");
}
}
catch (Exception e)
{
MessageBox.Show(e.Message);
}
}
StopEncoding.Dispatcher.BeginInvoke(DispatcherPriority.Normal, new System.Action(() => { StopEncoding.IsEnabled = false; Encode.IsEnabled = true; }));
}
private void OpusEncode(string filename,AutoResetEvent OpusCheck)
{
OpusEncoder.StartInfo.UseShellExecute = false;
OpusEncoder.StartInfo.RedirectStandardInput = true;
OpusEncoder.StartInfo.FileName = SC.GetOpusEncPath();
OpusEncoder.StartInfo.Arguments = string.Format("{0} - \"{1}\"", SC.GetOpusSettings(true), filename + ".opus");
OpusEncoder.Start();
byte[] temp;
while (QU.TryTake(out temp, Timeout.Infinite))
{
if (temp.Length == 0)
break;
OpusEncoder.StandardInput.BaseStream.Write(temp, 0, temp.Length);
}
OpusEncoder.StandardInput.Close();
OpusEncoder.WaitForExit();
OpusCheck.Set();
}
I want to know if this approach is the way to go, or if iI am handling this wrong. And also if it can be more efficient, which probably goes in hand with it being righright/wrong.
