Some sermons won't play, and download is different

All the sermons on our website until 23/6/2013 play correctly, but it suddenly seems that those from 16/6/2013 to 28/4/2013 won't play in Firefox on Ubuntu. Bizarrely, they are all ok on Chrome on Ubuntu!!

(see: streetbaptist.co.uk/teaching/sermon-reco...mon/sermons?start=30 and look at 2013-06-23-am compared to 2013-06-16-am).

The files are all held on an S3 bucket. I've compared the tags on the files using EasyTag (which we set the tags with) and all looks identical. I'm totally confused by what is causing the difference. All the files are tested on the site to ensure they play when they are uploaded, and there have been hundreds of plays on each, but there suddenly seems to bea problem.

Interestingly, and this may be a pointer to the problem, in Firefox when selecting the 'Download' button, those after 23/6/2013 play in a new window using the inbuilt player whilst those from 16/6/013 to 28/4/2013 bring up a download box. In Chrome, the download button causes all to play in a new window using the inbuilt player. There must be a difference in the file attributes that cause this different behaviour, though I can't see any.

It's a wierd problem!! Can you help??

Thanks!

You can look directly in the database if there is some difference how you stored the filename that causes the issue.
However it's more likely that you have changed some encoding settings when you create the mp3 files and that Firefox on Ubuntu has issues with it.

Ok ... checked the DB ... identical. Also checked the file type ... got this output:

alwyn@barry-laptop-3:~/Desktop$ file 2013-06-16-am.mp3
2013-06-16-am.mp3: Audio file with ID3 version 2.4.0, contains: MPEG ADTS, layer III, v1, 128 kbps, 44.1 kHz, Monaural
alwyn@barry-laptop-3:~/Desktop$ file 2013-06-23-am.mp3
2013-06-23-am.mp3: Audio file with ID3 version 2.4.0, contains: MPEG ADTS, layer III, v1, 128 kbps, 44.1 kHz, Monaural
alwyn@barry-laptop-3:~/Desktop$ file -i 2013-06-16-am.mp3
2013-06-16-am.mp3: audio/mpeg; charset=binary
alwyn@barry-laptop-3:~/Desktop$ file -i 2013-06-23-am.mp3
2013-06-23-am.mp3: audio/mpeg; charset=binary

Also rechecked the tags ... identical apart from name and comment, but the names are both the same format (2013-06-16-am v 2013-06-23-am in the tags, and with .mp3 added for the actual file names).

I agree - it must be the way Firefox is reacting to the information presented to it, but where is the difference in information???

Alwyn

What happens if you store the files on your local server instead of S3? Just to rule out an issue from there?