MultEQ-X?

[elchupoopacabra]

Is it possible to support MultEQ-X files?

I saw your MultEQ-X decoder repo, I used that to extract the measurement files from my .mpx, and I manually created the Toole target curve file. I tried forcing your script to run on the extracted measurements and the target curve, by removing the disabled property on the Start Optimization button and running it after dropping the measurements & curve in to REW & enabling the API server, but: 10:08:08 PM [ERROR] SyntaxError: "undefined" is not valid JSON - program execution has stopped!

[chrisbope]

At the moment, no. MultEQ-X files are encrypted.

[Aroton]

I may look at this a bit this week.

The MQX exporter does work to get all the measurements into REW, so it feels like it wouldn't be that difficult to update the original script to just read the rest of the JSON and still export as ADY. This would however require multi eq x owners to ALSO own the iOS/Android app.

I just don't want to lose my calibrated mic readings.

@chrisbope are you aware of what is actually encrypted in the mqx? The measurements are def base64 of some sort of binary, but considering we can get the measurements out with the other script, that would mean they aren't encrypted.

[Aroton]

And to be clear the reason @elchupoopacabra hack doesn't work, is because the script reads other inputs from the ADY file and those need to be converted to read from MQX. (Assuming they exist in the MQX)

[Aroton]

So, I have a very hacky set of code that converts the MQX to an ADY file and lets you run it through the AudysseyOne script afterwards. I haven't tested it yet to see if it sounds good, doing that here in a minute.

The biggest problem with this approach is the MQX files have more information than the ADY files do. The proper approach would be to input the MQX and output an MQX do you use with multiEQ-x.

I'm also struggling to get the mic calibration found in the MQX config to a usable format, I was hoping it was the same format the measurements use, but that doesn't seem to be the case. I submitted a ticket to see if Audyssey would at least email me a usable format.

[ObsessiveCompulsiveAudiophile]

That's why I didn't write A1 for MQX, they encrypt mic cal file.

Sent from Gmail Mobile

On Tue 18. Jun 2024 at 06:26, Jeremy Bird @.***> wrote:

So, I have a very hacky set of code that converts the MQX to an ADY file and lets you run it through the AudysseyOne script afterwards. I haven't tested it yet to see if it sounds good, doing that here in a minute.

The biggest problem with this approach is the MQX files have more information than the ADY files do. The proper approach would be to input the MQX and output an MQX do you use with multiEQ-x.

I'm also struggling to get the mic calibration found in the MQX config to a usable format, I was hoping it was the same format the measurements use, but that doesn't seem to be the case. I submitted a ticket to see if Audyssey would at least email me a usable format.

— Reply to this email directly, view it on GitHub https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/21#issuecomment-2174893879, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLH4THZU35QZW5SLQX2QPTZH6SFPAVCNFSM6AAAAABIXUT7BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZUHA4TGOBXHE . You are receiving this because you are subscribed to this thread.Message ID: @.*** .com>

[Aroton]

Support got back, they seem very against ever letting those calibration files be in customer hands.

It might still be worth doing an MQX version, but honestly if you can't use the calibrated mics there doesn't seem to be a bunch of value over just using the mobile app. Since you are already doing correct speed of sound correction etc. So, might as well just push the cheaper version.

Only advantage I see is the ability to do more measurements.

[Aroton]

So, one interesting thing.

Support confirmed that the mic corrections are already applied in Multi-EQX. Is there any added benefit to having the calibration file in REW if they are already corrected?

I did some spot checking, and the measurements are identical between Multi-EQX and REW.

[ObsessiveCompulsiveAudiophile]

Maybe they have changed recently but some months back, when I was importing mqx measurements to REW, they had mic cal file kind of differences and this was confirmed by others, too. If that's the case, Evo can run with mqx files, too.

On Tue, 18 Jun 2024 at 22:46, Jeremy Bird @.***> wrote:

So, one interesting thing.

Support confirmed that the mic corrections are already applied in Multi-EQX. Is there any added benefit to having the calibration file in REW if they are already corrected?

I did some spot checking, and the measurements are identical between Multi-EQX and REW.

— Reply to this email directly, view it on GitHub https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/21#issuecomment-2176838374, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLH4THVL5TEOHJGP54JJFDZICFDFAVCNFSM6AAAAABIXUT7BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWHAZTQMZXGQ . You are receiving this because you commented.Message ID: @.*** com>

[Aroton]

For context here is the transcript.

[ObsessiveCompulsiveAudiophile]

They are not exactly saying REW imports will have cal file applied. In the past they didn't.

On Wed, 19 Jun 2024 at 01:49, Jeremy Bird @.***> wrote:

For context here is the transcript.

image.png (view on web) https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/assets/1364243/357acc6e-73bf-40d1-81f0-be19c14ce951

— Reply to this email directly, view it on GitHub https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/21#issuecomment-2177213508, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLH4TDMNLLN7YGHFPIQAM3ZIC2RLAVCNFSM6AAAAABIXUT7BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZXGIYTGNJQHA . You are receiving this because you commented.Message ID: @.*** com>