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

trash80 wrote:

Don't use VBR?

Worth trying.

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.

trash80 wrote:

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

In a perfect world...
smile

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

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

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

sinewave wrote:

Loads of people must be using Lame though (i use audacity for example)...

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?

@trash80 I'm using Chrome, too. I think it's a Chrome bug with the internal html5 player at certain bitrates. I was able to reproduce the issue in Chrome with the same file uploaded somewhere else. So I played around with it a bit, switched programs to encode and uploaded it elsewhere after playing with quality and bitrates and I got it working outside of Weekly Beats, so I'm hoping my next track will work.

A couple people in the comments for my song reported this, so I tested it and I get the same thing. But a few other people were able to listen to the full song. When I download the song, it's fine, and I checked the source mp3 I uploaded and there's no problem (for me) for that either. Is there some maximum kpbs setting for the MP3s to work in the player or something? Is it a PC/Mac thing? Other songs play for me fine, what's the deal?

http://weeklybeats.com/#/music/view/irregular-orbit