In guitar_pedal_ui.cpp it is written:

// These will be called from the UI system. @see InitUi() in UiSystemDemo.cpp
void FlushCanvas(const UiCanvasDescriptor& canvasDescriptor)
{
    ...
}

I can't seem to find the file in the repo.

There is an issue causing noise in the signal when there is one of my pedals using a Rev7 Daisy Seed has another one of my pedals connected to the output of the first pedal. It doesn't matter which rev Daisy Seed is in the second pedal, the noise will occur.

This issue does not occur when using multiple of my pedals with Rev 5 Daisy Seeds in each of them back to back.
This issue does not occur when there is only a single one of my pedals in the signal chain.

Working with Electro-Smith to identify and resolve the issue. No further information at this time.

This issue affects the GuitarPedal125b design. The TRS 1/8" Midi jacks on the PCB can cause the PCB to be quite difficult to be removed from the 125b enclosure. This is because the end of the midi jack must protrude part way through the enclosure to allow the plug to make proper contact with the jack on the PCB.

The second row of pots (4-6) on the GuitarPedal125b hardware are non-ideally rotated 180 degrees. The primary issue with this is exacerbated by the fact that the pots are D-shaft which makes it so that any D-shaft knobs used don't have their indicators line up properly. The work around is to use smooth shaft knobs, but these are hard to secure properly and hard to level properly when used on the d-shaft.

The rotation was unfortunately necessary to be able to fit all the elements onto the PCB. It's not a simple matter of rotating the elements on the PCB 180 degrees. The elements will no longer fit anymore if that is done. I've explored a number of possible alternative layouts to make it work, but it doesn't seem possible with the current set of features.

The use of D-shaft pots was also unfortunately necessary due to the fact that the Bournes PRS11R family of Pots is only available in D-shaft. This family of pots was selected because it was the only pot slim enough to pair well and match the height of the Bounes PEC11R family of encoders.

This issue affects the GuitarPedal125b hardware design. There are a number of through-hole components that are directly under the PCB mounted PRS11R pots. If these protruding pins touch the underside of the pots they can cause electrical shorts causing the hardware to malfunction or not behave as expected. This is specifically an issue with Pot1, Pot3, and Pots 4-6.

This issue is mentioned in the hardware build instructions and the recommend work around is to isolate the pots from the pcb using doublesided foam tape as described here. This is less than ideal, but it works.

Potential future workarounds include redesigning the PCB to use surface mount parts instead of the through-hole parts that are protruding, but would require a fairly large re-layout of the entire PCB.

Flash utilization is 97.16% after the latest changes. It is unlikely more than one or two new effects can be added. I am wondering if there is a cheap way to decrease that.

Hi, I just built a GuitarPedal1590b-SMD and I'm trying to flash the Daisy Seed. I followed the instructions to set up the build environment and compile the code, which all worked correctly, but when I try to run make program-dfu I get:

dfu-util -a 0 -s 0x90040000:leave -D build/guitarpedal.bin -d ,0483:df11
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Warning: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release
Deducing device DFU version from functional descriptor length
Deducing device DFU version from functional descriptor length
Opening DFU capable USB device...
Device ID 0483:df11
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading element to address = 0x90040000, size = 138352
dfu-util: Last page at 0x90061c6f is not writeable
make: *** [libDaisy/core/Makefile:330: program-dfu] Error 64

I'm able to flash the Blink program from DaisyExamples just fine - any idea what's going on?

The current software implemented of local storage on QSPI for the storage of effect parameters settings is quite simplistic and limited.

The current implementation in guitar_pedal_storage.h & .cpp is hard coded to treat each effect parameter as a u_int8 type and to simply allocated a block of memory in the QSPI region that is SETTINGS_MAX_EFFECT_COUNT * SETTINGS_MAX_PARAM_COUNT * sizeof(u_int8) bytes. Using this approach, it's quite easy to look up the stored value for a parameter by simply using an offset into this block of memory. Unfortunately, this is quite limited and not very flexible for future use. In the current code base SETTINGS_MAX_EFFECT_COUNT is set to 8 and SETTINGS_MAX_PARAM_COUNT is set to 16. Which effectively limits the device to a max of 8 active effects with up to 16 parameters each. This is not a hardware memory limit. Those numbers were chosen quite arbitrarily. If you need more parameters feel free to adjust those defines for your own purposes.

This presents a great opportunity for someone wanting to contribute to the project to get started with something that wouldn't be too hard to improve. Some ideas that would make this a lot more flexible:

• Allow an arbitrary number of presets
• Allow an arbitrary number of effect parameters per preset
• Only allocate the actual amount of storage needed to save a preset for a particular effect module
• Support additional stored data types beyond u_int8. In would be nice to store some parameters as floats for instance.
• Bonus points if presets stored in the old format can easily be updated to the new format.