Re: command line perl tool to create ogg/Vorbis picture comments

Ian Malone <[email protected]> Tue, 17 Apr 2012 23:44:20 +0100
Newsgroups gmane.comp.multimedia.ogg.vorbis.devel
Message-ID <CAL3-7Mq9uWc5Jw2-vTVjqpYwG+5=-DiMV5=VvMiy0Ev=cZKd2A@mail.gmail.com>
On 17 April 2012 12:36, Silvia Pfeiffer <[email protected]> wrote:
> On Tue, Apr 17, 2012 at 8:58 PM, Ian Malone <[email protected]> wrote:


>> Adding linked image handling would need some work and I'd need a bit
>> of feedback on it. Was never particularly taken with that bit of the
>> specification due to security implications for remote links and the
>> fragility of local links, has to be done carefully.
>
> Are you suggesting we have two ways of associating images with
> chapters: URLs and base64 images? If so, we should have two different
> vorbiscomment headers for these.
>

We do have two ways of associating images, this is a consequence of
using a FLAC/ID3V2-like block for the images.
http://wiki.xiph.org/VorbisComment#Linked_images added some
restrictions about what was allowed.
The tool creates the block preamble for track art as set out in
http://wiki.xiph.org/VorbisComment#METADATA_BLOCK_PICTURE

I have to admit I hadn't really been following this chapter
discussion. It looks like straight base64 encoding of the images was
suggested, I think it may be best to try and stick with the FLAC block
format, if only so people writing a Ogg comment handler have a single
type of image container to deal with. You may want to disallow links
altogether in the spec for chapter images, the only other thing that
would be required would be explicitly saying the restriction to one of
each picture type doesn't apply to different chapters.

-- 
imalone
http://ibmalone.blogspot.co.uk