Strict Standards: Redefining already defined constructor for class wpdb in /homepages/26/d190919995/htdocs/live/wp-includes/wp-db.php on line 49

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d190919995/htdocs/live/wp-includes/cache.php on line 35

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/26/d190919995/htdocs/live/wp-includes/cache.php on line 400

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 534

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 534

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 534

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 534

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 553

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 649

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 649

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 649

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 649

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/26/d190919995/htdocs/live/wp-includes/classes.php on line 674

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d190919995/htdocs/live/wp-includes/query.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/26/d190919995/htdocs/live/wp-includes/theme.php on line 505

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_query_vars() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_where() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_where() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_join() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_search_join() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_posts_groupby() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_tag_templates() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 123
Micky Green au Nouveau Casino at 4Live
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_add_meta_keywords() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 123

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method BDPRSS2::tag() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 123

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 11

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 20

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 22

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 25

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 11

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 20

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 22

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-includes/functions.php on line 25

Micky Green au Nouveau Casino


Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/26/d190919995/htdocs/live/wp-includes/formatting.php on line 76

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method UltimateTagWarriorActions::ultimate_the_content_filter() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 48

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 642

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 642

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 643

Strict Standards: Non-static method UltimateTagWarriorActions::regExEscape() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-content/plugins/UltimateTagWarrior/ultimate-tag-warrior-actions.php on line 643

4 Décembre 2007, 20h40, Nouveau casino. Emmitouflée dans une doudoune couleur or, Micky Green prend place sur la minuscule scène du club parisien de la rue Oberkampf. Entourée par une formation basse/batterie/clavier, elle entonne White T-Shirt, titre ayant donné son nom à un premier album sorti au mois d’Août 2007. Avec une instru minimaliste, la chanson embarque immediatement l’auditoire dans l’univers de cette jeune australienne de 23 ans. Douceur de la mélodie et délicatesse de la voix forment un préambule élégant à la ligne de basse à venir, destinée à faire bouger les foules. Comme si la patience n’était pas son principale soucis, Micky Green enchaîne rapidement son hit du moment, le sacrement bon : Oh !. Simple et efficace, elle laisse entrevoir par le biais de ce single toutes ses influences allant de la folk à la funk en passant par la soul, le tout avec une fraîcheur presque innocente. Les titres de l’album s’enchaînent sans fioriture et finissent par laisser un gout étrange. Répliques exactes de ceux enregistrés en studio, les morceaux ne crées aucune asperité propre à la scène. Lorsque la nouvelle égérie de Renaud Létang (Feist, Manu Chao,…) annonce la reprise d’un classique funky, revenu au gout du jour grâce à Tarantino, on s’attend alors à être surpris. Si le morceau est toujours aussi efficace, l’attaque vocale de Micky Green se trouve bien en dessous de l’originale et ne parvient pas à combler l’attente d’une salle bourrée à craquer.


Une sortie de scène plus tard, propice à un changement de tenue, Micky Green continue à faire défiler ses titres, chacun ne dépassant que trop rarement le format imposé par une radio. Et c’est peut-être ce que l’on pourrait reprocher : ne pas parvenir à créer des moments moins convenus, des instants plus rares. Même si l’intimisme de certaines chansons (Now It’s gone, Some sun, May Be,…) ou la pop flamboyante d’un titre tel que Soulda, parviennent à entraîner dans un univers musical singulier, la chanteuse semble comme trop apprêtée et surtout bien moins aventureuse musicalement que sa personnalité le laisse présumer. Le live naît presque uniquement lors de respirations entre deux morceaux, laissant entrevoir un sourire complice et une petite folie communicative.
Et c’est peut-être là que nous percevons autre chose qu’une simple présentation, expédiée en tout juste une heure.
C’est peut-être dans ces moments que nous avons réellement l’impression de vivre un temps de scène.



Face aux premiers pas d’une artiste, intialement déstinée lors de ces dates à n’assurer que des premieres parties, l’indulgence est de mise. L’album de Micky Green demeure un très bon premier opus, mélangeant des influences riches et laissant transparaître une voix maitrisée et séduisante. Espérons juste que ce tour de chauffe permettra à la tournée à venir d’être à la hauteur d’un talent indéniable…

________________________
La page MySpace de Micky Green

Quelques vidéos glanées sur le net :

Le clip du titre Oh! :

Oh!, toujours, mais en live sur Europe 2 :

Une interview naze en video :


Aucun commentaire pour “Micky Green au Nouveau Casino”  

  1. No Comments

Ajouter un commentaire



Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method BDPRSS2::updateOldest() should not be called statically in /homepages/26/d190919995/htdocs/live/wp-includes/plugin.php on line 123

Strict Standards: Non-static method BDPRSS2::update() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rssaggregator-db.php on line 381

Deprecated: Function eregi_replace() is deprecated in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rssfeed.php on line 209

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 247

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 250

Strict Standards: Non-static method BDPRSS2::w3cdtf() should not be called statically, assuming $this from incompatible context in /homepages/26/d190919995/htdocs/live/wp-content/plugins/bdprss/bdp-rss-aggregator.php on line 252