You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been running into problems trying to pull the eeprom data from my Shruthi.
The shruthi itself is set to channel 16, midi out off (also tried with thru)
Have been getting this error in the max console.
The shruthi was updated to 1.02 (the firmware you included in the repo), and I'm running Max7 w/ the midi interface being a Motu ultralite 3 hybrid. The sysex is definitely getting to the shruthi (feedback from the LCD and LEDs), but nothing is getting back to Shreditor.
Let me know if there's a simple fix, otherwise if it's something more fundamental happy to do some digging and submit a PR if appropriate.
(Side note/other problem: the packaged app was considered corrupt by OSX Sierra 10.12.6, hence why I'm running directly in Max. If I can get the patch itself running successfully I might repackage/hunt down why that was the case)
The text was updated successfully, but these errors were encountered:
First, thanks for this brilliant tool.
I've been running into problems trying to pull the eeprom data from my Shruthi.
The shruthi itself is set to channel 16, midi out off (also tried with thru)
Have been getting this error in the max console.
The shruthi was updated to 1.02 (the firmware you included in the repo), and I'm running Max7 w/ the midi interface being a Motu ultralite 3 hybrid. The sysex is definitely getting to the shruthi (feedback from the LCD and LEDs), but nothing is getting back to Shreditor.
Let me know if there's a simple fix, otherwise if it's something more fundamental happy to do some digging and submit a PR if appropriate.
(Side note/other problem: the packaged app was considered corrupt by OSX Sierra 10.12.6, hence why I'm running directly in Max. If I can get the patch itself running successfully I might repackage/hunt down why that was the case)
The text was updated successfully, but these errors were encountered: