Audiolense 6.13

[Bernt Rønningsbakk]

[20 dec 2020]

Audiolense 6.13 (64 bit) 

Audiolense 6.13 (32 bit)  

• Made improvements to the wasapi measurement method

Wasapi gave too few available channels with certain sound cards and dacs. A change has been made that will hopefully eliminate this problem.

Wasapi capture does (still) not work on Lynx Hilo,  which has been used for testing. Time will show if this is a widespread problem. Wasapi does however seem to work well for render and capture on realtek (embedded) sound cards.

In any case, this change will hopefully make it easier for several users to combine usb dac with usb mic during measurement.

 

I have also done some testing of win mme and direct sound measurement. Both seem to work well. Both of these are “shared mode” methods that goes via windows sound mixer. The signal will be resampled if the sample rate used for measurement differs from the default rate for the device in Windows. The resampling seems to work pretty well, though. For multichannel measurement, the sound card has to be configured for multichannel playback in Windows, or else these measurement methods will only work for stereo. Wasapi uses exclusive path and has none of these limitations.

 

 

Mvh,

Bernt

 

[Tim]

Hi Bernt,

 

I still get the same error message when trying to directly use WASAPI direct with or without the “use separate record/playback streams” option. 

 

It would be helpful to display (or log) the exact mismatch type(s) to narrow down the problem.  The ambiguous error dialog is still indicating the indeterminate permutations of 4 potential causes.

 

Configuration:

 

·         Win 7-64-bit Ultimate, 2 SSDs, 16GB Memory, Intel i7 4 core/8 thread processor

·         Spectrum Labs Calibrated UMIK-1 USB Mic (only supports 24-bit/48KHz)

·         OKTO Research DAC8 PRO USB DAC

·         DAC configured to 7.1 channels in Windows Control Panel/Sound/Device

·         DAC configured to default of 24/48KHz in Windows

·         Stereo 3-way, using 6 of the 8 channels.

 

 

Sincerely,

Tim

--
--
Audiolense User Forum.
http://groups.google.com/group/audiolense?hl=en?hl=en
To post to this group, send email to audio...@googlegroups.com
To unsubscribe, send email to audiolense+...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Audiolense User Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to audiolense+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/00b401d6d6e3%248352f2e0%2489f8d8a0%24%40lyse.net.

[Fabien THOMAS]

Hello,

On my side last time I was not able to record Umik1 and Motu 8A with Wasapi.

Fabien

Télécharger Outlook pour Android

---

From: audio...@googlegroups.com <audio...@googlegroups.com> on behalf of Tim <emai...@adelphia.net>
Sent: Sunday, December 20, 2020 8:58:29 PM
To: audio...@googlegroups.com <audio...@googlegroups.com>
Subject: RE: [audiolense] Audiolense 6.13

 

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/000301d6d70a%247d40eca0%2477c2c5e0%24%40adelphia.net.

[Omid Mostachfi]

Hi Fabien (and anyone using a Motu Dac/adc),

I use a calibrated EMM6 mic with a phantom power supply (~$100 total) hooked up to my MOTU 8A which allows playback and recording to be synchronized on the same clock. I use the motu pro driver instead of wasapi. It’s not perfect. I still get intermittent errors and knocking sounds during the sweep but it’s less trouble than a USB microphone. 

Omid. 

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/DB7PR02MB454039F0AE3CAC188A0E64FCF5C10%40DB7PR02MB4540.eurprd02.prod.outlook.com.

[Fabien THOMAS]

Hi Omid,

Thanks for your feedback.

To be honest I found Audiolense quite sensitive. Normally there is no issue with Umik1 as it is used by a lot of people with REW or Dirac.

Fabien

Télécharger Outlook pour Android

---

From: audio...@googlegroups.com <audio...@googlegroups.com> on behalf of Omid Mostachfi <omidmo...@gmail.com>
Sent: Sunday, December 20, 2020 9:51:47 PM
To: audio...@googlegroups.com <audio...@googlegroups.com>
Subject: Re: [audiolense] Audiolense 6.13

 

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/CANZ9VTD91QLrjLYUrmVCh8kXfPZVbFm_pd6eVWro9tQWQ8RPPg%40mail.gmail.com.

[Bernt Rønningsbakk]

Hi Tim,

 

The same ambiguity exists in Window’s audioclient api. The format is either accepted or rejected, including number of channels, sample format, sample rate and exclusive / shared mode.

 

This is the subjectcall: https://docs.microsoft.com/en-us/windows/win32/api/audioclient/nf-audioclient-iaudioclient-isformatsupported

 

 

Audiolense only uses exclusive mode with wasapi. Wasapi shared mode is practically the same as dsound and win mme.

 

 

 

Have you configured the two devices for allowing exclusive mode in windows?

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Tim
Sent: søndag 20. desember 2020 20:58
To: audio...@googlegroups.com
Subject: RE: [audiolense] Audiolense 6.13

 

Hi Bernt,

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/000301d6d70a%247d40eca0%2477c2c5e0%24%40adelphia.net.

[Fabien Thomas]

Hi,

 

Another test with Wasapi using 7.1 48Khz/24b (default format for headphones / microphone).

It failed with this error. It should work normally ?

 

Fabien

 

De : Bernt Rønningsbakk
Envoyé le :Sunday, December 20, 2020 4:19 PM
À : audio...@googlegroups.com
Objet :[audiolense] Audiolense 6.13

--

[Tim]

Hi Bernt,

 

Here are the Win7-64 settings for the UMIK-1 and the DAC8 PRO WASAPI drivers.

 

Are there any other EXCLUSIVE MODE configurations that should be set elsewhere ?

 

FWIW, I noticed that Windows 10’s playback device options list the number of channels in the FORMAT GUI, but Win7-64 does not.

 

 

Here is the Win7-64 7.1 channel configuration for the DAC8 PRO WASAPI driver.

 

Let me know what I should try or if there are any other settings to be made.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/00ec01d6d71c%24abef2140%2403cd63c0%24%40lyse.net.

[Bernt Rønningsbakk]

 

Wasapi seems to work with multichannel on my asus u7 usb dac with 6 channels in and out. It starts, runs and stops. I am testing without speakers and mic connected, but it is reasonable to expect that the streaming is OK.

Wasapi works on Lynx Hilo for  multichannel output, but does not accept the IAudioClient::IsFormatSupported() call for the input although it has 8 input channels available in any of the other 3 methods.

Realtek on my laptop accepts everything except Asio. It doesn’t have an Asio driver.

 

The two last cases posted here by Fabien and Tim should have come past the format checking if they had responded properly to the IAudioClient::IsFormatSupported() call, which is a very basic function in Windows’ core audio api. I have hard-coded 128 available channels for input and output, because  the most logical way to poll for number of channels has shortcomingsm and channel support anyway is covered by the isformatsupported call.  I believe  IAudioClient::IsFormatSupported() call returns with a “this format is not supported” value in these cases. There is one call for input and another for output, btw.  If any of the two devices are rejected, the configuration will not be accepted.

 

Issues such as these arise from time to time. It usually involves USB devices that doesn’t come with a custom made driver.

 

I have asked Lynx Studio to check the subject call on wasapi rendering on the Lynx Hilo. If they get back with a response I may learn something from that. Or maybe they will find a bug. That is unlikely to matter in this case since you guys do get a rendering reject. Right now there isn’t much else I can do to make wasapi recording work unless you guys have suggestions.

 

 

 

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Fabien Thomas
Sent: søndag 20. desember 2020 23:10
To: audio...@googlegroups.com
Subject: RE : [audiolense] Audiolense 6.13

 

Hi,

[Bernt Rønningsbakk]

Your settings look all right to me.

 

Which format gui are you referring to, btw?

 

And does jriver work with 8 channel wassapi rendering? You can test this by choosing 7.1 as output format in jriver’s dsp studio and choos DIYNHK wasapi as the output device. I know someone I could ask a couple of questions if this works.

 

And if you e.g. choose direct sound for your dac (in Audiolense) and stick to the wasapi for the microphone – do you get a green light?

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/001301d6d729%24ba997b20%242fcc7160%24%40adelphia.net.

[Tim]

Hi Bernt,

 

I was refering to the format in the “Speakers Properties” GUI, “24 bit, 48KHz (Studio Quality)”. 

 

Windows 10 displays something like “8 channel, 24 bit, 48KHz (Studio Quality)”.

 

 

JRMC handles 6 or 8 channels of the DAC8 PRO fine with either the ASIO or WASAPI driver (No ASIO4ALL or FlexASIO required) with or without convolution up to 192KHz PCM or DSD128.

 

When I measure in REW, I measure through JRMC’s WDM so I get safe volume control, XO, frequency, phase, delays and OB/Dipole rolloff compensation filters.  Input is REW’s Java and output is JRMC’s WDM.  I would like to replace REW and RePhase with an automated integrated solution.

 

I have JRMC’s WDM defined as the default Windows output device so I don’t blow out my tweeters by other Windows apps bypassing the crossovers.  I should probably disable Windows OS sounds if I haven’t already (e.g. error bleeps, boot sounds, etc.).  Web based audio aps use JRMC’s default WDM driver (youtube, Pandora, Spotify, etc.).

 

I don’t know what green light you are referring to.

 

When I use “Enable Direct Sound”,  Direct Sound as output and WASAPI as input, it allows me to check all 6 speakers correctly, but I get the same mismatch error when trying to measure, with or without “Use separate record/playback streams”.  If it sees all 6 speakers on the speaker check, it should know what a mic is.  Note: I have not done any special configurations for “Direct Sound” and don’t know where I would do that.  Maybe it needs to be set to 24/48 like the mic.

 

When I try the same thing with “Windows MME”, I get a paUnanticipatedHostError when trying to check speakers and the same mismatch error when trying to measure.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/011001d6d72f%24f738d520%24e5aa7f60%24%40lyse.net.

[Bernt Rønningsbakk]

There’s no channel count for Lynx Hilo on my 64 bit Win10. So I wouldn’t worry about that.

 

 

I have a miniDSP Ears unit here. So I figured I’d test with that. It appears that it does not support exclusive mode, even though it has the check box for it in the Sound control panel that you inserted a picture of below. Perhaps the same is the case for the Umik. Both are driverless and both are hardcoded with 24 bit / 48 kHz.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/001201d6d73c%2405be3750%24113aa5f0%24%40adelphia.net.

[Fabien Thomas]

Hi,

 

It seems you are right, in this case the headphones does not support exclusive Wasapi (tested with Qobuz App).

Maybe adding the information that Exclusive is not available and capture without it ?

 

Fabien

 

De : Fabien Thomas
Envoyé le :Sunday, December 20, 2020 11:10 PM
À : audio...@googlegroups.com
Objet :RE : [audiolense] Audiolense 6.13

[Bernt Rønningsbakk]

Yes I think I will implement shared mode as an option. Then Audiolense will have three of the kind…..

 

At least it will give one more winning ticket in the lottery for those pieces of hardware that doesn’t have a proper driver.

 

Mvh,

Bernt

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/E83DBCD9-EC06-4C36-BAAF-689CAF1FD6DE%40hxcore.ol.

[Johnny Jensen / JJAZ]

Your site is being reported by google as having malicious content. Has something happened?

Greetings from Denmark

Johnny

[Bernt Rønningsbakk]

I’m on it. Most likely false alarm.  The web hotel is having technical problems.

 

 

 

Mvh,

Bernt

--

--
Audiolense User Forum.
http://groups.google.com/group/audiolense?hl=en?hl=en
To post to this group, send email to audio...@googlegroups.com
To unsubscribe, send email to audiolense+...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Audiolense User Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to audiolense+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/805a3daf-6875-47db-8c64-7ee6b6bc20e2n%40googlegroups.com.

[Johnny Jensen / JJAZ]

Thanks, I was just about to download 6.13 and play with it. I really want to pull the trigger and buy an XO license, but still fighting with getting it to work exactly like I want it to :)

Greetings from Denmark

Johnny

[Bernt Rønningsbakk]

You can use the link down below.

 

I’ve checked that those files hasn’t been tampered with.

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Johnny Jensen / JJAZ
Sent: tirsdag 22. desember 2020 17:00
To: Audiolense User Forum
Subject: Re: [audiolense] Re: Audiolense 6.13

 

Thanks, I was just about to download 6.13 and play with it. I really want to pull the trigger and buy an XO license, but still fighting with getting it to work exactly like I want it to :)

 

Greetings from Denmark

Johnny

 

 

On Tuesday, December 22, 2020 at 4:46:05 PM UTC+1 BerntR wrote:

I’m on it. Most likely false alarm.  The web hotel is having technical problems.

 

 

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Johnny Jensen / JJAZ
Sent: tirsdag 22. desember 2020 16:41
To: Audiolense User Forum
Subject: [audiolense] Re: Audiolense 6.13

 

Your site is being reported by google as having malicious content. Has something happened?

Greetings from Denmark

Johnny

 

Error! Filename not specified.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/a5b3b393-2fa8-4ce5-8ce9-02b15b9f98d4n%40googlegroups.com.

[Johnny Jensen / JJAZ]

Thanks, will try it right away.

On 6.12 I "can almost" measure through JRiver (which would solve my subwoofer summation issue), but am seeing delays that are sometimes correct and sometimes not.

[Johnny Jensen / JJAZ]

Unfortunately still the same WASAPI issue with my Prism Sound Atlas (The channel setup is not supported by the sound card. Perhaps too many channels?)

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-22_al613_wasapi_error.jpg

On Tuesday, December 22, 2020 at 5:38:22 PM UTC+1 BerntR wrote:

[Bernt Rønningsbakk]

I believe that should work, but use Asio through jriver if you can.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/8aa3fba8-77d7-459c-829f-97e1630c0905n%40googlegroups.com.

[Omid Mostachfi]

Hi Johnny,

Aside from your present measurement issues, I realized/remembered you can implement delays for your subwoofers without going through JRiver. You just open your cfg file and manually input the delays per subwoofer channel, if the delay is not too long. 

“ The delay cannot exceed half the partition length.  So if you are using a 44.1kHz and a filter that is 131072 taps long, for example, you cannot delay by more than 1486ms (131072 / 44.1 / 2)”

http://convolver.sourceforge.net/config.html

Omid. 

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/69aea606-aacd-441b-96f0-c6830772afd7n%40googlegroups.com.

[Bernt Rønningsbakk]

I am still looking into this. I have four devices here for testing various wasapi settings, and they do not respond the same way at all. Between the two multichannel sound cards I am using, there are shortcomings that will require serious workaround coding to find out if it will  work.  Getting some audio through the right channels is just first base. But I am considering it. The two multichannel cards I am testing with seem to do 2,4 and 6 channels OK, but not 3 and 5. Lynx Hilo accepts 1 channel rendering, but the audio that goes out is a stereo signal that has nothing in common with the log sweep it’s supposed to be. And then Hilo only accepts 8 channels for the recording stream. I believe it works too,  but I need to implement multichannel capture in Audiolense just to find out.  

 

Wasapi is messy and I don’t know if I will be able to work around all the unexpected responses I am getting.  I’ll try, though.

 

As for now, direct sound and winmme behave more predictable and reliable … most of the time, and Asio4All is the best way to stay clear of the Windows mixer during measurement when true Asio drivers are missing.

 

Nothing comes close to native Asio, though. It is more stable, the audio streams are much less likely to skip or hang, the protocol is transparent with literally no ambiguity,  and practically any sound card respond the way they are sopposed to on most commands. It is a pity that Microsoft hasn’t been able to make something that is equally reliable.

 

If you get fed up of all these measurement problems, get a Lynx Aurora, an RME sound card or something similar that is made for the professional market and has a native Asio driver.

 

And Johnny, could you do me a favour and test the Prism with different number of output channels? You probably have an embedded microphone on your pc that you can assign for the capture … just to keep it out of the way….

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/69aea606-aacd-441b-96f0-c6830772afd7n%40googlegroups.com.

[Fabien Thomas]

Hi Bernt,

 

Just a proposal : If you can give us a debug tool that dump WASAPI info we can give back the debug log for you to look at.

 

Regards,

Fabien

 

De : Bernt Rønningsbakk
Envoyé le :Tuesday, December 22, 2020 7:26 PM
À : audio...@googlegroups.com
Objet :RE: [audiolense] Re: Audiolense 6.13

1.      Made improvements to the wasapi measurement method

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/025201d6d88f%24ed913dd0%24c8b3b970%24%40lyse.net.

 

[Johnny Jensen / JJAZ]

The weird "file open error" still exists for Direct Sound and WME (through JRiver), if I use them for both input and output. Also, it is evident on the "Microphone input monitor" that no signal is registered on the input.

If I choose Direct Sound/WME as output (through JRiver), and ASIO as input the file open error is gone. It appears to be almost stable, but I get occasional clicks/pops (WME is a lot more stable than Direct Sound on my setup).

Interestingly, both Direct Sound and WME output (through JRiver) measures a longer delay on my "farthest away" subwoofer than when measured through ASIO (without Jriver). If all other channels measure delays exactly like ASIO, that subwoofer measures 11.75ms (WME/Direct Sound) and 12.25ms (ASIO). A 0.5ms difference really does not matter with an XO @100Hz, but still strange.

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-22_al613_directsound_fileopenerror.jpg

ASIO through JRiver does not work, I get the same paDeviceUnavailable as I did in 6.12. Sometimes the "Check Speaker Connections" will "work" for the first speaker, albeit with lots of dropouts, if I press ok to get the next speaker the paDeviceUnavailable shows its ugly face :-(

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-22_al613_asio_jriver_error.jpg

Note: The above is for a 2.1 speaker setup: Front Left small, Front Right small, Subwoofer (1 or 3 channels)

Extending my tests to a 2.1 with: Front Left small (100-250Hz), Front Right small (100.01-250Hz), Front Left small (>250Hz), Front Right small (>250Hz), Subwoofer (1 channel)

Now I see different delays, but fairly consistent from one WME measurement (JRiver) to the next.

The delays no longer match what I measured direct via ASIO, perhaps because I route two channels (my left and right midbass) in JRiver to get them on "reachable channels" (routing them in JRiver from Surround Left/Right to channel9+10 on the Prism device).

Delays ASIO Prism:

Left tweeter: 0.00

Right Tweeter: 0.15

Left midbass: 1.42

Right midbass: 1.58

Subwoofer: 12.27

Delays WME JRiver: (with just left, right & Sub, no midbass)

Left tweeter: 0.00

Right Tweeter: 0.15

Subwoofer: 11.75

Delays WME Jriver: (left tweeter, right tweeter, left mid, rigfht mid, sub)

Left tweeter: 0.15

Right Tweeter: 0.29

Left midbass: 0.00

Right midbass: 0.54

Subwoofer: 11.92

That change in delays are odd..

On Tuesday, December 22, 2020 at 5:38:22 PM UTC+1 BerntR wrote:

[Johnny Jensen / JJAZ]

Hi Omid,

Are you sure it works? According to the JRMC wiki, input delays are not supported in the cfg-file? (https://wiki.jriver.com/index.php/Convolution)

But, the real problem is that I need the delays and routing, to be in place before I measure with Audiolense. Audiolense must see all of my subwoofers as one unit, and not measure (and correct) them as individual subwoofers.

[Johnny Jensen / JJAZ]

I will do what I can to help.

1. If you get fed up of all these measurement problems, get a Lynx Aurora, an RME sound card or something similar that is made for the professional market and has a native Asio driver.

Answer: The Prism Sound Atlas is a 4.200 EUR professional sound card with native ASIO drivers. Its intended use are music studios. It only features 10 analog outputs though, so I have daisy chained a custom 2-channel DAC (hardware from Digital Audio Denmark) via SPDIF to get 12 channels in total.

2. And Johnny, could you do me a favour and test the Prism with different number of output channels? You probably have an embedded microphone on your pc that you can assign for the capture … just to keep it out of the way….

Prism with different number of output channels, you mean adjusting the number of output channels in JRiver -> Output Format? Currently I have it set to 12, but can try 14 and 16, if that is what you mean?

My HTPC does not have an embedded microphone, but I can attach another USB soundcard (Focusrite Scarlett 18i20 or 2i2) and use that as the microphoone input?

The above testing, is that for Audiolense output as WASAPI, ASIO or something else, and what input type (WASAPI/ASIO/..) do you want me to use on the Scarlett USB soundcard?

I did try one thing, to use a different mic interface (Steam Streaming Microphone) WASAPI. JRiver ASIO output is still full of drops outs, and JRiver WASAPI still give the same error.

[Tim]

FWIW, JRMC supports delays via their “Parametric Equalizer/Add/Delay” option.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/3b38a45d-df69-4d86-a4eb-0c1c3993a346n%40googlegroups.com.

[Johnny Jensen / JJAZ]

I know, and I use that. But, it doesn't solve my Audiolense measurement issues, since I have troubles measuring with audiolense through JRiver.

[Bernt Rønningsbakk]

Hi Fabien,

 

I don’t think it will give me any new info. If IAudioClient::IsFormatSupported() returns OK, Audiolense will tell you that the format is supported.

 

https://docs.microsoft.com/en-us/windows/win32/api/audioclient/nf-audioclient-iaudioclient-isformatsupported

 

I have already implemented sharemode wasapi, which will be out in the next release. Maybe that will work for some.

 

Mvh,

Bernt

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/1543AD43-B5AC-432A-95A9-B30A08C62CFB%40hxcore.ol.

[Bernt Rønningsbakk]

Hi Johnny,

 

Clearly something is happening through jriver here.

 

The measurement you’ve done with Asio seems reliable.  Same delay between left and right tweeter and left and right midbass.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/c998bd9c-e170-4a16-8666-f05d4291efefn%40googlegroups.com.

[Bernt Rønningsbakk]

Much appreciated, Johnny

 

I could potentially modify the code to round up to the nearest supported channel count if I get some indication that channel count support is the bottleneck here.

 

It would be helpful if you could test wasapi out with your sound card.

 

Start out with a 1 speaker configuration and see how wasapi in Audiolense responded. Preferrably listen to the output as well, since I am experiencing a funny stereo output on my Hilo with one speaker out.

 

Then try odd number speakers and just check if the format is supported. And if the wasapi input is not supported by your sound card just use something else, the microphone or line level input on the embedded sound card on your PC will do just fine.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/6eb24d36-1f8f-4f25-8e30-3c6d056667efn%40googlegroups.com.

[Johnny Jensen / JJAZ]

I will do my best, when Christmas family-time permits.

Today I connected the Focusrite Scarlett and use it to output an analog signal to an input on the Prism Sound Atlas. This enables me to measure with REW through JRiver (ASIO Line-In). It is totally stable, but a little inconvenient :-)

As soon as possible I will make the WASAPI experiements for you.

[Johnny Jensen / JJAZ]

I am afraid I won't be of much help.

The amount of channels (in Audiolense) on the JRiver (WASAPI) device does not matter, I get the same errors.

As Microphone Input Device I tried with the Focusrite Scarlett 18i20 in WASAPI mode, and I also tried with a USB headset (Jabra Evolve) in WASAPI mode. Lastly I tried with the embedded "Mic: High Definition Audio Device", and got the same errors.

If I have disabled "Separate play and recording streams" I get the "Invalid channel count" error.

If I have enabled "Separate play and recording streams" I instead get the "paInvalidDevice" error.

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_invalid_channel_count.jpg

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_invalid_channel_count2.jpg

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_invalid_channel_count3.jpg

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_painvaliddevice_separatestreams_1.jpg

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_painvaliddevice_separatestreams_2.jpg

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_wasapi_1ch_painvaliddevice_separatestreams_3.jpg

One funny observation. When choosing a 1-channel speaker setup in Audiolense, sometimes it still shows an 80Hz crossover in the graphics :-)

https://www.jjaz.dk/privat/hifi/audiolense/2020-12-23_1-channel_xo_issue.jpg

On Wednesday, December 23, 2020 at 11:48:21 AM UTC+1 BerntR wrote:

[morr...@tpg.com.au]

Bernt

Have you been able to progress getting WASPI to work ? I downloaded and tried 6.13 and still get the same error message about too many channels. I am using Windows 10 pro with a Metric Halo ULN8 - an 8 channel DAC/ADC using usb connection to the windows computer. It uses the built in windows driver. The windows mme  option works but I would much prefer not togo through windows mixer.

Apart from mme the only other option that works for me is ASIO4all however I get occasional clicks during the playback of the recording steps if I use ASIO4all.

I am using 8 channels out on the ULN8. I also use the ULN8 for mic input for the measurements.

Regards

Mark

[Bernt Rønningsbakk]

I have enabled shared mode, which will be out in the next release.

 

What I have seen so far of wasapi implementations is a mixed bag. I believe the code in Audiolense is already OK when wasapi is properly implemented in the driver. But this is quite often not the case. E.g. Lynx Hilo only accepts standard source formats with 2, 4, 6 and 8 channels. And on the input side it only accepts that all 8 input channels are used. And I don’t even know if that really works or just reports to be supported. The Hilo also accepts one channel playback, but what comes through is a total mess … in stereo! So I contacted the driver designer in Lynx and told him of my findings. It  appears that they don’t do USB drivers themselves, but  are  using a widely used 3^rd party driver. This could mean that the problems I am seeing with the Hilo is widespread. And those who doesn’t even accept exclusive mode may have other problems.

 

I am considering implementing a probing approach, probing for the nearest accepted channel count that is high enough, but I haven’t decided whether it is worthwhile to try this. It will complicate the code a lot because I will need to do double book-keeping on channel count and channel routing. Actually a triple, since double book keeping was implemented with the channel override option. And I fear that there are more surprises waiting to surface.

 

I have contacted the driver manufacturer. Their first response was that Lynx did not use their driver. So I gave them a direct quote from Lynx Studio. Haven’t heard anything from them since. Perhaps they are looking into it and will come back with new info. I am still tempted to try the probing approach, though.

 

Mvh,

Bernt

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/dfa8f8aa-390d-47cf-b9c5-3dd18475b27bn%40googlegroups.com.

[morr...@tpg.com.au]

Thanks for the update Bernt. I will wait for the next release and see if that works with the Metric Halo ULN8.

On a seperat item. Do you send out a reminder when our yearly support payment is due ?

Regards

Mark

[Bernt Rønningsbakk]

Hi Mark,

 

Sorry, I don’t have a system for keeping up when support periods expires.  

 

I could put it in Audiolense and the convolver, so that you get a reminder if you use the apps when the support period had run out. But wouldn’t it appear to be fussy?

 

PS Please sign up to the new forum at AVNirvana so we can get it going 100%.

To view this discussion on the web visit https://groups.google.com/d/msgid/audiolense/38a5afd7-379a-4980-9ca5-9928751abcedn%40googlegroups.com.