Rank: Advanced Member
Groups: Registered
Joined: 3/11/2014(UTC)
Posts: 42
Location: Florida, USA
Thanks: 6 times
Was thanked: 2 time(s) in 2 post(s)
|
I won't even try to address if this has ever implied as a feature :)
Lets try to focus on the fact that it is a much needed (and requested) feature, and is fairly easy to code up (there are plenty of MSDN examples).
So where is it? What is the hold up?
Understaffing in the coding dept? No big maintenance customer has demanded it yet? No internal need for it?
I can even make a case for providing it as an upsell or add-on revenue stream, as customers are purchasing 3rd party code, and would prefer to hand over the bucks to the VMix folks.
Keep the price reasonable, and we will buy!
Please?
|
|
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 1/13/2010(UTC) Posts: 5,228  Location: Gold Coast, Australia Was thanked: 4332 time(s) in 1528 post(s)
|
Hi,
vMix Audio is available and works in most applications.
Some applications will only work with a physical sound driver which is a lot more complicated to build as it is a Kernel mode
driver rather than a User mode device.
Driver development takes a lot of resources and time to build properly.
"Plenty of MSDN Examples" is a bit disingenuous, as there is only one example that is related and that is the "msvad driver sample"
and it is very basic and only has around 10% of the code needed to build a robust high quality virtual microphone driver.
I would happily outsource development to anyone who has expertise in this area.
Regards,
Martin
vMix
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
