Are BlackHole Output devices also readable/usable from with /dev
too ?
#771
Answered
by
gchilds
davidandreoletti
asked this question in
Q&A
Replies: 1 comment 2 replies
-
The libASPL sample device writes to a UDP socket:
https://github.com/gavv/libASPL/blob/main/examples/NetcatDevice/Driver.cpp
…On Thu, 7 Mar 2024 at 5:05 pm David Andreoletti ***@***.***> wrote:
Hi,
Here is my use case / setup.
Local music client:
- Some music player
- No support for streaming the music over TCP/UDP/etc
Remote Audio Server:
- Accept any kind of audio stream over TCP/UDP
I would like to bridge the two endpoints as follow:
Local music client -> Aggregated Blackhole device -> cat /dev/aggregated_black_hole | nc remote-audio-server 3333 -> Speaker
Is there a block/char device readable within the /dev file hierarchy for
each BlackHole Output devices ?
—
Reply to this email directly, view it on GitHub
<#771>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQLZLIRMNP6SIBQWCZMOSDYXCF43AVCNFSM6AAAAABELI3KGOVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGMZTONJXGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
davidandreoletti
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Here is my use case / setup.
Local music client:
Remote Audio Server:
I would like to bridge the two endpoints as follow:
Is there a block/char device readable within the /dev file hierarchy for each BlackHole Output devices ?
Beta Was this translation helpful? Give feedback.
All reactions