Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to request eeprom from Max7 patch #1

Open
lovettbarron opened this issue Aug 1, 2017 · 1 comment
Open

Unable to request eeprom from Max7 patch #1

lovettbarron opened this issue Aug 1, 2017 · 1 comment

Comments

@lovettbarron
Copy link

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.
screen shot 2017-08-01 at 09 48 05

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)

@0x80
Copy link
Owner

0x80 commented Aug 2, 2017

I have no easy way to reproduce this anymore since I move to a new machine and don't have the Shreditor on there at all.

The messages about bundle corruption are familiar. You can find more info in this thread https://forum.mutable-instruments.net/t/shreditor-v1-0-open-source-release/8043/10

Maybe you can try to work around it using the suggestions there and see if you can launch it from the app.

But I doubt that will solve the problem.

You could also try to monitor your sysex with something like midimonitor, and try to see what the payload for cmd 43 is.

Maybe also try to set your Shruthi to midi channel 1...

I hope you find a clue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants