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 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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

    • By kongondo
      Media Manager
       
      Released 31 March 2016
      https://processwireshop.pw/plugins/media-manager/
      Documentation 
      http://mediamanager.kongondo.com/
      As of 10 May 2019 ProcessWire versions earlier than 3.x are not supported
      *******************************************************   ORIGINAL POST   *******************************************************
      API Example (frontend; will be added to documentation site)
      Accessing and outputting the contents of the MediaManager field(s) in your template is quite simple. The fields are accessed like many other ProcessWire fields. The fields return an array of type MediaManagerArray that need to be looped to output each media within. Assuming you created a field of type MediaManager named 'media', you can loop through it for a given page as shown below.
        @note: Each MediaManager object has the following 5 basic properties:   DATABASE (saved properties) 1. id => pageID of the page where the media lives (hidden in admin and not important to know about) 2. type => integer denoting media type (1=audio; 2=document; 3=image [for variations this will be 3x, where x is the number of the variation of an original image]; 4=video)   RUNTIME 3. typeLabel => user friendly string denoting media type (audio, document, image, video) 4. media => a ProcessWire Image/File Object including all their properties (ext, filesizeStr, height, width, description, tags, filename, basename, etc.) 5. title => title of media (@note: this is the title of the page where the media lives; may or may not be the same as the name of the media file itself). This can be used as a user-friendly name for your media $media = $page->media;// returns a MediaManagerArray. Needs to be looped through foreach ($media as $m) { echo $m->id;// e.g. 1234 (hidden page in /admin/media-manager/media-parent/) echo $m->type;// e.g. 3 (a media of type image) OR 1 (a media of type audio) echo $m->typeLabel;// e.g. 'document' (i.e. type would be 2) echo $m->title;// e.g. 'My Nice Trip' (whose media file could be my-nice-trip.mp4) /* @note: - $m->media returns an object; either a ProcessWire Image (for image media) or File object (for audio, document and video media) - This means you have access to all the properties of that object, e.g. ext, tags, description, url, filename, basename, width, height, modified, created, filesize, filesizeStr, etc as well as associated methods, e.g. size() */ echo $m->media->tags; } // only output images foreach ($media as $m) { if($m->typeLabel =='image') { echo "<img src='" . $m->media->size(100,75)->url . "'><br>"; } } // There's also a toString() method so you can do: echo $page->media; /* All your media will be output wrapped in appropriate HTML tags, i.e.: audio: <audio></audio>; document: <a></a>; image: <img>; video: <video></video>; */  
      *******************************************************   ORIGINAL POST   *******************************************************
       
      The topic of a central media manager feature for ProcessWire has come up several times:
       
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42578
      https://processwire.com/talk/topic/4330-get-image-from-other-pages-via-images-field/?p=42582
      https://processwire.com/talk/topic/425-file-manager/
      https://processwire.com/talk/topic/425-file-manager/?p=13802
      https://processwire.com/talk/topic/425-file-manager/?p=13861
      https://processwire.com/talk/topic/10763-asset-manager-asset-selector/
       
      More recently, regarding my Visual Page Selector module, I have been asked several times why the module does not have an in-built feature to upload images.
       
      There's two camps on the topic of a central media manager: those who like them (especially those coming in to PW from other CMSes) and those who don't like them (primarily because of the chaotic way some CMSes (dis)organise their media management) . I think that we can have our cake and eat it too! If done the right way, closely following the principles of and harnessing the power of ProcessWire, we can have a well-implemented, organised, feature-rich, site-wide media manager.
       
      Introducing Media Manager: (a commercial module)
       
      Alongside a number of modules I am currently working on (both free and commercial), I have been developing  a centralised Media Manager for ProcessWire. Before you cast the first stone, no, this is not going to be a one-large-media-bucket as in other CMS where it gets very messy very quickly . In the backend things are neatly stored away, yes, in pages. However, those are pages you will not see (just like repeater pages). Before anyone has a go at pages, remember a page is not that thing you see on the ProcessWire Tree (that's just its visual representation); A page is a record/row in the database    . For the end-user of Media Manager, all they will see is the 'familiar media bucket' to select their media from. As long as it works efficiently, I don't think they care about the wizardry behind the scenes  . 
       
      The module allows for the comprehensive management of several media types:
      Audio Video Images Documents Each media type will be handled by its own sub-module so the user can pick and install/choose the type of media management they want.
       
      Features include:
      Access controls Centralized uploads of media Bulk management of media: tag, delete, describe, replace, etc. Bulk upload: zip; scan, single Quick upload in page edit mode Usage stats across pages (maybe?) Etc.. Would love to hear your thoughts and any feature suggestions. I think there's enough demand for such a module. If not, please let me know so that I can instead focus on other things  , thanks.
       
      How other CMS do it

       
      The more efficient (PW) way of doing it

    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.
      ![Hanna tag widget]
      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Advanced: define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
×
×
  • Create New...