https://bugs.kde.org/show_bug.cgi?id=510820
--- Comment #6 from Marvin1099 <[email protected]> --- (In reply to Marvin1099 from comment #4) > (In reply to Junxuan Liao from comment #3) > > (In reply to Jean-Baptiste Mardelle from comment #1) > > > Indeed, MLT does currently not really allow > > > selecting a device. > > > > So Capture -> Audio -> Device just affects the monitoring but not recording, > > right? > > Sadly none of my virtual recording devices are detected, unless they are > these invisible ones. > Check out this screenshot: https://postimg.cc/NyLSSgzk After some testing: The invisible ones seem to include my my mic. But is invisible so, well i can see it so can really verify what i clicked on. Something else: I mostly made this report since when selecting pipewire as backend it ignores my default device (virtual device). > As example my default virtual device is this file "10-game.conf" and has > contents: > context.objects = [ > { factory = adapter > args = { > factory.name = support.null-audio-sink > node.name = "game" > media.class = Audio/Sink > audio.position = [ FL FR ] > audio.channels = 2 > monitor.channel-volumes = true > adapter.auto-port-config = { > mode = dsp > monitor = true > position = preserve > } > } > } > ] This is my default device btw. Kdenlive Just keeps on using my Monitor HDMI audio output, annoying. I had not mentioned this, yet i think. If the pipewire backend would use my default device i would actually be good. Then the title actually is more correct, since the Pipewire Audio Driver ignores the default device if its a virtual one. Anyway if anything should be in focus, i would say Pipewire should use virtual devices if they are the default device. Device selection can come later. -- You are receiving this mail because: You are watching all bug changes.
