Skip to content

Instantly share code, notes, and snippets.

View foxtrotcharlie's full-sized avatar

Charles Tanton foxtrotcharlie

View GitHub Profile
@foxtrotcharlie
foxtrotcharlie / musicality-resources.md
Created February 28, 2023 18:40 — forked from IonutBajescu/musicality-resources.md
List of Musicality Resources for Swing Dancers

List of Musicality Resources for Swing Dancers

If you are a swing dancer and ever wanted to delve into musicality, you know how painful it can be. Google and YouTube searches tend to result in only a couple of results, and half of those are little relevant to what you are looking for.

Reading List on Interpreting Swing Music

  • What is this thing called swing? Adaptation of Dan's class “musical structures” for dancers.
  • Swing this Music Comprehensive series of articles on musicality. Covers topics such as Having Swing, Basic Terminology, Identifying and Following the Beat, Recognising the 1, Recognising the Structure and Accent-Based Musicality. This resource will prove immensely useful if you also watch and listen to all the audio and videos files embedded into the articles.
  • Artistry in Rhythm 70
@foxtrotcharlie
foxtrotcharlie / xdebug_log.txt
Created May 28, 2019 17:17
xdebug log file for debugging PHP Storm/xdebug/ddev issue
This file has been truncated, but you can view the full file.
[2629] Log opened at 2019-05-28 12:52:46
[2629] I: Connecting to configured address/port: host.docker.internal:9000.
[2629] I: Connected to client. :-)
[2629] -> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" fileuri="file:///var/www/html/web/index.php" language="PHP" xdebug:language_version="7.2.16-1+0~20190307202415.17+stretch~1.gbpa7be82" protocol_version="1.0" appid="2629" idekey="uid_501"><engine version="2.7.1"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[https://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2019 by Derick Rethans]]></copyright></init>
[2629]
[2629] <- feature_set -i 1 -n show_hidden -v 1
[2629] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="feature_set" transaction_id="1" feature="show_hidden" success="1"></response>
[2629]
[2629] <- feature_set -i 2 -n max_depth -v 1
[2629] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xde