![]() In /etc/lightdm/nf you can define a script at #greeter-setup-script=. But be aware that a broken script can leed to the effect that your loginmanager won't be loaded correctly (blackscrren). If you setup everything right, then your loginmanager should always be displayed on the monitor which is active at boot and you can switch your monitors&sink with a simple keybind.įirst, you can add a script to lightdm to config your monitors so that everything is displayed correctely. I have similar setup and I got everything working what you might want if I understood you corretely. Threads on the internet concerning this are incredibly sparse and I'm hoping someone has specific experience with this issue or this API and can point out what I need to do differently. ![]() But sometimes it is recreated with 48 kHz still and it continues to sound robotic. when the AudioContext is correctly recreated it switches from 48 kHz to 16 kHz and then it sounds find. I suspect this has something to do with sample rates. If I wait for some time and then recreate it again, it works so I'm worried about some type of garbage collection issue with the processor when attempting this, but that might be beside the point. I've tried some options such as detecting when this happens using 'ondevicechange' event, closing the old AudioContext & nodes and recreating everything, but this only works some of the time. I've created a small React app here that reproduces the problem: Also if you simply create the AudioWorkletNode, but don't even connect it to the others, this also reproduces the issue.
0 Comments
Leave a Reply. |