GNOME Bugzilla – Bug 543306
Use oga (Ogg Vorbis, audio) as the default extension extension for adding music to collection
Last modified: 2010-01-22 16:19:48 UTC
the bug has been reported on https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/241973 " Binary package hint: rhythmbox From wikipedia: "The term ‘Ogg’ is commonly used to refer to audio file format Ogg Vorbis, that is, Vorbis-encoded audio in the Ogg container. Previously, the .ogg file extension was used for any content distributed within Ogg, but as of 2007, the Xiph.Org Foundation requests that .ogg be used only for Vorbis due to backwards-compatibility concerns. The Xiph.Org Foundation decided to create a new set of file extensions and media types to describe different types of content such as .oga for audio, .ogv for video (including Theora), and .ogx for applications." - http://en.wikipedia.org/wiki/Ogg Original reference on xiph.org: http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions Most importantly, see this page for different patches related to adding http://wiki.xiph.org/index.php/MIME-Migration See IETF draft: http://www.ietf.org/internet-drafts/draft-goncalves-rfc3534bis-01.txt"
Created attachment 114674 [details] [review] change ogg to oga in the corresponding profile
ok to apply with a change in grecord/doc/ru/gnome-sound-recorder.xml as well <filename>.ogg</filename> -> <filename>.oga</filename> (<filename>.ogg</filename> audio file) or something. We are already in string freeze, so may be this should be delayed. What do you think?
there is still over a month before the string freeze, now changes only have to be correctly announced
(In reply to comment #3) > there is still over a month before the string freeze, now changes only have to > be correctly announced > ah ok! I just learned that very quickly, i was not familliar with that. Fine then, please commit!
I've commited the profile change now: 2008-07-30 Sebastien Bacher <seb128@ubuntu.com> * profiles/gnome-audio-profiles.schemas.in.in:use oga naming rather than ogg for the ogg vorbis audio profile (bug #543306) the gconf values are not translated so that doesn't require a string change notification, I didn't touch change the documentation because I'm not sure who is in charge of this one, the translations are handled by the translations teams and should not be updated by hackers, the C documentation could be updated though but I'll let you decide about that and notify the concerned team if that's required
(In reply to comment #5) > I've commited the profile change now: > > 2008-07-30 Sebastien Bacher <seb128@ubuntu.com> > > * profiles/gnome-audio-profiles.schemas.in.in:use oga naming > rather than ogg for the ogg vorbis audio profile (bug #543306) > > the gconf values are not translated so that doesn't require a string change > notification, I didn't touch change the documentation because I'm not sure who > is in charge of this one, the translations are handled by the translations > teams and should not be updated by hackers, the C documentation could be > updated though but I'll let you decide about that and notify the concerned team > if that's required > Alright, I have updated the C version, I'll send a small notice to the translation team during 2.23.91 release.
I hate to do this, but the Xiph page says "Vorbis and Speex may use .oga, but it is not the prefered [sic] method of distributing these files because of backwards-compatibility issues." I assume this is for the benefit of hardware players.
This isn't such a problem, IMO, until we actually get reports of problems. Then we can start working on a solution. Not our fault the Xiph guys were brain-dead...
Given that the files created by this pipeline don't seem to use any of the features mentioned for the .oga profile (multiplexed streams, skeleton logical bitstream, etc), this seems like a dubious change. We aren't taking advantage of any newer ogg features while getting all the downsides of breaking compatibility. I've run into a number of programs that have trouble with .oga files. Often the changes are small, but it is a pain to track down. I wouldn't be surprised to see problems on hardware players as mentioned in comment 7. The Xiph documented recommends we use .ogg, so why are we using .oga?
This is totally broken. People, me for example, have hardware (ie. music players), that understand .ogg but don't know about .oga. I know how to work around this, but Joe user who copies his music onto a music player from Linux and can't play it will just decide that Linux "sucks" and switch back to Windows or Mac OS. Fail.
I just looked at http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions and it says: "Vorbis and Speex may use .oga, but it is not the prefered method of distributing these files because of backwards-compatibility issues." Please revert the naming of vorbis files to ogg.
I went ahead and reverted back the changes due to popular request. OGA is for freaks! :)
*** Bug 607762 has been marked as a duplicate of this bug. ***
The status of this bug should be "Won't fix" not resolved, as the changes have been reverted.