#1 Question - Why Use This? Also, Timing…

[Anonymous]

Originally created by: AaronHorn

Hi,

I saw this project by chance when I saw your post on the usbip-win2 forum.

I had a few questions. Mainly I’m just curious, no criticism or expectation from my part!

1) Why? Obviously tools such as VB-Audio are well established and work well for many applications including broadcast where a card with mixer DSP such as an AudioScience isn’t available. I see that you explain your approach, using native USB audio drivers over a proprietary drive etc but you then need the usbip-win2 driver. Why is your approach better than the traditional solutions? Or are you not saying it’s better, just that it’s different? One assumes something seeing the name of the interface just sees something generic which might help if something fingerprints VB-Cable usage…

2) How is timing handled? For example, if you have lots of cables, are they are running from the same clock to avoid desync? How does it handle working with real sound cards?

3) Are you anticipating being able to exceed the current 16 bit limit? Obviously dithering could be an issue for high quality source material?

4) I assume other formats eg ASIO could be considerably more complex

5) One interesting use case might be network scenarios where the ‘ends’ of the cables are on different hosts. I guess this is something usbip-win2 could assist with, but you’d presumably have lots of challenges with timing and control needing separate channels to the USB over IP one.

Cool work! Will follow for sure!

[Tarek Wasfy]

Hi,
I am happy to answer your questions.
1) It actually is just different and at the moment the other options are better, but I am planing on updating the propriatery version in the Microsoft Store to match the bitrate and frequence of the other softwares. It could become the better option. Right now it is cheaper than VAC and VB-Audio, wich might be a selling point.

2) Timing is a thing I am working on. The cables do share the same host timebase, but currently have independent stream timelines.

3) Yes I will update it to be 32 bit and it is possible but unstable at the moment. My Hi-Fi Cables are 32 bit https://apps.microsoft.com/detail/9p4q4f08zntj?hl=en-US&gl=US

4) Actually my experience is that ASIO and DirectSound are very simple to route, but creating a WASAPI device or endpoint is the hard part.

5) Thats true and I have the Virtual Network Audio Cables for that, they route it over the network with many audio protocoles implemented and 32 bit aswell. https://apps.microsoft.com/detail/9n7zcc3814bp?hl=en-US&gl=US

[Tarek Wasfy]

Hi,
I have updated Virtual Cables in the propriatery Microsoft Store version. https://apps.microsoft.com/detail/9nm06h53pj7g?hl=en-US&gl=US

New functions:

• Now with up to 32 bit and 192 kHz.
• All cables are now running from the same clock

I hope this helps.