Linked by Adam S on Mon 1st Feb 2010 18:19 UTC

Thread beginning with comment 407358
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Funny, but I can't shake how very similar that statement is to some of the reasons put out by big companies to stay with H.264. How exactly does creating an ogg file greatly increase your work load? It's simple enough to transcode and it's not as though it takes that long. Better yet just save as aiff (you use Garageband) and make an mp3 and an ogg from the same source material.
It’s down to workload, that’s all. Creating an OGGcast increases our workload at the moment, and that’s not an option. If we can do transcoding on the server side, then I’d be happy to include OGG files.
I'm no Ogg fanboy, but how much would that really increase the workload? I did a quick test, starting the download of them the MP3 right after hitting the reply button - and the conversion just finished as I type this. That's maybe 5 minutes effort, including the time necessary to upload and link to the file.
I also find that justification a little odd in light of your vocal opposition to Flash; developers who use Flash for video delivery could give the exact same justification, and it would arguably be more applicable/valid in that context (outputting two versions of the same video increases the workload much more than doing the same with an audio file of comparable length).
Member since:
2008-07-15
Have to agree here. MP3 is a universally readable format, not contesting this. However, if you're going to rant and rave about how we all need to switch to free codecs (a statement with which I also agree) then you need to walk the walk and not just pay lip service to that ideal.