C Carnaval New member Mar 13, 2024 #1 Hello there, How can I fix this issue : [E2100] Failed to update title (Output 0): error 2100 Thanks in advance.
Hello there, How can I fix this issue : [E2100] Failed to update title (Output 0): error 2100 Thanks in advance.
D djsoft Well-known member Staff member Mar 13, 2024 #2 Does it always happen, or it's only occasional? What RadioBOSS version do you use?
C Carnaval New member Mar 13, 2024 #3 djsoft said: Does it always happen, or it's only occasional? What RadioBOSS version do you use? Click to expand... Thank you for replaying me. It's just for a few days ago. From Monday to now. The versión is 5 .7.0.2
djsoft said: Does it always happen, or it's only occasional? What RadioBOSS version do you use? Click to expand... Thank you for replaying me. It's just for a few days ago. From Monday to now. The versión is 5 .7.0.2
patrick.de-bruyn Active member Mar 13, 2024 #4 experience has shown that it is sufficient to change the metadata encoding to UTF-8 to solve the problem
experience has shown that it is sufficient to change the metadata encoding to UTF-8 to solve the problem
C Carnaval New member Mar 13, 2024 #5 Hello , Patrick.de-bruyn. I did it yesterday and the result was the same. Thanks a lot.
D djsoft Well-known member Staff member Mar 14, 2024 #6 Carnaval said: Thank you for replaying me. It's just for a few days ago. From Monday to now. The versión is 5 .7.0.2 Click to expand... I'm sorry but this version is very old and is no longer supported. Please consider updating to the recent versions.
Carnaval said: Thank you for replaying me. It's just for a few days ago. From Monday to now. The versión is 5 .7.0.2 Click to expand... I'm sorry but this version is very old and is no longer supported. Please consider updating to the recent versions.
D djsoft Well-known member Staff member Mar 14, 2024 #7 patrick.de-bruyn said: experience has shown that it is sufficient to change the metadata encoding to UTF-8 to solve the problem Click to expand... It will work if the server also configured to use UTF8 (pretty common nowadays, but not always).
patrick.de-bruyn said: experience has shown that it is sufficient to change the metadata encoding to UTF-8 to solve the problem Click to expand... It will work if the server also configured to use UTF8 (pretty common nowadays, but not always).