Timeline for Record USB System Audio and Send to Named Pipe
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2023 at 12:05 | comment | added | stiw47 |
ffmpeg -f alsa -i hw:0,12 -f u16le -acodec copy udp://192.168.0.21:8899 You can determine your device with aplay -l and/or arecord -l. In above example, -i hw:0,12, 0 is sound card, and 12 is device number (subdevice). TL;DR I wanted to send audio via network from my rooted LG TV to my Archlinux home server to LedFx webOS is slightly different Linux (but still Linux). So I uploaded FFMpeg binary for arm64 to TV, and this is working. It is working very well and accurate, but I have latency of about 3 seconds, so most probably will search for another approach (server AUX maybe).
|
|
| Jun 4, 2023 at 11:48 | comment | added | stiw47 | Hehe, I'm using exactly the same docker container :) In mean time, I found different way as well. If you have no Pulse installed, or if you cannot compile FFMpeg with pulse enabled (as far as I can see, precompiled FFMpeg binaries for arm64 weren't compiled with pulse), you can use alsa as source format, e.g. in my case: ffmpeg -f alsa -i hw:0,12 -f u16le -acodec copy udp://192.168.0.21:8899 | |
| Jun 4, 2023 at 3:51 | vote | accept | Byte11 | ||
| Jun 4, 2023 at 3:50 | comment | added | Byte11 | I don't remember the details of this question anymore, but I think I went with a different approach. I did succeed though, the code is here: github.com/ShiromMakkad/LedFxDocker | |
| May 31, 2023 at 20:27 | review | Late answers | |||
| Jun 2, 2023 at 0:05 | |||||
| S May 31, 2023 at 20:03 | review | First answers | |||
| Jun 14, 2023 at 20:03 | |||||
| S May 31, 2023 at 20:03 | history | answered | stiw47 | CC BY-SA 4.0 |