similar to: comment writing in opus / liboggz

On 31 December 2016 at 14:03, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Ian Malone wrote: >> >> out, due to the Opus pre-seek, I think. Fixing that probably requires >> adding an Opus-specific metric to liboggz, since the current default >> linear one doesn't deal with first granule position being set. Thought >> I'd check before getting

On 31 December 2016 at 21:04, Mark Harris <mark.hsj at gmail.com> wrote: > Ian Malone wrote: >>>> Another thought, could vorbiscomment do with having Opus comment support >>>> added? >>> >>> >>> Or make an opuscomment for opus-tools. I'm not sure which is the better >>> approach, though the latter certainly seems like it

Ian Malone wrote: >>> Another thought, could vorbiscomment do with having Opus comment support >>> added? >> >> >> Or make an opuscomment for opus-tools. I'm not sure which is the better >> approach, though the latter certainly seems like it would be less surprising >> for users. > > It'd certainly make sense for it to be included with

Ian Malone wrote: > out, due to the Opus pre-seek, I think. Fixing that probably requires > adding an Opus-specific metric to liboggz, since the current default > linear one doesn't deal with first granule position being set. Thought > I'd check before getting into that whether anyone has looked at this > already? I thought Mark Harris implemented this in

Hello, I am new to using opus but so far I really am loving it. At 16kbps spoken content sounds fabulous. I am using opusenc on 64-bit linux - mostly with flac input. The one thing I can't figure out how to do is add album art. I tried passing the vorbis way of adding a metadata_block_picture comment field to opusenc but it complained about the length. I can't seem to find any

On 14 April 2012 23:40, Ian Malone <ibmalone at gmail.com> wrote: > On 14 April 2012 23:34, Ian Malone <ibmalone at gmail.com> wrote: > >> http://pastebin.com/xXhPyZuQ > >> ./jpegtoblock.pl ?-i DSCN7376.JPG -o flacblock > >> You'll need to add the "METADATA_BLOCK_PICTURE=" which makes it into a >> comment file yourself. >> >

The biggest problem with Vorbis comments are too loose specifications and too little standardisation. Another problem is attribution of involved parties. Currently only the ARTIST field name is supported in software. More standardised field names need to be worked out for organisations and persons involved in the production of the recording. See:

On 02/10/2007, Ian Malone <ibmalone@gmail.com> wrote: > Martin Leese wrote: > > 2. Following on from 1, a tool which inputs an > > Ogg containier with one or more streams, and > > outputs a new Ogg container with the same > > streams plus an Ogg Skeleton stream stuffed > > in front would be very helpful. The tool could > > also

On 02/10/2007, Ian Malone <ibmalone@gmail.com> wrote: > Martin Leese wrote: > > 2. Following on from 1, a tool which inputs an > > Ogg containier with one or more streams, and > > outputs a new Ogg container with the same > > streams plus an Ogg Skeleton stream stuffed > > in front would be very helpful. The tool could > > also

The definition of granule position for an OggDirac elementary stream isn't the same as theora. Index: tools/oggz_tools.c =================================================================== --- tools/oggz_tools.c (revision 3759) +++ tools/oggz_tools.c (working copy) @@ -454,7 +454,15 @@ iframe = granulepos >> granuleshift; pframe = granulepos - (iframe << granuleshift);

Hi, The following changes allow vorbiscomment to read and edit the tags for the first occuring vorbis stream in a muxed (and chained) Ogg bitstream, while retaining the renormalisation. I've tested it on a number of combinations of muxed and chained streams, using the write comments from file option for vorbiscomment to rewrite the comment header and then cmp for binary differences. Seems

A widely used platform doesn't bother to have C99 integer types, so this allows building with it. Reported by sirlemonhead on IRC. Index: src/tools/oggz_tools.c =================================================================== --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9;

So wiki discussion on the new metadata format is ongoing. I'd like to move some things about a bit. MDMF is a discussion of the metadata XML format itself, Metadata gives some background an overview and a few old sample cases. I'm not sure how many people read the wiki talk page so I thought I'd ask here if there were any objections before doing it. What would most likely happen

On 02/05/07, Elaine YueLien <et@ihear.com> wrote: > Hi, > > Several months ago, I asked a question about seeking without a metric. > You can find one answer in this beta release, demonstrated in the > example program multiThreadSeek. There is also an example demuxer, and a > rewriter. Hi Elaine, congratulations :-) that's a nicely designed API you've got there.

> any new fields. However, I cannot even find Dirac in oggz > http://git.xiph.org/?p=liboggz.git;a=blob;f=src/liboggz/oggz_auto.h; There's dirac.[ch] in the tools directory, though I haven't looked at what's in there. Not sure why it's segregated like that.

Hello learned ogg folks, and welcome to 2007. Sadly I am back at work already, and I'd like to seek your advice. We need to store raw RTP packets on disk as they are received from the network. There will be multiple streams of media--at least one audio and one video--that all need to go in the same file. We have decided to use ogg because it is the simplest container format that meets our

Hello to the people reading this list! I am developing tagging support for ogg vorbis in Nero products and we are currently thinking of supporting cover art in ogg files. What is the current state of proposal for cover art in ogg files? Is this http://wiki.xiph.org/index.php/VorbisComment#Cover_art still the latest information? Regards, Goran -------------- next part -------------- An HTML

Hi, A week or two ago Viktor Gal migrated the liboggplay source repo to git.xiph.org, and this week I moved the liboggz and libfishsound repositories. You can see the git repositories available via gitweb at http://git.xiph.org/ I wrote some brief news about the move, and instructions for getting the code: http://blog.kfish.org/2009/04/liboggplay-liboggz-libfishsound.html Thanks to Ralph Giles

Hi, A week or two ago Viktor Gal migrated the liboggplay source repo to git.xiph.org, and this week I moved the liboggz and libfishsound repositories. You can see the git repositories available via gitweb at http://git.xiph.org/ I wrote some brief news about the move, and instructions for getting the code: http://blog.kfish.org/2009/04/liboggplay-liboggz-libfishsound.html Thanks to Ralph Giles

Hi, A week or two ago Viktor Gal migrated the liboggplay source repo to git.xiph.org, and this week I moved the liboggz and libfishsound repositories. You can see the git repositories available via gitweb at http://git.xiph.org/ I wrote some brief news about the move, and instructions for getting the code: http://blog.kfish.org/2009/04/liboggplay-liboggz-libfishsound.html Thanks to Ralph Giles