Amit Ashara wrote:> 1. Since the stream I am working with is a mono channel, what should be > the advised page_segments to use. I am using an embedded system so > keeping the flash and SRAM usage are vital for the development.The number of channels has no impact on this at all.> 2. In the OpusTag the is the libopus a mandatory field?Yes.
Hello Tim Yes, I understand that mono channel has nothing to do with it, but is there any guideline or thumb rule on the value in page_segments to use Regards Amit On Mon, May 9, 2016 at 4:01 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote:> Amit Ashara wrote: > >> 1. Since the stream I am working with is a mono channel, what should be >> the advised page_segments to use. I am using an embedded system so >> keeping the flash and SRAM usage are vital for the development. >> > > The number of channels has no impact on this at all. > > 2. In the OpusTag the is the libopus a mandatory field? >> > > Yes. > > > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160509/be335b5f/attachment-0001.html>
Amit Ashara wrote:> Yes, I understand that mono channel has nothing to do with it, but is > there any guideline or thumb rule on the value in page_segments to useThe factors involved are latency, buffering, and header overhead. For normal use cases, I'd generally recommend around 1 second of audio per page (50 packets @ 20 ms). This is what opus-tools uses by default.
Hello Tim Is there a format document on the OpusTag structure? Search always shows up Vorbis but not Opus. Regards Amit On Mon, May 9, 2016 at 4:01 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote:> Amit Ashara wrote: > >> 1. Since the stream I am working with is a mono channel, what should be >> the advised page_segments to use. I am using an embedded system so >> keeping the flash and SRAM usage are vital for the development. >> > > The number of channels has no impact on this at all. > > 2. In the OpusTag the is the libopus a mandatory field? >> > > Yes. > > > _______________________________________________ > opus mailing list > opus at xiph.org > http://lists.xiph.org/mailman/listinfo/opus >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160510/6fbf1f74/attachment.html>
On 10/05/16 02:37 PM, Amit Ashara wrote:> Is there a format document on the OpusTag structure? Search always shows > up Vorbis but not Opus.The basic format is shared with Vorbis, but the 'magic signature' is different ('OpusTags' instead of '0x05vorbis') and vorbis puts a 0x01 value in an extra byte after the last tag. The OpusTag packet layout is described in https://tools.ietf.org/html/rfc7845.html#section-5.2 Common tag names used for interoperability are described in the Vorbis documentation. See https://www.xiph.org/vorbis/doc/v-comment.html There are more extensive tag lists on some other sites. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: <http://lists.xiph.org/pipermail/opus/attachments/20160510/8fc199fc/attachment.sig>