similar to: AW: AW: packets and OGG pages

Hello all, my name is Mathias, I'd like to ask about some details of the OGG format because I'm quite new to it. I'd like to write a native .NET library for reading and writing Vorbis comments. It's going to be open-sourced as soon as it's finished. So here it goes: 1) When packing (Vorbis) packets to OGG pages, does a new packet always begin on a fresh OGG page? Within the

Ralph, thanks for your help. >>Since the length of the precedent identification header is fixed, this even is a fixed offset >>into the logical ogg stream. >This will work for all the vorbis-only files I've seen (because no one >pads the first packet). You should really implement a proper ogg parser, >but by all means get a hack working first. I will of course use the

hi list, i have the same problem as mentioned here: http://forums.digium.com/viewtopic.php?t=2678&view=next&sid=bd94cefd823b23156c5748843febb3ab my asterisk version is 1.2.12.1 any ideas? ___________________________________________________________ Der fr?he Vogel f?ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

OK, I've found the answer for one of my previous question myself in the meantime. The comment header can of course be split over more than 1 ogg page since the comment header can be greater than 64K. It also seems to be possible that both comment AND setup headers are placed on a single ogg page only (as stated in the Voribs specs). Due to the fact that the first audio packet also begins on

hello, I have a problem with an unsuitable font in the windows menus/dialogs with the above versions of wine (dont think this depends much on the versions, though. Have not tried other versions so far.) when using debian sarge. The font seems to look a bit ugly, usually destroys partly the menu/dialog structures, and, most important, has no German umlaut's (the diphtongs ae, oe, ue and

Thanks for your replys. >packets don't always begin at the >start of a page OK, since I only want to read / write the Vorbis comments, I can limit it to the Vorbis header packets. http://xiph.org/vorbis/doc/Vorbis_I_spec.html stats that the comment header always begins on the second ogg page. Since the length of the precedent identification header is fixed, this even is a fixed offset

Hello Versions 10,11,12 and X3 aren't working yet. The only one who works (nearly clean) is Version 9. But you need some additional native dlls and wine until version 0.9.22. Version 0.9.23 - 25 have a strong regression. Roland ----- Urspr?ngliche Mail ---- Von: "news@swwwk.com" <news@swwwk.com> An: wine-users@winehq.org Gesendet: Dienstag, den 14. November 2006, 07:15:16

>That would be great! We always need help improving our documentation. OK. I'm going to start writing this lib now, and as soon as it works well I'm going to write specs about how to tag vorbis files. I'll let you know then. Maybe I have to ask you some further questions during development. Let's see. Thank you so far, Mathias

Hello, I'm Rene living in Germany. I have a problem when I use syslinux versions greater than 3.xx for booting DOS (over dos.bss) and DSL-linux from a hard disk. (I've tried version 3.11 and the newest 3.36). The problem occurred after booting DOS - I can not access to the ordinary 3.5'-floppy drive (e.g. the command "dir a:" fails after a while). DOS not even notices

Hi there, my name is Sebastian Dziallas and I would like to contribute to the CentOS Wiki. I thought a bit about what I could do and I think I would like to help translating the wiki in other languages. I speak English, German and also French. My UserName is - what a surprise - SebastianDziallas. On the HowToContribute-Page you said that I should know where to put the articles. As you

Hello together! I've found a couple of bugs with current compiz git, most of them related to the use of KDE and wanted to let you know. 1. kde-window-decorator crashes every now and then. This seems to be especially often when starting kaffeine media player, but not exclusively. I've attached a backtrace, though I don't know if it is useful in this form... 2. Resizing a

Hi there Managed to get Xen up and running, also to get a 1394 controller to be hidden from dom0 to domU. I run an lvm in raid5 in domU as a fileserver. when I copy data to the raid, I get *hundreds* of these error messages: (XEN) APIC error on CPU0: 02(02) my system is: PC-Chips 848A with AMD Geode NX1750 2 G Ram Raid 1 with md0 that holds Dom0 Raid 1 with md1, that holds lvm for domUs All

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I thought I would separate this out into a separate mail since it's not comment specific stuff -- There seem to be a couple of inconcistanies in the Ogg spec as regards to lacing values: *) "The raw packet is logicaly divided into [n] 255 byte segments and a last fractional segment of < 255 bytes." However, in the wild, I've

we are using samba Version 1.9.18p8 and want to connect WIN-NT 3.5.1 to Samba- supportet Unix-Drives; but for any reason the password for this connection is always needed (we did the registry for enableplaintextpassword); the same connection is done well on WIN95 could you figure out, what our problem is??? thank you Klaus-Dieter Wurm (dieter.wurm@de.origini-it.com)

I noticed that, when decoding an ogg vorbis file that was encoded with the xiph library, that the comment header and setup header are encoded on one page. Okay, the vorbis documentation says you can do this, no problem. My question is, the lacing values seem to indicate where the packet boundaries for the two of these are, is this required, or is this just a hint? Further, I'm seeing

Hi ! Playing yetisports 1,2,4 and 5 works with cvs version of wine- Starting yetisports 8,7,6 and 3 fails: yetisports 8 -------------- wine: Unhandled page fault on read access to 0x02af1d74 at address 0x0000:0x00403f0e (thread 0009), starting debugger... WineDbg starting on pid 0x8 First chance exception: page fault on read access to 0x02af1d74 in 32-bit code (0x00403f0e). Register dump:

Hi, I'm currently trying to implement the Ogg specification in pure Java from scratch. (I know, something like that does exist, but that's a rewrite from C, at least that's my impression). I'm a bit confused with the number of lacing values/segments in a page, and the maximum length a page can have. The specification says, that there can be 255 segments in a page, 255 bytes each

Hello, I try to run an windows application with wine the first time, read faqs and howtos, but I do not have a clue where to find a solution for my problem. Maybe you can give me a hint. I installed the windows application "SchildNRW" with jochen@rod:~$ wine .wine/drive_c/SchildBasisSetup.exe That was all right. ( Invoking /usr/lib/wine/wine.bin .wine/drive_c/SchildBasisSetup.exe

Someone could tell me the question about the question about lacing values values of segments. I mean i know what happens about segmentation but reading ogg specs i didn't understand this lines: "We simply add the lacing values for the total size; the last lacing value for a packet is always the value that is less than 255. Note that this encoding both avoids imposing a maximum packet

Hi all, Here are some thoughts on Vorbis framing, which may make it easier to stream Vorbis in real time. The suggested changes also move more audio data closer to the beginning of each page. A note in the Vorbis framing spec suggests a simple 'bandwidth limited' mode whereby important information is placed at the front of each page and the end of each page is discarded. When operating