Audiolens 6.3 Initial Setup

[Leo]

Hi,

I am running Audiolens 6.3 XO trial on Windows 10 Home (1909) within a Parrallels virtualisation on a Mac mini with macOS 10.15.3 

Within Audio lens

- Mic calibration file is loaded.

- seperate play and recording streams

- RME ADI-2 DAC (RME MADIface ASIO Driver) 

- miniDSP UMIK-1 (ASIO4ALL Driver)

- Format and device combination is supported

- Check Speaker Connections is performed ok

When running a measurement a "paDeviceUnavailable" message is displayed.

Questions:

1 - What is the meaning of this cryptic error message ?

2 - How can this error be resolved.

[carl marchetto]

Leo thanks so much for sharing your results 

Awesome!

--
--
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/9c6e6fd5-b4df-4aab-8aad-8e0f41d44a04%40googlegroups.com.

[Omid Mostachfi]

I had similar problems. I reinstalled ASIO4ALL And realize there were a couple of extras that I had declined to install the first time. If you install the extras, it may get rid of the problem. You should also go in the offline control panel for A4 And make sure that the microphone is selected as an input, And your RME as an output. Also make sure the buffer is at the max. In the windows control panel make sure that both input and output devices are at the same sampling frequency rate. 

If that does not work try selecting direct sound Or one of the other drivers. 

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

[Leo]

Thank you for your responses.

To be clear about my configuration RME MADIface ASIO is NOT enabled within ASIO4ALL. miniDSP UMIK-1 is enabled within ASIO4ALL

RME MADIface ASIO Driver is selected within Audiolens as the Playback device. RME MADIface Driver and selection of ASIO MADIface USB (ASIO) was the only option that corrected performed the Audiolens Speaker Connections test.

ASIO4ALL is selected within Audiolens as the input devices. Audiolens stated other configuration variations where unsupported. Using any driver type other that ASIO caused Audiolens to disappear into thin air.

I have confirmed that as devices , drivers where set to 48,000Hz and ASIO buffers where increased to 2048.

So my question stands. Audiolens detected a measurement error condition and displayed “paDeviceUnavailable” - What does error message actually mean and related to. Understanding that message will help my to focus the troubleshooting.

[Bernt Rønningsbakk]

Hi,

 

The meaning of the message is that the device(s) you have chosen refuse to be initiated.

 

The reason is that you can not use ASIO for two different devices at the same time.

 

You can either configure asio4all to communicate with both devices or you can try wasapi on one of the devices – or both.

 

Mvh,

Bernt

--

[Leo]

Hi,

Thank you for responding.

I have attempted various configurations; My configuration is now:

- Audiolens 6.3 XO trial on Windows 10 Home (1909) within a Parrallels virtualisation on a Mac mini with macOS 10.15.3

- Windows 10: RME MADIface Driver Installed
- Windows 10: RME and UMIK-1 Configured as only Sound Devices
- Windows 10: Notifications Sounds on Low

- Windows 10: Notifications Disabled
- Windows 10: Windows Defender Disabled

- Windows 10: Firewall Disabled

- Audiolens Setup: Default Directory Changed to Read Write Location

- Audiolens Setup: Open Speaker Setup, Edit Speaker Setup, Save Speaker Setup - All tested OK

- Audiolens Measurement: Mic calibration file is loaded

- Audiolens Measurement Advanced Settings: Seperate play and recording streams

- Audiolens Measurement Advanced Settings: Use Clock Drift Correction

- Audiolens Measurement Advanced Settings: WASAPI Disabled (RME MADIface ASIO and WASAPI UMIK-1 Format and device combination NOT supported)

- Audiolens Measurement Advanced Settings: Direct Sound Measurement Enabled (RME MADIface ASIO and Direct Sound UMIK-1 Format and device combination IS supported)

- Audiolens Measurement: Check Speaker Connections tested OK

- Audiolens Measurement: Quick Measurement selected

- Audiolens Measurement: Measuring Channel 3/3 Sweeps performed ok

Resulting Error Message - Measurement Error - File open error - See attached screenshot

I have changed Audiolens default directory and tested read/write access within Audiolens by saving Speaker Setup Files.

What is the file open error related to? How would I overcome this issue? 

[DavidV]

Hi Leo,

This previous thread may shed shed some light on your issue: https://groups.google.com/forum/#!topic/audiolense/4IsyKc1G-V0

Hope it helps.

Regards,

David

[Leo]

Hi,

Thank you for responding.

From the Google Group thread you linked it would seem file open errors have been from at least Audiolens 5.5

I have ensure there is not Google Drive, One Drive or Dropbox enabled on the Windows 10 Virtual Machine or the underlying macOS.

I have ensured that the Audiolens Default Directory is on the Windows 10 Drive C: - Audiolens then creates a directory structure as shown in the attached screenshots

During the first measurement run files are created as shown in the attached screenshots.

During a second measurement run (without closing Audiolens), sweeps are performed but no files appear to be created. My assumption is that temporary files are be utilised within the program; Please confirm or deny this assumption?

In order to assist in debugging Audiolens file access what debug log options are available to view Audiolens files access events and file access locations?

[Bernt Rønningsbakk]

The file open error could be related to Windows Defender. I haven’t paid the dollars needed for Audiolense to be regarded as “safe”. You can put Audiolense on the friendly list.

 

There can be other causes too, and some of them are temporal and disappear if you simply restart the computer.

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Leo

Sent: lørdag 4. april 2020 18:28
To: Audiolense User Forum

--

--
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/335e0413-5534-4bdf-93f5-8f35db15eb17%40googlegroups.com.

[Leo]

Hi,

Thank you for responding. As suggested I have add an exclusion to Widows Security:

1- Go to Start  > Settings  > Update & Security  > Windows Security > Virus & threat protection.

2- Under Virus & threat protection settings, select Manage settings, and then under Exclusions, select Add or remove exclusions.

https://support.microsoft.com/en-au/help/4028485/windows-10-add-an-exclusion-to-windows-security

I have then performed a measurement run:

- Audiolens Measurement: Measuring Channel 3/3 Sweeps performed ok

- Resulting Error Message - Measurement Error - File open error - See attached screenshots

In order to assist in debugging Audiolens file access what debug log options are available to view Audiolens files access events and file access locations?

[Bernt Rønningsbakk]

Hi Leo,

 

I’ve spent some time examining the code and trying to figure out what’s going on here.

 

You are correctly assuming (as per your first post) that the files you saw in the measurement folder are re-used during the measurement process. And the fact that the program is allowed to create those – and that they hold the measurement sweep – indicate that this is not an access problem after all.

 

The error message you get is most likely true, and related to opening the sweepmeasurement.wav, which contains the recorded signal. It is opened 3 times in the post processing, and it seems like it is blocked the 2^nd or 3^rd time. My guess is that something is going wrong during the first open, when the impulses are supposed to be extracted. The error handling in the code is such that it should be properly closed each time no matter what, but the file operations are asynchronous and sometimes they can hang even though the close file command has been run.

 

I suggest that you do the following:

 

1)      Check the size of the sweeepmeasurementfile.wav. It should contain the recorded sweep, so it should have a significant size, more than 1 Mb.

2)      If you’re well versed with audio programs you could open the sweepmeasurementfile.wav in Audacity (open source) and check if a real sweep has been recorded.

3)      Check that the Microphone input monitor comes alive when you start the measurement.

 

 

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Leo
Sent: søndag 5. april 2020 02:02
To: Audiolense User Forum
Subject: [audiolense] Re: Audiolens 6.3 Initial Setup

 

Hi,

--

--
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/76f26aa1-9043-44b4-98a9-f992cfe2bb88%40googlegroups.com.

[Leo]

Hi,

Thank you for your response.

I have captured a video of Windows Audiolens measurements, measurement files, and Audacity view of sweep file.

https://drive.google.com/file/d/1yBvsoD2pcid71gpVbP8cYHJqNEOMqJqI/view?usp=sharing

[Bernt Rønningsbakk]

Hi Leo,

 

Good job with the video.

 

You are not getting a proper signal in from the microphone here. You need to sort out that.

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Leo
Sent: søndag 5. april 2020 19:51
To: Audiolense User Forum
Subject: [audiolense] Re: Audiolens 6.3 Initial Setup

 

Hi,

--

--
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/f7eeadbd-fa3c-4104-8a86-e598b3cd994f%40googlegroups.com.

[Leo]

Hi,

Thank you for your response.

Before I go a build a physical Windows 10 machine, I would like to understand how a typical physical Windows 10 Machine would be configured with Audiolens to utilise an RME ADI-2 DAC and miniDSP UMIK-1.

RME ADI-2 DAC: RME MADIface drivers must be installed to obtain playback.

miniDSP UMIK-1: miniDSP forums discuss the use of ASIO4ALL.

Is it possible to configure Windows 10 and Audiolens to use ASIO for both RME ADI-2 DAC and miniDSP UMIK-1? How ?

[Omid Mostachfi]

 I don’t know if this will help. I find that sometimes when I get a file error, it will keep on giving me the same error (even if I close the program and restart windows), until I start from zero. That means put a new speaker configuration [2.0 in your case], load the mic calibration, and then try your measurement. Sometimes the error goes away that way. 

--

[Jeffrey Robbins]

I have fixed that kind of error the Same way as Omid. But, I note that your output is ASIO and the mic input is Direct Sound. I recommend setting your output and the mic input in ASIO4all and then use ASIO4all for both input and output so they match. That solved my initial setup problems. JCR

[Bernt Rønningsbakk]

Only with Asio4All. You will not be able to tell the difference between a correction made from an Asio measurement compared to e.g. windows mme.

 

Mvh,

Bernt

 

From: audio...@googlegroups.com [mailto:audio...@googlegroups.com] On Behalf Of Leo
Sent: mandag 6. april 2020 00:30
To: Audiolense User Forum
Subject: [audiolense] Re: Audiolens 6.3 Initial Setup

 

Hi,

--

--
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/8d8262ff-203a-44ba-b6b0-b986e3070f34%40googlegroups.com.

[Bernt Rønningsbakk]

Omid and Jeffrey,

Thank you for sharing.

Mvh,
Bernt

[Leo]

Hi,

With the Easter weekend here I able to perform more troubleshooting my Audiolens initial setup issues.

I believe that I have validated my hardware and driver software configuration by installing REW for Windows and performing a successful measurement.

My environment is now:

- RME ADI-2 DAC

- miniDSP UMIK-1

- Windows 10 Home (1909) within a Parrallels virtualisation on a Mac mini with macOS 10.15.3

- ASIO4ALL Driver (Note: RME MADIface Drivers are not installed)

- Audiolens 6.4 XO Trial

- Windows 10: RME and UMIK-1 Configured as only Sound Devices - - Other standard devices disabled

- Windows 10: Notifications Sounds on Low
- Windows 10: Notifications Disabled
- Windows 10: Windows Defender Disabled
- Windows 10: Firewall Disabled
- Audiolens Setup: Default Directory Changed to Read Write Location
- Audiolens Setup: Open Speaker Setup, Edit Speaker Setup, Save Speaker Setup - All tested OK

- Audiolens Measurement: New

When opening a new measurement, there was no option to configure any Playback device or Microphone input device. 

Resulting Error Message - Measurement initialisation error - Failed to initialise the wave player - See attached screenshot

How can I resolve this error?