Features:
|
- Raspberry Pi 3
- Custom PCB Data Files
- Screen
- LED rings and NeoPixels
- Analog Input break out board
- Infinite turn pots
- Photos:
- Dependencies:
- Lgi on SDL generally needs:
sudo apt-get install build-essential libmagic-dev libgstreamer1.0-dev \ libappindicator3-dev libssh-dev libsdl2-2.0-0
But you may need to add libgtk3.0-dev if you want to run the IDE to update the makefiles.
And you might add mercurial if you want to pull the latest source.
That said it's been a long time since I created the initial dev environment on the Rpi. This list is just a starting point. You may need to add more packages as needed.
- Lgi on SDL generally needs:
- Rpi Source and Binaries:
- Lgi binary: Code/lgi/trunk/Debug/liblgi-gtk3d.so
This needs to be in the LD_LIBRARY_PATH. - Mc4 binary: Code/MidiHw/mc4/linux-rpi/mc4
Run command 'sudo ./mc4'.
- Lgi binary: Code/lgi/trunk/Debug/liblgi-gtk3d.so
- Architecture:
- Gui thread: Handles display of all windows and user interaction.
- Mc4Ui class in Code/MidiHw/mc4/src/mc4ui.cpp
- Hardware thread: Handles talking to the hardware for everything AND sending and
receiving MIDI to the Axefx device.
- Mc4Logic class in Code/MidiHw/mc4/src/mc4logic.cpp
- HardwarePriv class in Code/MidiHw/mc4/src/HardwarePi.cpp
- Windows desktop version:
- See Code/MidiHw/mc4/windows/mc4.sln
Visual Studio 2015
- See Code/MidiHw/mc4/windows/mc4.sln
- Gui thread: Handles display of all windows and user interaction.
- Screenshots:
- Notes:
- To work on the software I generally connect using sshfs to the Rpi to mount the home folder. And then use an IDE on the desktop to edit the code. Before building via an ssh. To run the software I vnc into the MC4 and use a terminal on the device's actual screen. This avoids issues with the X servers DISPLAY setting. You can run the mc4 binary from the ssh connection but it takes extra setup steps.
- The user interface resources are editable in LgiRes. The actual dialog definitions and string resources are in Code/MidiHw/mc4/resources/mc4.lr8.