similar to: Proposal: An extension to rules all others

>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

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

> > That might be true. However, the main problem I see with this is > > that by using only the codecs as the extension you make it > > impossible to filter for audio/video without knowing all the codecs. > > You cannot easily do file searches without specifying all those > > extensions either. > > > Nor can filter audio/video without specifying all of `wma`,

Hi, The standards for audio and video to be used by the Wikimedia projects (like Wikipedia) are Ogg Vorbis and Ogg Theora. The use of Ogg Vorbis files is growing fast. For now the use of video is still very limited. The problem is that an audio and an video file looks the same because of the same file extension. This is very annoying because you do not know what for file it is when you look at

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Sorry, but I think generic extension names are far from perfect. Here are some additional problems to consider: 1) Language. When people talk about file types, they almost never say "dot" at the beginning. They say "MP3 files". For example, "Does that player support MP3 files?" If you have an extension of ".music" this ends up being "Does that

Well, I only recently subscribed to this mailing list and do not know all the history of this extension debate (I passed up on reading the hundreds of messages that seem to have been written about this topic). I just wanted to make one quick point: from my experience, the average user does not know about file formats, only about content (my experience stems from working for ashampoo

Hi all, Xiph aims at developing open-standards media formats. Though xiph.org tells about vorbis/theora/flac/speex, nothing is mentioned about container to use (that is ogg/ogm). I have a few questions Is there a difference between ogg and ogm? I guess its only the extension that is different and everything else is same. Some tools (like ogmtools) are available to create ogm files. What is

Theora and Vorbis both uses same extension .ogg. I know ogg is a container, just like avi. But in my opinion video and audio files should have different extensions (using .ogv can be a nice idea). To a media player it doesn't matter what extension a file uses, but to a human who does a ls in a directory full of media files having different extensions will help a lot. I know one can use file

> Sylvia Pfeiffer said: > > > Now, leading on from here to file extensions is a different issue. I > > would recommend to have different file extensions for each of the > > defined Ogg media mappings ogg-theora, ogg-vorbis and ogg-speex. My > > reasoning is that it makes it easier for programs to map > from the file > > extension to the MIME type and from

> Sylvia Pfeiffer said: > > > Now, leading on from here to file extensions is a different issue. I > > would recommend to have different file extensions for each of the > > defined Ogg media mappings ogg-theora, ogg-vorbis and ogg-speex. My > > reasoning is that it makes it easier for programs to map > from the file > > extension to the MIME type and from

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

Dear David, I hope it's ok to forward your email to the developer lists. I have not seen a comprehensive scheme for MIME type naming and file extensions for ogg files yet - please anybody put me in the picture if there is. However, I have seen application/x-ogg used for ogg-vorbis files, which is according to MIME type registration rules an unregistered and experimental MIME type (see

> All true. But note what the user wants according to these definition: > he wants different icons for audio vs. video. Yes, he doesn't know > the difference between `.mp3` and `.ogg`. But that's precisely why > windows hides the extensions from him by default. If he does know, he > would have disabled this hiding. Exactly. The main reason for different extensions from

Alright folks, here's the solution. 1) Keep extensions to 3 letters for audio & video. Except for special situations where the user might be doing a codec specific name. Since the official extensions are 3 letters, those can always be used on any 8.3 device. 2) introduce a new extension .OGV for ogg container video. With a strong preference for Xiph only codecs. (If you want 3rd

Thanks for the feedback, > I have looked into the patch. It doesn't take into consideration > neither Skeleton, which is used now in pretty much everything encoded > in Ogg (except for single stream Vorbis and Speex files), nor the file > extension for Theora, which is now .ogv. To be honest, I just added Theora because I needed a simple way to multiplex streams. Also, it'd

> Good point. File extensions normally represent groups of related > formats. I don't propose differentiating everything (e.g. standalone > FLAC from Ogg FLAC). I do want as a minimum to tell apart these > categories: > > - Lossy audio: Vorbis, Speex. But speech is useful to distinguish > from music, so making Speex separate is not a bad idea. > - Lossless audio: