Overiding mediaelement.js options in code, preprocess?

I've trying to do the above as well.

More specifically, I want to be able to add eventListeners using the success option.

I'm having trouble even hacking the module's js to get it working -- I've added this to mediaelement.module:

     $js_settings['opts']['success'] = "success:function(player, node){console.log(player);}";

No luck so far.

Futhermore, if i add video markup to the site by hand and in my theme's js do the following, it works, so I'm just not sure how to get it going in conjunction with the module.

$('#player1').mediaelementplayer({
  success: function (player, node) {
    console.log(player);
  }
});

what about if you're using mediaelement to render an audio field in a view? any idea how to go about that?

EDIT: looks like using similar code (using the options i needed) works with hook_views_pre_render(), so that was easier than i thought!

 function mymodule_views_pre_render(&$view) {
/*mediaelements js insertion*/
  $settings = array(
    'mediaelement' => array(
      'audio' => array(
        'controls' => TRUE,
        'opts' => array (
          'features' => array('playpause'),
          'startVolume' => 0.5,
          'playpause' => TRUE,
          /* make it just the size of my button */
          'audioWidth' => 24,
          'audioHeight' => 24,
          ),
       ),
    ),
);
drupal_add_js($settings, 'setting');
}

This works perfectly for me:

/* 
Your module's implementation of hook_js_alter
*/
function hook_js_alter(&$javascript) {
  foreach($javascript['settings']['data'] as $k => $v) {
    if(isset($v['mediaelement'])) {
      foreach($v['mediaelement'] as $class => $options) {
       $javascript['settings']['data'][$k]['mediaelement'][$class]['opts']['audioWidth'] = 700; 
      }
    }
  }
}

In my case, the hook_views_pre_render works better since I can limit it per views display with a switch/case statement...for instance, i want it to display the full player on the user's profile but only a little button on a views list with this field as part of the results. If you want to make the changes everywhere, the above works. If you want to get more specific my approach in #4 with an if statement or switch/case would be better...unless the hook_js_alter has a way to specify certain pages and i'm not seeing it.

so i should be able to paste this straight into template.php?

function mediaelement_js_alter(&$javascript) {
  foreach($javascript['settings']['data'] as $k => $v) {
    if(isset($v['mediaelement'])) {
      foreach($v['mediaelement'] as $class => $options) {
       $javascript['settings']['data'][$k]['mediaelement'][$class]['opts']['alwaysShowControls'] = true; 
      }
    }
  }
}

Hook overrides go in a custom module. I almost always end up creating one of these for random snippets like this, but all you need is a mymodule folder in your sites/all/modules folder with a mymodule.info and a mymodule.module file.
the .info file just needs this to get started and you can start putting any hook overrides in the .module file

name = My module
description = Provide random snippets for overriding other functions on my site
core = 6.x
package = Other

wow, that worked, never thought i would have to make my own module.
thanks.

There are two approaches here, javascript altering the setting array and javascript inserting into settings array. Both work okay for changing setting values, however neither of these techniques allow you to add success function callbacks to the mediaelement objects.

I think that using the drupal js settings to pass settings into the mediaelement on init is what's inhibiting 'success' callback functionality:
http://stackoverflow.com/questions/3855436/drupal-add-a-js-function-call...

Could the module maintain it's own JSON settings object somehow such that the field formatters inherit and override this object when initalising and any manual media items use the globals?
Or possibly there is a method in the mediaelement.js which allows you to attach functions to events after init success:? If so, events could just be attached with a custom theme js and the module can continue to use drupal.settings for just mediaelement settings values.

For me the simplest way is to override the modules JS with a copy that has my own options attached:
Go to js2coffee.org if you'd like to use JavaScript.

# When set to enable mediaelement for all audio/video files add it to the page.
Drupal.behaviors.mediaelement = attach: (context, settings) ->
  if settings.mediaelement isnt undefined
    
    $.each settings.mediaelement, (selector, options) ->
      opts = undefined
      
      $(selector, context).once "mediaelement", ->
        options.opts.success = (player, node) ->

          player.addEventListener "playing", ((e) ->
            console.log 'playing'
          ), false  
		  
          player.addEventListener "ended", ((e) ->
            console.log 'ended'
          ), false            
      
        if options.controls
          $(this).mediaelementplayer options.opts
        else
          $(this).mediaelement()
  
  # The global option is seperate from the other selectors as it should be run after any other selectors.
  if settings.mediaelementAll isnt undefined
    $("video,audio", context).once "mediaelement", ->
      $(this).mediaelementplayer()