But I noticed that if the mp3 is long or is quite heavy with a few MBs, then the bar wouldn’t be of any use. Perhaps maybe after its fully buffered. What is quite sad is that the mp3s that are long are the ones that need the track seeker most. I hope you’ll be able to work around this issue fast and easily.

i have long dj mixes and it would be great to be able to view my other pages without the music stopping.

thought id check.

thanks again.

I’m speculating here because I don’t know exactly how the player works under the hood as I didn’t write it. Unless the files you are playing are being streamed or the player is utilizing progressive downloading(which it does not appear to be) then yes the entire file would need downloaded.

Does the file start playing before the seek bar is available ? I will check this out as well.

Here’s the page where I’ve embedded scripts:
http://www.calvarystockport.co.uk/Media/AudioMessages/tabid/188/Default.aspx

The scripts are obviously working however if you click on a “play” icon and try to seek all it does is restart the track from the start.

Does it require that the entire track is buffered before you can seek? This would normally not be a big deal but on this particular site I’m working on the tracks are 60mins long!! …

Any ideas?

As far as the links go, they are still hosted here, and will be for the foreseeable future.

As far as browser incompatibilities, I was really only targeting firefox at the time. From the looks of things, since these files were pretty standards compliant, issues have gone away as browsers have come up to speed so yay for laziness on my part(I say to myself).

Just one question:
How about making the slider keyboard accessible (Shift + arrow right/left)

Greetings from Bavaria/Germany

Krister Axel, I’m curious at how you were able to “turn off” certain divs on the YMP. It would be great to remove the ymp-yahoo-logo and the ymp-relevance divs altogether without forking the original source. I’ve tried using some CSS hacks, but the results left something to be desired when the divs were still taking up space when rendered in the browser.

I’m thinking that if there was some way to get the YMP script to execute and then run another custom script to modify the DOM tree that was created by the YMP script, I could jump off to a good start. At the moment, I’m having trouble getting my custom script to execute AFTER the YMP script and when I look at the source in the browser, my script always ends up BEFORE the YMP script despite my efforts to explicitly place my scripting code AFTER the YMP script.

Thanks for any divine wisdom that may descend from upon high from the gods of Javascripting. Actually, I’d just greatly appreciate any help/advice anyne has to offer. =)