[GH-ISSUE #154] Data type mismatch #116

New issue

Closed

opened 2026-02-27 22:08:07 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 22:08:07 +03:00

Owner

Originally created by @ghost on GitHub (Jan 17, 2021).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/154

https://github.com/spotDL/spotify-downloader/issues/1123.
https://github.com/spotDL/spotify-downloader/issues/1119
Recieving number of views/artist name instead of duration.
If you could direct us as to how to remedy this we'd open a PR, else we would like to know how long a fix would take.

[Edit]

it would also be helpful is ytmusicapi provided parsed duration results (not necessary, just a sugession)
https://github.com/spotDL/spotify-downloader/pull/1113

Thank you.

Originally created by @ghost on GitHub (Jan 17, 2021). Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/154 - https://github.com/spotDL/spotify-downloader/issues/1123. - https://github.com/spotDL/spotify-downloader/issues/1119 - Recieving number of views/artist name instead of duration. - If you could direct us as to how to remedy this we'd open a PR, else we would like to know how long a fix would take. [Edit] - it would also be helpful is ytmusicapi provided parsed duration results (not necessary, just a sugession) - https://github.com/spotDL/spotify-downloader/pull/1113 Thank you.

kerem closed this issue

2026-02-27 22:08:08 +03:00

kerem commented

2026-02-27 22:08:08 +03:00

Author

Owner

@sigma67 commented on GitHub (Jan 18, 2021):

First off, are the users on the latest version 0.13.1? That should fix a lot of issues. With the search terms the user mentioned all I could find was a couple videos with no duration (duration field is None). Does your code account for that possibility?

Regarding parsed results, I've thought about it but in my opinion it's not a clear benefit, more of a trade-off.

For users that don't use the parsed data (not at all or just want the string), it's a potential source of errors. It could be mitigated with error handling, but the parsing overhead remains.

@sigma67 commented on GitHub (Jan 18, 2021): First off, are the users on the latest version 0.13.1? That should fix a lot of issues. With the search terms the user mentioned all I could find was a couple videos with no duration (duration field is `None`). Does your code account for that possibility? Regarding parsed results, I've thought about it but in my opinion it's not a clear benefit, more of a trade-off. For users that don't use the parsed data (not at all or just want the string), it's a potential source of errors. It could be mitigated with error handling, but the parsing overhead remains.

kerem commented

2026-02-27 22:08:08 +03:00

Author

Owner

@ghost commented on GitHub (Jan 18, 2021):

About parsing: 👍

About users being on the latest version: probably not. Will notify the guys over at discord.

I'll ping you if the error persist.

Thanks!

@ghost commented on GitHub (Jan 18, 2021): About parsing: 👍 About users being on the latest version: probably not. Will notify the guys over at discord. I'll ping you if the error persist. Thanks!