Centova Technologies Forum

Centova Cast v3 => General discussion => Topic started by: hbox2 on August 11, 2012, 12:22:40 am

Title: autodj character encoding
Post by: hbox2 on August 11, 2012, 12:22:40 am
Hi,

I created account with character encoding ISO-8859-1, but for some reason autodj playlist is setup with UTF-8

<?xml version="1.0" encoding="UTF-8" ?>

And constantly recieve this log

msg:Failure converting filename to metadata Bad UTF-8 code (a6) at position 46

Title: Re: autodj character encoding
Post by: DrO on August 11, 2012, 03:38:56 am
That looks very much like the SHOUTcast sc_trans log output, and if that is what you're using then there are a number of bugs in it's handling of titles which can cause that error to appear (even in valid scenarios).

I do have a newer test build but as i've changed other things, i don't think it's going to be safe to provide you that until Steve, etc have had a chance to test things out with it (if using in a non-managed setup then i probably would provide it).

-daz
Title: Re: autodj character encoding
Post by: Centova - Steve B. on August 11, 2012, 06:06:07 pm
I created account with character encoding ISO-8859-1, but for some reason autodj playlist is setup with UTF-8
This is documented in the manual.  The character encoding setting is used only for interpreting ID3 tags in MP3s, so that Centova Cast can correctly convert them to Unicode.  Everything in Centova Cast uses Unicode as is the standard for modern web applications (and, really, applications in general).

And constantly recieve this log
msg:Failure converting filename to metadata Bad UTF-8 code (a6) at position 46
That's an sc_trans2 log message which is unrelated to your character encoding setting in Centova Cast, and DrO provided some insight above (thanks!) as to what that might mean.
Title: Re: autodj character encoding
Post by: allocazik on November 03, 2014, 06:08:09 am
bonjour j'ai un décalage quand j'encode en direct de 3mm sa peut etre quoi?
Title: Re: autodj character encoding
Post by: winstongel on August 20, 2017, 11:16:56 pm
Most software is not designed to handle 16 bit or 32 bit characters, yet to create a universal character set more than 8 bits was required. Therefore, a special format called UTF-8 was developed to encode these potentially international characters in a format more easily handled by existing programs and libraries. UTF-8 is defined, among other places, in IETF RFC 3629 (updating RFC 2279), so it’s a well-defined standard that can be freely read and used. UTF-8 is a variable-width encoding; characters numbered 0 to 0x7f (127) encode to themselves as a single byte, while characters with larger values are encoded into 2 to 4 (originally 6) bytes of information (depending on their value).

http://net-informations.com/q/faq/encoding.html