I have an odd problem with audio nodes. I have a weekly podcast (a sermon) that runs between 60-70 minutes. Once it's recorded it's uploaded to the website and then audio_import is used to pull it into Drupal. This works fine. But when you look at the audio information, it shows the proper run-time, but the length as 8meg. Playing it with the flash player stops after 8meg, and even downloads are 8meg. If I go into files/audio and look at the file, it is the proper length still (usually about 16meg.)
I have not modified php.ini yet, because it was my understanding this changes uploaded file size, and a download shouldn't matter. I looked through the audio.module file, but nothing caught my eye as to limiting he file served to 8meg.
An example is here: http://www.kewaneefirstchristian.org/content/first-commandment-promise
And the file size from shell:
-rw-rw-r-- 1 xxxxx xxxxx 16627506 2008-07-20 12:16 sservice[07-20-2008-10-25-02].mp3
I'm hosting this on Dreamhost, so changing php.ini is possible, just not the easiest.
Is anyone else having this problem or have any ideas?
Thanks,
Denny Reiter
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | audio-int.patch | 1.63 KB | mfb |
Comments
Comment #1
sleary commentedHaving a possibly related problem, only without error messages, using 5.x-1.4.
Comment #2
fffizzz commentedIm having the same issue.
http://drupal.org/node/288549
Comment #3
mfbI can download the 16MB file via direct link http://www.kewaneefirstchristian.org/sites/default/files/audio/sservice%...
so the problem is happening during the PHP download.
audio module is sending a Content length header based on the file_size info stored in the db:
'Content-Length: '. $node->audio_file['file_size'],
I haven't looked into this any further but it looks like for some reason you have bad data here?
Comment #4
cymru2000 commentedLooks like the same problem as http://drupal.org/node/288549
If you go into the Audio table in you database and change file_size from MEDIUMINT to INT it will work OK. You'll need to update the file sizes in any current uploads though.
MEDIUMINT has a max value which is coincidentally the same as 7.999999 MB in Bytes whereas INT is nearer 2GB. This means that although the whole file is uploaded, SQL is declaring it at 8MB stopping the downloads and streaming short
Comment #5
mfbIn this patch I also fixed the vid and nid fields which should be unsigned normal int not medium int.
Comment #6
fffizzz commentedthat did the trick!
thanks!
Comment #7
reiterd commentedThis fixed it. Thanks very much, I really appreciate it!
Comment #8
mfbComment #9
mfbComment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #11
drewish commentedmarked #277039: data element causes problems on file size as a duplicate
Comment #12
yan commentedI experienced the same problem on a site that was created with Drupal 5 and then upgraded to Drupal 6. All the audios that show as 8mb of size although they're larger, have that problem. When I edit the node and save it again, the size is displayed correctly and the audios play completely. I guess this is due to the fact that in the meantime the MEDIUMINT has been changed to INT.
Since I have many audio nodes with that problem, I'm wondering if there is an easier way than editing and re-saving the nodes. Does somebody know a way to have the audio module "re-scan" the mp3 files?