Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 720827" data-attributes="member: 21313">I would indeed guess that similar changes would give the same (good) results. But the code in Argus is written in C#, and tswriter in C++ (plus the internal handling of the stream and demuxer is totally different). So using (parts of) my code directly is not really an option.Duplicating the same two changes in behavior is an option. Perhaps disaster123 can look at this, like he did for the .tshift format?For those confused by the term, asynchronous I/O is a standard feature of Windows: <a href="http://msdn.microsoft.com/en-us/library/aa365683(v=vs.85).aspx" target="_blank">Synchronous and Asynchronous I/O (Windows)</a>And pre-creating the next .ts file is pretty easy too: just make sure the .ts2.ts is there when writing commences on .ts1.ts. Then create .ts3.ts the moment writing starts on .ts2.ts, and so on... Until you loop and all files are there.</blockquote>

[QUOTE="dvdfreak, post: 720827, member: 21313"] I would indeed guess that similar changes would give the same (good) results. But the code in Argus is written in C#, and tswriter in C++ (plus the internal handling of the stream and demuxer is totally different). So using (parts of) my code directly is not really an option. Duplicating the same two changes in behavior [u]is[/u] an option. Perhaps disaster123 can look at this, like he did for the .tshift format? For those confused by the term, asynchronous I/O is a standard feature of Windows: [url=http://msdn.microsoft.com/en-us/library/aa365683(v=vs.85).aspx]Synchronous and Asynchronous I/O (Windows)[/url] And pre-creating the next .ts file is pretty easy too: just make sure the .ts2.ts is there when writing commences on .ts1.ts. Then create .ts3.ts the moment writing starts on .ts2.ts, and so on... Until you loop and all files are there. [/QUOTE]

Verification