Nice! also, GRR.

Yay! CBR is the way to go, I guess. Last upload was 128kbps CBR and works fine. So there you go.

Worth trying.

Don't use VBR?

Well, using a lower kbps didn't work. Uploaded Week 3 at 128kbps and it didn't make any difference. Seriously, I'm stumped. I've tried 2 different encoding programs. I guess I'll try Audacity next.

In a perfect world...

We'd all be better off if ogg was more popular.

That makes sense. Adobe can afford to have their own proprietary codec or use the Fraunhofer codec.

Haha well I have a Adobe Cloud license now so I've been using Adobe Audition. Which has a pretty badass encoder. It takes just a few seconds for a 5 min song to save.

@trash80 what do you use as your encoder if not Lame?

I wouldn't go low quality. I've found Lame has issues when using Chrome is all I meant. I tend to just use 320kbps CBR, seems to work well.

I'm pretty sure then that it's the quality because I tend to use high VBR or 320kbps. I'll make a low quality version next time around.

128kbps is so 1997 ;p

128 kbps. That's actually what I meant - that Audacity uses Lame. I could have been clearer but I meant that the options when using Lame encoding must be what the difference is.  Perhaps you took something slightly higher, and some of us had some bad internet conditions...? Can't think what else it would be really, as it played for some.

I'm pretty sure that Audacity uses Lame, too, since they say on their site that they can't distribute mp3 encoding software themselves due to software patents (http://audacity.sourceforge.net/help/fa … i=lame-mp3), so I don't think that's really the difference. What kbps do you encode at?

What I did to listen to the song is pause it immediately and click on the progress bar to like 5 seconds in. The song then played just fine.