video overlay

[matt]

Do either of the drivers (RadeonHD or fglrx) support video overlay
acceleration on the x1250? I'm wanting to use my gigabyte mobo with
HDMI and the x1250 IGP as a media center (linux + mythtv) but I'm not
getting very good performance out of the video drivers when I switch
to fullscreen mode in vlc.

Thanks!

[JoJo jojo]

Hi Matt

set overlay using this under fglrx.
#aticonfig --overlay-type=Xv

if you mean hardware video playback acceleration, thats called AVIVO
(look here for AVIVO capability
https://groups.google.com/group/x1250/web/ati-radeon-x1250-specifications )

AVIVO does _not_ work under linux(FGLRX, RADEONHD)....currently.

-Jojo

[Petr Hlávka]

Hello,

IMHO XVideo overlay is not supported even with fglrx driver, see

http://www.phoronix.com/forums/showthread.php?t=6240

however gl2 video output works fine for me with mplayer.

Petr Hlavka.

[djdoo]

Folks the only think I can say for video playback on linux until now
for our card is that it is problematic.
We cannot use Xv overlay and also TexturedVideo is not working for us
either for the moment of speaking.

The only program that can play good video for me is Xine with the
openGL video driver selected and as OpenGL Renderer-> 2D_Tex_Tiled. I
wonder if this action means beta support for TexturedVideo... Who
knows...

The most weird thing is that programs that use Xine-engine (example
Kaffeine) cannot load the openGL video driver!!

Only Xine-Ui works here. And it gives excellent video quality for me
with openGL video driver :)... Try the same combo and tell me your
results.

[macauhtpc]

The latest AMD Catalyst 7.12 Linux driver supports XV overlay for
X1250. However, I got diagonal tearing on the videos when enabling Xv
overlay in mplayer. Has anyone here experience the same issue?
BTW, I am using Asus Barebone P2-MA690G. Can I upgrade my video bios
with the video rom file provided in this forum? Thanks!
-Bruce

[JoJo jojo]

Hi Bruce

How did you conclude that XV/XVideo is supported for X1250 ?

As per the release notes, the diagonal tearing noticed by you is a
"known issue".
(so in short, yeah, everyone has noticed it)

The purpose of uploading the Video BIOS was to help the RadeonHD devs,
code around the issues with various BIOS software,
it is not intended for users to flash their video BIOS with ;-)

All you can be adviced to do is to get the latest BIOS/firmware
updates from your board manufacturer(Asus in this case) & apply those.

If it interests/suits you, you can help by testing & filing bugs with
the latest RadeonHD driver, on their mailinglist.

-Jojo

[djdoo]

> > The latest AMD Catalyst 7.12 Linux driver supports XV overlay for
> > X1250. However, I got diagonal tearing on the videos when enabling Xv
> > overlay in mplayer. Has anyone here experience the same issue?
> > BTW, I am using Asus Barebone P2-MA690G. Can I upgrade my video bios
> > with the video rom file provided in this forum? Thanks!
> > -Bruce
>

No way man...

7.12 Driver Kernel 2.6.24-rc6:

(WW) fglrx(0): Textured Video is currently not supported on IGP
hardware.
(WW) fglrx(0): Video Overlay not supported on AVIVO based graphics
cards.

From my xorg.0.log...
Will they ever give us the oportunity to watch some damn stable video
with this chip??

[macauhtpc]

Hi Jojo,

Thanks for the information!
BTW, I am not the only one who had the xvideo working on x1250 with
the latest driver. Here is a post I found on the forum.

http://www.phoronix.com/forums/showthread.php?t=7007&page=16

I will post my Xorg.0.log later after I go home.

I have tried the readeonhd driver too. I was surprised by the quality
of the driver. The first time I tried, I could not get the display out
of my HDMI, but the next try with 1.1.0 version, HDMI worked. I ran
even better than fglrx. However, it doesn't support XVideo overlay
currently. :( Once XV is working with radeonhd, I think I will switch
off fglrx.

BR,
Bruce

[djdoo]

On 28 Δεκ, 05:24, macauhtpc <bruce.si...@gmail.com> wrote:
> Hi Jojo,
>
> Thanks for the information!
> BTW, I am not the only one who had the xvideo working on x1250 with
> the latest driver. Here is a post I found on the forum.
>
> http://www.phoronix.com/forums/showthread.php?t=7007&page=16
>
> I will post my Xorg.0.log later after I go home.
>
> I have tried the readeonhd driver too. I was surprised by the quality
> of the driver. The first time I tried, I could not get the display out
> of my HDMI, but the next try with 1.1.0 version, HDMI worked. I ran
> even better than fglrx. However, it doesn't support XVideo overlay
> currently. :( Once XV is working with radeonhd, I think I will switch
> off fglrx.
>
> BR,
> Bruce
>

Hmm...

I tried the exact configuration this guy posted at Phoronix but I
still get the 2 classical warnings about XV and Textured Video at my
xorg.0.log....

But the fact that OpenGL driver works with Xine is very strange
also....

OpenGL 2D = Textured Video?? Or am I wrong here?

According to my xorg.0.log I should not be able to play DVD Video at
all... What's going on here?

Also the warning about TexturedVideo sais "not currently supported"...
This supposed to mean it will be in the near future?

Maybe for the mobile version of the card it is already here. Cause the
post at Phoronix spoke about a laptop.

Fog is all around the video playback...

[macauhtpc]

jojo,

Here is some log info..

dmesg
...
[ 12.772000] fglrx: module license 'Proprietary. (C) 2002 - ATI
Technologies, Starnberg, GERMANY' taints kernel.
[ 12.784000] [fglrx] Maximum main memory to use for locked dma
buffers: 804 MBytes.
[ 12.784000] [fglrx] ASYNCIO init succeed!
[ 12.784000] [fglrx] PAT is enabled successfully!
[ 12.784000] [fglrx] module loaded - fglrx 8.44.3 [Dec 19 2007] on
minor 0
...

/var/log/Xorg.0.log

(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
...
(II) Primary Device is: PCI 01:05:0
(II) ATI Proprietary Linux Driver Version Identifier:8.44.3
(II) ATI Proprietary Linux Driver Release Identifier:
UNSUPPORTED-8.443.1
(II) ATI Proprietary Linux Driver Build Date: Dec 19 2007 21:29:14
(--) Assigning device section with no busID to primary device
(--) Chipset Supported AMD Graphics Processor (0x791E) found
(II) AMD Video driver is running on a device belonging to a group
targeted for this release
(II) AMD Video driver is signed
...
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin, [x]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): PCI bus 1 card 5 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp
pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "OpenGLOverlay" "off"
(**) fglrx(0): Option "VideoOverlay" "on"
(**) fglrx(0): Option "DPMS" "true"
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(--) fglrx(0): Chipset: "ATI Radeon X1200 Series" (Chipset = 0x791e)
(--) fglrx(0): (PciSubVendor = 0x1043, PciSubDevice = 0x8287)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT
original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xf0000000
(--) fglrx(0): MMIO registers at 0xfe9f0000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.1.0
ABI class: X.Org Video Driver, version 1.2
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 10.48
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies
Inc.
(II) fglrx(0): VESA VBE OEM Product: RS690
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
...

I had the same error message complaining XVideo not supported in IGP,
but it is gone in 7.12.
BTW, the installation of kernel module in 7.12 is kind of differernt
then 7.11.
Hope the info helps you.

-B

[Lelik Bolik]

I think everything is more or less clear about XVideo support: in
early version of fglrx driver 8.30.3 it was reported, that loading of
xvideo extension caused segfault of X server. So instead of fix that
bug, not so clever ATI engineers just disabled this feature. I can
confirm, that 7.12 driver on my x1250 X reports, that currently there
is no Xvideo support for avivo cards. So let's hope, that radeonhd
will support it soon.
Best regards.

[Oleksiy Kokachev]

Dear all.
Good news here. AMD/ATI will release next week specs for ATI RS690
chip.
http://www.phoronix.com/scan.php?page=news_item&px=NjI2MQ
So let's hope, that x1250 will be fully supported by radeonhd and
radeon drivers ay the beginning of 2008.

On 27 дек, 21:47, "JoJo jojo" <onetwoj...@gmail.com> wrote:
> Hi Bruce
>
> How did you conclude that XV/XVideo is supported for X1250 ?
>
> As per the release notes, the diagonal tearing noticed by you is a
> "known issue".
> (so in short, yeah, everyone has noticed it)
>
> The purpose of uploading the Video BIOS was to help the RadeonHD devs,
> code around the issues with various BIOS software,
> it is not intended for users to flash their video BIOS with ;-)
>
> All you can be adviced to do is to get the latest BIOS/firmware
> updates from your board manufacturer(Asus in this case) & apply those.
>
> If it interests/suits you, you can help by testing & filing bugs with
> the latest RadeonHD driver, on their mailinglist.
>
> -Jojo
>

[Oleksiy Kokachev]

I think everything is more or less clear about XVideo support: in
early version of fglrx driver 8.30.3 it was reported, that loading of
xvideo extension caused segfault of X server. So instead of fix that
bug, not so clever ATI engineers just disabled this feature. I can
confirm, that 7.12 driver on my x1250 X reports, that currently there
is no Xvideo support for avivo cards. So let's hope, that radeonhd
will support it soon.
Best regards.
On Dec 28, 2007 1:11 PM, djdoo <jimd...@yahoo.gr> wrote:
>
>
>

[djdoo]

@macauhtpc:

Can you please pastebin your complete xorg.conf and your xorg.0.log in
order to configure them the same way ??
Or just post them here...

I would be really glad to find out what's going on here and how the
hell you do not get the classic warning message at xorg.0.log...

[macauhtpc]

Jojo,

I've uploaded the Xorg.o.log and xorg.conf file in file section. It is
named Xorg.tar.gz.
Hope it helps.

Best,
Bruce

[djdoo]

@macauhtpc:

Thanks a lot for the 2 files my friend...

I think I figured out what's going on here...

If you haven't noticed it at your xorg.0.log, you also have
TexturedVideo Enabled and X also loads GLESX module which is a
hidden's option result and boosts 2D visuals but at your xorg.conf
there is nowhere the option "Textured2D" "True"!!

I think the only difference we have is that you are using a 32-Bit
system and I am using a 64-Bit one!!

And I think this is the case!
XV and Textured features work now under 32-bit environment with 7.12
Fglrx but under 64-bit they still don't work...

And btw I'm djdoo not JoJo...

[JoJo jojo]

well well well,
another year gone by, AMD/ATI is _still_ behind NVIDIA,
there's hope that AMD/ATI will move in the generally right direction, and
that fglrx will be as good as its windows version in terms of features,
radeonHD/Suse seems a bit disappointing currently, and plans are to
_maybe_ achieve 80% of features of the _current_ windows fglrx driver !

At this point we have to review, how many bugs have each of us filed ?
in either of the 2 drivers?
or for that matter how many of us are following up on existing
bugs/bug discussions ?

@Bruce S, thanks for the xorg.log

@djdoo, are you sure that's the _only_ difference?
he's using sharp HDMI interface, are you using HDMI interface as well?

I believe we need a more basic test for video overlay,
How can i determine whether video overlay is working on my gfx card?
here is what we are talking about
http://en.wikipedia.org/wiki/Hardware_overlay

apparently, if h/w video overlay (XV/XVideo) is working,
then the screenshot of a video playing can't be captured
(at the very least thats my understanding of it)

OR, in mplayer preferences>video, under videodriver select XV,
and see if it works.

Does anyone have a better idea,
we all would love to hear what you have to say.

-JoJo

[djdoo]

@Jo Jo:

I don't think HDMI interface has anything to do with the fact that he
can load XV, TexturedVideo and GLESX and I can't. Also HDMI uses the
same controller with DVI port so what's the difference?

We run the same driver, we have the same Xorg version, we have exactly
the same video chipset, but we use different system architecture.

Let me remind you of a bug that FGLRX had about XV video overlay under
64-bit systems with X1k Radeon cards that caused X to restart each
time you were trying to play a video file. It happened only under 64-
bit environments!!

If I have understood correct the new fglrx driver has a new 3D
codebase! 2D seems to have the same problems with the 8.40.4 version.
And I can confirm 3D framerates more than doubled here since 8.40...

Btw I have HDMI interface available here cause my MB is MSI K9AG Neo2
Digital and it is enabled I just cannot try it right now cause I don't
own one of those Huge LCD TVs :( ...

Also about RadeonHD why should anyone use it right now exept for
helping the devs go on improving it?
It offers nothing for us at the moment (no 3D, no 2D accel) so we are
stuck with fglrx where at least we can play 3D games and run Compiz-
Fusion...

My conclusion for the year is that AMD has really changed the way ATI
used to support the opensource community but there is still a lot of
work to be done...

Also for me FGLRX has a much more prominent future in comparison with
nvidia driver, cause it uses
Xorg's acceleration architectures and AIGLX. I was an nvidia user some
months ago and if you think that nvidia driver is bug less or works
properly better think again...

I got rid of nvidia cause they showed me that they don't really care
to improve problems and bugs all they do is maintain a driver which
someday will be much worser than fglrx(that day is not far for me)
cause it doesn't use Xorg's features and architectures!

FGLRX works better for me than nvidia driver used to work with my old
GeForce FX 5200.
1) I can finally suspend my PC under Linux!! Never worked with nvidia
no matter what I tried...
2) I can use Compiz-Fusion WITHOUT Black Windows Bug and dozens of
options at xorg.conf to tweak the damn driver...
3) I can use 2.6.24 kernel
4) The only thing that's missing is Accelerated Video but if it is
here for 32-bit systems it will be soon reality for 64-bit too.

Also AMD sais that there is still a lot of work to be done and the
fact that they give out specs open is very important!
That's why I chose to use ATI at my new PC. Nvidia thinks it rules the
universe in Linux with this damn driver being exactly static in
development for more than a year!

If I don't post again till midnight...
Happy New Year to Everyone guys!!
I wish health first of all and all of your wishes to come true
including Accelerated Video Playback! ;)

Jim

[macauhtpc]

Happy New Years, guys!

djdoo, I am sorry that I'm confused your name with JoJo.

I forgot to paste my xvinfo. In case you need it, it is here...

bruce@bruce-desktop:~$ xvinfo
X-Video Extension version 2.2
screen #0
Adaptor #0: "ATI Radeon AVIVO Video"
number of ports: 4
port base: 131
operations supported: PutImage
supported visuals:
depth 24, visualID 0x23
depth 24, visualID 0x24
depth 24, visualID 0x25
depth 24, visualID 0x26
depth 24, visualID 0x27
depth 24, visualID 0x28
depth 24, visualID 0x29
depth 24, visualID 0x2a
depth 24, visualID 0x2b
depth 24, visualID 0x2c
depth 24, visualID 0x2d
depth 24, visualID 0x2e
depth 24, visualID 0x2f
depth 24, visualID 0x30
depth 24, visualID 0x31
depth 24, visualID 0x32
depth 24, visualID 0x33
depth 24, visualID 0x34
depth 24, visualID 0x35
depth 24, visualID 0x36
depth 24, visualID 0x37
depth 24, visualID 0x38
depth 24, visualID 0x39
depth 24, visualID 0x3a
depth 24, visualID 0x3b
depth 24, visualID 0x3c
depth 24, visualID 0x3d
depth 24, visualID 0x3e
depth 24, visualID 0x3f
depth 24, visualID 0x40
depth 24, visualID 0x41
depth 24, visualID 0x42
depth 24, visualID 0x43
depth 24, visualID 0x44
depth 24, visualID 0x45
depth 24, visualID 0x46
depth 24, visualID 0x47
depth 24, visualID 0x48
depth 24, visualID 0x49
depth 24, visualID 0x4a
depth 24, visualID 0x4b
depth 24, visualID 0x4c
depth 24, visualID 0x4d
depth 24, visualID 0x4e
depth 24, visualID 0x4f
depth 24, visualID 0x50
depth 24, visualID 0x51
depth 24, visualID 0x52
depth 24, visualID 0x53
depth 24, visualID 0x54
depth 24, visualID 0x55
depth 24, visualID 0x56
depth 24, visualID 0x57
depth 24, visualID 0x58
depth 24, visualID 0x59
depth 24, visualID 0x5a
depth 24, visualID 0x5b
depth 24, visualID 0x5c
depth 24, visualID 0x5d
depth 24, visualID 0x5e
depth 24, visualID 0x5f
depth 24, visualID 0x60
depth 24, visualID 0x61
depth 24, visualID 0x62
depth 24, visualID 0x63
depth 24, visualID 0x64
depth 24, visualID 0x65
depth 24, visualID 0x66
depth 24, visualID 0x67
depth 24, visualID 0x68
depth 24, visualID 0x69
depth 24, visualID 0x6a
depth 24, visualID 0x6b
depth 24, visualID 0x6c
depth 24, visualID 0x6d
depth 24, visualID 0x6e
depth 24, visualID 0x6f
depth 24, visualID 0x70
depth 24, visualID 0x71
depth 24, visualID 0x72
number of attributes: 10
"XV_SET_DEFAULTS" (range 0 to 1)
client settable attribute
"XV_DOUBLE_BUFFER" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
"XV_BRIGHTNESS" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_CONTRAST" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_SATURATION" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_COLOR" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_HUE" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_RED_INTENSITY" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_GREEN_INTENSITY" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
"XV_BLUE_INTENSITY" (range -1000 to 1000)
client settable attribute
client gettable attribute (current value is 0)
maximum XvImage size: 4096 x 4096
Number of image formats: 2
id: 0x32315659 (YV12)
guid: 59563132-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)
id: 0x30323449 (I420)
guid: 49343230-0000-0010-8000-00aa00389b71
bits per pixel: 12
number of planes: 3
type: YUV (planar)

After using the AMD 7.12 linux driver for a while, I decide to switch
back to RadeonHD 1.1.0. Even I got Xvideo working with fglrx driver,
the picture quality is very bad under XVideo. There is always an
annoying digonal line and the color is washout. Also after I have the
system on for a while, the screen starts to flickering.. Even the
fickering is not very serious, It is also very annoying.

Regarding to the HDMI interface, yes, I am connecting my barebone to a
Sharp 46" LCD TV via the HDMI. Both fglrx and radeonhd drivers are
working fine with my TV via HDMI. However, in 1080p mode, the picture
quality with the radeonhd driver is better than one with fglrx driver.
The radeonhd driver even gives me bigger screen than fglrx driver. I
can post some pictures later if you guys are interested in the
difference.

BTW, is anyone able to get the audio out via HDMI?

Anyway, hope we will heard more good news from AMD/ATI soon.

-B

[Oleksiy Kokachev]

About HDMI audio: I use SPDIF out from HDMI. Its works fine. Do You
need help to configure SPDIF audio? if so, there is good page, which
describes how to configure it: http://alsa.opensrc.org/DigitalOut

[djdoo]

Wow! "ATI Radeon AVIVO Video"?!!

Take a look at my xvinfo:

djdoo@dhcppc0:~> xvinfo

X-Video Extension version 2.2
screen #0

no adaptors present

Hehe... maybe soon we will have XV too on 64-bit!

But with RadeonHD you don't have 3D acceleration man... why choose it?
just for video quality? Don't you use Compiz-Fusion?

That damn diagonial line is present here too... In video playback is
obvious for me also and under 3D usage not only video... It is there
also in Compiz's animations.

Oh well, I have a good feelling guys for the new year's presents! I
think at last ATI took the correct path...

We will see...

[macauhtpc]

Oleksiy, thanks for the info. I had SPDIF working and AC3 pass-through
to my surround stereo system. However, I just could not get the audio
out to my TV via HDMI. "aplay -l "showed there was a HDMI digital
device (Card 1 and device 1), but neither aplay or mplay could get the
sound out to it. Anyway, I am happy with SPDIF digital audio from my
surround stereo system, and the HDMI audio will be a plus to my
current setup.
-B

On Jan 1, 6:47 pm, "Oleksiy Kokachev" <kokac...@gmail.com> wrote:
> About HDMI audio: I use SPDIF out from HDMI. Its works fine. Do You
> need help to configure SPDIF audio? if so, there is good page, which
> describes how to configure it:http://alsa.opensrc.org/DigitalOut
>

[macauhtpc]

djdoo,

The ASUS barebone is meant to be a HTPC system. So, the only purpose
is for movies playing (maybe recording TV later.) I can sacrifice the
3D eye candies for the video quality for right now. But I am happy to
show off my friends the 3D eye candy if it doesn't affect the video
quality. :)

-B

[Oleksiy Kokachev]

Bruce, it sounds strange. In my case "aplay -l" shows the following:
card 1: HDMI [HDA ATI HDMI], device 0: ATI HDMI [ATI HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0

And to play sound over this device I use the following option of
mplayer "ao=alsa:device=iec958". And it work. Could You post full
output of "aplay -l"
command?
P.S. Happy new year!! :-)

[macauhtpc]

Oleksly,
Here is the output of 'aplay -l':

**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: ALC883 Analog [ALC883 Analog]

Subdevices: 1/1
Subdevice #0: subdevice #0

card 0: SB [HDA ATI SB], device 1: ALC883 Digital [ALC883 Digital]

Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 0: ATI HDMI [ATI HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0

-B

On Jan 2, 12:25 pm, "Oleksiy Kokachev" <kokac...@gmail.com> wrote:
> Bruce, it sounds strange. In my case "aplay -l" shows the following:
> card 1: HDMI [HDA ATI HDMI], device 0: ATI HDMI [ATI HDMI]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> And to play sound over this device I use the following option of
> mplayer "ao=alsa:device=iec958". And it work. Could You post full
> output of "aplay -l"
> command?
> P.S. Happy new year!! :-)

> ...
>
> read more »

[Oleksiy Kokachev]

Bruce. Your output is same as mine.
So to enable audio over HDMI:
1. Make sure, that it is not muted. To check it use "alsamixer -c 1".
Read man for alsamixer.
2. To test it use command: "mplayer -ao alsa:device=hw=1,0" or
"mplayer -ao alsa:device=plughw=1,0"
good luck!

[macauhtpc]

Okeksly,
Thanks!
-B

On Jan 3, 12:42 pm, "Oleksiy Kokachev" <kokac...@gmail.com> wrote:
> Bruce. Your output is same as mine.
> So to enable audio over HDMI:
> 1. Make sure, that it is not muted. To check it use "alsamixer -c 1".
> Read man for alsamixer.
> 2. To test it use command: "mplayer -ao alsa:device=hw=1,0" or
> "mplayer -ao alsa:device=plughw=1,0"
> good luck!
>

[djdoo]

Still no XV or Textured stuff for me...

Damn!...