search for: opustags

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://...

...Version > 00 = Header > 00 00 00 00 00 00 00 00 = Granule Position > a5 73 00 00 = Bit Stream Serial Number > 01 00 00 00 = Page Sequence Numner > 90 a9 36 42 = Checksum > 03 = Page Segments > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > 4f 70 75 73 54 61 67 73 = OpusTags > 0b 00 00 00 = Vendor String Length of 11 > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > 03 00 00 00 = User Comment List Length of 3 > 25 00 00 00 = User Comment #0 String Length of 37 > 45 4e 43 4f 44 45 52 3d 6f 70 75 73 65 6e 63 20 66 72 6f 6d 20 6f 70 75 > 73...

Would it be possible to include a re-export of the malloc, calloc, realloc, and free being used by opus file's implementation of OpusTags handling? This might seem redundant or ridiculous but I'm having difficulty getting the right versions that my compiler allows that's compatible with libopusfile. In the debugger I can see that the memory location that my malloc is returning is different from what libopusfile is returning...

...= Granule Position >> > a5 73 00 00 = Bit Stream Serial Number >> > 01 00 00 00 = Page Sequence Numner >> > 90 a9 36 42 = Checksum >> > 03 = Page Segments >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) >> > 4f 70 75 73 54 61 67 73 = OpusTags >> > 0b 00 00 00 = Vendor String Length of 11 >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" >> > 03 00 00 00 = User Comment List Length of 3 >> > 25 00 00 00 = User Comment #0 String Length of 37 >> > 45 4e 43 4f 44 45 52 3d 6f 70 75 73...

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.

...= Granule Position > > a5 73 00 00 = Bit Stream Serial Number > > 01 00 00 00 = Page Sequence Numner > > 90 a9 36 42 = Checksum > > 03 = Page Segments > > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > > 4f 70 75 73 54 61 67 73 = OpusTags > > 0b 00 00 00 = Vendor String Length of 11 > > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > 03 00 00 00 = User Comment List Length of 3 > > 25 00 00 00 = User Comment #0 String Length of 37 > > 45 4e 43 4f 44 45 52 3d 6f 70 75 73...

...56 PM, Timothy B. Terriberry > <tterribe at xiph.org <mailto:tterribe at xiph.org>> wrote: > > alpha thinktink wrote: > > is returning in tags handlers. So of course when I call > opus_tags_clear > > or any other tags modification routine on an OpusTags struct with > > contents created by my call to malloc it throws an exception. > > Yes, this doesn't work in Windows (it works everywhere else). You can't > use malloc/free across module boundaries unless both modules are linked > to the same DLL version of...

...ing more data? 4f 67 67 53 = Oggs 00 = Version 00 = Header 00 00 00 00 00 00 00 00 = Granule Position a5 73 00 00 = Bit Stream Serial Number 01 00 00 00 = Page Sequence Numner 90 a9 36 42 = Checksum 03 = Page Segments ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) 4f 70 75 73 54 61 67 73 = OpusTags 0b 00 00 00 = Vendor String Length of 11 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" 03 00 00 00 = User Comment List Length of 3 25 00 00 00 = User Comment #0 String Length of 37 45 4e 43 4f 44 45 52 3d 6f 70 75 73 65 6e 63 20 66 72 6f 6d 20 6f 70 75 73 2d 74 6f 6f 6c 73 20 30 2e 31...

...= Bit Stream Serial Number > >> > 01 00 00 00 = Page Sequence Numner > >> > 90 a9 36 42 = Checksum > >> > 03 = Page Segments > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > >> > 4f 70 75 73 54 61 67 73 = OpusTags > >> > 0b 00 00 00 = Vendor String Length of 11 > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > >> > 03 00 00 00 = User Comment List Length of 3 > >> > 25 00 00 00 = User Comment #0 String Length of 37 > >...

...00 00 00 00 00 00 00 00 = Granule Position > > a5 73 00 00 = Bit Stream Serial Number > > 01 00 00 00 = Page Sequence Numner > > 90 a9 36 42 = Checksum > > 03 = Page Segments > > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > > 4f 70 75 73 54 61 67 73 = OpusTags > > 0b 00 00 00 = Vendor String Length of 11 > > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > 03 00 00 00 = User Comment List Length of 3 > > 25 00 00 00 = User Comment #0 String Length of 37 > > 45 4e 43 4f 44 45 52 3d 6f 70 75 73 65 6e 63 20 66 72 6...

...t; > a5 73 00 00 = Bit Stream Serial Number > >> > 01 00 00 00 = Page Sequence Numner > >> > 90 a9 36 42 = Checksum > >> > 03 = Page Segments > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > >> > 4f 70 75 73 54 61 67 73 = OpusTags > >> > 0b 00 00 00 = Vendor String Length of 11 > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > >> > 03 00 00 00 = User Comment List Length of 3 > >> > 25 00 00 00 = User Comment #0 String Length of 37 > >> > 45 4e 43 4...

...>> > 01 00 00 00 = Page Sequence Numner > > >> > 90 a9 36 42 = Checksum > > >> > 03 = Page Segments > > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > > >> > 4f 70 75 73 54 61 67 73 = OpusTags > > >> > 0b 00 00 00 = Vendor String Length of 11 > > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > >> > 03 00 00 00 = User Comment List Length of 3 > > >> > 25 00 00 00 = User Comment...

...r > > >> > 01 00 00 00 = Page Sequence Numner > > >> > 90 a9 36 42 = Checksum > > >> > 03 = Page Segments > > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > > >> > 4f 70 75 73 54 61 67 73 = OpusTags > > >> > 0b 00 00 00 = Vendor String Length of 11 > > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > >> > 03 00 00 00 = User Comment List Length of 3 > > >> > 25 00 00 00 = User Comment #0 String Length...

...uence Numner >> > > >> > 90 a9 36 42 = Checksum >> > > >> > 03 = Page Segments >> > > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) >> > > >> > 4f 70 75 73 54 61 67 73 = OpusTags >> > > >> > 0b 00 00 00 = Vendor String Length of 11 >> > > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" >> > > >> > 03 00 00 00 = User Comment List Length of 3 >> > > >&...

...00 00 = Page Sequence Numner > > > >> > 90 a9 36 42 = Checksum > > > >> > 03 = Page Segments > > > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 BYTES) > > > >> > 4f 70 75 73 54 61 67 73 = OpusTags > > > >> > 0b 00 00 00 = Vendor String Length of 11 > > > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > > >> > 03 00 00 00 = User Comment List Length of 3 > > > >> > 25 00 0...

Hi all! Using the code in opus_demo.c I write a c program for encode and decode the audio from one microphone, I can encode and decode raw audio into .opus file, but really is not an opus file because i need to add the "OpusHead" and the "OpusTags". In order that any opus player can play that file. So I only need in my c program how to add this streams to my file an how to create the complete opus file I do not find any information about creating the header and how to store the opus packets that i encode and decode Grettings Toni --...

...; > >> > 90 a9 36 42 = Checksum > > > >> > 03 = Page Segments > > > >> > ff ff fe = Each Segment Size (TOTAL SIZE IS 764 > BYTES) > > > >> > 4f 70 75 73 54 61 67 73 = OpusTags > > > >> > 0b 00 00 00 = Vendor String Length of 11 > > > >> > 6c 69 62 6f 70 75 73 20 31 2e 31 = "libopus 1.1" > > > >> > 03 00 00 00 = User Comment List Length of 3 > >...

...ll! > > > > Using the code in opus_demo.c I write a c program for encode and decode > > the audio from one microphone, I can encode and decode raw audio into > > .opus file, but really is not an opus file because i need to add the > > "OpusHead" and the "OpusTags". In order that any opus player can play > > that file. > > > > So I only need in my c program how to add this streams to my file an how > > to create the complete opus file > > > > I do not find any information about creating the header and how to store &gt...

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

I would like to be able to add/modify tags (like artist, album, title) to opus files. The opusenc utility does a fine job of creating tags when creating opus files, but I would like to be able to modify existing opus files from the command line. vorbiscomment can add tags to existing ogg files, but it doesn't work with opus files. Does anyone have a solution for this? Thanks, Chris