Announcement

Collapse
No announcement yet.

10.5 is out. come and get it.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    WildcatWhiz
    Junior Member

  • WildcatWhiz
    replied
    Originally posted by LinuxID10T View Post
    No, it isn't working, but that was said in the other thread. In fact, it may never come to the 5xxx series through UVD. Perhaps in a shader powered OpenCL version, but not in the driver unfortunately. I will say this though, ATI always has something up their sleve, for example they were the first to have OpenGL 3.3 & 4.0 in Linux. So perhaps they will surprise us. It is still a hope though. Seriously though, I don't particularly like getting into flame wars.
    My apologies if we've been getting into a flame war. I'd advise you to be careful about calling people "noobs". It's very demeaning.

    MAN I wish I knew that feature wasn't support in Linux before I bought the card. I feel like such a schmuck for not doing my research.

    So what I've come to understand is that my tearing problem is related to the fact that I'm using a compositor, whether it be Kwin or Compiz.

    (If any ATI developers out there are listening) My wishlist for improved features would be:

    *Vsync that works when a compositor is enabled.
    *GPU-accelerated video playback. I know I know, modern CPUs can do just fine. But it's nice to know that my beast of a card is being put to good use (that's what I bought it for, right ) and my CPU can happily process other tasks.

    Leave a comment:

  • LinuxID10T
    Senior Member

  • LinuxID10T
    replied
    Originally posted by WildcatWhiz View Post
    Really? Do you have to get the last word in? I actually did read a vast majority of the pages. My question is valid: what is the status of xvba support with the HD5xxx (R800) series cards?
    No, it isn't working, but that was said in the other thread. In fact, it may never come to the 5xxx series through UVD. Perhaps in a shader powered OpenCL version, but not in the driver unfortunately. I will say this though, ATI always has something up their sleve, for example they were the first to have OpenGL 3.3 & 4.0 in Linux. So perhaps they will surprise us. It is still a hope though. Seriously though, I don't particularly like getting into flame wars.

    Leave a comment:

  • mirv
    Senior Member

  • mirv
    replied
    Originally posted by WildcatWhiz View Post
    Really? Do you have to get the last word in? I actually did read a vast majority of the pages. My question is valid: what is the status of xvba support with the HD5xxx (R800) series cards?
    As far as I knew, xvba isn't officially supported in fglrx at all. It's there, people can use it, but AMD haven't officially released it.

    Leave a comment:

  • WildcatWhiz
    Junior Member

  • WildcatWhiz
    replied
    Originally posted by WildcatWhiz View Post
    Really? Do you have to get the last word in? I actually did read a vast majority of the pages. My question is valid: what is the status of xvba support with the HD5xxx (R800) series cards?
    For the rest of you out there who interested in Catalyst 10.5, and not our flame wars, I apologize

    Leave a comment:

  • WildcatWhiz
    Junior Member

  • WildcatWhiz
    replied
    Originally posted by LinuxID10T View Post
    Yeah, posts #824 and #825. You obviously didn't read the other 82 pages. You problem was long since explained. There is a reason that nobody replied to your post.
    Really? Do you have to get the last word in? I actually did read a vast majority of the pages. My question is valid: what is the status of xvba support with the HD5xxx (R800) series cards?

    Leave a comment:

  • LinuxID10T
    Senior Member

  • LinuxID10T
    replied
    Originally posted by WildcatWhiz View Post
    I have posted a couple of times now in the "AMD's UVD2-based XvBA Finally Does Something On Linux" thread. Do your own research, pal.
    Yeah, posts #824 and #825. You obviously didn't read the other 82 pages. You problem was long since explained. There is a reason that nobody replied to your post.

    Leave a comment:

  • WildcatWhiz
    Junior Member

  • WildcatWhiz
    replied
    Originally posted by LinuxID10T View Post
    All I was trying to say is that this issue has been discussed already. If you looked at the "AMD's UVD2-based XvBA Finally Does Something On Linux" you would have known already, rather than complaining into a thread that really has nothing to do with your problem. In fact, 10.5 actually FIXED video acceleration for me. Unfortunately you have a 5xxx series card that doesn't have XvBA. On the 2xxx-4xxx series with a little hack you get h.264 video acceleration. However even with video acceleration, it has NOTHING to do with tearing. BTW, DVDs are not encoded in h.264. Again I am not trying to belittle you, but you have been making yourself look like a so called "noob" by not doing more research before posting. If you did, but had a problem and posted it, my tone here would be dramatically different. Also, Vsync is Vsync, if you get tearing still, there is probably something else wrong.
    I have posted a couple of times now in the "AMD's UVD2-based XvBA Finally Does Something On Linux" thread. Do your own research, pal.

    Leave a comment:

  • LinuxID10T
    Senior Member

  • LinuxID10T
    replied
    Originally posted by WildcatWhiz View Post
    Calling me a "noob" isn't belittling?

    Fact: On Windows 7, which has full GPU-decoding of H.264 content, I experience no tearing.

    Fact: On Linux, where GPU-decoding is not supported (hence all decoding of h.264 content is handled by the CPU) I do experience tearing, even with OpenGL/Vsync enabled. The HD5xxx cards don't support GPU-decoding in Linux. Plain and simple. Unless someone figures out how to tap into xvba, I'm screwed.

    What doesn't make sense to you?
    All I was trying to say is that this issue has been discussed already. If you looked at the "AMD's UVD2-based XvBA Finally Does Something On Linux" you would have known already, rather than complaining into a thread that really has nothing to do with your problem. In fact, 10.5 actually FIXED video acceleration for me. Unfortunately you have a 5xxx series card that doesn't have XvBA. On the 2xxx-4xxx series with a little hack you get h.264 video acceleration. However even with video acceleration, it has NOTHING to do with tearing. BTW, DVDs are not encoded in h.264. Again I am not trying to belittle you, but you have been making yourself look like a so called "noob" by not doing more research before posting. If you did, but had a problem and posted it, my tone here would be dramatically different. Also, Vsync is Vsync, if you get tearing still, there is probably something else wrong.

    Leave a comment:

  • bwat47
    Senior Member

  • bwat47
    replied
    omg I hate the one minute edit limit on these forums so much. Anyway was gonna ad at the end of my post:

    With compiz off I also have to use opengl + ccc vsync to get no tearing.

    Leave a comment:

  • bwat47
    Senior Member

  • bwat47
    replied
    Originally posted by bridgman View Post
    1. OK, separate issue. You *want* video decode, that's fair. The point I'm trying to make is that the presence or absence of decode acceleration is not related to tearing.

    OSes with the largest market share tend to get new features first, then those features trickle down to OSes with lesser market share over time. Video decode acceleration is mid-trickle.

    2. You need to turn off your compositor for testing, so you can feel confident that tearing and video decode acceleration are not linked. Then you can turn it back on again.

    I'm not sure what the exact deal is with compositors and vsync; opinions seem to vary between compositor bugs which need driver hacks to work around them to missing, but unspecified features in the driver which *would* be used if they were present. Then again, my focus is on the open source side so I haven't really looked into fglrx + compositing + video.
    I've been told its because fglrx uses indirect rendering for compositing which does not work with vsync at all. The open source driver seems to use direct rendering.

    With fglrx setting vsync to always on, and/or setting compiz to sync to vblnank has zero effect and compiz tears quite noticeably. I can get video to not tear with compiz if I set ccc to always vsync, output video in opengl, use undirect fullscreen windows in compiz and play the vid in fullscreen but the opengl output looks like crap for me.

    Leave a comment:

Working...
X