10 comments
-
HiFiBerry team What sound card do you use?
-
Hoang viet I am using DAC+ DSP.
-
HiFiBerry team What's the error message?
-
Hoang viet # journalctl -u beocreate2 -f
Oct 14 02:29:03 hifiberry node[673]: (node:673) UnhandledPromiseRejectionWarning: FetchError: request to https://musicdb.hifiberry.com/roomeq/curves failed, reason: getaddrinfo ENOTFOUND musicdb.hifiberry.com
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.<anonymous> (/usr/lib/node_modules/node-fetch/lib/index.js:1461:11)
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.socketErrorListener (_http_client.js:475:9)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorNT (internal/streams/destroy.js:106:8)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorCloseNT (internal/streams/destroy.js:74:3)
Oct 14 02:29:03 hifiberry node[673]: at processTicksAndRejections (internal/process/task_queues.js:82:21)
Oct 14 02:29:03 hifiberry node[673]: UnhandledPromiseRejectionWarning: FetchError: request to https://musicdb.hifiberry.com/roomeq/curves failed, reason: getaddrinfo ENOTFOUND musicdb.hifiberry.com
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.<anonymous> (/usr/lib/node_modules/node-fetch/lib/index.js:1461:11)
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.socketErrorListener (_http_client.js:475:9)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorNT (internal/streams/destroy.js:106:8)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorCloseNT (internal/streams/destroy.js:74:3)
Oct 14 02:29:03 hifiberry node[673]: at processTicksAndRejections (internal/process/task_queues.js:82:21)
Oct 14 02:29:03 hifiberry node[673]: at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
Oct 14 02:29:03 hifiberry node[673]: at processPromiseRejections (internal/process/promises.js:247:11)
Oct 14 02:29:03 hifiberry node[673]: at processTicksAndRejections (internal/process/task_queues.js:96:32)
Oct 14 02:29:03 hifiberry node[673]: (node:673) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52)
Oct 14 02:29:03 hifiberry node[673]: FetchError: request to https://musicdb.hifiberry.com/roomeq/curves failed, reason: getaddrinfo ENOTFOUND musicdb.hifiberry.com
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.<anonymous> (/usr/lib/node_modules/node-fetch/lib/index.js:1461:11)
Oct 14 02:29:03 hifiberry node[673]: at ClientRequest.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.socketErrorListener (_http_client.js:475:9)
Oct 14 02:29:03 hifiberry node[673]: at TLSSocket.emit (events.js:400:28)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorNT (internal/streams/destroy.js:106:8)
Oct 14 02:29:03 hifiberry node[673]: at emitErrorCloseNT (internal/streams/destroy.js:74:3)
Oct 14 02:29:03 hifiberry node[673]: at processTicksAndRejections (internal/process/task_queues.js:82:21)
-
Hoang viet Can you help me, please? A few days ago it worked fine. But after switching to a new set of speakers, I measured the room, but for the past three days, I haven't been able to create a new room compensation.I have tried DAC+ DSP Universal 11 to 15, but none of them worked. I also tried reinstalling HiFiBerryOS, but it didn't help.
-
HiFiBerry team Looks like a server problem. We'll look into this, but it might take a bit.
-
Hoang viet Thank you very much.
-
Hoang viet Excuse me. Could you please tell me when the room compensation feature will be available again ?
-
HiFiBerry team Sorry for the delay. It's should work again now.
-
Hoang viet Oh, it's working again. Thank you very much!