Thanks @jason mayo, I noticed earlier today the new firmware was already published last month, I missed it. Hopefully all the SD cards issues are now solved - I'll report here if I still encounter any problem

Hi @Jason Mayo , Are you still planning to release a firmware update solving the sd card issues? If so, do you have a planned date for releasing the new version? thanks!

Thanks Jason. It is great to hear you have been able to identify and fix the issue - I'm looking forward the firmware update.

Hi Jason - did you manage to replicate this issue? I'm curious to know if this is a problem with my unit or a general one and if it can be fixed via a firmware update. The unit also becomes irresponsive moving from and to that sound preset in an inconsistent way

Hi Jason, I have continued having the same problem described above. Strangely enough, I have found the culprit is the file `6_EP200.pfon` in the standard library. When I boot the module with that sound selected (number 6), the module (consistently) fails to boot and becomes irresponsive. This happens 100% of the times. Booting with any other sound selected, boots without issues (at least for the other few I have tried). It seems to be a problem with that file, since swapping sounds in the library (ie, renaming the file to `5_EP200.pfon` and renaming previous 5 to `6_ToyPiano.pfon` results in booting ok when sound 6 is selected (ToyPiano), but failing to boot with sound 5 (EP) is selected. I don't know if you have encountered this problem before. Any help in solving it would be appreciated since this has become an annoying issue using this great module. Thanks for your help, M;

Thanks for your comments Jason - just updating on the issue: Deleting the settings.dat file on the original SD card didn't solve the issue. Using another SD card with the pianophonic library and the original settings.dat file seems to solve the problem - at least for now I'll reply to this thread again if the problem comes back. Thanks again!

Thanks Jason, will try asap. Quick other question - It took me a bit to make the module respond to my midi keyboard when I first plugged it in because by default it was listening to a specific midi channel rather than omni - setting it to omni fixed the issue, but would that also point to a problem in the Settings.dat file? Thanks again! M;