search

ObsessiveCompulsiveAudiophile / AudysseyOne

Audyssey MultEQ calibration optimization with REW API
https://www.youtube.com/watch?v=iU1ZBsru76M
MIT License
54 stars 7 forks source link

Issue - Error Fetching Result: TypeError: Failed #5

Open ianfretwell opened 3 months ago

ianfretwell commented 3 months ago

I have two PC's both more or less identical (same motherboard, CPU, RAM, etc. both connected to the same devices)

On one of them the script works just fine, on the other I get the issue - Error Fetching Result: TypeError: Failed.

I've tried uninstalled, restarted, re-installed REW on both PC's and the issue persists. What/where else do I need to be looking at to work out whats going wrong on the problematic one ?

Thanks

DorianPuscas commented 3 months ago

Hy, try to move the forlder on PC floder like on desktop or downloads, not in cloud , dropbox. Mine worked after i moved it on desktop

DorianPuscas commented 3 months ago

Unpack the zip file and add the measurements

ianfretwell commented 3 months ago

I'm working from a local D:\ drive in both cases - so that's not it.

Not entirely sure what you mean by unpacking the zip....it's imposssible to add the measurements without unpacking the zip (as far as I'm concerned) - so that's already happening too...

But thanks for the suggestions all the same!

Nesstark88 commented 2 months ago

Hi, you may have already found the solution, but I thought I would share what worked for me as I had the same issue today when trying this tool. Navigate to REW preferences, then the API tab, then click on Start Server. That fixed it for me, I also allowed REW to have full Windows firewall access, though I'm not sure if that played a part as well.

ianfretwell commented 2 months ago

Thanks, but no - that's not it. The API is already started (because none of this works without that anyway). Firewall won't be relevant as I (and most probably you too) are running this all from the one machine anyway. I have upgraded from beta 21 to beta 23 of REW - but that's made no difference either.

The error itself suggests that the browser script simply can't see the REW API though - since the exact same thing works fine for me on another machine. So presumably something I've had on the machine previously is somehow affecting it.

Nesstark88 commented 2 months ago

Ah ok, no idea then. You could be right in regard to another app on that specific system or maybe even corrupted files. Well, I hope you find a solution.

ObsessiveCompulsiveAudiophile commented 2 months ago

Could be your firewall.

Sent from Gmail Mobile

On Wed 10. Apr 2024 at 15:03, ianfretwell @.***> wrote:

Thanks, but no - that's not it. The API is already started (because none of this works without that anyway). Firewall won't be relevant as I (and most probably you too) are running this all from the one machine anyway. I have upgraded from beta 21 to beta 23 of REW - but that's made no difference either.

The error itself suggests that the browser script simply can't see the REW API though - since the exact same thing works fine for me on another machine. So presumably something I've had on the machine previously is somehow affecting it.

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

ianfretwell commented 2 months ago

Firewall's don't work 'internally' on a single machine...the traffic isn't moving between any zones that would be considered different.

I am beginning to think it might be the config within Chrome itself though - not had chance to try another browser to confirm that though.

ianfretwell commented 2 months ago

OK - tried another browser (Firefox in this case). Script now starts OK (so this confirms that something in the Chrome settings is stopping it), but immediately ends with:-

14:03:54 [ERROR] Error: Speaker names have different numbers of indices. - program execution has stopped!

But they don't (clearly 8 measurements for each speaker). Plus, this set of measurements - created from the same ady file - works fine on the other machine.

So still stumped. And it's very much a 1st World Problem since I know I can use the other machine anyway.

rajcheval commented 1 month ago

I am running the latest version of REW on my MacBookPro I have tried to use Firefox and Chrome. I downloaded the files to my PC's downloads directory. I am getting this error repeatedly.

I was unable to find a way to start the API Server. I am on REW v5.31.1 I go to preferences and I don't see API tab. So I cannot start the API Server. I am thinking of giving up Mac and Trying to use a windows PC next. Let me know if anyone has a suggestion for me.

rajcheval commented 1 month ago

I installed the beta version for mac and I found api tab and I was able to start the api server.