Has anyone ever gotten different samples working?

Pete posted Oct 20 '17, 11:52:

I've gone through the forums and seen tons of posts of people not able to get the other sample packages working. I'm having the same trouble. Nothing seems to be working, can't edit the samplerbox.py file because it says its read only. I don't know why this is still such a big issue for so long.

I'm running a pi3 and a akai lpk25

AlexM posted Oct 20 '17, 13:11:

Hi Pete - going to need a bit more information about your sample packages to help work out where the problem lies. eg samplerate, bitdepth, are you naming your files correctly OR are you using a definition.txt file to define your samples, are you using a USB stick?

Regarding samplerbox.py you must re-mount the filesystem as read-write:

mount -o remount,rw /

and then you should be able to edit and save:

nano SamplerBox/samplerbox.py
Glenn posted Oct 20 '17, 18:19:

I have downloaded all of the instruments on the page: http://www.samplerbox.org/instruments
and gotten them all to work. As I recall, some of them worked right away, and some of them I had to mess with the definition.txt file.

To see what's going on, I logged in to a console (ssh) and killed the samplerbox process (as it is automatically started when the system boots up)
Then I cd into the Samplerbox directory and run ./samplerbox.sh to start it up again, but this time error messages are displayed in the console.
It will show you what instrument is being loaded and if it is successfully loaded. when you press the "change preset" button, you will see the next instrument name and message about loading it.

Pete posted Oct 20 '17, 21:14:

Alex - I'm just running the default Mellotron flute and Yamaha Piano from the downloads page and putting them on usb in folders names "1 Flute" and "2 Piano". I haven't edited the def txt. so it still reads " *_%notename.wav "
Do I need to change that?

Gleen- What did the dir path look like on your USB? And what did you have to edit in the definition.txt?

Pete posted Oct 21 '17, 00:08:

Alright, I've got it to play the Mellotron Flute sounds by using a different USB and renaming the flute file "0 Flute", but I still can't change to any other sounds?

I'm using the akai lpk25, which they use in the demos, so I'm wondering if it's because it doesnt have dedicated buttons for +/- sounds, just 4 different keys to switch between 4 sounds?

HansEhv posted Oct 21 '17, 00:52:

Midi implementation chart of lpk25 shows it has no support for program change messages.
So you will need to use the buttons of samplerbox

AlexM posted Oct 21 '17, 10:27:

For your LPK25 you may need to hack away at the samplerbox.py a little bit. You'll be interested in these lines here:

elif messagetype == 12:  # Program change
    print 'Program change ' + str(note)
    preset = note


I suggest you add some print statements higher up to find out what messagetype and midinote messages your LPK25 buttons are sending -- perhaps you can use ARP ON/OFF and TAP TEMPO. Just remember to add velocity == 127 to your conditional otherwise the program change will trigger twice.

HansEhv posted Oct 21 '17, 17:06:

According to the midi implementation chart, these instructions will be sent via manufacturer specific system exclusive messages. To see them either filtering on midichannel should be set off, or filter on channel 15 instead. But in the last case you will loose the keyboard as this will undoubtedly default to channel 1.
You can find docs at http://www.akaipro.com/products/keyboard-controllers/lpk-25

Dario posted Dec 11 '17, 20:38:

@AlexM, should I do the same to enable program change from a Launchkey 25? I tried changing the config file but obviously not the right way. I'm not sure what to do...it seems silly to buy buttons for the RPI with all those unused pads, buttons and encoders on the Launchkey doing nothing. How can I remap a MIDI command from the launchkey to act on program change?

AlexM posted Dec 12 '17, 00:57:

@Dario - perhaps the easiest way to map these keys - and it is possible with your keyboard because I have the same one ;) - is to use my forked version:


The to set up your navigation keys (left, right, enter, cancel). You'll need to have access to the console for this:

NB1: left and right will act as program change unless you enter the menu
NB2: the menu system will be useless without a connection to a screen/SSH OR an LCD module wired to the GPIO pins

Bonus! Once this is set up you can map a few other controls via the MIDI mapping feature:

Dario posted Dec 13 '17, 21:05:

@AlexM, thanks, I'm pretty sure I was already using your version, I guess I just don't know how to change the config file... I've tried based on some tips from Glenn (see the "launchkey" post on this forum), but I failed miserably.

I should add that I'm new to raspberry pi, or any sort of coding...any hope you'd share your config file with me since you have the same controller? :P

In any case, thanks for the help so far, and for the work you guys put into this. Even just by using it one sample at a time (right now I've changed the config file to load grand piano by default) this thing is awesome and it has already helped me make new music.


PS: this forum is unlike any I've ever seen, I don't seem to have a way of being notified about replies, there's no "search" function and so on...interesting.


  (not published)
  I want to post as guest