Hi there,

I am currently having a problem with Audio in creating new audio content. When I submit the file I get this error:

Fatal error: Maximum execution time of 90 seconds exceeded in C:\apache2\htdocs\xxxx\xxxx\index.php on line 12

Now, I have had my php.ini max_execution_time put up to 3600, but I still keep getting this error message, even when apache has been restarted (i've checked using phpinfo() and the setting is correct). Anyone have any ideas???

Anyway, this brings me to my feature request. Instead of having only an option to upload an audio file, could there be drop down in the audio file info section that allows you to have other options such as putting in a URL to a audio file location.

This way a file can be uploaded via a FTP client first, or even hosted on another server. When you click submit, audio could then read the ID3 file over the HTTP connection. Podpress for Wordpress supports this option. I also think, like Podpress, another cool feature would be to include a small flash-based player such as this one (http://www.1pixelout.net/code/audio-player-wordpress-plugin/).

Anyway, thats my $0.02, keep up the good work :)

Comments

drewish’s picture

drewish commented
Status: Needs review » Closed (works as designed)

Fatal error: Maximum execution time of 90 seconds exceeded in C:\apache2\htdocs\xxxx\xxxx\index.php on line 12

You x'ed out the import part of the error message. Where's the error? I know your running Apache2 on Windows but that's about it ;)

Anyway, this brings me to my feature request. Instead of having only an option to upload an audio file, could there be drop down in the audio file info section that allows you to have other options such as putting in a URL to a audio file location.

there's already an existing feature request to do this: http://drupal.org/node/47998 you should look at the audio_import module that's distributed by default with the audio module. it lets you upload audio to your server and then import it into drupal.

When you click submit, audio could then read the ID3 file over the HTTP connection. Podpress for Wordpress supports this option. I also think, like Podpress, another cool feature would be to include a small flash-based player such as this one (http://www.1pixelout.net/code/audio-player-wordpress-plugin/).

podpress uses the same library to read id3 tags as the audio module so i can say with some certainty that it will not read the ID3 tags over the HTTP connnection. the file has to be on the same server as the the plugin (or in our case module). i'll chalk this up to your inability to get a file uploaded but the audio module has a flash player.

so give the audio_import module a try.

tanepiper’s picture

tanepiper commented

Hi there,

Thanks v. much - I found the audio import eventually, and it worked a treat, so i'm pretty happy with the results.

As to the xxx, thats the location of my directory, i'm working on a secret project, and the name of the directory might give it away ;)

At the moment, I feel the audio import feature is enough for me. Thanks.

seek3r’s picture

seek3r commented

When you click submit, audio could then read the ID3 file over the HTTP connection. Podpress for Wordpress supports this option. I also think, like Podpress, another cool feature would be to include a small flash-based player such as this one (http://www.1pixelout.net/code/audio-player-wordpress-plugin/).

podpress uses the same library to read id3 tags as the audio module so i can say with some certainty that it will not read the ID3 tags over the HTTP connnection. the file has to be on the same server as the the plugin (or in our case module). i'll chalk this up to your inability to get a file uploaded but the audio module has a flash player.

Your wrong about this. In podPress I download the first MB or so of the file, and then kill then downloading. I take the part of the file I got and it processes thru the ID3 lib just fine because the id3 tags are all at the start of the mp3

drewish’s picture

drewish commented
Title: Issue with time-outs + feature request » Read ID3 remotely.
Status: Closed (works as designed) » Postponed

id3v2 tags are written to the beginning of the file but id3v1 tags are historically at the end of the file. it maybe a moot point though, i imagine most software is writing id3v2 these days.

it's an interesting feature request that would be cool. i'll have to take a look at podpress again and see what good ideas i can steal ;)

ekendra’s picture

ekendra commented

just subscribing