[solved] MP 1.38 crashes with video play after updating from 1.37 to 1.38 (1 Viewer)

[doskabouter]

well, I'm still running 32bit and use subtitles quite a lot, so no structural problem with that I suppose

 

[ajs]

I think it's related to Titan (too heavy for my 4 GB VRAM ?), because I don't see those messages with my normal setup that uses Default Wide HD (MP's debug tool forces switching to Titan to generate the logs)

I'm using Titan on i3 3225 with integrated graphics, no problems.

 

[ajs]

ReClock which is 32-bit only.

This external software, as far as I remember, should also connect to x64.

 

[ajs]

Is it possible to install 32-bit and 64-bit MP concurrently on the same machine to test?

Yes

 

[el Filou]

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.

Edit: source:

LAV Filters changelog - 0.23 - 2011/04/21

LAV Splitter

• Added support for using the "File Source (Async)" (and others) together with LAV Splitter
• This is the new default mode for improved compatibility!

I'm using Titan on i3 3225 with integrated graphics, no problems.

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.

This external software, as far as I remember, should also connect to x64.

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.

 

[ajs]

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.

Maybe it's not the video memory, I don't know what DirectX uses. But I've never used DefaultWide HD, I've always used Titan since it came out. And I've never seen such an error, although I use all possible fanart and clearart etc.