search for: oggtext

So, I abandoned the hope of using the ogg python bindings to do pure ogg container encoding. I started looking at the libogg in the hopes of retooling the bindings to follow a better object model and it actually looks like the problem is down in libogg, not the bindings. Am I crazy or does libogg rely on libvorbis to return ogg_packets, and that there are no functions that will build an ogg_packet

>Paul E Wrote [snip] >Windows 2000 (although it's the same for all of them) doesn't read in >any mime-type to correctly identify a file, it just uses the extension. [snip] What if, at least for Windows, someone wrote a simple application which when associated with .ogg files and an .ogg file was opened simply read enough of the ogg stream to identify the type of content and then