PhilsComputerLab wrote:

brostenen wrote:

Phil:

Was those scripts in the link to the midi-diy that I mentioned, at any use?

Hmm I don't see how these are related to be honest...

I was just thinking, that you might be interrested in how to add a shutdown button for standalone midi module without any monitor. 😀

Oh, I thought you were talking about compiling Munt.

Nono.... 😁 😁 (sorry that I was not that specific)

I was just referring to the post I made on the first page of this tread.
I saw that you started with fluidsynth, and I remembered that the PiMidi on Instructables,
were based on Fluidsynth. And I remembered that it had a shutdown/reset thing going on.

Ah, no worries, I get it now 😀

Personally, Id just target pi3, it has the best performance. adding stuff to target the much slower pi1/pi2 is pointless imo.

BloodyCactus wrote:

Personally, Id just target pi3, it has the best performance. adding stuff to target the much slower pi1/pi2 is pointless imo.

I'd be happy with that 😀

Would the idea of a small TFT screen on the PI, add something useable?

brostenen wrote:

Would the idea of a small TFT screen on the PI, add something useable?

Yes, I was hoping others go nuts with stuff like this 😀

Sweet.... So... Basically, one could build a standalone synth, with Munt or Fluidsynth UI loaded upon boot and have it touchscreen controlled.

And even add a cool sound card (originally by Wolfson) 😀
https://www.element14.com/community/community … ogic_audio_card

Perhaps a tone regulator module from eBay too... To add treble and bass controll ?
And perhaps add real 5-Pin DIN midi plugs as well. (MIDI in/through/out)

PI + Wolfson + TFT + Tone regulator + 5-Pin DIN.... 😜

And if it is capeable to load SF2 banks, then there must be a ton of use for this device.

BloodyCactus wrote:

Personally, Id just target pi3, it has the best performance. adding stuff to target the much slower pi1/pi2 is pointless imo.

Until Raspbian gets a 64 bit version, Pi 2 and Pi 3 are kind of the same thing from a software perspective.

gdjacobs wrote:

BloodyCactus wrote:

Personally, Id just target pi3, it has the best performance. adding stuff to target the much slower pi1/pi2 is pointless imo.

Until Raspbian gets a 64 bit version, Pi 2 and Pi 3 are kind of the same thing from a software perspective.

Yeah. Im only aware of the arm8-a (pi3) having CRC instrutions that clang enables by default thats not in pi2's arm7-a core, but otherwise a pi3 arm8 binary should be able to run on a pi2 ok. and of course a pi2 binary would run fine on a pi3, just not be as well optimised.

When i switched my pinball controller out from a pi2 to pi3 the performance difference was huge (but I am using threading and such), Id rather target pi3 over 2 than deal with stuff like people complaining about choppyness or dropped midi frames or whatever.

As far as I'm aware, the convention so far has been to build a ARMv7 binaries and use them for both the Pi 2 and 3. The foundation doesn't seem in much of a hurry to move to ARMv8.