Mureka AI Describe Song (Official Edition):
This legacy BizyAirPlus node sends a song to Mureka’s official speech-to-text endpoint and returns the text provided by the service. It lets you bring a song into a text-based workflow, where you can review or reuse the returned content. Its bundled display name is “Mureka AI Describe Song (Official Edition),” but the supplied source does not establish what wording or level of detail the service will return. This documentation describes the node in the official bizytrd 0.1.8 bundled registry; the current remote registry uses the different node ID BizyTRD_Mureka_Official_A2T_API, so a current installation may show that newer node instead. The node interface was verified, but a paid Mureka request was not executed, and remote service availability is not confirmed.
Mureka AI Describe Song (Official Edition) Input Parameters:
audios
Required AUDIO input for the song you want processed. Connect one compatible audio output to this socket; the bundled definition permits one audio input, and the node rejects a missing one before attempting a service request. The interface tooltip describes the source as a song URL and names MP3 and M4A as supported formats, while the verified socket itself is typed AUDIO: in the workflow, connect audio rather than typing a URL into a text field. The node prepares the connected audio for upload and sends its resulting URL in the request’s audio_urls field. Minimum: one connected audio input. Maximum: one input slot. Default: none.
api_config
Optional BIZYAIR_OPENAPI_CONFIG connection for overriding the API base URL and API key for this request. You can leave it disconnected to use the configured service settings. When connected, a nonempty api_key in the supplied configuration replaces the configured key, and a nonempty base_url changes where the request is sent. If you supply a different or unparseable host without an explicit key, the node clears the inherited key to avoid sending it to that host; that configuration may then fail authentication. This setting changes the request destination or credentials, not the requested song-processing task. Minimum/maximum: not applicable to this connection. Default: no per-request override.
skip_error
Optional BOOLEAN setting that controls what happens if task creation, waiting, or output retrieval raises an error. Its default is false: the node raises an error and the workflow stops at that point. Set it to true to let the workflow continue with the error message in the result text output instead. This does not turn a failed request into a successful description, and errors during input validation or audio preparation can occur before this error-handling path. Options: false or true. Default: false.
Mureka AI Describe Song (Official Edition) Output Parameters:
result
STRING containing the text returned from the service. If the service supplies multiple text items, the node joins them with line breaks; if it supplies no text items, this output is an empty string. When skip_error is enabled and a handled request error occurs, this output contains an error message instead of song-related text. Check its contents before using it as a caption, prompt, or other creative input.
request_id
STRING containing the task’s request ID after task creation succeeds. Keep it alongside the result when you need to identify which request produced a particular response or investigate a failure. It can be an empty string if the failure happened before the node received a task ID.
Mureka AI Describe Song (Official Edition) Usage Tips:
- Connect one
AUDIOsource toaudios. The interface names MP3 and M4A as supported source formats, but the workflow socket requires audio, not a manually entered URL. - Start with
skip_errorset tofalseso a failed request is visible while you configure the workflow. Set it totrueonly when downstream steps can recognize and handle an error message inresult. - Leave
api_configdisconnected unless you need a per-request configuration change. When changing to a different service host, provide the intended API key explicitly in that configuration. - Inspect
resultbefore treating it as usable song text: an empty string means no text items were returned, while an error message withskip_errorenabled indicates the request failed. - Retain
request_idwhen available to help correlate a result or reported error with its task. Neither an ID nor a configured endpoint guarantees that the remote service will complete the request.
Mureka AI Describe Song (Official Edition) Common Errors and Solutions:
'audios' requires at least 1 media file
- Explanation: The required
AUDIOsocket did not supply an audio value. The node checks this before preparing an upload. - Solution: Connect a single valid
AUDIOoutput toaudiosand run the workflow again.
code: <code>, request_id: <id>, message: <message>
- Explanation: When an API error contains these fields, the node may display a shortened message in this form. The code and message describe the reported failure; the request ID identifies the associated request when one is available.
- Solution: Read the actual message for the cause, check the audio and configuration, and retain the request ID for troubleshooting. Do not assume every API error will include all three fields.
第三方API节点未找到
- Explanation: This example message in the supplied source means the third-party API node was not found. It may appear in an API error response; the source does not establish which service-side conditions produce it.
- Solution: Check that your installation and service configuration support the endpoint used by this legacy node. Also confirm whether your installation exposes the newer
BizyTRD_Mureka_Official_A2T_APIID instead; changing IDs may require reviewing your saved workflow.
内容安全审查未通过...
- Explanation: The supplied source shows this as an example of a service-side content-safety failure message. The exact response and reason depend on the service.
- Solution: Review the submitted audio against the service’s applicable requirements. Use the returned request ID, if present, when seeking details through your service provider.
原始输出下载地址: <URLs>,请手动下载。错误信息: <message>
- Explanation: If an error occurs after the node has collected original output URLs, the source shows that it can report those addresses with the error. The failed step may involve retrieving an output rather than submitting the song.
- Solution: Check the reported error first. If the addresses are available and you are authorized to access them, try retrieving the outputs manually; otherwise retry the request or investigate the download problem.
Authentication or connection error from the configured service
- Explanation: The node passes its chosen API key and base URL to the request client, but the supplied source does not specify a fixed error string for rejected credentials or unreachable hosts. In particular, a different
api_confighost without its own key does not receive the inherited key. - Solution: Verify the configured host and credentials. If you intentionally override the host, supply the correct
api_keyin the sameapi_configconnection; then use the actual returned message to diagnose any remaining failure.
