Skip to content

Some errors with opus format #257

@vvrein

Description

@vvrein

I feel awkward, since times ago it was my request to add opus support 😅
Maybe I'm the only one who uses this format, but nevertheless, I found few issues and hasten to share them. Thank you for this opportunity!

With opus, there is a few issues:

  • track length isn't extracted
  • peaks doesn't work
Image

Request

/api/peaks/main%2Fyoutubedl%2Frandom%2FPhaxe%20-%20Del%20Tango-uRTz7M44fnM.opus

Response

Audio decoding error: `unsupported feature: core (codec):unsupported codec`

Log

18:24:20 [ERROR] [src/server/axum/logger.rs:58] [500 Internal Server Error] GET /api/peaks/main%2Fyoutubedl%2Frandom%2FPhaxe%20-%20Del%20Tango-uRTz7M44fnM.opus
  • debug build doesn't show anything more
  • verbose logging shows the same

For second problem I did a patch-work for myself:

    location @byte {
        return 200 È;
    }

    location /api/peaks/ {
        proxy_buffering off;
        proxy_read_timeout 300;
        proxy_connect_timeout 300;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
        proxy_pass http://127.0.0.1:5050;
        error_page 500 = @byte;
        proxy_intercept_errors on;
    }

It makes nginx send È (ascii symbol with integer code 200) instead of response, if upstream replies with 500 code.
Which makes frontend draw pretty decent and reliable straight line 😆
Image

So, I think something same can be done in backend?

As of first issue - it don't revealed to me...

I'm not so consistent getting in-touch and replying/updating the issue, so please close it if it is no longer needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions