-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live harbor - Bad song title encoding only harbor #411
Comments
You should look at this parameter in
Try setting it to |
I've checked this before.
|
Some solution? I use the newest (compiled) liquidsoap and the problem is still there. Additionally, sometimes in the logs I see something like that (this is not related to the harbor):
|
For polish it looks like you should try: |
Not working - https://i.snag.gy/Hi7xMO.jpg :(
Is coding properly changing here?:
|
Who's the base client? If that client encodes metadata with the wrong encoding before sending it to liquidsoap then there isn't much liquidsoap can do. Also, you logs still show automatic encoding detection from |
SHOUTcast Source DSP v2.3.5 (latest). Now I've checked and it's probably the problem of the base client. So the matter resolved. Sorry! And what about this?:
|
Hmm. Okay, what is your configuration now? |
|
Try adding:
and possibly more of the |
Unfortunately, none of this. I tried from ISO-8859-1 to ISO-8859-10. I even have an English song that has no strange characters in the name, and there is a coding problem with it. Should I send you these MP3 files? |
Ok, sorry now I realize what's going on. Historically, The only option is to force I've just added a change that allows to change
And then:
|
There is no error now. It looks like it works. Thanks! Generally, I have not noticed before that some characters were displaying badly. Currently, they are displayed in the same way, only there is no error in the logs. This error appeared even with no files that had no other characters than English. For example, the file "Bruno Mars - Thats What I Like.mp3". I think it may have something to do with ID3 tags. Although there are also no special signs there. EDIT: |
Glad to hear! |
Also change IcyInfo.rawMetatadata from String to byte[] ICY doesn't specify the character encoding, and there are streams not using UTF-8 (issue:#6753). It seems the default of at least one server is ISO-8859-1 so let's support that as a fallback: savonet/liquidsoap#411 (comment) Also update IcyDecoder to skip strings it doesn't recognise at all instead of decoding invalid characters. The feed from issue:#6753 now decodes accents correctly: EventLogger: ICY: title="D Pai - Le temps de la rentrée", url="null" PiperOrigin-RevId: 285388522
Also change IcyInfo.rawMetatadata from String to byte[] ICY doesn't specify the character encoding, and there are streams not using UTF-8 (issue:#6753). It seems the default of at least one server is ISO-8859-1 so let's support that as a fallback: savonet/liquidsoap#411 (comment) Also update IcyDecoder to skip strings it doesn't recognise at all instead of decoding invalid characters. The feed from issue:#6753 now decodes accents correctly: EventLogger: ICY: title="D Pai - Le temps de la rentrée", url="null" PiperOrigin-RevId: 285388522
Oryginal (broadcasting by SHOUTcast DSP):
start ę€ół.śążźćń end
(Polish characters and Euro symbol)Send to SHOUTcast 2 via input.harbor/output.shoutcast:
start ê�ó³.�¹¿�æñ end
Filename:
start ę€ół.śążźćń end.mp3
Liquidsoap log:
2017/03/23 14:37:56 [input(dot)harbor_5820:3] New metadata chunk ? -- start ê�ó³.�¹¿�æñ end.
If I load this file in the liquidsoap playlist, there is no problem with encoding only if I broadcasts by harbor.
Screens:
The text was updated successfully, but these errors were encountered: