See inside an Ogg bitstream.
safe · secure · no server · works offline · fast
…or just start typing at the cursor.
safe · secure · no server · works offline · fast
…or just start typing at the cursor.
Ogg is a page-oriented container: the file is a sequence of
pages, each with the OggS capture pattern, a granule position, a
bitstream serial number, a CRC and a segment table that laces the codec’s
packets back together. Drop the file and OmniViewer’s
PAGES tab lists every page — its sequence number, the
serial and codec of the logical bitstream it belongs to, its
BOS/EOS/continued flags, its granule position, its segment
count and its byte size — so you can see exactly how Vorbis or Opus is
framed on disk. It reads a bounded prefix, so even a huge file lists instantly.
The same drop reads and edits the tags, plays the audio, and reports the codec, channels, sample rate and duration — nothing is uploaded.
It’s one lens on OmniViewer’s OGG Viewer — Tags & Bitstream: drop a file and every tab is one click away. OmniViewer opens every file format, entirely in your browser — no upload, no server.
No. OmniViewer is a static page with no server-side processing: your Ogg file is read directly by your browser and never leaves your computer. Even the re-tag download is assembled locally, from byte slices of your original file.
Ogg is a container format, not a codec. The file is a sequence of pages — each with the "OggS" capture pattern, a granule position (a codec-defined timestamp), a bitstream serial number, a CRC and a segment table — and those pages lace the codec’s packets back together. The codec inside is usually Vorbis or Opus, but can be FLAC, Speex or Theora (video). One file can multiplex several logical bitstreams, each with its own serial number.
They are all the same Ogg container. Historically .ogg meant Ogg Vorbis; .oga is Ogg audio generally; .opus is the conventional extension for Ogg Opus. OmniViewer detects the container from the file’s OggS magic and the codec from its first packet, so it opens all three the same way regardless of the extension.
Yes — that is the point. The VorbisComment/OpusTags metadata lives in a small comment header at the front of the stream. OmniViewer rebuilds just those header pages with your edits and copies every audio page byte-for-byte, so the audio is never touched and loses no quality. The header is padded to keep its page count identical, which is what lets the downstream pages be copied unchanged and makes re-tagging instant even on a multi-gigabyte file.
Open the METADATA tab. It lists every VorbisComment/OpusTags field — TITLE, ARTIST, ALBUM, DATE, GENRE and any custom key — as an editable KEY=value row. Change what you want, add or remove tags, and click "Download re-tagged copy". Editing is available for single-stream Vorbis and Opus files; multiplexed files (e.g. Ogg Theora with an audio track) are read-only for now.
Effectively unlimited. The codec headers and the metadata sit in the first pages, and the duration comes from the granule position of the last page — so opening the file, reading its tags and stats, and even re-tagging it cost a handful of small reads at any size. The audio body is only touched by the browser’s player, which streams it.
It is Ogg’s per-page timestamp: the number of samples (for Opus, always at 48 kHz, minus the pre-skip) decodable by the end of that page. OmniViewer reads the last page’s granule position to compute the total duration without decoding the audio, and shows every page’s granule in the PAGES tab.