Postponed (maintainer needs more info)
Project:
Audio
Version:
5.x-2.x-dev
Component:
players
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Oct 2008 at 06:00 UTC
Updated:
14 Nov 2009 at 17:22 UTC
Jump to comment: Most recent file
Comments
Comment #1
bonobo commentedAt a quick glance, this feels like less of an audio issue, and more the role of a helper module --
Or, if I understand this correctly, this could be achieved using Views, and possibly nodequeue -- drop your audio nodes into a queue, use views to display the player, and you're done.
Changing status to minor, marking as needs more info --
If I misiunderstand the need, please post back with additional info, and ideally a screenshot showing what you'd like to achieve.
Comment #2
onejam commentedI think mike15 was asking if using this audio module allows for posting up more than one instance of the player in the same node. If this is what you're after then from what i know, this is not possible but http://drupal.org/project/asset should allow you to post multiple players.
thanks,
Comment #3
mike15 commentedHi Guys,
Let me try to clarify my original question. I have seen a number of examples on the Internet where 1pixelout players are somehow linked to one another therefore preventing a user from playing two songs at the same time. While listening to a song, the user clicks on the second player play button, the first player stops playing automatically so the songs don't overlap with one other.
Here is the example:
http://www.1pixelout.net/code/audio-player-wordpress-plugin/
Hope this helps a bit
Thanks in advance.
Mike
Comment #4
medway commentedI have the same issue.
I took a look at that example and at first thought maybe the linking was due to
the same file being used for both instances. I tried this on my own site but
for the second instance I just get a 'sorry flash not available' error instead.
Btw the current top post on the blog over at the 1pixelout site has a similar
question so perhaps an answer will come there.
I did read this from 2007 though:
"Pierre: are you using my player in WordPress? If you aren’t then you are probably missing the javascript file needed for the “automatic closing” feature. At the moment there isn’t a JavaScript API for the player."
Comment #5
tommy kaneko commentedI also have an issue with this. I've looked at the page here:
http://www.1pixelout.net/code/audio-player-wordpress-plugin/
It seems that the "id" value is the important bit, within the "object" tag. In the page above, the players have unique ID values within the "object" tag. Each time the play button on a player is pressed, a script is run, which stops all players with an ID that is not the id of that particular player.
On the 1pixelout.net page, there is javascript file in the "head" element which works with the object ids which enables 'automatic closing' feature. This is shown below. I can only diagnose - I'm not competent enough to make this work! I hope someone can make a start from this.
Comment #6
felicyco commentedhi
has this been resolved? i have the same exact problem.
thanks
Comment #7
jonk1011 commentedI am having the same problem, too.