summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2017-07-21 01:02:32 -0400
committerJack Humbert <jack.humb@gmail.com>2017-07-23 14:59:29 -0400
commitfe113ebad56e758d635724dc35f2a4e26a6985ee (patch)
tree5a56d684acda911c31457008a42b1317b05d4e7a
parent6a3c66776cb10888b24400526241b46deeb051a8 (diff)
start updating audio docs
-rw-r--r--docs/modding_your_keyboard.md3
-rw-r--r--quantum/quantum.c5
2 files changed, 3 insertions, 5 deletions
diff --git a/docs/modding_your_keyboard.md b/docs/modding_your_keyboard.md
index 44e6e6e72a..30ff4f91af 100644
--- a/docs/modding_your_keyboard.md
+++ b/docs/modding_your_keyboard.md
@@ -41,7 +41,8 @@ Wherein we bind predefined songs (from [quantum/audio/song_list.h](https://githu
So now you have something called `tone_plover` for example. How do you make it play the Plover tune, then? If you look further down the keymap, you'll see this:
```
-PLAY_NOTE_ARRAY(tone_plover, false, 0); // Signature is: Song name, repeat, rest style
+PLAY_NOTE_ARRAY(tone_plover, false, LEGATO); // song name, repeat, rest style
+PLAY_SONG(tone_plover); // song name (repeat is false, rest is STACCATO)
```
This is inside one of the macros. So when that macro executes, your keyboard plays that particular chime.
diff --git a/quantum/quantum.c b/quantum/quantum.c
index 31a6fc7133..b76a114186 100644
--- a/quantum/quantum.c
+++ b/quantum/quantum.c
@@ -41,10 +41,7 @@ extern backlight_config_t backlight_config;
#define AG_SWAP_SONG SONG(AG_SWAP_SOUND)
#endif
#ifndef DEFAULT_LAYER_SONGS
- #define DEFAULT_LAYER_SONGS { SONG(QWERTY_SOUND), \
- SONG(COLEMAK_SOUND) \
- SONG(DVORAK_SOUND) \
- }
+ #define DEFAULT_LAYER_SONGS { }
#endif
float goodbye_song[][2] = GOODBYE_SONG;
float ag_norm_song[][2] = AG_NORM_SONG;