Replies: 1 comment 2 replies
-
Maybe the RPi 2 is "overloaded". Have you tried it with |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Following the examples from the book "The Complete DX7" I noticed three things:
Operating MiniDexed with the rotary encoder and display seems to be much more intuitive (at least to me) than using the original DX7. The book "The Complete DX7" has to use a lot of words to describe which buttons to press in which order and what to see on the display, whereas MiniDexed has a "normal" menu that is pretty much self-explanatory once you know what double-clicking, clicking, and rotating-while-keeping-button-pressed mean. Operation may be a bit slower than with the many keys of the original DX7, but I could imagine that many DX7 users never knew which buttons they had to press in the first place. Which makes our menu a winner! The shortcuts (rotating-while-keeping-button-pressed) are really valuable, I use them all the time. Hats off @rsta2!
Unlike with the original DX7, even changes that affect the level of an operator are immediately audible on MiniDexed. Cool!
Does MiniDexed produce unintended artefacts in the generated sound? I noticed this when doing exercise 25, which goes like this:
You should hear a beating sound. But on a Raspberry Pi 2 with HDMI I also hear something "interrupting" the sound briefly every ~1 second or so.
My hypothesis is that other stuff is running on the same CPU core which can lead to this effect.
TODO: Try to reproduce this with Dexed on a computer, and/or with MiniDexed on other Raspberry Pi/sound output combinations.
Beta Was this translation helpful? Give feedback.
All reactions