Reply to thread

Message

<blockquote data-quote="el Filou" data-source="post: 1303707" data-attributes="member: 78516">OK I found the cause: before I saw the posts about the VC redist, because I had noted that the crashes were only happening with files other than .ts - i.e. those that were loaded by LAV instead of TsReader - I had tried changing the codec config from &quot;LAV Splitter Source&quot; to &quot;File source (async)&quot; because I had remembered reading in LAV's official thread on Doom9 that File source (async) was supposed to be the default way of reading from media files.Now I've set this option back to LAV Splitter Source and I have no crashes anymore. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> Thanks anyway for the ideas. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" />Edit: source:OK. It's still weird that Titan gives those errors: I have 4 GB dedicated VRAM and 8 GB system RAM, so 8 GB usable by the GPU in total, and no other application opened when I took the logs. Anyway, that was not the issue as I am not seeing those errors with DefaultWide HD.Unfortunately not. It works by being loaded as a DirectShow audio renderer filter, so it needs to be the same architecture as the process, like is the case with other filters like LAV.</blockquote>

[QUOTE="el Filou, post: 1303707, member: 78516"] OK I found the cause: before I saw the posts about the VC redist, because I had noted that the crashes were only happening with files other than .ts - i.e. those that were loaded by LAV instead of TsReader - I had tried changing the codec config from "LAV Splitter Source" to "File source (async)" because I had remembered reading in LAV's official thread on Doom9 that File source (async) was supposed to be the default way of reading from media files. Now I've set this option back to LAV Splitter Source and I have no crashes anymore. :) Thanks anyway for the ideas. (y) Edit: source: OK. It's still weird that Titan gives those errors: I have 4 GB dedicated VRAM and 8 GB system RAM, so 8 GB usable by the GPU in total, and no other application opened when I took the logs. Anyway, that was not the issue as I am not seeing those errors with DefaultWide HD. Unfortunately not. It works by being loaded as a DirectShow audio renderer filter, so it needs to be the same architecture as the process, like is the case with other filters like LAV. [/QUOTE]

Verification