Search:

Type: Posts; User: Deathsimple; Keyword(s):

Page 1 of 4 1 2 3 4

Search: Search took 0.25 seconds.

  1. The driver tells the state tracker what mode it...

    The driver tells the state tracker what mode it supports (field vs. frame) and which should be used by default. The VDPAU state tracker can deal with both, but NV_vdpau_interop can't.

    My...
  2. As far as I know the RV515 is the only R5xx card...

    As far as I know the RV515 is the only R5xx card with UVD.
  3. Sounds like the fallback works better than I...

    Sounds like the fallback works better than I thought. But take a screen shot and compare it (binary) with a VDPAU output. You will find that you only got halve the desired resolution.

    The issue is...
  4. Ah! Thanks for the notification, that's just a...

    Ah! Thanks for the notification, that's just a bug. Going to provide a mesa patch.



    The field based output is needed to correctly display the picture after decoding. E.g. you will still see the...
  5. Well that's the point where the only best effort...

    Well that's the point where the only best effort starts ;)

    The first problem is that in theory the released code should work on the very few R5xx boards that have UVD as well, but nobody ever...
  6. Maybe I should explain a bit more UVD isn't a...

    Maybe I should explain a bit more UVD isn't a singular block. You've got a VCPU, memory controller, register bus, motion compensator etc...

    Those blocks where updated separately in different UVD...
  7. Actually Jay Cornwall implemented this stuff and...

    Actually Jay Cornwall implemented this stuff and Alex pushed it through review.

    I was just the one to cleanup and release the patches.
  8. Correct, there is no support for it before NI and...

    Correct, there is no support for it before NI and even NI-CIK only support it for VRAM not GART.
  9. You should have waited a slightly bit longer....

    You should have waited a slightly bit longer. I've just pushed out a patch that will improve performance for SI and CIK quite a bit:...
  10. I think the problem is rather that before using...

    I think the problem is rather that before using VCE the hardware is scaling up and down depending on 3D load as expected, but after using VCE for the first time that doesn't seem to work any more.
    ...
  11. Quite nice, considering how often we copy the...

    Quite nice, considering how often we copy the data from VRAM to system memory and back, but I guess you didn't tried any full screen 3D application. There is still allot of things we can optimize.
    ...
  12. Yeah, and it was just another missing flush as...

    Yeah, and it was just another missing flush as well.

    Just updated my branch on fdo, anybody interested should pull and retest.

    Christian.
  13. Thx for testing, going to work a bit more on...

    Thx for testing, going to work a bit more on this.



    We currently only support NV12 as input, try putting a "videoconvert" element in between.
  14. No, it was actually quite a bit faster, take a...

    No, it was actually quite a bit faster, take a look at the progress numbers.

    It looks more like we never reached 100% done because of some error in the EOS handling and then Pontostroy killed the...
  15. Yes, here is my gstomx.conf: [omxh264dec]...

    Yes, here is my gstomx.conf:



    [omxh264dec]
    type-name=GstOMXH264Dec
    core-name=/usr/lib/libomxil-bellagio.so.0
    component-name=OMX.radeonsi.video_decoder.avc
    rank=256
    in-port-index=0
  16. What mesa branch are you using? I only pushed the...

    What mesa branch are you using? I only pushed the decoder upstream, the encoder can be found here: http://cgit.freedesktop.org/~deathsimple/mesa/log/?h=vce-release

    Cheers,
    Christian.
  17. The probably best way is to contact me direct by...

    The probably best way is to contact me direct by mail (christian.koenig@amd.com).

    I can give you a walkthrough how to build and use the necessary software components.

    Cheers,
    Christian.
  18. VDPAU is still our primary recommendation for...

    VDPAU is still our primary recommendation for desktop video decoding. The OpenMAX state tracker is mostly for VCE bringup and to better support GStreamer.



    Correct yes. Appart from that the...
  19. The flexibility is more on the input side. E.g....

    The flexibility is more on the input side. E.g. you can push a variety a data in it, but you always get an elementary stream as result. We might get slice level data output in a future VCE...
  20. Sorry forgotten to explain that. The encoding...

    Sorry forgotten to explain that. The encoding part of VA-API works with slice level data, but the output of VCE is an elementary stream.

    So to support VA-API the software stack would look...
Results 1 to 20 of 74
Page 1 of 4 1 2 3 4