I suspect 4x20 screens would work as well with re-arrangement of the output pins and formatting of the output. The communications method is the same.

Yeah I ordered a blue one and I'll see what it's like when it shows up. I prefer the blue color anyways.

20x4 seem to be much easier to get.
I might buy one of those as well and change around some things to get that to work too. (it probably already does though)

I agree it would work fine but I think it would be a little to big for the 5 inch bay enclosure.I guess they are easier to find because they are used a lot for 3D printers.

20x4 displays should work as well with the current code. The third and fourth row would be unused though.

20x4 would not fit into a 5 inch bay as far as I know.

I bought this display now:

https://www.ebay.de/itm/Black-IIC-I2C-TWI-Cha … QQAAOSwW1JdU2wH

I like the black&white a lot and wanted a negative display. Now I just need to wait. 😁

Yes, 20x4 displays are 60mm high, so you would need a full height (or double) bay to mount it internally.

Here's the company that makes those displays. It might be cheaper to buy directly from them depending on where you live.
https://www.buydisplay.com/default/arduino-bl … y-high-contrast

If these seem to be readily available than that'll be the official screen that we should support.

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

Awesome! Glad to see everything is working. I finally got my buttons so I can extend the code to support changing the profiles via external buttons. Probably will do that this weekend.

Cool thing, will follow this thread 😀

t9999clint wrote:

My LCDs finally came in so I was able to test out the new LCD code. Looks like everything's working so I merged the changes to t […]
Show full quote

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

I've got an old Pi2 that will soon be redundant, so I'll give it a go with that 😀 Hopefully it's not too slow for being a wavetable.

Did anybody try it with a single-core Pi?
I have one I was using as a print server but don't need anymore. It's a first generation B+

Thermalwrong wrote:

t9999clint wrote:

If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

I've got an old Pi2 that will soon be redundant, so I'll give it a go with that 😀 Hopefully it's not too slow for being a wavetable.

Other similar projects were able to run on a rasp pi 2 so I don't see why this one wouldn't work. There will be glitches of course, but it should still run.
I just want to make sure before I claim that it's compatible.
In theory the ras pi zero should work as well, but only with soundfonts, not with MUNT.

Badscrew wrote:

Did anybody try it with a single-core Pi?
I have one I was using as a print server but don't need anymore. It's a first generation B+

No not yet. I'd be interested to see the results of that. It won't run munt, but it should still run soundfonts (if they're simple).
I wrote a few scripts that are supposed to detect the architecture and scale the settings accordingly.
I won't know for sure though until I see it running.

Allright, understood!

t9999clint wrote:

My LCDs finally came in so I was able to test out the new LCD code. Looks like everything's working so I merged the changes to t […]
Show full quote

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

I can confirm that it works with the rpi2 but Munt does not like it at all, it's very slow and it misses a lot of notes. I did have munt running on the rpi2 before though.
Soundfont works fine, tested with DOOM.

Thermalwrong wrote:

t9999clint wrote:

My LCDs finally came in so I was able to test out the new LCD code. Looks like everything's working so I merged the changes to t […]
Show full quote

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

I've got an old Pi2 that will soon be redundant, so I'll give it a go with that 😀 Hopefully it's not too slow for being a wavetable.

You may have to tune polyphony, but otherwise you should be good.

DonZott wrote:

t9999clint wrote:

My LCDs finally came in so I was able to test out the new LCD code. Looks like everything's working so I merged the changes to t […]
Show full quote

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

I can confirm that it works with the rpi2 but Munt does not like it at all, it's very slow and it misses a lot of notes. I did have munt running on the rpi2 before though.
Soundfont works fine, tested with DOOM.

Sounds like Munt didn't build with optimizations. The other common cause is downclocking because of a weak 5V supply.

gdjacobs wrote:

DonZott wrote:

t9999clint wrote:

My LCDs finally came in so I was able to test out the new LCD code. Looks like everything's working so I merged the changes to t […]
Show full quote

My LCDs finally came in so I was able to test out the new LCD code.
Looks like everything's working so I merged the changes to the github. I also tweaked a few minor things with the installation scripts.
If you already have the LCD working on your version than this release won't add anything new for you.
I also got a Raspberry Pi 4 B (4gb) and was able to test it with that one as well. Everything is working great with the 3 and 4.
If anyone has a Raspi 2 that they can test with please let me know. I'd like to see if WavePi works with that generation as well.

Here's the latest release. It's recommended to use DietPi as the OS now. Raspbian Lite should still work fine though.
https://github.com/t9999clint/WavePi/releases/tag/v0.8.0

I can confirm that it works with the rpi2 but Munt does not like it at all, it's very slow and it misses a lot of notes. I did have munt running on the rpi2 before though.
Soundfont works fine, tested with DOOM.

Sounds like Munt didn't build with optimizations. The other common cause is downclocking because of a weak 5V supply.

Hi gdjacobs, thanks for the tips! I did set the optimizations and i'm using the same power source that I've used for the rpi4. But I will try it with an other psu. On the rpi4 everything works super, have been playing day of the tentacle and space quest 3 for 20 minutes, it's super stable.
I'm figuring out stuff with t9999clint rn.

Could also be one of the following issues:

- reverb and chorus enabled => disable them
- I'm using the built-in DAC => will try it with a usb DAC

Could be reverb and chorus. Using another DAC will result in better audio quality, but CPU usage shouldn't be substantially higher. Run vcgencmd get_throttled to see if the SoC is being or has been underclocked. 0x50005 indicates clock limiting due to undervoltage currently happening, 0x50000 indicates it has happened but not currently, and 0x0 indicates normal function.

gdjacobs wrote:

Could be reverb and chorus. Using another DAC will result in better audio quality, but CPU usage shouldn't be substantially higher. Run vcgencmd get_throttled to see if the SoC is being or has been underclocked. 0x50005 indicates clock limiting due to undervoltage currently happening, 0x50000 indicates it has happened but not currently, and 0x0 indicates normal function.

Allright, thanks! I'll test it asap.