Subtitles issues v1.3.0.0 (1 Viewer)

[Sebastiii]

When talking with Tourette about the issue :
1) D3DERR_INVALIDCALL - more infor would be needed. He needs to use DirectX debug logging from the DirectX itself to be able to see why the call is invalid
2) Timeout=1,84467440737096E+19 <--- almost infinite subtitle timeout - not sure how it can happen

Since all is working with DVBSub2 but maybe something wrong with DirectX and new implementation in DVBSub3.

 

[tourettes]

Since all is working with DVBSub2 but maybe something wrong with DirectX and new implementation in DVBSub3.

DVBSub2/3.ax aren't using DirectX (althou if I would have some extra time they would be optimized ).

 

[burr]

I have tested your build to fix the enumeration exception and this error is not there anymore but the directx exceptions still remain.

I have also tested to do a clean install of the client but still the same.

 

[Sebastiii]

Can you try :
http://www.softpedia.com/get/System/OS-Enhancements/Microsoft-DirectX-Control-Panel.shtml
Start file inside zip files (directx.cpl) go to direct3d :
Use debug version of direct3d and set debug output level to more.
it will give more info about the issue
Ah also :
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
and then use that Debug View to see the DirectX logging ...don't be scared... you will get LOT of warnings
I'm quoting Tourette here
Thanks.

 

[burr]

Do i have to download directx SDK to get to debug mode, i can't move the slider when i open "directx.cpl"?

 

[Sebastiii]

Ah good question, it's possible i have the sdk and i can move the slider.

 

[burr]

The SDK was the trick here is the logs

00020862 20:46:06 [3524] Direct3D9: (ERROR) 3DUSAGE_DYNAMIC cannot be used with managed vertex buffers
00020863 20:46:06 [3524]
00020864 20:46:06 [3524] Direct3D9: (ERROR) :Failure trying to create Vertex Buffer

 

[Scythe42]

Dynamic Textures cannot be used with a managed D3D Pool. Or in D3D terms. D3DUSAGE_DYNAMIC and D3DPOOL_MANAGED are incompatible.

In this case it's about the Vertex Buffers. Static Vertex Buffers are placed into video memory and dynamic ones in the AGP memory. If D3DUSAGE_DYNAMIC is not specified the vertex buffers are made static.

The only reason to use dynamic vertex buffers is that you don't have to lock them. Locking has huge performance penalties as the lock forces a wait until the GPU finished reading vertex/inde data from the buffer before control is given back to an app. Locking a static buffer several times per frame prevents the GPU from buffering rendering commands. Without buffered commands the GPU remains idle until the app finished filling the vertex buffer/index buffer.

Normally the vertex or index data should not change. There are of course applications where this is needed on every frame. This is the only reason to use D3DUSAGE_DYNAMIC.

So if we don't change vertex/index data no need of D3DUSAGE_DYNAMIC should be given. Need to take a look at the code itself what we do with the vertex buffers. But honestly the vertex buffer should be the always the same. At least during one frame. Locking between frames would be OK, but still has performance penalties.

Subtitles should be rendered to a texture, and the texture is displayed with the same vertices anyway. Don't really see the need to change the vertices here. Rendering each letter as it's own object would be a bit of an overkill. Rendering them to a texture and them pumping this texture to the GPU should be faster.

I need to take a look at the code itself to see what we are doing. But if this can be fixed easily I guess as it seems to be introduced recently. But let me take a look at the code first.

 

[burr]

Dynamic Textures cannot be used with a managed D3D Pool. Or in D3D terms. D3DUSAGE_DYNAMIC and D3DPOOL_MANAGED are incompatible.

In this case it's about the Vertex Buffers. Static Vertex Buffers are placed into video memory and dynamic ones in the AGP memory. If D3DUSAGE_DYNAMIC is not specified the vertex buffers are made static.

The only reason to use dynamic vertex buffers is that you don't have to lock them. Locking has huge performance penalties as the lock forces a wait until the GPU finished reading vertex/inde data from the buffer before control is given back to an app. Locking a static buffer several times per frame prevents the GPU from buffering rendering commands. Without buffered commands the GPU remains idle until the app finished filling the vertex buffer/index buffer.

Normally the vertex or index data should not change. There are of course applications where this is needed on every frame. This is the only reason to use D3DUSAGE_DYNAMIC.

So if we don't change vertex/index data no need of D3DUSAGE_DYNAMIC should be given. Need to take a look at the code itself what we do with the vertex buffers. But honestly the vertex buffer should be the always the same. At least during one frame. Locking between frames would be OK, but still has performance penalties.

Subtitles should be rendered to a texture, and the texture is displayed with the same vertices anyway. Don't really see the need to change the vertices here. Rendering each letter as it's own object would be a bit of an overkill. Rendering them to a texture and them pumping this texture to the GPU should be faster.

I need to take a look at the code itself to see what we are doing. But if this can be fixed easily I guess as it seems to be introduced recently. But let me take a look at the code first.

Have you had any time to look at the code?

 

[Scythe42]

Not yet, currently in the hospital. But I didn't forget this.