foo45 / stagger

Automatically exported from code.google.com/p/stagger
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

Human readable tag transport/editing format #15

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
We need a human readable format for easy editing of tags.

A lightweight format such as RFC822 or JSON would work best.  XML would be 
much too verbose for this purpose.

Original issue reported on code.google.com by Karoly.Lorentey on 21 Jun 2009 at 12:27

GoogleCodeExporter commented 8 years ago
Binary data are a problem -- such data should not be included in the format (it 
would 
easily overwhelm all text data, and would also make it harder to edit the tag 
dump).

Long data of binary frames (>100 bytes) should be elided from the text format.  
However, the user should be able to set such data by specifying the name of the 
file 
containing the desired data.  There must be a user command (separate from the 
one 
producing the editable text format) for saving the contents of a binary field 
in a 
file.

$ stagger --get track01.mp3
TIT2: Foobar baz
APIC[Cover]: "Cover art" <254353 bytes of JPEG data>
$ stagger --set track01.mp3
TIT2: Fred Foo
APIC[Cover]: "Cover art" read("cover.jpg")
^D
$ stagger --save APIC cover2.jpg
$ stagger --save APIC[Cover] cover2.jpg
etc.

Original comment by Karoly.Lorentey on 24 Jun 2009 at 11:38