search

takaswie / linux-firewire-dkms

Currently this repository is maintained for Linux firewire subsystem and unit drivers.
http://ieee1394.docs.kernel.org/
39 stars 8 forks source link

Integration with PulseAudio #9

Closed muranyia closed 9 years ago

muranyia commented 9 years ago

I am opening this thread not to mess up another one with my questions.

So far I have learned that Unity will not boot up unless I disable Pulseaudio as described here: https://wiki.ubuntu.com/PulseAudio/Log

I have noticed now, that starting Pulseaudio afterwards actually works and the firewire card is listed, although by a weird name: screenshot from 2014-10-14 16 18 20

Another thing to note is that the card is detected as 10-channel surround despite the settings I have applied, suggested here.

takaswie commented 9 years ago

So far I have learned that Unity will not boot up unless I disable Pulseaudio as described here:

I cannot reproduce this in my Ubuntu.

$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

So this is an invalid ticket in this meaning.

I have noticed now, that starting Pulseaudio afterwards actually works and the firewire card is listed, although by a weird name:

This is a bug in PulseAudio side. This should be fixed but there're few developers interested in this issue, however I currently have no time for this issue...

Another thing to note is that the card is detected as 10-channel surround despite the settings I have applied.

This is an expected behaviour. Currently PulseAudio cannot apply any of profiles except for a profile that FireWire sound device supports. In your case, 10 ch for playback and 10 ch for capture. https://github.com/takaswie/snd-firewire-improve/issues/7#issue-44999900

muranyia commented 9 years ago

So far I have learned that Unity will not boot up unless I disable Pulseaudio as described here:

I cannot reproduce this in my Ubuntu.

$ cat /etc/lsb-release DISTRIB_RELEASE=14.04 So this is an invalid ticket in this meaning.

I am on the same release, so I am accepting that you cannot reproduce, thus no bug. I guess my problem is because the card is not properly working yet. If the problem does not go away when the card is OK, I may come back to you for advice.

I have noticed now, that starting Pulseaudio afterwards actually works and the firewire card is listed, although by a weird name:

This is a bug in PulseAudio side. This should be fixed but there're few developers interested in this issue, however I currently have no time for this issue...

Filed https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475

Another thing to note is that the card is detected as 10-channel surround despite the settings I have applied.

This is an expected behaviour. Currently PulseAudio cannot apply any of profiles except for a profile that FireWire sound device supports. In your case, 10 ch for playback and 10 ch for capture.

Unless you say this is really the expected and best behaviour, I would like to file a bug to PulseAudio for this too. I understand that my problem is part of the bigger picture which is that PA fails to find a working profile which describes multichannel devices, isn't it?

takaswie commented 9 years ago

For this issue, developers' work is required in both of ALSA and PulseAudio. But you're not. So please keep it pending because I have a plan to work for this in next year.

Please keep in mind that there're a few developers for a combination between Linux and FireWire sound devices. I'm welcome developers' works, but want to avoid user's excess requests.

muranyia commented 9 years ago

Sir, yes Sir.