Originally Posted by soupiraille ➡️

This is definitely it, but I must add that there must not be any DC filter at all.

Originally Posted by SteveDanger ➡️

I'm not sure. The newer Anubis measurements also seem to be better and AFAIK Anubis had the Monitor Mission for a long time. Now of course we (or I) don't know what was used in the older measurements.

Originally Posted by greenmike ➡️

Lynx Mesa

Originally Posted by greenmike ➡️

The 05 and 5 at the end means -0.5 and -5 and the output fader in Pro Tools of the track.

Originally Posted by didier.brest ➡️

mesa 24 bit 34 out to 12 in 05_01.wav
1.790690 ms, 0.4334 dB (L), 0.4410 dB (R), -58.9380 dBFS (L), -59.0491 dBFS (R)
mesa 24 bit 34 out to 12 in 5_01.wav
1.790690 ms, 4.9334 dB (L), 4.9410 dB (R), -58.9383 dBFS (L), -59.0492 dBFS (R)
mesa 24 bit 34 out to 34 in 05_01.wav
1.790690 ms, 0.4407 dB (L), 0.4425 dB (R), -58.9395 dBFS (L), -59.0495 dBFS (R)
mesa 24 bit 34 out to 34 in 5_01.wav
1.790690 ms, 4.9404 dB (L), 4.9423 dB (R), -58.9396 dBFS (L), -59.0495 dBFS (R)


Doest it mean that the digital stream from your DAW at the DAC input is attenuated with respect to the original ? Then it is not compliant with the test rules.

Originally Posted by soupiraille ➡️

What’s the point of lowering the output? ..?

Originally Posted by soupiraille ➡️

You cannot clip your DAW coming from your ADC.
According to the results, your ADC comes out at about -0.06dB.

Originally Posted by greenmike ➡️

Is that ok?

Originally Posted by soupiraille ➡️

Your ADC generates a 24 bit fixed point (integer) stream, it cannot go over 0.
Also, -0.5 + 0.441 = -0.059.

—
If your ADC is clipping internally, that would not show up in your DAW’s meters. The maximum is 0 in fixed point (integer) format, you won’t ever see something more than 0dBFS coming from your ADC (unless it’s a floating point ADC, which the Mesa does not seem to be).

In order to actually avoid possible clipping, you need to gain stage properly before the actual A to D conversion occurs.

Originally Posted by didier.brest ➡️

In an ideal world, you should play Original2.wav unchanged to the tested machine (audio interface or converter). Any level adjustment should be done by means of this machine settings (gain, volume, reference analog level (0 dBFS--> x dBu), ...).
I understand that the digital audio stream incoming your Lynx Mesa from Pro Tools (through USB, Thunderbolt or anything else for linking a computer and an audio interface) was not peaking to 0 dBFS unlike Original2.wav but to about -0.5 dB or -5 dB. Is there no playback volume control at Lynx Mesa line outputs that you could use for avoiding digital clipping at the line inputs ?

Originally Posted by soupiraille ➡️

@ greenmike probably due to how different DAWs work, I think I’ve misunderstood what you said, so please discard anything I said about your gain staging.

Originally Posted by greenmike ➡️

I can simply bring down the output of the track by -0.1 on the output of the track in Pro Tools before it goes out of 3-4 or do it on the Lynx Mesa mixer app which also allows me the bring down the output volume. Is there a difference between either of it?

Originally Posted by didier.brest ➡️

Likely there should not be any significant difference in the test results but bringing down the output volume in the Lynx Mesa app is compliant with the test rules while playing back to the Lynx Mesa a reduced gain version of the original generated in Pro Tools is not. I would prefer a compliant test if you can and have time to make it. If not I will add your Pro Tools -0.5 dB tests to the next issue of the list of the results.

Loopback tests requested by forum members: Eventide H8000FW (for validating or invalidating the test from jeamsler), Pacific Microsonics Model One and Model Two, RME M-32 AD Pro --> M-32 DA Pro, RME M-1610 Pro, Prism Dream DA-2 --> AD-2, BlackLion Audio Revolution 2×2, SSL BiG SiX, Prism Sound Dream ADA-128, anything from Qes Lab, JCF, Burl and Linn, iZ RADAR, Avid HD OMNI, Fractal Audio Systems Axe-Fx III, NEVE MBC, Sound Blaster X7, Focusrite ISA 428, Elektron Octatrack MKII , Burl B2 Bomber ADC ---> DAC, dCS, Antelope Audio Amari, Black Lion mods (e.g. Apollo X mods), Lynx Hilo 2, new (2024) MOTU 828, Forssell MDAC-2 ---> MSB Studio ADC as master, Solid State Logic SSL 18, Ferrofish PULSE8 AE, Pulse 16 and Pulse16 AE, Dangerous Music Convert-2 into CONVERT-AD+. Of course any other one welcome!

Originally Posted by euggie2000 ➡️

Anubis Premium

Originally Posted by didier.brest ➡️

anubis_mon_mission_1-2_to_3-4_slow.wav
-1.112046 ms, -0.3994 dB (L), -0.3971 dB (R), -51.4818 dBFS (L), -52.2145 dBFS (R)

To be added to the next issue of the list of the results.

Loopback tests requested by forum members: Eventide H8000FW (for validating or invalidating the test from jeamsler), Pacific Microsonics Model One and Model Two, RME M-32 AD Pro --> M-32 DA Pro, RME M-1610 Pro, Prism Dream DA-2 --> AD-2, BlackLion Audio Revolution 2×2, SSL BiG SiX, Prism Sound Dream ADA-128, anything from Qes Lab, JCF, Burl and Linn, iZ RADAR, Avid HD OMNI, Fractal Audio Systems Axe-Fx III, NEVE MBC, Sound Blaster X7, Focusrite ISA 428, Elektron Octatrack MKII , Burl B2 Bomber ADC ---> DAC, dCS, Antelope Audio Amari, Black Lion mods (e.g. Apollo X mods), Lynx Hilo 2, new (2024) MOTU 828, Forssell MDAC-2 ---> MSB Studio ADC as master, Solid State Logic SSL 18, Ferrofish PULSE8 AE, Pulse 16 and Pulse16 AE, Dangerous Music Convert-2 into CONVERT-AD+. Of course any other one welcome!

Originally Posted by paulthesparky ➡️

How often do you normally leave it for on average from update to latest update?

Originally Posted by euggie2000 ➡️

My Anubis was participating before, but there was a request for the one with recent firmware and in the "monitor mission"
So here it is - Anubis Premium, btw from the repair (diff story), at least with one internal card replaced.
https://www.mediafire.com/file/obfpx..._slow.wav/file