Hi, I am on the last step in a work flow to automate the transciption of audio files into notion via whisper. When i try to test the Whisper transciption function i get the message below. I have also recieved the 401 error message. Any assistance would be appreciated
at null.settle (/tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/axios@1.6.7/node_modules/axios/dist/node/axios.cjs:1967:12)
at IncomingMessage.handleStreamEnd (/tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/axios@1.6.7/node_modules/axios/dist/node/axios.cjs:3066:11)
at IncomingMessage.emit (node:events:529:35)
at null.endReadableNT (node:internal/streams/readable:1368:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Based on the error message you’ve received, it seems like the issue is related to the format of the audio file you’re trying to transcribe using the Whisper transcription function. The error message indicates that the file format you’ve used is not recognized and lists the supported formats: ['flac', 'm4a', 'mp3', 'mp4', 'mpeg', 'mpga', 'oga', 'ogg', 'wav', 'webm'].
To resolve this issue, please ensure that the audio file you’re attempting to transcribe is in one of the supported formats listed in the error message. If your file is not in one of these formats, you may need to convert it to a supported format before attempting to transcribe it again.
Additionally, the 401 error message you mentioned typically indicates an authentication issue. This could mean that there’s a problem with how the authentication token is being passed in your request. Make sure that you’re correctly authenticating your request to the Whisper API by including a valid API key or token as required.
If you continue to experience issues after checking the file format and ensuring proper authentication, it might be helpful to review the specific code you’re using to make the request to the Whisper transcription function. If you’re comfortable sharing that code, I can provide more targeted advice on how to address the problem.
For further assistance, you can also visit Pipedream’s support page for more support options.
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double-check my answers and code! Learn how to build your own.
at null.settle (file:///tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/axios@1.6.7/node_modules/axios/lib/core/settle.js:19:12)
at RedirectableRequest.handleResponse (file:///tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/axios@1.6.7/node_modules/axios/lib/adapters/http.js:537:9)
at RedirectableRequest.emit (node:events:530:35)
at RedirectableRequest.RedirectableRequest._processResponse (/tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/follow-redirects@1.15.5/node_modules/follow-redirects/index.js:398:10)
at ClientRequest.RedirectableRequest._onNativeResponse (/tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/node_modules/.pnpm/follow-redirects@1.15.5/node_modules/follow-redirects/index.js:91:12)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:518:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:693:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
at TLSSocket.socketOnData (node:_http_client:535:22)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at Object.run (file:///tmp/__pdg__/dist/code/515c7421c8307b88b25f1013554e724d8dfff81cfa0849045c8b4e54d96c4f0b/code/actions/create-transcription/create-transcription.mjs:232:24)
at null.executeComponent (/var/task/launch_worker.js:294:22)
at MessagePort.messageHandler (/var/task/launch_worker.js:791:28)