Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Virtual Audio Cable Full
11 views
Skip to first unread message
Hue Charters
Dec 20, 2023, 11:28:30 PM12/20/23
to
Virtual Audio Cable is a software product based on WDM multimedia driver that allows a user to transfer audio streams from one application to another. Any application is able to send an audio stream to the input side of a "virtual cable" while a corresponding application can receive this stream from the output side. Since all transfers are made digitally, there is no loss in sound quality. VAC is the audio equivalent of a MIDI loopback device such as MultiMid or Hubi, and can be used instead of "Stereo Mix" or "What U Hear" features of audio adapters.[1][2]
Virtual Audio Cable Full
DOWNLOAD https://7gratmul-caeno.blogspot.com/?vr=2wRElZ
If more than one application is sending audio through an output virtual cable, VAC is able to mix all of the streams together or create separate corresponding virtual input cables. Similarly, more than one application is able to receive audio from an input cable, whether it's sharing the same audio data with another target or receiving its own personal audio stream.[3] VAC is useful for recording an application's audio output in almost real time or transferring a sound stream to another application so it may process it. A person could use two or more software audio generators, synthesizers or sequencers to produce audio streams and send them to a VAC output cable and record the mixed stream from the VAC input cable using any type of recording software.
Because VAC routes audio streams in almost real time, it is able to be utilized in various manners. A person is capable of using VAC to record an output audio stream from an application that normally does not allow saving the audio to files.[4] Practically, the input port records the audio signal (for example from a music player) and sends it to the destination program (such as a sound processor or analyzer) using the output port.[5] A user could also manipulate VAC into recording conversations through Voice Over IP (VoIP)[6] or Internet telephony applications such as Skype[7][8] (for example, with SAM Broadcaster[9]), produce live audio podcasts,[10] redirect audio channels to multiple monitors,[11] or even decode weather faxes.[12]
VAC creates a set of virtual audio devices. Each device simulates an audio adapter (usually named a "card") whose output is internally connected to the input, making an audio loopback. If an application plays audio to the output of such device, the sound will not be audible because the signal is looped back to the input. But if another application records from the input, it receives the sound produced by the first app.
Such virtual devices are named Virtual Cables. The term "Virtual Cable" is used only in the description of VAC product, as a placeholder. Actual names of virtual audio devices/endpoints that you will see in applications' menus, are different (for example, "Line 1", "Line 2" etc.).
Each side of any Virtual Cable can be used by several audio apps at the same time. If two or more apps play sounds to the same playback endpoint, these sounds are mixed, and the result is transmitted to the recording side. It two or more apps record from the same endpoint, each app gets a copy of the sound.
There is no quality loss (if no format conversion and/or volume control are involved). If all these conditions are met, audio transfer is bitperfect, suitable for audiophile applications. In well-tuned systems, signal latency is very low.
VAC just performs things what it is intended for: passes audio streams between applications, converting audio formats if necessary. It never guides you to advertising pages, nor pops up busily on the screen, nor installs hidden activities in your system. VAC does only actions that you explicitly demand for.
VAC driver and the supplied applications can only collect and use information directly related to their functionality. For example, VAC driver can query processor functions to optimize performance, request process/thread information to display it in a log, Audio Repeater applications request audio device/endpoint properties, etc. Since they do not work with personal, business, geographical, economic or political data, they do not access such data sources at all.
In Windows I have the program Virtual-Audio-Cable for this and I already read that pulse-audio should serve this functionality, but when I install pulse-audio I don't get this sound-redirecting to work and I get Bugs like my music is stopping when I start Teamspeak or any application with sound output.
So I wan't to have it (if possible) without using pulseaudio (I already removed it from my system).
Jack is certainly the de facto solution for advanced audio routing on Linux. Qjackctl provides a graphical control panel, exposes connections, and allows automatic connections through a virtual patchbay. However, for non-jack-aware apps, you need to use the alsa plugin. [1]
Then send sound to loop_sink and record from loop_source.
Edit: If you want to listen and record at the same time, then you should be able to use module-virtual-sink I think and record from the monitor channel for the virtual sink.
I have Virtual Audio Cable successfully installed on my Windows Server 2008 R2 SP1 x64 virtual machine. It seem like driver works (new audio device in Device Manager group and VAC control panel works perfectly), but unfortunately if you go to Control Panel -> Hardware -> Sound there is no audio devices (neither playback or recording). And so my software doesn't see any audio devices.
Audio is special in a lot of ways, and audio drivers run in the context of a "session" in Windows, so each remote desktop user gets their own audio. Even on a physical machine, when you connect via remote desktop, you see different audio devices in device manager from the ones you see sitting a local keyboard.
The short answer to your question is that a VMware virtual audio device will only be visible in the "console" session, not in secondary remote desktop sessions. You can remote audio through your remote desktop, with our without a VMware virtual audio device.
Virtual Audio Cable works fine with 2008 R2 , but it needs to be installed on a session basis, it will not replicate over RDP, you need to connect with Team Viewer or something similar to access the audio streams.
To make virtual audio devices that work like virtual audio cables, you can use PulseAudio commands. I make a pair of them to allow two software defined radio apps (eg: WSJT-X or JS8Call) to communicate bidirectionally with each other for testing purposes without needing any hardware:
Tada, from there you will have a virtual audio device. Playing to it as input will result in its output, just as VAC does. However, in pulse audio, it will also show up named as, "Built-in Audio Analog Stereo" - this is probably a bug needing to be fixed in pulse audio. But you'll notice there are two of them, one will be your virtual/loopback device.
It can create a virtual audio connector using JACK as its backend.It allows you to save your patchbay and Studio session, which can save a lot of time. Especially if you need to launch additional shell commands.All you need to do is configure your microphone at Configure -> Driver -> Device.
Virtual Audio Cable is essentially a MIDI (musical instrument digital interface) loopback device you can use to connect different applications. Virtual Audio Cable can connect to more than 250 different applications where audio can be mixed and allocated.
The installer returns immediately and the process installs in the background. However the installation only took about 10 seconds at most. If you needed to catch a failed install I would suggest monitoring the active audio device and timing out based on that.
Virtual Audio Cable connects audio applications together in real time. It's like a sound card with hardwired input and output: when an application sends an audio stream to a virtual cable, other applications can record this stream from the other cable end. Thus, you can record and process output of almost any audio application by almost any other audio application.
I am trying to write data to a virtual audio cable using python. So far I don't really care which module I use, so I tried PyAudio and Sounddevive. I installed the Virtual Cable from VB-Audio. It does show up in my device list. The problems arise once I want to initialize an output stream with the cable. An Error is raised: OSError: [Errno -9998] Invalid number of channels
Is there any equivalent of Virtual Audio Cable driver for Windows that works on Ubuntu? I wanna stop using Windows at all but this is very important for me cause I host a TS server so I can connect all audio from my devices and listen it with 1 headset on my main machine. I even have a script that opens and connects my devices on boot (but this is off topic). I searched web for any solutions and I found these: -audio-cable-in-linux-ubuntu.htmland Virtual Audio Cable For Ubuntubut they don't work with TS or even Discord. Is there anything else I can try.P.S. Maybe I could configure JACK to do it for me but I don't really know how to handle JACK
Next, change go to VAC's control panel (make sure you start with admin rights) and click "Restart" (In the driver parameters) and then "Reset Counters". The outputs "streams" should reset to 0, not change the cables to however many you like, or change any of the others settings.
0aad45d008
Virtual Audio Cable Full
DOWNLOAD https://7gratmul-caeno.blogspot.com/?vr=2wRElZ
If more than one application is sending audio through an output virtual cable, VAC is able to mix all of the streams together or create separate corresponding virtual input cables. Similarly, more than one application is able to receive audio from an input cable, whether it's sharing the same audio data with another target or receiving its own personal audio stream.[3] VAC is useful for recording an application's audio output in almost real time or transferring a sound stream to another application so it may process it. A person could use two or more software audio generators, synthesizers or sequencers to produce audio streams and send them to a VAC output cable and record the mixed stream from the VAC input cable using any type of recording software.
Because VAC routes audio streams in almost real time, it is able to be utilized in various manners. A person is capable of using VAC to record an output audio stream from an application that normally does not allow saving the audio to files.[4] Practically, the input port records the audio signal (for example from a music player) and sends it to the destination program (such as a sound processor or analyzer) using the output port.[5] A user could also manipulate VAC into recording conversations through Voice Over IP (VoIP)[6] or Internet telephony applications such as Skype[7][8] (for example, with SAM Broadcaster[9]), produce live audio podcasts,[10] redirect audio channels to multiple monitors,[11] or even decode weather faxes.[12]
VAC creates a set of virtual audio devices. Each device simulates an audio adapter (usually named a "card") whose output is internally connected to the input, making an audio loopback. If an application plays audio to the output of such device, the sound will not be audible because the signal is looped back to the input. But if another application records from the input, it receives the sound produced by the first app.
Such virtual devices are named Virtual Cables. The term "Virtual Cable" is used only in the description of VAC product, as a placeholder. Actual names of virtual audio devices/endpoints that you will see in applications' menus, are different (for example, "Line 1", "Line 2" etc.).
Each side of any Virtual Cable can be used by several audio apps at the same time. If two or more apps play sounds to the same playback endpoint, these sounds are mixed, and the result is transmitted to the recording side. It two or more apps record from the same endpoint, each app gets a copy of the sound.
There is no quality loss (if no format conversion and/or volume control are involved). If all these conditions are met, audio transfer is bitperfect, suitable for audiophile applications. In well-tuned systems, signal latency is very low.
VAC just performs things what it is intended for: passes audio streams between applications, converting audio formats if necessary. It never guides you to advertising pages, nor pops up busily on the screen, nor installs hidden activities in your system. VAC does only actions that you explicitly demand for.
VAC driver and the supplied applications can only collect and use information directly related to their functionality. For example, VAC driver can query processor functions to optimize performance, request process/thread information to display it in a log, Audio Repeater applications request audio device/endpoint properties, etc. Since they do not work with personal, business, geographical, economic or political data, they do not access such data sources at all.
In Windows I have the program Virtual-Audio-Cable for this and I already read that pulse-audio should serve this functionality, but when I install pulse-audio I don't get this sound-redirecting to work and I get Bugs like my music is stopping when I start Teamspeak or any application with sound output.
So I wan't to have it (if possible) without using pulseaudio (I already removed it from my system).
Jack is certainly the de facto solution for advanced audio routing on Linux. Qjackctl provides a graphical control panel, exposes connections, and allows automatic connections through a virtual patchbay. However, for non-jack-aware apps, you need to use the alsa plugin. [1]
Then send sound to loop_sink and record from loop_source.
Edit: If you want to listen and record at the same time, then you should be able to use module-virtual-sink I think and record from the monitor channel for the virtual sink.
I have Virtual Audio Cable successfully installed on my Windows Server 2008 R2 SP1 x64 virtual machine. It seem like driver works (new audio device in Device Manager group and VAC control panel works perfectly), but unfortunately if you go to Control Panel -> Hardware -> Sound there is no audio devices (neither playback or recording). And so my software doesn't see any audio devices.
Audio is special in a lot of ways, and audio drivers run in the context of a "session" in Windows, so each remote desktop user gets their own audio. Even on a physical machine, when you connect via remote desktop, you see different audio devices in device manager from the ones you see sitting a local keyboard.
The short answer to your question is that a VMware virtual audio device will only be visible in the "console" session, not in secondary remote desktop sessions. You can remote audio through your remote desktop, with our without a VMware virtual audio device.
Virtual Audio Cable works fine with 2008 R2 , but it needs to be installed on a session basis, it will not replicate over RDP, you need to connect with Team Viewer or something similar to access the audio streams.
To make virtual audio devices that work like virtual audio cables, you can use PulseAudio commands. I make a pair of them to allow two software defined radio apps (eg: WSJT-X or JS8Call) to communicate bidirectionally with each other for testing purposes without needing any hardware:
Tada, from there you will have a virtual audio device. Playing to it as input will result in its output, just as VAC does. However, in pulse audio, it will also show up named as, "Built-in Audio Analog Stereo" - this is probably a bug needing to be fixed in pulse audio. But you'll notice there are two of them, one will be your virtual/loopback device.
It can create a virtual audio connector using JACK as its backend.It allows you to save your patchbay and Studio session, which can save a lot of time. Especially if you need to launch additional shell commands.All you need to do is configure your microphone at Configure -> Driver -> Device.
Virtual Audio Cable is essentially a MIDI (musical instrument digital interface) loopback device you can use to connect different applications. Virtual Audio Cable can connect to more than 250 different applications where audio can be mixed and allocated.
The installer returns immediately and the process installs in the background. However the installation only took about 10 seconds at most. If you needed to catch a failed install I would suggest monitoring the active audio device and timing out based on that.
Virtual Audio Cable connects audio applications together in real time. It's like a sound card with hardwired input and output: when an application sends an audio stream to a virtual cable, other applications can record this stream from the other cable end. Thus, you can record and process output of almost any audio application by almost any other audio application.
I am trying to write data to a virtual audio cable using python. So far I don't really care which module I use, so I tried PyAudio and Sounddevive. I installed the Virtual Cable from VB-Audio. It does show up in my device list. The problems arise once I want to initialize an output stream with the cable. An Error is raised: OSError: [Errno -9998] Invalid number of channels
Is there any equivalent of Virtual Audio Cable driver for Windows that works on Ubuntu? I wanna stop using Windows at all but this is very important for me cause I host a TS server so I can connect all audio from my devices and listen it with 1 headset on my main machine. I even have a script that opens and connects my devices on boot (but this is off topic). I searched web for any solutions and I found these: -audio-cable-in-linux-ubuntu.htmland Virtual Audio Cable For Ubuntubut they don't work with TS or even Discord. Is there anything else I can try.P.S. Maybe I could configure JACK to do it for me but I don't really know how to handle JACK
Next, change go to VAC's control panel (make sure you start with admin rights) and click "Restart" (In the driver parameters) and then "Reset Counters". The outputs "streams" should reset to 0, not change the cables to however many you like, or change any of the others settings.
0aad45d008
0 new messages