Trackname encoding for metadata publishing

You have a question or need an advice about how to do something? Ask it here!
Post Reply
sokl1
Posts: 29
Joined: 15 Apr 2020 18:20
Trackname encoding for metadata publishing

Post by sokl1 »

Dear support,
Is it possible to get access to url encoding or "cleaning" functions in actions like EXEC_SEND_HTTP_GET/POST ? Especially accented characters are not well supported depending on target systems.
The same problems happens when we use the function EXEC_WRITE_PLAYLISTFILE to export a json or xml file. Functions *[STRING are not interpreted in those contexts ?
Thank you in advance. Best regards
User avatar
radio42
Site Admin
Posts: 7277
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Trackname encoding for metadata publishing

Post by radio42 »

ProppFrexx internally always uses unicode (resp.UTF-8) where any character specific encoding is NOT needed.
This includes the EXEC_WRITE_PLAYLISTFILE function as well as the EXEC_SEND_HTTP_GET/POST methods - all is handled in UTF-8 here!
So I doubt, that any encoding or cleaning function will help you here - the unicode/UTF-8 character format already is multi-byte and supports any special characters in any language!

I assume, that the origin issue already happens when reading the metadata. eg. when reading from the audio file!
Many formats, like WAV RIFF or even MP3s often use/require the Latin1 character encoding. Latin1 however only supports a limited character set, i.e. no special characters accented characters.
However, you have various options (default is strict handling), see the general settings, section Meta Data/WaveForm, e.g. Use UTF-8 for Riff Info (.wav) or Use Broken Latin1 (.mp3).
These options will allow to read the meta data content in a multi-byte format and don't handle the data fully according the specifications - as some tools do write incorrect meta data to the files.

Please try this or send me a sample audio file where you have issues with - after you have tried the above.
sokl1
Posts: 29
Joined: 15 Apr 2020 18:20
Re: Trackname encoding for metadata publishing

Post by sokl1 »

Dear Bernd,
We have seen that the json file resulting from EXEC_WRITE_PLAYLISTFILE begins with a BOM (Byte-order-mark) : EFBBBF. Is it possible to remove it to get a 100% valid json file ?
Here is the command we use :
EXEC_WRITE_PLAYLISTFILE now.json|template.json
Thank you in advance. Best regards
Attachments
Archive.zip
(25.79 KiB) Downloaded 5 times
User avatar
radio42
Site Admin
Posts: 7277
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Trackname encoding for metadata publishing

Post by radio42 »

The EXEC_WRITE_PLAYLISTFILE currently always writes its content in UTF-8 format, which also (by default) always contains the BOM at the beginning of a file, as that function is not tailored to write specifically JSON files, but any. And by default (in .Net) all UTF-8 files does contain a BOM.

However, I'll take a look of what can be done instead...e.g. for certain html or json file extensions I might explicitly omit the BOM.

Post Reply