Software help archive
No Unicode in ID3 tag "Comment" possible (& destroyed)
Support
No Unicode in ID3 tag "Comment" possible (& destroyed)
A read-only archive of old serato.com help threads.
No Unicode in ID3 tag "Comment" possible (& destroyed)
Product
Scratch Live
Version
2.3.0
Hardware
Rane SL1
Computer
PC
OS
Platform
-
pueblofunky
7:44 AM - 23 August, 2011
Product: scratchlive
Version: 2.3.0
Hardware: scratchlive-sl1
Computer: pc
OS Version: win764
---
Hi,
my bug report in 2.3 Public Beta <serato.com has been closed without any notice or reply like "We've logged this bug internally" as for discussion #496797 so I report it again here:
I hope this bug will be fixed in the next release.
Step 1
Import an empty WAV into SSL23065.
Step 2
Double click into the COMMENT field and enter e.g. the character for inch: ″ (U+2033), press enter and Writing tags appear in the status line.
Step 3
Press ALT+DEL for the track. Restart SSL (maybe not required).
Step 4
Import the file again into SSL.
Actual Result
Missing the (Unicode) character (or value is not there).
Marker "1" for Unicode is saved but the saved bytes is only one - the beginning of the BOM header for UTF-16 is only there (xFF) - which is invalid. See following screen shot (hex dump).
Maybe only happens on WAV files.
Also happens in SLL 2.2 and maybe before.
Expected Result
Unicode-Characters should be saved & displayed as for all other frames.
Workaround
?
Version: 2.3.0
Hardware: scratchlive-sl1
Computer: pc
OS Version: win764
---
Hi,
my bug report in 2.3 Public Beta <serato.com has been closed without any notice or reply like "We've logged this bug internally" as for discussion #496797 so I report it again here:
I hope this bug will be fixed in the next release.
Step 1
Import an empty WAV into SSL23065.
Step 2
Double click into the COMMENT field and enter e.g. the character for inch: ″ (U+2033), press enter and Writing tags appear in the status line.
Step 3
Press ALT+DEL for the track. Restart SSL (maybe not required).
Step 4
Import the file again into SSL.
Actual Result
Missing the (Unicode) character (or value is not there).
Marker "1" for Unicode is saved but the saved bytes is only one - the beginning of the BOM header for UTF-16 is only there (xFF) - which is invalid. See following screen shot (hex dump).
Maybe only happens on WAV files.
Also happens in SLL 2.2 and maybe before.
Expected Result
Unicode-Characters should be saved & displayed as for all other frames.
Workaround
?
Zach S
4:51 PM - 23 August, 2011
Your thread was closed by a Serato developer and was logged as a bug.
I'm going to also close this thread as they are aware of the issue.
I'm going to also close this thread as they are aware of the issue.
pueblofunky
10:26 AM - 18 December, 2011
Please can someone invite me for 2.3.3 Beta.
Until 2.3.1 this is NOT fixed.
Thx
Robert
Until 2.3.1 this is NOT fixed.
Thx
Robert
pueblofunky
9:06 PM - 19 December, 2011
The link for 2.3.3 "release notes" (serato.com) shows the 2.3.1 changes.
Correct link should be serato.com
You should fix this on serato.com
Correct link should be serato.com
You should fix this on serato.com