hunke.ws

F-Droid repo

2026-10-06T11:16:16-06:00

I have started an F-Droid repo for the Android apps and games I am working on.

Add it to your phone or try some of them out in your browser by clicking on the Play in Browser link next to each listing.

Dan

Multisample Repository

2024-12-01T08:25:09Z

These are multisample packs I have sampled myself using samples recorded from VSTs or physical instruments. Samples are created with Extreme Sample Converter and occasionally edited in Audacity.

These are royalty free samples and you are free to use them as you wish. No credit is needed, all I ask is that you use these to make some music that you enjoy. Samples are in WAV format for easy loading into the Synthstrom Deluge, Dirtywave M8, Sonicware SmplTrek/Lofi-12 XT, etc.

SQ8L

168 presets from the SQ8L VST

Multisamples (Deluge)

3 notes per octave, 5 octaves
Synthstrom Deluge - 44.1kHz/24 bit stereo WAV | 5.63GB uncompressed | MEGA

Middle C (M8, SmplTrek, Lofi-12, etc)

DirtyWave M8 - 44.1kHz/16 bit stereo WAV | 296MB uncompressed | MEGA
Sonicware SmplTrek - 48kHz/16bit stereo WAV | 282MB uncompressed | MEGA
Sonicware Lofi-12 XT - 24kHz/16 bit mono WAV | 71MB uncompressed | MEGA

Roland EP-7

5 instruments (Piano, Electric Piano, Organ, Vibraphone, Strings) from the Roland EP-7 Digital Piano
Each instrument has two versions - naked (no effects) and chorus (with built in chorus effect enabled)
4 notes per octave, 5 octaves
24 bit/44.1kHz WAV | 709MB uncompressed | MEGA

Dan

Raspberry Pi USB MIDI Host

2024-04-23T06:57:17-06:00

This guide exists to help you create a USB MIDI router out of a Raspberry Pi so that you can connect USB MIDI devices together easily. If you add a battery to your Raspberry Pi, like in my Otto project, you can connect these devices anywhere!

The information from this guide largely comes from Fabio Barbon’s guide at Neumatic Studio. I also relied on my previous guide on how to set up an Orange Pi USB MIDI router.

I provide a preconfigured 32 bit Raspberry Pi OS Legacy (Debian Bullseye) image that can be flashed to an 8GB or larger microSD card. This image is created using the step by step instructions below it.

This should work on any Raspberry Pi capable of running 32 bit Raspberry Pi OS.

It has been tested in a Raspberry Pi Zero 2W as well as a Raspberry Pi 2B+

Usage

Insert the flashed microSD card in your Raspberry Pi and turn it on. Give the device ~10-30 seconds to boot (depend on speed of Pi and microSD card) and then plug in your USB MIDI devices. They should be automatically connected to each other and transmitting/receiving data in both directions.

When done, simply remove the power to the Pi. The image is set to read only and there is no risk to corrupting the card as there will be no writes to interrupt.

Rinse and repeat as needed.

Preconfigured image

The latest preconfigured image can be found at my Otto project on github, at this link.

To flash the image, download the latest release zip file and extract the .img file inside. Then write that image to an 8GB or larger microSD card. You can use Rufus or Win32 Disk Imager for Windows, or dd on linux/mac.

Step by step instructions

Download the Raspberry Pi Imager and set up the microSD card. Choose the Legacy 32 Lite image (no desktop is needed). You will need to enter in a username/password, set up wifi, and enable SSH access (on the second tab) in order to finish the setup. Setting the hostname can also be helpful.
Insert the microSD in your Raspberry Pi and boot it up. It will take some time to connect to your WIFI, you can watch your router’s DHCP logs to see what IP it pulls or try to ping the hostname you set until you see a response.
Connect to the Pi using SSH
Perform sudo apt update and sudo apt upgrade to update all current packages
Perform sudo apt install git ruby to install required packages
Create and edit the connection script sudo nano /usr/local/bin/connectall.rb
Paste the following code as the contents:

#!/usr/bin/ruby
#

t = `aconnect -i -l`
ports = []
t.lines.each do |l|
  /client (\d*)\:/=~l
  port = $1
  # we skip empty lines and the "Through" port
  unless $1.nil? || $1 == '0' || /Through/=~l
    ports << port
    #names << name
  end  
end

ports.each do |p1|
  ports.each do |p2|
    unless p1 == p2 # probably not a good idea to connect a port to itself
      system  "aconnect #{p1}:0 #{p2}:0"
    end
  end
end

Save and exit the file (Ctrl+X, then Y, then enter)
Set permissions on the file sudo chmod +x /usr/local/bin/connectall.rb
Connect one or more USB devices to otto and issue connectall.rb to perform a test connection
Check the results with aconnect -l, it should show connected devices
Create a udev rule to run the script when USB devices are connected sudo nano /etc/udev/rules.d/33-midiusb.rules
Paste the following as contents:

ACTION=="add|remove", SUBSYSTEM=="usb", DRIVER=="usb", RUN+="/usr/local/bin/connectall.rb"

Restart the udev service to enable sudo udevadm control --reload and sudo service udev restart
Create a systemd service to configure any attached devices at boot sudo nano /lib/systemd/system/midi.service Paste the following as contents:

[Unit]
Description=Initial USB MIDI connect

[Service]
ExecStart=/usr/local/bin/connectall.rb

[Install]
WantedBy=multi-user.target

Reload the systemctl daemon sudo systemctl daemon-reload
Enable sudo systemctl enable midi.service the service.
Reboot the device sudo reboot

At this point USB MIDI routing should be working as expected, you can plug and unplug devices as desired and they should be automatically connected to each other.

In order to prevent microSD card corruption you will want to set it up as read-only.

Reconnect to the device via SSH
Clone the rpi-readonly git git clone https://gitlab.com/larsfp/rpi-readonly
Enter the directory cd rpi-readonly and run the setup sudo ./setup.sh

When setup is complete your install will be set to read only mode. You are now ready to make music!

If you want to make changes in the future you can turn read/write mode on with the command rw

When done making changes you can turn read-only mode back on using the command ro

Dan

Orange Pi USB MIDI Host

2019-06-29T15:48:35Z

I was looking for a way to get my Deluge to play nice with other USB MIDI devices while waiting for the 3.0 firmware to come out. I happened to have an Orange Pi +2E laying around, knew that this had been done with a Raspberry Pi, and thought “how hard could this be?”

Turns out, not so hard.

Side note: I found this guide by Neuma Studio very helpful and have adapted many parts of it for my own writeup. Credit for the ruby script goes to Morten Johannes Ervik and can be found here.

If you are not familiar with the setup of armbian the getting started guide can be very helpful.

You’ll need the legacy armbian image for Orange Pi or MIDI will not work correctly, for the Orange Pi +2E the link is at the bottom of this page. Write the armbian image to your microSD of choice (4GB is a good size, 2GB is fine if you use overlayroot to set the filesystem read only), connect your your Orange Pi to a TV/keyboard (if using wireless) or to an ethernet cable if you prefer to set it up that way.

Boot the Pi, setup the new root password, new user account, display resolution (if using a TV) and reboot to resize the filesystem. If you are using a 2GB microSD card you will always get a notice on boot that you need to reboot to resize, this will go away when you enable overlayroot.

Set up the wireless and update the system using apt.

nmtui-connect 
apt update
apt upgrade

Install ruby.

apt install ruby

I disable the nodm service as I think it’s a waste of time to load X on something that t will not have a monitor attached.

sudo systemctl disable nodm

I also disable the NetworkManager-wait-online service as it usually adds ~30 seconds or so to the boot time.

sudo systemctl disable NetworkManager-wait-online

You can use the systemd-analyze blame command if you are curious to see what services take how long to start up and remove any more you don’t see any use for.

At this point you should follow the entire section called CONFIGURING AUTOMATIC MIDI CONNECTION at the Neuma Studio blog. Remove or comment out the line in the script that says names << name as that part is not required for this application and will cause errors when you run the script.

I will copy the section (lightly edited due to formatting issues) here just in case something happens to the source page:

issue the command

sudo nano /usr/local/bin/connectall.rb

and copy the following content (all credits for this goes to the author of this page). (to save and exit from nano editor, issue ctrl + O followed by ctrl + X)

#!/usr/bin/ruby
#

t = `aconnect -i -l`
ports = []
t.lines.each do |l|
  /client (\d*)\:/=~l
  port = $1
  # we skip empty lines and the "Through" port
  unless $1.nil? || $1 == '0' || /Through/=~l
    ports << port
    #names << name
  end  
end

ports.each do |p1|
  ports.each do |p2|
    unless p1 == p2 # probably not a good idea to connect a port to itself
      system  "aconnect #{p1}:0 #{p2}:0"
    end
  end
end

issue the command

sudo chmod +x /usr/local/bin/connectall.rb

You can test the auto-connection with command

connectall.rb

and checking results with

aconnect -l

Configure automatic MIDI connection/disconnection on USB device connect/disconnect:

sudo nano /etc/udev/rules.d/33-midiusb.rules

copy the following content and save the file

ACTION=="add|remove", SUBSYSTEM=="usb", DRIVER=="usb", RUN+="/usr/local/bin/connectall.rb"

issue the following commands:

sudo udevadm control --reload
sudo service udev restart

Configure MIDI connection at system boot: sudo nano /lib/systemd/system/midi.service

copy the following content and save the file

[Unit]
Description=Initial USB MIDI connect

[Service]
ExecStart=/usr/local/bin/connectall.rb

[Install]
WantedBy=multi-user.target

issue the following commands:

sudo systemctl daemon-reload
sudo systemctl enable midi.service
sudo systemctl start midi.service

To test automatic connection, you can use the command aconnect -l

If you want to make your system read-only so that you can yank the power any time without worrying about hurting the OS, setup overlayroot.

You need an ODROID XU4 or Allwinner A10, A20 or H3 board with legacy kernel where we added support for overlayfs. Works only on Ubuntu Xenial. 
Login as root and execute:

apt-get install overlayroot
echo 'overlayroot="tmpfs"' >> /etc/overlayroot.conf
reboot
After your system boots up it will always remain as is. If you want to make any permanent changes, you need to run:

overlayroot-chroot

For some reason running overlayroot-chroot does not appear to be enough for me when I want to make further changes. If I want to make changes after overlayroot is enabled I have to run the following commands:

sudo overlayroot-chroot
sudo mount -o remount,rw /dev/mmcblk0p1

Then I edit the file /etc/overlayroot.conf and change the last line from

overlayroot="tmpfs"

overlayroot="disabled"

I am then able to reboot and make any changes I want. When I want the system to go back to read-only I edit /etc/overlayroot.conf and change the last line back to tmpfs.

At this point you should be able to reboot your Orange Pi and have a MIDI host that automatically inter-connects any USB MIDI devices you connect to it. If you setup overlayroot you should be able to power up/off the Orange Pi repeatedly without worrying about filesystem corruption.

Thanks to everyone whose work I stole for this little project.

Dan