FS#15636 - [audacity] 1.3.8-1 Broken input/output sound device selection with OSSv4

Attached to Project: Arch Linux
Opened by Mauro Santos (R00KIE) - Wednesday, 22 July 2009, 12:46 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 12 December 2009, 14:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

(1) It is not possible to select the sound input / output device in the preferences.
The interface shows as OSS but both playback and recording devices selection do not show any devices, it just says "No devices found". Deleting the configuration folder does not solve this problem, the previous audacity package does work properly.

This is not a related problem but a bug anyway, so I'm reporting it too.
(2) The waveform display does not work as intended when dri is used (radeonhd 2400, up-to-date xorg-server and related packages and xf86-video-ati-git). If dri is not used then the waveform is displayed correctly. The previous audacity package does have the same problem.

(3)
The icon for the application is not displayed in the xfce menu (and probably other DE too). The previous audacity package does show the icon properly.


Additional info:

audacity 1.3.8-1
oss 4.1_1052b-1
xf86-video-ati-git 20090716-1
xorg-server 1.6.2-1
xorg-server-utils 7.4-6
ati-dri 7.5-1
Let me know if you need any more info about any other packages


Steps to reproduce:

(1) Open audacity, go to Edit -> preferences -> Devices, The interface host should be OSS and both playback and recording devices selection shows only "No devices found".

(2) Open any audio file, the waveform display is not correct. (see attached file, I will attach a file with the proper waveform display when I can shutdown X and disable dri).

(3) Open the xfce menu and point to multimedia, audacity has no icon.

(Hope this bug report is properly done ^^;)
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 12 December 2009, 14:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  menu item is fixed. Others are upstream.
Comment by Mauro Santos (R00KIE) - Wednesday, 22 July 2009, 16:38 GMT
As I can't edit the bug report here goes the printscreen of how audacity should display the waveform (same test file, same window size).
Comment by Eric Belanger (Snowman) - Friday, 24 July 2009, 02:46 GMT
1. I don't use the oss package (OSS does work with alsa-oss). I'll need to test that later.
2. the waveform displays correctly here with dri (x86_64, nvidia and i686, intel-legacy). If you use xf86-video-ati from extra, does it work?
3. Confirmed.
Comment by Mauro Santos (R00KIE) - Friday, 24 July 2009, 17:03 GMT
Regarding 1, I've found out that if I install alsa-utils and if I create /etc/asound.conf with

pcm.oss {
type oss
device /dev/dsp
}

inside then audacity is able to "detect" all the OSS4 devices plus the alsa emulated one. This must be a new upstream bug because the previous version of audacity worked just fine without alsa-utils and asound.conf.

Regarding 2, the problem still stands with xf86-video-ati from extra, started X without a xorg.conf, dri is active but says r300 instead of r600 which I get with the git driver but the problem is the same. I'm not using any other Xorg related package from git, everything is from the repos.
Comment by Mauro Santos (R00KIE) - Friday, 24 July 2009, 17:05 GMT
Small correction, it's not alsa-utils, it is alsa-plugins as explained here http://wiki.archlinux.org/index.php/OSS#ALSA_emulation to get alsa emulation.
Comment by Mauro Santos (R00KIE) - Monday, 16 November 2009, 21:16 GMT
Bug report follow up

(3) has been taken care long ago

(2) is most probably due to a driver bug http://bugs.freedesktop.org/show_bug.cgi?id=21561 I do use the open source driver, the description fits.

(1) probably caused by some bug in portaudio v19, capture with oss is also broken with portaudio v19, the patch suggested here does fix it http://forum.audacityteam.org/viewtopic.php?f=18&t=9178 but this patch still isn't in CVS upstream.

I guess this can be closed because the problems are not Arch related, they are all upstream problems. Should I press the "Request closure" button?
Comment by Eric Belanger (Snowman) - Monday, 16 November 2009, 21:40 GMT
No, keep it open. I'll apply the patch for (1) when it'lll be commited to audacity cvs.
Comment by Eric Belanger (Snowman) - Monday, 16 November 2009, 22:24 GMT
The patch was posted on the audacity-devel mailing list on last March: http://www.opensource-archive.org/showthread.php?t=113010 but there wasn't any response. You could try to revive the thread or repost the patch. If they accept it, I'll apply it for the package. Otherwise, I'll just close this.

Loading...