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 dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often 🙂
      If you find out something useful or cool with Tester make sure to share.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread: