search

projectM-visualizer / frontend-sdl-cpp

Standalone application based on libSDL that turns your desktop audio into awesome visuals. Available on most platforms supported by both libprojectM and libSDL.
GNU General Public License v3.0
68 stars 35 forks source link

[Feature Request] Change mic inputs / local sound card #60

Closed hammy414 closed 1 year ago

kblaschke commented 1 year ago

Could you please elaborate a bit more on what new feature you're requesting here?

Switching audio devices is already implemented, simply press Ctrl-i to cycle through them.

You can also use the --listAudioDevices (Linux/macOS) / /listAudioDevices (Windows) command-line switch to get a list of available devices and then add your favorite device name to the projectMSDL.properties file, then it'll be selected automatically on startup (if available).

Note that to be able to use "monitor" devices in SDL on Linux, you'll need libSDL2 version 2.0.16 or higher.

On macOS, due to system API restrictions, only external recording devices are available without using special loopback drivers.

On Windows, it should work just fine, as projectMSDL directly uses WASAPI to capture audio.

NikkyAI commented 1 year ago

on MacOS projectMSDL --listAudioDevices does not do anything different than no argument at all (it just starts).. in fact neither does -h or --help assuming i figure out how to find the right monitor device to use.. what is the configuration keys that i should use ?

kblaschke commented 1 year ago

If this is the Homebrew or Steam version, it won't work as this is an old version (which has the same executable name) which didn't have any command-line arguments.

This only works with my development pre-release, which can be found here: https://github.com/kblaschke/frontend-sdl2/releases/tag/2.0-macos-pre1

Should have noted this earlier to avoid confusion, sorry!

kblaschke commented 1 year ago

No more information provided by original reporter. As the new frontend has the ability to change audio devices (within OS limitations of course), this shouldn't be an issue with future versions.