Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Ogg Prak - the .ogm killer. (Read 5815 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Ogg Prak - the .ogm killer.

snipped - http://www.vorbis.nu/forum/viewtopic.php?t=41


<metrom> thanks for the Vorbis 1.0 release. but what's your plan now? what will you work on?
<Vakor> metrom: world domination
<metrom> you have already started that, just give it some time...
<metrom> ogg theora?
<Emmett> Ogg Theora's the 'big push,' but we have some more stuff in the background, as well
<Garf> metrom: catch up sleep for a month, then theora and further developmen on the ogg layer
<Emmett> I think we might actually release Ogg Prak next week, so that's a nice little bonus
<Emmett> Ogg Prak: Because Windows Is Fuckin' Retarded.
<Emmett> Ogg Prak is a launcher for Win32... You assign the .ogg extension to Ogg Prak, and then you configure Prak to say 'Here's my audio player' and 'Here's my video player'
<Emmett> So we can keep the extension .ogg for audio *and* video files, and Prak will sort it out.
<greenskeleton> and it will run seemlessly in the background?
<Emmett> greenskeleton: Yup.
<kare> Yay, kill .ogm.
<Emmett> Ogg Prak is kind of cool, I talked about it with a developer a couple months ago, he showed up last week and said, 'Merry Christmas!' and gave me a completed app.
<Vakor> We talked about doing something like that a year or two back, but at the time decided that it was too utterly pointless to bother with
<Emmett> Okay, I'm going to go tend to my wife
<Emmett> I'll bbl

Ogg Prak - the .ogm killer.

Reply #1
Why does a container format have to have one prefix?

Sure "prak" or whatever the hell it is can sort it, but your eyes can't sort it. What if every file on your drive were .ogg you wouldn't know what the hell anything is

Just seems kinda un-needed.

Emmett may think windows is shit, but I remember when (if he still is) humping mac's, which most files don't even have a prefix but just a header of a certain kind, if you've used Resourceror you'll know what I'm talking about (mac file digging tool).

For nix, this is similarly true, but for non-executable or basic, storage is usually prefixed. I'd prefer a folder full of .ogm and .ogg rather than just .ogg to my eyes in a shell.

Ogg Prak - the .ogm killer.

Reply #2
meff,

I agree with you.  I wondered why Ogg Vorbis files had to be .ogg insead of .ogv, .ovb, or even .vrb.  Especially once Ogg starts seeing more usage as a container for other formats, it's going to be hard to tell them apart.  Is that 15 MB foobar~1.ogg an ogg flac song, a long ogg vorbis stream, or a short ogg theora clip?

Even with something like Ogg Prak, there's still no facility to handle displaying the filetype to users in Explorer.  Unless a shell extension is written that peers into each file and then reports the correct type back to explorer -- which is going to make file displays hella slow.

Ogg Prak - the .ogm killer.

Reply #3
agreed (for the most part)

Ogg Prak - the .ogm killer.

Reply #4
Is there any problem with using .vorbis.ogg, .theora.ogg,...

Even more generic:

.audio.ogg
.video.ogg
...

Just my 2 (euro)Cents

 

Ogg Prak - the .ogm killer.

Reply #5
Quote
Originally posted by ManyFaces
Is there any problem with using .vorbis.ogg, .theora.ogg,...

Even more generic:

.audio.ogg
.video.ogg
...

Just my 2 (euro)Cents


Because users would probably make sure to use the right .--- than some internal prefix, and alot of people would be more willing to cheat this way, ie, naming a movie file as an audio one for advertising purposes..

Just thoughts.

Ogg Prak - the .ogm killer.

Reply #6
Still, in Windows at least, association wise they couldn't be associated with different sets of programs and have different icons and stuff.  I believe that Windows only looks at the extension after the last dot and doesn't handle multiple extensions.

(Or I can be totally wrong and just made my self look like a f-ing moron, either way)

Ogg Prak - the .ogm killer.

Reply #7
Quote
Originally posted by meff


Because users would probably make sure to use the right .--- than some internal prefix, and alot of people would be more willing to cheat this way, ie, naming a movie file as an audio one for advertising purposes..

Just thoughts.


The right extension? If i have an ogg-flac file, .flac.ogg is a true candidate for right extension.

And if people is willing to cheat, they can do it naming an audio file .video.ogg as well as .ogm.

Or I didn't (probably) understood you properly, or i don't get your point...

Ogg Prak - the .ogm killer.

Reply #8
Quote
Originally posted by Ardax
meff,
...
Even with something like Ogg Prak, there's still no facility to handle displaying the filetype to users in Explorer.  Unless a shell extension is written that peers into each file and then reports the correct type back to explorer -- which is going to make file displays hella slow.


There isn't facility to handle the correct type of a .mov file, being it a photo, a video, an audio stream, a game or whatever. Just open it and see.

Ogg Prak - the .ogm killer.

Reply #9
Quote
Originally posted by Ardax
meff,
I agree with you.  I wondered why Ogg Vorbis files had to be .ogg insead of .ogv, .ovb, or even .vrb.  Especially once Ogg starts seeing more usage as a container for other formats, it's going to be hard to tell them apart.  Is that 15 MB foobar~1.ogg an ogg flac song, a long ogg vorbis stream, or a short ogg theora clip?


This has always been the situation with .avi and all other related microsoft formats as well.

I dont even think this is an issue, but then again, I use descriptive filenames.

--
GCP

Ogg Prak - the .ogm killer.

Reply #10
Quote
Originally posted by Garf
This has always been the situation with .avi and all other related microsoft formats as well.

I dont even think this is an issue, but then again, I use descriptive filenames.


Hmm, I hadn't thought of that.  The .avi codecs are so ubiquitous on Windows systems that I forgot all about that.  The only real exception are divx movies, so when I open an .avi that doesn't work, that's the first thing I check.

mpegs are much the same way, as one doesn't know what kind of mpeg file is contained, with the exception of .mp3 of course.

It still seems like a silly thing to do, even if everybody else is doing it. 

This does seem to be the closest thing to "a better way", short of implemeting resource forks into Windows (which is one thing I do dearly love about Macs).

Swag,

I'm pretty sure you're correct on the "last extension" bit with Windows.  It is possible to get different icons on things by writing a shell extension though (see mp3Ext).  I don't know if they can get Explorer to display a different type string.

Ogg Prak - the .ogm killer.

Reply #11
Sounds good,
how about the subtitle and chapter support ?