Asio Link Pro Patch
Jules Altier
My experience is that it works flawlessly and with near zero latency. I normally run 64 samples @ 48kHz and in round trip testing measure zero different with the ODeus wrapper running vs. not running.
How much additional latency have you incurred by inserting this into the audio chain? It looks VERY interesting, but to me, stability and latency have to be solid and low. If this really worked well, I would likely introduce it so I can run two instances of GP, one as a rackspace that holds all of my large samples in Kontakt so I can just reference from rackspaces in my main rack.
Can you confirm you can go on using the RME driver with it ? (no need to use ASIO4ALL).
How does it work, does your audio interface becomes ASIO4ALL Link and which agglomerates both the RME and virtual inputs ?
First of all thanks for the details.
I wanted to test loopBeAudio and compare it with the RME internal loopback. When starting loopBeAudio it acts like a virtual audio interface and it has to be agglomerated to the RME one which was only possible using the ASIO4ALL driver which replaces the RME driver and induces additional latency. If you want to record vst outputs in GP you need to loopback the outputs you want to record. For now I use the internal RME loopback, but perhaps there is something interesting to do with this ASIO link.
Thanks again.
If you want to record vst outputs in GP you need to loopback the outputs you want to record. For now I use the internal RME loopback, but perhaps there is something interesting to do with this ASIO link.
I had already committed to using multiple instances of GP. The only question was whether I ran them on the same PC and used a different audio interface, or ran one on a remote PC and ran the sound back and forth through ADAT. Plus it only applies to my studio rig, since my RME is the traveling interface and that handles multiclient very well.
@cclarry mentioned the product on the old forum back in 2015: -Deus-Audio-releases-ASIO-Link-Pro-v24-m3283843.aspx, however when I tried to purchase it about a year ago, I found that I couldn't because the original developer had sadly passed away... and now the original website has gone.
"This ASIO driver extends your audio interface ASIO driver and adds windows audio with no additional latency. It also allows you to use your ASIO driver from more than one application with the inbuilt multi-client support, and you can even send ASIO audio over the network.
This effectively allows you to use more than one ASIO interface at the same time in CbB (even ones on an external networked PC), allowing up to 64 input/output channels. At the moment I've no idea how this affects latency, but I guess if it's lots of inputs you need then it's likely it's a whole band you're recording and this will be less of a concern. I can also see it being really useful for making tutorial videos.
The great news is that it is indeed latency free. The CPU usage is increased only very slightly, but my projects play exactly as before and are still happily working with a buffer of 64 (1.5ms). I didn't try recording, but playing a piano VSTi through it showed absolutely no change in latency.
The bad news is that you can only select one "real" ASIO interface, so additional interfaces have to be selected as WDM and routed to the ASIOLink ASIO driver like ASIO4ALL does. I've not worked out how to select WASAPI instead yet, but it does claim to support it. It's not really a big deal though for recording whole bands, and it does mean you don't need to swap drivers/modes all the time. And unlike ASIO4ALL, you can save & recall your routing configurations.
What I've not tried yet is using other interfaces with ASIO on another PC and using the network interface. I'm only set up for WiFi in my studio at the moment, so I don't think that would be a fair test.
Not sure if this will be a solution for me, but using my Focusrite 2i4 (1st gen) is giving me constant drop outs (on playback/tracking) and everso-slight latency (which drives me nuts) using my amp sims. Will read a bit more on ODeus and see if this will solve my issue. Appreciate you posting this Mark.
I have recently discovered this and thanks @msmcleod for sharing the information.
It is such a shame that we lost a great developer but thankfully the y were able to come up with this wonderful solution to make ASIOLink available again.
My experience over the past few days has been amazing, ASIOLink has been running very solid and stable and I look forward to learning more about how to integrate it into my webcasts, tutorials, etc.. I am not finding any type of manual or instructions so I have just been bumping around looking for other resources to help understand the capabilities. I even ran across a video (5 hours long) that was very interesting (no I did not watch the entire 5 hours).
Thanks for any additional insight on how to use ASIOLink Pro.
Can you use these drivers so the interface is a general/global audio player, and if you open your DAW it won't hesitate to NOT keep audio to itself,
then quitting your DAW, and not hesitating to "release" the asio drivers: in other words, as long as you have your global/general audio Windows 10 settings
the same as your projects (let's say 44 khz) if you open your DAW or close it while watching youtube audio doesn't crack or anything, is just one big audio environment?
I have a TASCAM 16x08 and those guys took forever to nail the drivers but they are 99% there, but if these drivers worked 100% great, then... awesome... thanks.
@Carlos, I am just learning how to use this driver myself so I am not sure how it would work in your situation. What I am discovering is their stability and performance not only in Cakewalk but other audio recording and capturing apps as well.
I found that if you "RIGHT CLICKED" on the Title BAR that you could in fact MINIMIZE the interface to the tool tray area.
It comes in handy when you want to get the GUI out of the way for a little bit.
The software seems to be binded with some sort of malicious software, indeed. FUD Crypter's are used to fool Anti-virus scans, therefore called FULL UNDETECTED Crypter's. You can reverse engineere some of it, and you'll see the things i've posted. It shouldn't activate remote desktop and other things, just like backdoors/trojans does.
>
Installation/Persistance
Monitors specific registry key for changes
Remote Access Related
Reads terminal service related keys (often RDP related)
Unusual Characteristics
Imports suspicious APIs
Installs hooks/patches the running process
Hiding 2 Suspicious Indicators
I was not aware this was an issue and I have not experienced anything crazy but will check it out. The only thing I could think of is where you might have originally downloaded your version. @msmcleod, any thoughts on this?
The ASIOLink has to use RPC to bridge ASIO calls between processes (FWIW BitBridge & JBridge do a similar thing). It also uses network calls for the ASIO over network functionality. It may be that the developer decided to use the RDP protocol to enable RPC calls over the network, which would save him having to roll his own solution.
I can't see anything in the list of suspicious characteristics that can't be explained by the nature of what ASIOLink does, but someone would have to monitor network activity closely to be absolutely sure (i.e. check if any remote sites are being contacted or if there's any unexplained incoming traffic).
c80f0f1006