Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

I guess that makes sense. But it just seems like the driver should be able to take the audio from VLC or similar and pump it out to Ventrilo without having to worry about whether or not it's going to be "heard" by an audio device on the machine itself. After all, I can stream movies from that VM through VLC over the Internet without issue.
– omghai2u
Commented Jun 7, 2010 at 4:09
@omghai2u - those are two different tasks. To "pump" the audio to a remote server you would have to process it on the local machine, which is impossible in ESXi. Hosting video to stream via VLC is totally different. In that case, the server hosts the files and provides a way for the client to connect and stream the files. The audio and video processing are done on the client.
– MDMarra
Commented Jun 7, 2010 at 13:34
@MarkM: I see what you're saying; I just don't see why it's impossible to do on the VM or how it's very different from my movie scenario. It doesn't need to output the sound to an actual device (which, I can clearly see would be impossible), it just needs to take an audio stream (from a file) and send it to the listening client (ventrilo) running on the same machine. Having only written a few drivers for Windows myself, this seems doable. I just don't get why it would require something special to move one audio buffer to an awaiting client that's expecting an audio buffer.
– omghai2u
Commented Jun 8, 2010 at 5:59
@omhhai2u - It's because there is no audio device to write the driver for.
– MDMarra
Commented Jun 8, 2010 at 10:45
Just wanted to update that, after much hard word, I did write the driver I outlined here and it works wonderfully. Too bad it was apparently impossible.
– omghai2u
Commented Jan 3, 2011 at 10:34

| Show 1 more comment

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »