[Bug 1908832] Re: jack audio dev produces no sound

2021-05-13 Thread Thomas Huth
Ticket has been moved here (thanks, José!): https://gitlab.com/qemu-project/qemu/-/issues/278 ... thus closing this on Launchpad now. ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #278 https://gitlab.com/qemu-project/qemu/-/issues/278 ** Changed in: qemu Status: Incomplete =

[Bug 1908832] Re: jack audio dev produces no sound

2021-05-12 Thread Christian Schoenebeck
Just for the records: the proposed patch was discussed on the QEMU mailing list, but there was no final consensus (yet) to accept the patch. Full discussion: https://www.mail-archive.com/qemu-devel@nongnu.org/msg78.html It's probably Ok to let this report expire for now. If there are more use

[Bug 1908832] Re: jack audio dev produces no sound

2021-05-12 Thread Thomas Huth
The QEMU project is currently moving its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting the bug state to "Incomplete" now. If the bug has already been fixed in the latest upstream version of QEMU, then plea

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
Yes, I agree, the patch itself is a quick fix, indeed, if I look to the graphs in QJackCtl, I would expect to see new bubbles from qemu connected to the system ports, as it happens when I connect Firefox or Falkon through alsa -> jack plugin, as per the output you can see it's using some sort of nu

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread Christian Schoenebeck
c->opt->connect_ports is an optional user supplied configuration argument which allows the user to specify a regular expression pattern which is used by QEMU's JACK audio driver to automatically connect its JACK ports to. From qapi/audio.json: ## # @AudiodevJackPerDirectionOptions: # # Options of

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
just for completeness, this is how the output of the vm launch looks like after the change: jack: connect out-(null):output 0 -> system:playback_1 jack: connect out-(null):output 1 -> system:playback_2 jack: JACK output configured for 48000Hz (1024 samples) jack: connect system:capture_1 -> in-(nu

Re: [Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread no-reply
Subject: [Bug 1908832] Re: jack audio dev produces no sound === TEST SCRIPT BEGIN === #!/bin/bash git rev-parse base > /dev/null || exit 0 git config --local diff.renamelimit 0 git config --local diff.renames True git config --local diff.algorithm histogram ./scripts/checkpatch.pl --mailback b

[Bug 1908832] Re: jack audio dev produces no sound

2021-02-24 Thread José Pekkarinen
Hi, I spend some time debugging this during the morning, I found that there is a check while connecting the ports that always exits the function without connecting the jack ports, simplifying it as in the following diff lets me build and use the audio outputs correctly in the vm: diff --git a/au

[Bug 1908832] Re: jack audio dev produces no sound

2020-12-20 Thread José Pekkarinen
I unmasked qemu-5.2.0-r1, well, actually any newer qemu coming from gentoo, and rebuild the software. The situation is still reproducible, which confirms what I tested yesterday with the patch. I also cleaned up the launch script to remove several spice related unneeded since I use the gtk display,

[Bug 1908832] Re: jack audio dev produces no sound

2020-12-20 Thread José Pekkarinen
I'm afraid it didn't. Jack version is: * media-sound/jack2 Latest version available: 1.9.16 Latest version installed: 1.9.16 Size of files: 952 KiB Homepage: https://jackaudio.org/ Description: Jackdmp jack implemention for multi-processor machine Licens

[Bug 1908832] Re: jack audio dev produces no sound

2020-12-20 Thread Christian Schoenebeck
Does this patch make a difference for you? https://github.com/qemu/qemu/commit/a6e037390dd91276f4a631d41188c87e8a60bb3f If not, what's the precise JACK version you are using. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bu