Apache Labs Community Forum

W4WMT wrote:

m0cke wrote:Hardware is nothing special, either the on board sound card or a pair USB headphones.
Where can I find the buffer setting please as I've looked in the driver and cannot see the buffer setting.

Hi Jim,

Are you sure that your on board sound card and/or your USB headphones have an ASIO driver? If so, have you figured out what the name of their ASIO drivers are? That would be the first step.

73,
Bryan

I dont believe they do, I've been trying to find a ASIO driver, I assumed that Voicemeeter Banana would allow me to use it's ASIO in and play back to WDM / MME device.

M-Audio M-Track Solo should be here today so I'll try that

Jim

W4WMT wrote:Hi Jim,

Do you have DebugView from sysinternals.microsoft.com? If so, you can use it to see debug output from Thetis while it is starting which will show what went wrong with cmASIO.

Otherwise, there's a couple of Voicemeeter pitfalls you can check.
Voicemeeter's virtual ASIO driver buffer size should be set to default.
It's sample format type should be set to Int32LSB.
Your actual hardware device driver, you didn't say what you are using, buffer size must be set to 64 and sample rate set to 48000.
Voicemeeter sample rate should follow the hardware driver to 48000, but if it doesn't you may have to force it.

I recommend you first get cmASIO working with your actual hardware device driver (UMC ASIO Driver, Studio 192 ASIO) whatever that may be. Once you've populated the registry key value with its name, then the rest should be completely automatic. Then having assured yourself that everything is working with that configuration, you'll have a better starting place with the Voicemeeter effort. Or you may decide it works fine that way, and you don't really need Voicemeeter after all.

73,
Bryan

Hi Bryan

So I have the M-Audio M-Track Solo and have installed the software
Using hostsample I get

driverCount = 5
ASIO4ALL v2
M-Track Solo and Duo ASIO
Voicemeeter AUX Virtual ASIO
Voicemeeter Insert Virtual ASIO
Voicemeeter Virtual ASIO
Press any key to continue . . .

So I updated the registry key with
M-Track Solo and Duo ASIO

Started Thetis and still have the red CM icon with the same message

Debugview shows
00000001 0.00000000 [11076] RegGetValue(sz) status = 0
00000002 0.00001840 [11076] Initializing cmASIO with:
00000003 0.00001840 [11076] block size = 64
00000004 0.00001840 [11076] sample rate = 48000
00000005 0.00001840 [11076] driver name = M-Track Solo and Duo ASIO
00000006 0.00001840 [11076]
00000007 0.03536030 [11076] prepareASIO return = 1

Thats all

Any ideas?

Jim M0CKE

Hi,

1) did you shutdown VM? Otherwise the device maybe blocked by VM
2) did you try the ASIO4ALL v2 ?

73 Ernst, OE3IDE

m0cke wrote:So I have the M-Audio M-Track Solo and have installed the software
Using hostsample I get

driverCount = 5
ASIO4ALL v2
M-Track Solo and Duo ASIO
Voicemeeter AUX Virtual ASIO
Voicemeeter Insert Virtual ASIO
Voicemeeter Virtual ASIO
Press any key to continue . . .

Hi Jim,

Was that the only output from hostsample? No details shown for the M-Audio device?
The error code from debugview shows the driver didn't load, which usually means the device is not running, or another app has captured it.
Also, if you didn't get any output from hostsample about the M-Audio, that means it's not running, or another app has captured it.
As Ernst says above, Voicemeeter may have captured the driver, make sure Voicemeeter is not running.
Can you double check things
73,
Bryan

Should he change his regedit to the M-Track Solo and Duo ASIO not VM?

M Track is the M audio device.

K4IBC wrote:Should he change his regedit to the M-Track Solo and Duo ASIO not VM?

He did that already, as reported in the debug dump.

Jim,

If it helps, here's how I've got my setup:
Notice that I have the Registry pointing to "Voicemeeter Virtual ASIO", which is Voicemeeter's Channel 1. So any signal appearing on VM channel 1 output (my mic audio in this case) will get routed by cmASIO in Thetis to TX audio, and any RX audio will get routed by cmASIO to VM channel 1 input (which I have routed to the speakers).

Notice my Voicemeeter setup. My Motu M Series driver is used by VM channel 1 ( which is always assigned the reserved VM name "Voicemeeter Virtual ASIO" by Voicemeeter), which uses Virtual Input Strip B1 to capture RX audio coming in from Thetis (that Strip is labeled "In from VAC1") and uses Output Bus B1 to send TX audio out to Thetis (labeled "Out to VAC1") due to the cmASIO assignment in the Registry. In VM my mic audio is routed from Hardware Input Strip #1 (labeled "Condenser Mic") to Output Bus B1 where it gets sent to Thetis.

Hope that helps,
Mark

Edit: To clarify, the labels "In from VAC1" and "Out to VAC1" in VM were formerly used to feed audio back and forth from VAC1 but those I/O's are now captured by cmASIO (I just never bothered to change the label names).

Hi Bryan,

I took a shot at running cmASIO this evening and it is nothing short of spectacular! Thanks for the PDF instructions which made it a pure plug and play experience with my UMC202HD. After doing the registry edit I was up and running in about 2 minutes. Great job!

73, Rob W1AEX

W4WMT wrote:

m0cke wrote:So I have the M-Audio M-Track Solo and have installed the software
Using hostsample I get

driverCount = 5
ASIO4ALL v2
M-Track Solo and Duo ASIO
Voicemeeter AUX Virtual ASIO
Voicemeeter Insert Virtual ASIO
Voicemeeter Virtual ASIO
Press any key to continue . . .

Hi Jim,

Was that the only output from hostsample? No details shown for the M-Audio device?
The error code from debugview shows the driver didn't load, which usually means the device is not running, or another app has captured it.
Also, if you didn't get any output from hostsample about the M-Audio, that means it's not running, or another app has captured it.
As Ernst says above, Voicemeeter may have captured the driver, make sure Voicemeeter is not running.
Can you double check things
73,
Bryan

Hi Brian

I've removed Voicemeeter and ASIO4ALL, now I just have the 1 ASIO device, hostsample shows this and can sucessfully start the device as seen below

driverCount = 1
M-Track Solo and Duo ASIO
Press any key to continue . . .

ASIO driver: [0] = M-Track Solo and Duo ASIO
asioVersion: 2
driverVersion: 3501
Name: [M-Track Solo and Duo ASIO]
ErrorMessage: No ASIO Driver Error
ASIOGetChannels (inputs: 2, outputs: 2);
ASIOGetBufferSize (min: 16, max: 2048, preferred: 64, granularity: 16);
ASIOGetSampleRate (sampleRate: 44100.000000);
ASIOOutputReady(); - Supported
AsioCanReportOverload Not Supported
ASIOGetLatencies (input: 175, output: 174);
channel: 0 isInput: 1 isActive: 1 channelGroup: 0 type: 18 name: In 1
channel: 1 isInput: 1 isActive: 1 channelGroup: 0 type: 18 name: In 2
channel: 0 isInput: 0 isActive: 1 channelGroup: 0 type: 18 name: Out 1
channel: 1 isInput: 0 isActive: 1 channelGroup: 0 type: 18 name: Out 2

ASIO Driver started successfully. Closing hostsample the M-Audio device goes into Not Streaming

Regedit shows the correct device Now starting Thetis I still get the red CM and M-Audio is still in Not Streaming DeBugView shows it's initialising cmASIO I'm really at a loss as i've reset the thetis database, just in case.

Hair getting thinner

Jim M0CKE

Try changing the sample rate from 44100 to 48000

That's correct Tony, about the sampling rate.

Repeat all of yours above, but this time with the M-Audio sampling rate having been set to 48000 in advance.

Looking at your debugview output suggests that you may have had the hostsample detail screen open while Thetis was trying to start. Because it's not even making it to the part where it would try to change the M-Audio sample rate from 44.1 to 48. It's not able to load the M-Audio driver, possibly because the hostsample detail screen had the driver open at the same time.

73

W4WMT wrote:That's correct Tony, about the sampling rate.

Repeat all of yours above, but this time with the M-Audio sampling rate having been set to 48000 in advance.

Looking at your debugview output suggests that you may have had the hostsample detail screen open while Thetis was trying to start. Because it's not even making it to the part where it would try to change the M-Audio sample rate from 44.1 to 48. It's not able to load the M-Audio driver, possibly because the hostsample detail screen had the driver open at the same time.

73

Exactly the same results, rebooted PC, M-Audio M-Track set to 48000 and buffer size 64 Registery set to the device Start Thetis and get the red CM icon Messages states "Issue starting CM ASIO. Check drive rname in registry

Same messages ininb DebugView I'm going to try the M-Audio on a different PC

Jim M0CKE

I see your VAC1 is enabled.
What is it connected to?

m0cke wrote:Exactly the same results, rebooted PC, M-Audio M-Track set to 48000 and buffer size 64
I'm going to try the M-Audio on a different PC

Hi Jim,
One more thing I just remembered you should check. When you populated the registry key value with your driver name, if you left a trailing space at the end of the driver name it will cause the failure to load that you're seeing. Please check that this isn't the case. Maybe you should re-enter the name to make sure.
73,
Bryan

Running 2.10.3.5 pre-release 5 and I just noticed that the CM icon in the Thetis status bar is gone:
Anyone else seeing (rather, not seeing) this?

Mark

Hi Mark,

Look to the right. Richie moved it for pre-release-5, but it's still there!

73,
Bryan

BOOM!! I see it, thanks Bryan!

W4WMT wrote:

m0cke wrote:Exactly the same results, rebooted PC, M-Audio M-Track set to 48000 and buffer size 64
I'm going to try the M-Audio on a different PC

Hi Jim,
One more thing I just remembered you should check. When you populated the registry key value with your driver name, if you left a trailing space at the end of the driver name it will cause the failure to load that you're seeing. Please check that this isn't the case. Maybe you should re-enter the name to make sure.
73,
Bryan

Hi Bryan

Update from here

So I tried the M-Audio on a laptop, had the same results
So I then installed Voicemeeter Banana on both the PC and the Laptop, same result
So I then installed ASIO4ALL and this works, I get the green icon and I can route the audio to the M-Audio output in ASIO4ALL. The only thing I'm changing is the device name in the registry key as per the information from hostsample.

So why does ASIO4ALL work and none of the others do, and this is the same on both the laptop and desktop units I have here.

I have hand typed in all the names, I've copied and pasted, nothing works for VM Banana and M-Audio ASIO's but does for ASIO4ALL

It must be a bug of some kind but I dont have the ability to look

I am willing to give a developer remote access to the PC so as to help resolve the issue.

Jim M0CKE

Correct me if I am wrong but isnt cmASIO designed for hardware ASIO devices?

Just reconfigured to use cmASIO last night and it works great on the Scarlett, got VAC working on both receivers so I can send audio to OBS and the digital recorder without impacting ASIO. Could never do that before and is a great addition, thanks.

Jim,

You never replied to my post above so I don't know if you ever tried the configuration I suggested. It's the same setup Scott advised me to try in an earlier post and it's working for me.

One thing that's quirky about that setup is the ASIOdrivername in Registry is NOT set to the name of the driver that came with my audio interface (MOTU M Series), rather it's set to "Voicemeeter Virtual ASIO", which is the reserved name for Channel 1 in VM Potato. That's where my audio stream flows inside VM, and that's where the Registry is telling CM-ASIO to go to interface with my audio.

If you haven't tried that, you might want to. That works for me and it works for Scott.

Just sayin,
Mark

NC3Z wrote:Correct me if I am wrong but isnt cmASIO designed for hardware ASIO devices?

Just reconfigured to use cmASIO last night and it works great on the Scarlett, got VAC working on both receivers so I can send audio to OBS and the digital recorder without impacting ASIO. Could never do that before and is a great addition, thanks.

That's right Gary, it's designed for (ASIO) hardware device drivers, not virtual device drivers. That said, you might get lucky, as Scott did.

What is the driver name for the Scarlett? Is it the same as for the other Focusrite boxes?

73,
Bryan

m0cke wrote:Update from here

So I tried the M-Audio on a laptop, had the same results

Hi Jim,

As far as I know, you are the first user to try the M-Track Solo (or any M Audio device for that matter) with cmASIO. So, it's possible that the M-Track ASIO driver is just plain incompatible with cmASIO. I will have an M-Track Solo in my hands for testing late this afternoon. So let's see how that turns out, and we'll go from there. Hang in there and I will report back.
73,
Bryan

K1LSB wrote:Jim,

You never replied to my post above so I don't know if you ever tried the configuration I suggested. It's the same setup Scott advised me to try in an earlier post and it's working for me.

One thing that's quirky about that setup is the ASIOdrivername in Registry is NOT set to the name of the driver that came with my audio interface (MOTU M Series), rather it's set to "Voicemeeter Virtual ASIO", which is the reserved name for Channel 1 in VM Potato. That's where my audio stream flows inside VM, and that's where the Registry is telling CM-ASIO to go to interface with my audio.

If you haven't tried that, you might want to. That works for me and it works for Scott.

Just sayin,
Mark

Hi Mark

Ive tried VM Banana and VM Potato on 3 different PC's now and none work

I've also tried ASIO4ALL and this seems to work to get the audio from cmASIO to the PC soundcard

Jim

W4WMT wrote:

m0cke wrote:Update from here

So I tried the M-Audio on a laptop, had the same results

Hi Jim,

As far as I know, you are the first user to try the M-Track Solo (or any M Audio device for that matter) with cmASIO. So, it's possible that the M-Track ASIO driver is just plain incompatible with cmASIO. I will have an M-Track Solo in my hands for testing late this afternoon. So let's see how that turns out, and we'll go from there. Hang in there and I will report back.
73,
Bryan

Hi Bryan

OK thanks, Maybe a list of known working hardware is required, out of interest what hardware did you find that works out?

ASIO4ALL seems to work here which is software only on 3 different machines so far.

Jim M0CKE

ASIO4ALL is just a wrapper around the standard WDM driver and will create more latency than the WDM driver by itself. It's kind of a joke.

This is where Voicemeeter can be useful. It will allow an ASIO connection via its virtual ASIO drivers. Then you can route through Voicemeeter to any sound app or device.

W4WMT wrote: What is the driver name for the Scarlett? Is it the same as for the other Focusrite boxes?

Yes Bryan, it was the standard Focusrite name. Really cool update!

K1LSB wrote:Running 2.10.3.5 pre-release 5 and I just noticed that the CM icon in the Thetis status bar is gone:

Capture.jpg
Anyone else seeing (rather, not seeing) this?

Mark

I am not seeing this. cmASIO seems to be working. I have it set up to deliver Thetis sound directly to the sound card via cmASIO. I am also using pre-release 5.

rbduck wrote:

K1LSB wrote:Running 2.10.3.5 pre-release 5 and I just noticed that the CM icon in the Thetis status bar is gone:

Capture.jpg
Anyone else seeing (rather, not seeing) this?

Mark

I am not seeing this. cmASIO seems to be working. I have it set up to deliver Thetis sound directly to the sound card via cmASIO. I am also using pre-release 5.

It's on the right side between CAT-Status icon and utc-clock.

oe3ide wrote:

rbduck wrote:

K1LSB wrote:Running 2.10.3.5 pre-release 5 and I just noticed that the CM icon in the Thetis status bar is gone:

Capture.jpg
Anyone else seeing (rather, not seeing) this?

Mark

I am not seeing this. cmASIO seems to be working. I have it set up to deliver Thetis sound directly to the sound card via cmASIO. I am also using pre-release 5.

It's on the right side between CAT-Status icon and utc-clock.

OK, maybe I have something configured incorrectly. Hare are a couple of captures that might tell a story. My intention with the cmASIO feature is to send Thetis sound directly to the sound card which it seems to be doing.

Your screenshot is not not showing "ASIOdrivername" entry ?

"Add a new ‘String Value’ with the name ASIOdrivername.
Populate the new string value with the name of your ASIO drive"

rbduck wrote:

oe3ide wrote:

rbduck wrote:
I am not seeing this. cmASIO seems to be working. I have it set up to deliver Thetis sound directly to the sound card via cmASIO. I am also using pre-release 5.

It's on the right side between CAT-Status icon and utc-clock.

OK, maybe I have something configured incorrectly. Hare are a couple of captures that might tell a story. My intention with the cmASIO feature is to send Thetis sound directly to the sound card which it seems to be doing. capture.pngcapture2.png