Jump to content
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 11: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 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 Male Extra because it worked for me, 

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 Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...