[Bug 237168] audio/mumble and audio/audacity open record sound device second time error

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Apr 9 18:38:28 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237168

            Bug ID: 237168
           Summary: audio/mumble and audio/audacity open record sound
                    device second time error
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: chris2000sp at mailbox.org
                CC: feld at FreeBSD.org, xxjack12xx at gmail.com
                CC: feld at FreeBSD.org, xxjack12xx at gmail.com

I didn't found a report so i write my first my first here.

Reference:

https://github.com/mumble-voip/mumble/issues/3278

Explanation:

If a audio Program with playing and recording at once works until the same
record device is opened a second time. The playing device works but the
recording device not.

In audio/mumble the device could be opened second time if just open Preferences
change some things and push the apply or OK button.

I know i write that bug in "Ports & Packages" but i believe it has nothing to
do with that packages and it is a Sound-server bug. I use audio/mumble heavily
and i did discovered that audio/audacity has the same bug so that's why i think
its a Sound-Server (OSS) bug.

Workaround:

I got to workaround that issue with using audio/jack & audio/qjackctl. That way
the bug is pushed away to jack so that jack got the problem and not the used
program in that case audio/mumble or others. I know that the audio program has
to support jack but it works that way for me. Jack has some nice routing
abilities.

audio/jack support in FreeBSD seems to be disabled by default in other ports so
it has to be enabled while building the port.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list