Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] DX11 several optimizations of copying frames to/from gpu. #7637

Merged
merged 3 commits into from
Aug 21, 2015

Conversation

afedchin
Copy link
Member

Set of improvements. For more info please see commit messages.

  1. CopyDXVA2Picture - here is a comparsion between different methods of copying dxva FHD frame into sysmem.
    gpucopy
  2. CProcessorHD::Convert - here is a comparsion between old memcpy and new sse2 method (used FHD frame).
    dxvacopy

@fritsch @FernetMenta please take a look.

@afedchin afedchin added RFC PR submitted for gathering feedback v16 Jarvis labels Jul 27, 2015
return SUCCEEDED(hr);
}

void YUVBuffer::PerformCopy()

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

@a11599
Copy link

a11599 commented Jul 28, 2015

Does it make sense to keep the AS setting with this speed improvement? We could maybe honor the GUI setting for PS render method now. Those who want DXVA rendering for HW decoded video can still use Auto render method.

@afedchin
Copy link
Member Author

@FernetMenta I've updated this. moved the copying frame back to a decoder thread. please take a look

@a11599 I'm not sure. We get a real benefit on sse4 systems only. But at the other side, porting to dx11 already drops supporting some very old and legacy GPUs. Those who want PS rendering with hw decoder already knows about AS setting. Also take in account what we enabled HQ scalers with dxva rendering already by-default. Which benefit of PS rendering? Need to discuss this.

@a11599
Copy link

a11599 commented Jul 29, 2015

Actually the benefit I see from PS rendering over DXVA is that the D3D11 video processor will not do something behind your back with the image. Good for purists. Also currently both PS and Auto render method do the same without the AS making the two options redundant. But I do not want to hijack this PR so sorry for the noise.

@afedchin
Copy link
Member Author

@a11599 I need your opinion also. Let's start a thread at the forum (perhaps public) to discuss that. What do you think?

@a11599
Copy link

a11599 commented Aug 5, 2015

For now I think this is good as-is. Maybe later if (ever) our PS renderer gets some quality improvements like dithering we migth rethink the AS. Would be nice to test on a non-sse4 cpu but I do not have any. Maybe we can provide some test build and ask for testers on the forum?

@FernetMenta
Copy link
Contributor

@afedchin sorry, I almost missed that you pinged me. You are the expert here. From what I can tell it looks ok.

@afedchin afedchin force-pushed the dx11_optimize3 branch 2 times, most recently from e2626d4 to 19907fb Compare August 6, 2015 13:13
@afedchin
Copy link
Member Author

afedchin commented Aug 6, 2015

updated and squashed. jenkins build this please

@MartijnKaijser
Copy link
Member

jenkins build this please

@MartijnKaijser MartijnKaijser added this to the Jarvis 16.0-alpha2 milestone Aug 11, 2015
@hudokkow
Copy link
Member

@afedchin please rebase

@afedchin
Copy link
Member Author

jenkins build this please

@afedchin
Copy link
Member Author

jenkins build and merge

@jenkins4kodi jenkins4kodi merged commit cdb3fa7 into xbmc:master Aug 21, 2015
@afedchin afedchin deleted the dx11_optimize3 branch August 21, 2015 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC PR submitted for gathering feedback v16 Jarvis
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants