Closed eikowagenknecht closed 1 year ago
Switching around the input seems to add the line "SoundCardIndex = 0" to the TOML and then it works?
Crashing TOML:
[Configuration]
ServerPort = 5901
AutoResume = false
SoundCard = "Logitech Headset (Logitech PRO X Wireless Gaming Headset)"
LogLevel = "DEBUG"
SSDPIntervalMins = 10.0
AutoReconnect = true
DisableChunked = true
UseWaveFormat = false
BitsPerSample = 16
StreamingFormat = "Lpcm"
MonitorRms = false
CaptureTimeout = 2000
InjectSilence = true
LastRenderer = "Sonos Play:5 Büro - Sonos Play:5 Media Renderer"
LastNetwork = "192.168.40.110"
ConfigDir = 'C:\Users\mail\.swyh-rs'
ConfigId = "_cli"
Thanks, I'll try-out to reproduce and fix it.
I can not reproduce this using the GUI and starting without an existing config file. Can you describe how you can cause the crash when you start without an existing config file?
When you use the cli you are supposed to supply the options as commandline arguments, you're not supposed to edit the config toml.
One of the necessary options is the sound source index to select the correct sound card.
To get the necessary info you can run swyh-rs-cli -n -l info
once.
When I run /swyh-rs-cli -l info -o 192.168.0.254 -S true -s 0 -f wav
without an existing config file I don't get a crash.
I didn't try to edit the config file manually though.
But the sound source index should probably default to zero if you don't specify it, so I will change that.
Interesting. I get that I should have passed parameters into the CLI instead of modifying the config file. But I only tried the CLI because the GUI kept crashing and I hoped to get more info fron the CLI about why the crash happened. And yes, I did not see the GUI log file in the same dir as the config.toml, otherwise I would have posted that and skipped a lot of the confusion I apparently caused, sorry
But in the GUI no parameters should be needed, right?
Since changing the sound source from A to B and then back again fixed the issue (and added the missing entry in the config) my guess would be that the mechanism that prepopulates the available audio devices on first start does not set the parameter to 0 but that manually switching the device later does so.
My problem is that I can not reproduce it in the gui. The gui does not need parameters, but I can not get it to crash by enabling silence injection. It may be related to your hardware configuration (or not). The log files are in the same folder as the config file. If you could produce a crash with log level set to debug, and attach the complete resulting log file here, it may help me to pinpoint the bug...
Sure, I‘ll do it next week (on vacation for the weekend).
You are experiencing the problem because you have two audio devices with an identical name:
09:38:02 [INFO] Found Audio Source: index = 0, name = Logitech Headset (Logitech PRO X Wireless Gaming Headset)
09:38:02 [INFO] Selected audio source: Logitech Headset (Logitech PRO X Wireless Gaming Headset)
...
09:38:02 [INFO] Found Audio Source: index = 2, name = Logitech Headset (Logitech PRO X Wireless Gaming Headset)
09:38:02 [INFO] Selected audio source: Logitech Headset (Logitech PRO X Wireless Gaming Headset)
Without a sound source index in the config the last one "wins" (and it does not support injecting silence, hence the panic).
The problem was introduced with PR#95 that adds listing input devices in addition to output devices. Previously these were not listed as possible sound sources, and they do not support injecting silence.
Now that the sound source index defaults to 0 it should no longer happen.
Should be fixed in the new 1.8.4 release.
Can't really test it myself: I have no duplicate device names in my setup.
Thank you, it works just fine now with the new version!
Just noticed one minor thing:
Just noticed one minor thing:
- The website says "The current release is 1.8.5", the application reports as 1.8.4 and the readme.md that is opened after the install says "The current release is 1.8.3".
Yes, I was a bit hasty to get the corrected release online. Sorry about that... Perhaps I should release 1.8.6 where everything is synced correctly.
In fact only the setup and the readme were affected. I've corrected the readme and replaced the setup for 1.8.4. I hope I got it right this time.
As the title says, after activating the file on the following application restart, the app window opens for a second and then closes again, process terminated.
I needed to set
InjectSilence = false
in the .toml config file to get the app to start again.Not sure where to find the logs for the UI, but when I set the parameter in the CLI, the following is logged:
With RUST_BACKTRACE="full" and LOG_LEVEL="DEBUG":