Metadata code should be able to change automatically or manually.

[GoogleCodeExporter]

What steps will reproduce the problem?
Normally extract and transcode file from one format to another. 

How about the reproducibility (always, sometimes, rarely, ...)?
Sometimes

What is the expected output? What do you see instead?
Metadata should display correctly, whether the code of CUE file is. 

What version of the product are you using? On what operating system?
Version 20141129 (148.1)

Please provide any additional information below.
Metadata code should be able to change automatically, or can be changed 
manually when opening the file. 

Original issue reported on code.google.com by estelle....@gmail.com on 21 Apr 2015 at 1:29

[GoogleCodeExporter]

Preferences -> Metadata -> Edit tags before convert

Original comment by tmkkmac on 21 Apr 2015 at 1:34

[GoogleCodeExporter]

I have this function, but if encode of cue file is not the same encode selected 
within the app, everything will not display correctly. 

Some other apps could do this by changing the code of this file to display 
correctly. Medieval CUE Splitter is one of them doing well on this issue. 

Original comment by estelle....@gmail.com on 21 Apr 2015 at 3:43

[GoogleCodeExporter]

Do you mean character encoding?

Original comment by tmkkmac on 21 Apr 2015 at 3:51

[GoogleCodeExporter]

Yes. Character encoding. 

Original comment by estelle....@gmail.com on 21 Apr 2015 at 3:53

[GoogleCodeExporter]

Preferences -> Generic -> Character encoding of cuesheet

Original comment by tmkkmac on 21 Apr 2015 at 4:04

[GoogleCodeExporter]

OK. I think you may get the real thing. I need to change this setting every 
time I open a file, through preference page. What's worse, I need to restart 
the app to let changes take effect. 

I hope changes can take effect immediately, or I can preview the file before 
open it and change a right encoding option to proceed. 

Original comment by estelle....@gmail.com on 21 Apr 2015 at 4:12

[GoogleCodeExporter]

You don't have to restart to take effect. Open the file again.

Anyway this is not a defect.

Original comment by tmkkmac on 21 Apr 2015 at 4:25

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

So what if adding a function to let user adjust the encode setting before 
showing at the transcode window? It looks like I need to click more if I change 
it from the preference dialog. 

Original comment by estelle....@gmail.com on 21 Apr 2015 at 11:15

[GoogleCodeExporter]

Choosing encoding, then drag & drop .cue to XLD icon... I don't think this is a 
complicated process.

Original comment by tmkkmac on 22 Apr 2015 at 2:58

[GoogleCodeExporter]

But before you say this tip, I didn't realise this. Is this a common sense when 
using OS X? I don't know. 

Original comment by estelle....@gmail.com on 22 Apr 2015 at 3:03

[GoogleCodeExporter]

Do you mean drag & drop? I think it is a common sense.

Even if you didn't know drag & drop,
 - right click .cue and open with -> XLD
 - register XLD as a default application for .cue, then double-clicking .cue icon
will do. These operations are common in other platforms.

Original comment by tmkkmac on 22 Apr 2015 at 3:17

[GoogleCodeExporter]

The global file type association in OS X is more difficult than in Windows. 
Until now I have no idea what should I do to register a file type with certain 
application. 

What you say is, I don't need to restart the app, just drag CUE to XLD, and XLD 
will reload it with changed encoding setting? 

Original comment by estelle....@gmail.com on 22 Apr 2015 at 3:57

[GoogleCodeExporter]

Yes.

Original comment by tmkkmac on 22 Apr 2015 at 3:59

[GoogleCodeExporter]

Of course File -> Open is also OK.

Original comment by tmkkmac on 22 Apr 2015 at 4:00

[GoogleCodeExporter]

OK. I will try it. Thank you for your help until now. 

Original comment by estelle....@gmail.com on 22 Apr 2015 at 4:01