kixe

Audio MP3 Flash Player

Recommended Posts

Hello community,
based on the freely available flash mp3 player (http://flash-mp3-player.net) I set a module, which creates a field to store mp3-audio files in the backend and an audio player in the frontend.

mp3 files can be added by drag and drop. The audio player is configurable in module settings. (Size, colors, display of buttons, volume control, etc.)

About third party Code

More information
http://flash-mp3-player.net/players/

Code
https://github.com/neolao/mp3-player

License
http://creativecommons.org/licenses/by-sa/3.0/deed.en

Author
The Initial Developer of the Original Code is neolao (neolao@gmail.com).


How to install

download the 2 Files:
http://flash-mp3-player.net/players/maxi/download/
http://flash-mp3-player.net/medias/player_mp3_maxi.swf
http://flash-mp3-player.net/players/multi/download/
http://flash-mp3-player.net/medias/player_mp3_multi.swf

Download from github the module, unzip, copy module and the 2 swf Files in a folder /Audio_MP3/ and add the folder to your /site/modules/ directory.

Click *check for new modules* in ProcessWire Admin Modules screen. Click *install* for the module labeled: "Audio_MP3".

Now you will be on the module config screen. Please make note of the config options and set as you want.


How to use

Add the Audio field to your Template in Setup > Templates.
Add the following code to the template file
to get the title list:

$modules->Audio_MP3->player['title'];
 

to get the player:

$modules->Audio_MP3->player['code'];
 



Create a page using the Template.

Drag and drop mp3 or mp3.zip files in the audio field in the Page-Edit-Area.


How it works

If you store just one File in the Page-Edit-Area the Maxi-Player will be loaded. For 2 or more files the Module will switch to Multi-Player. If you want an alternative title, you can put it in the Description-field of the Audio Field, which is visible after the file upload.


Module Configuration

- width: Forces the video width.
- height: Forces the video height. //only Maxi-Player only one file stored
- volume: The initial volume, between 0 and 200. By default set to 50
- showstop: 1 to show the STOP button.
- showinfo: 1 to show the INFO button.
- showvolume: 1 to show the VOLUME button.
- showloading: 'alway','never','autohide') to show the LOADING bar// By default set to 'alway'
- showinfo: 1 to show the INFO button.
- buttonwidth: The buttons width. By default set to 30.
- volumewidth: The width of the VOLUME button. By default set to 30.
- volumeheight: The height of the VOLUME button. By default set to 10
- loadingcolor: The color of loading bar in hex format without #//default: ffff75
- sliderovercolor: Hover color of the bar in hex format without #
- buttonovercolor: Hover color of buttons in hex format without #

feel free to add more configuration options to the module. More information here:

http://flash-mp3-player.net/players/multi/documentation/
http://flash-mp3-player.net/players/maxi/documentation/

Need some help!

I would like to make the code available via
$page->player['code'];
but I don't know how.

 

README.txt

Audio_MP3.module

  • Like 5

Share this post


Link to post
Share on other sites

 Need some help!

I would like to make the code available via

$page->player['code'];

but I don't know how.

Hi Kixe, sorry not much time, (will look at it later)

//for example: 
wire()->addHookProperty("Page::player", null, "PageHookPlayer");

function PageHookPlayer($param) {
   // your code
   if('code'==$param) {
      // show player ...
}

don't know if you can use it like $page->player['code'], but you can use it like $page->player('code').

<kuckstDuHier>http://processwire.com/api/hooks/</kuckstDuHier>

Share this post


Link to post
Share on other sites

@ horst
Thank you for your help, will try out later. Have still to learn more OOP and the PW's Api.

@ kongondo & horst
Thanks. Had a look at Horst's  audio profile. Well done, looks nice.

I prefer the flash-mp3-player before using Yahoos and Google players, because it is more simple in layout and can be adaptet very individual to customer pages.

Share this post


Link to post
Share on other sites

Like discribed in the helloworld.module of ryan I put the following code to the module:

   public function init() {
        $this->addHookProperty('Page::player', $this, 'render');
    }

    protected function render() {
        $embedCode = "... code ..."  
        $titles = " ... code ..."
        $event->return = array('code'=>$embedCode, 'title'=>$titles);
    }

 

and that in the template

echo $page->player['code'];

 

But still doesn't work. What is wrong here?

Share this post


Link to post
Share on other sites

wow that's great. I'll try to help out when i get more time.

I was trying to turn this one into a plugin:

http://tympanus.net/codrops/2012/12/04/responsive-touch-friendly-audio-player/

it's really nice and html5, but the problem is that html5 audio isn't quite there yet...

so then i ended up using soundmanager2 which is super reliable (and in mass use now on sites like soundcloud) – it's cross platform and does hybrid html5 and flash; Since i'm doing mostly responsive design, doesn't make so much sense for me to do flash only; but i'll look at this module and see if it can be modded for a different player;

one reason why i didn't bother making a module is because it's easy to setup the template to output the desired markup for any given player, but then you also have to remember to include all the scripts and stylesheets and when applicable the flash objects etc,, so i can see a module being a good thing to house everything, and make it easier to re-use in different sites.

it would be good to eventually have audio modules for Soundmanager2, jPlayer, and maybe mediaelement.js; the latter 2 support video;

  • Like 1

Share this post


Link to post
Share on other sites

got it:

public function init() {
   $this->addHookProperty('Page::player', $this, 'render');
}

protected function render($event) {
   $page = $event->object;
   $embedCode = "... code ..." 
   $titles = " ... code ..."
   $event->return = array('code'=>$embedCode, 'title'=>$titles);
}
 
  • Like 1

Share this post


Link to post
Share on other sites

...

I prefer the flash-mp3-player before using Yahoos and Google players, because it is more simple in layout and can be adaptet very individual to customer pages.

Hi Kixe,

the Local Audio Files MP3-DB isn't meant to be a Player. The only reason why there is the YahooPlayer in it, is to show some of the possible functionallity of the DB and because it could be embedded with only one line of code. (lazy me)

The Local Audio Files MP3-DB was created to manage your MP3-Collection and let you import hundreds or thousands songs at once, and read the ID3-Tags to build the DB. It gives you some comprehensive tools to assist in building forms and playlists and that like. But all frontend stuff, including Player embedding has to be done by your self. So if you have some time you may want have a closer look to it and may be than you find it useful to setup your Audio MP3 Flash Player on top of it. (This was my intention when writing it) :)

Anyway, nice to see other audio related work here!

Share this post


Link to post
Share on other sites

update to Version 1.0.2

  • translatable
  • German Language Pack comes with Module
  • more configuration options
  • simplification of color setup
  • optimized Accesibility
  • Like 3

Share this post


Link to post
Share on other sites

Welcome motionmindz,

you have two install options:
1) Go to setup/Modules Manager (if module: 'Modules Manager' is installed) and click 'refresh', then choose from the list 'Flash MP3 Player' and click 'install'.Done.

2) conventional install (choosed by you?)

Check if all the following files exists under the path: site/modules/Audio_MP3/

Audio_MP3.module
player_mp3_maxi.swf
player_mp3_multi.swf

Check if you have file-access to these files?

Go to: admin/modules , click 'Check for New Modules', select from the list (under the headline 'Audio') 'Audio MP3', click install. Done.

Tell me if the problem still exists.

Share this post


Link to post
Share on other sites

hi kixe,

i have problems to get the template-codes to work. 1st i see is that the moduleInfo shows version 101 where it should be 102, isn't it? ---> ah, ok, forget this. got version 1.02 from git, it's not linked on module sites download.

while $page->player['title']; outputs the file-name or description ok, the $page->player['code'] does nothing. I get no errors, only notices for the undefined $titles and $string vars. am i doing anything wrong?

thanks for looking into it,

martin
 

Share this post


Link to post
Share on other sites
On 1/16/2014 at 10:04 AM, martind said:

hi kixe,

i have problems to get the template-codes to work. 1st i see is that the moduleInfo shows version 101 where it should be 102, isn't it? ---> ah, ok, forget this. got version 1.02 from git, it's not linked to https://skinnyexpress.com/phen375-review-and-results on phen375 module sites download.

while $page->player['title']; outputs the file-name or description ok, the $page->player['code'] does nothing. I get no errors, only notices for the undefined $titles and $string vars. am i doing anything wrong?

thanks for looking into it,

martin

Same thing here Martin, is this a bug? Did you find out how to fix this? If so please share. Thanks.

Share this post


Link to post
Share on other sites

This Module was one of the first modules I have written for PW. By myself I didn't use the module since a long time. Now I integrate Audioplayer normally with html5 audio tag and beautify it using the following 2 Javascript Libraries.
http://mediaelementjs.com/
https://github.com/johndyer/mediaelement/
or
https://kolber.github.io/audiojs/

But if you like it, I pushed an update (v1.2.0) to github and the modules directory and tested it under 3.0.x without problems. :)

Please read instructions, create a template file like:

// template file
echo $page->player['code'];
  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Anssi
      A simple module to enable easy navigation between the public and the admin side of the site. After installation a green bar will appear to the upper side of the screen, containing a few navigation elements and displaying the PW version number.
      Heavily inspired by @apeisa's great AdminBar (Thanks!). I needed a bit simpler tool for my projects and as a result, this was made. Available on GitHub .

    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
    • By David Karich
      Thanks to the great Pro module "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use this module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      With this proof of concept I have created a module which adds the feature to copy a repeater item to the clipboard so that you can paste this item to another page with the same repeater field. The module has been developed very rudimentarily so far. It is currently not possible to copy nested items. There is also no check of Min/Max. You can also only copy items that have the same field on different pages. And surely you can solve all this more elegantly with AJAX. But personally I lack the deeper understanding of the repeaters. Also missing on the Javascript side are event triggers for the repeaters, which would make it easier. Like e.g. RepeaterItemInitReady or similar.
      it would be great if @ryan would implement this functionality in the core of RepeaterMatrix. I think he has better ways to implement this. Or what do you think, Ryan?
      Everybody is welcome to work on this module and improve it, if it should not be integrated into the matrix core. Therefore I put it for testing and as download on GitHub: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDublicate
      You can best see the functionality in the screencast: 
       
    • By anderson
      Hi,
      Please take a look at this:
      https://templatemag.com/demo/Good/
      The upper nav bar, including dropdowns like "pages" and "portfolios", what do you call this whole thing? At first I guess it's called "dropdown nav bar", but seems not.
      AND of course, what's the simplest way/module to achieve this in PW?
      Thanks in advance.
    • By Sebi2020
      Hey, I'm new and I created a simple module for tagging pages because I didn't found a module for it (sadly this is not a core feature). This module is licensed under the GPL3 and cames with absolutly no warranty at all. You should test the module before using it in production environments. Currently it's an alpha release. if you like the module or have ideas for improvements feel free to post a comment. Currently this fieldtype is only compatible with the Inputfield I've created to because I haven't found  an Inputfield yet, that returns arrays from a single html input.
      Greetings Sebi2020
      FieldtypeTags.zip.asc
      InputfieldTagify.zip
      InputfieldTagify.zip.asc
      FieldtypeTags.zip