windows 10 setting up SoX for live-streaming Mikrophone-->---LAN--------Soundcard realtime audio-transmission

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Am 25.04.2021 um 18:43 schrieb Jan Stary:
On Apr 25 18:00:30, sox-users@xxxxxxxxxxxxxxxxxxxxx wrote:
I'm not familiar with linux.
It's not specific to linux, an UNIX-like system
will have something like that.

So I have to look if windows has a netcat equivalent.
Yes. And perhaps a native recordin/playing application.

Ideal would be a software which works: install
Please note that on many systems there is nothing to install.
Recoding and playing sound is largely considered a part of
general-purpose computing, so the system will already have
a tool that records/plays.

-  start -  adjust IP_adress / port
Just to rule out a misunderstanding: you don't "adjust"
your IP address; you machine has one.
I meant tell the sending PC the IP-adress of the receiving PC
Coming from windows, you might find it interesting that the two
separate pieces of that task (namely, recording/playing sound and
sending data accross a network) are performed by two separate
tools that have nothing to do with each other, and have no
knowledege they are working in such accord. In rec | nc,
rec has no idea where the recorded data goes, and nc has
no idea where the data came from (and that it is audio data);
each is just doing it's separate job.

Maybe I will just use a good old analog microphone / amplifier
and a looong speaker-cable
Why is it actualy that you need to record on one computer
and play it out on another?

	Jan
Ah ! I forgot to write about the real situation:  live-streaming across the local network.

I'm working as a teacher and have to teach a class that is separated into two halfs
each half in its own room to limit the number of persons per room.

I'm forced to use Big Blue Button as the video-conference solution.
Though the bandwidth of the internetconnection and/or the server-"bandwidth" to process the video-sreaming-data
for a lot of conferences at the same time.   Is limited which causes lagging of the audio.

Under this circumstances (small bandwidth/overloaded server)   Big Blue Button is more like a   Little-Black-Hole
that disrupts the data into nowhere-nexus  ;-)

So I'm searching for an alternative for "live-streaming the audio.
If the rooms are next to each other an oldfashioned analog microphone connected to an oldfashioned analog amplifyer
with a 50m long speaker-cable has 0 Milliseconds latency and is "rock-stable" as a neutron-star

best regards Stefan


      
Am 25.04.2021 um 16:51 schrieb Jan Stary:
On Apr 25 15:54:13, dipl-ing.ludwig@xxxxxxxxxxx wrote:
Am 24.04.2021 um 20:31 schrieb Jan Stary:
On Apr 22 21:13:48, sox-users@xxxxxxxxxxxxxxxxxxxxx wrote:
I would like to use SoX for this scenario
me speaking ----->  inbuild micrphone of my tablet (Windows 10)
---------->----------LAN------->---------second
PC----->------soundcard---->----Amplifier------>Speaker ----> my words as
*realtime* audio
I don't think this is a sox problem: any other audio application
will have to fit into that scenario similarly.

If I understand right I have to setup IP-adresses and ports.
Well, obviously, if you want to send data over LAN.
This has nothing to do with SoX.

Is there somewhere a collection of batch-files or a parameterlists
that show which parameters and options I have to use for this?
No.

I you just want to send the audio unchanged to another machine,
SoX might not even be the tool for you: you just need one machine
to record, and send the data to the other machine (as you would
send any other data), and have the other machine play it back.

It this wasn't windows, I would put a one-liner here
that does exactly that.

Jan
I have found this website
https://www.streamingmediaglobal.com/Articles/Editorial/Featured-Articles/DIY-Rudimentary-Audio-Streaming-124222.aspx?utm_source=dlvr.it&utm_medium=feed&utm_campaign=iti%20roundup

Which shows how to do it with SoX. But it seems a description for how to do
it on Linux-machines
Surprise: rec | nc

rec reads from a device and writes to stdout;
netcat reads from stdin and writes to a socket;
the opposite happens on the other end: nc | play.

On systems that have standard tools for fundamental things
(such as: read your input and send it down a network socket)
this is indeed a one-liner. But you are on windows;
maybe windows also has a netcat, I don't know.

Also note that this is not specific to SoX:
it could be arec/aplay with ALSA, or aucat/aucat on OpenBSD,
or any other program capable of recording/playback.

	Jan



_______________________________________________
Sox-users mailing list
Sox-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users


_______________________________________________
Sox-users mailing list
Sox-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users

_______________________________________________
Sox-users mailing list
Sox-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/sox-users

[Index of Archives]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux