Open amj opened 8 years ago
I ran into a problem getting the Arduino Leonardo to interface as a Monome because the USB descriptors are different. It's solvable, maybe reflashing the 16u2 on modern Leonardos but then again, it'd be hard to test the code unless you used ICSP to reflash program code in making changes.
Near the end I was making some changes in the code to get it to be recognized that probably were not necessary, just frustration.
I'd welcome any contributions!! Mike
On Tue, Oct 11, 2016 at 8:20 AM, Andrew Jackson notifications@github.com wrote:
Hey! 1st off, thanks for writing an awesome bit of code to make the untz' play nice w/ the monome software in max -- great, readable code, clearly legible, a huge THANK YOU. It's been super frustrating digging through what works & what doesn't in the 8+ years of documentation around the monome project, so a huge thank you for that.
there's a couple ?'s in the code about the mext protocol (how to reply to some /sys commands, baud rate, etc). Is there any way i can help resolve those?
I'm trying to troubleshoot a 8x16 grid and seeing all sorts of glitchy behavior w/ the standard monome apps -- looks like garbage bytes gettings blitted out, the works. I'll update w/ a video of some of the standard apps -- and i'm wondering if they're related to some of those ?s or maybe the mext protocol changed, or what.
Thanks in advance for any help!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TheKitty/Untz_Monome/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0scA-OZrxbi5_u56fl2h__bvNIUVySks5qyyq7gaJpZM4KTSBO .
Ah! I fixed that by flashing some better identifiers into the eeprom via 'piraterename', part of the buspirate suite: http://maxome.org/page/2 That got it recognized in max to get me started at least :) i'll see if i have any luck getting it cleaned up for some PRs!
On Tue, Oct 11, 2016 at 12:13 AM, Mike Barela notifications@github.com wrote:
I ran into a problem getting the Arduino Leonardo to interface as a Monome because the USB descriptors are different. It's solvable, maybe reflashing the 16u2 on modern Leonardos but then again, it'd be hard to test the code unless you used ICSP to reflash program code in making changes.
Near the end I was making some changes in the code to get it to be recognized that probably were not necessary, just frustration.
I'd welcome any contributions!! Mike
On Tue, Oct 11, 2016 at 8:20 AM, Andrew Jackson notifications@github.com wrote:
Hey! 1st off, thanks for writing an awesome bit of code to make the untz' play nice w/ the monome software in max -- great, readable code, clearly legible, a huge THANK YOU. It's been super frustrating digging through what works & what doesn't in the 8+ years of documentation around the monome project, so a huge thank you for that.
there's a couple ?'s in the code about the mext protocol (how to reply to some /sys commands, baud rate, etc). Is there any way i can help resolve those?
I'm trying to troubleshoot a 8x16 grid and seeing all sorts of glitchy behavior w/ the standard monome apps -- looks like garbage bytes gettings blitted out, the works. I'll update w/ a video of some of the standard apps -- and i'm wondering if they're related to some of those ?s or maybe the mext protocol changed, or what.
Thanks in advance for any help!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TheKitty/Untz_Monome/issues/1, or mute the thread https://github.com/notifications/unsubscribe- auth/AB0scA-OZrxbi5_u56fl2h__bvNIUVySks5qyyq7gaJpZM4KTSBO .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TheKitty/Untz_Monome/issues/1#issuecomment-252831677, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZzuXXih9wVbfjduCNaCV-t7XyQYnMLks5qyzcpgaJpZM4KTSBO .
Great work! Yes, I'd really like to see you get things further than I was able to take them
On Tue, Oct 11, 2016 at 11:31 AM, Andrew Jackson notifications@github.com wrote:
Ah! I fixed that by flashing some better identifiers into the eeprom via 'piraterename', part of the buspirate suite: http://maxome.org/page/2 That got it recognized in max to get me started at least :) i'll see if i have any luck getting it cleaned up for some PRs!
On Tue, Oct 11, 2016 at 12:13 AM, Mike Barela notifications@github.com wrote:
I ran into a problem getting the Arduino Leonardo to interface as a Monome because the USB descriptors are different. It's solvable, maybe reflashing the 16u2 on modern Leonardos but then again, it'd be hard to test the code unless you used ICSP to reflash program code in making changes.
Near the end I was making some changes in the code to get it to be recognized that probably were not necessary, just frustration.
I'd welcome any contributions!! Mike
On Tue, Oct 11, 2016 at 8:20 AM, Andrew Jackson < notifications@github.com> wrote:
Hey! 1st off, thanks for writing an awesome bit of code to make the untz' play nice w/ the monome software in max -- great, readable code, clearly legible, a huge THANK YOU. It's been super frustrating digging through what works & what doesn't in the 8+ years of documentation around the monome project, so a huge thank you for that.
there's a couple ?'s in the code about the mext protocol (how to reply to some /sys commands, baud rate, etc). Is there any way i can help resolve those?
I'm trying to troubleshoot a 8x16 grid and seeing all sorts of glitchy behavior w/ the standard monome apps -- looks like garbage bytes gettings blitted out, the works. I'll update w/ a video of some of the standard apps -- and i'm wondering if they're related to some of those ?s or maybe the mext protocol changed, or what.
Thanks in advance for any help!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TheKitty/Untz_Monome/issues/1, or mute the thread https://github.com/notifications/unsubscribe- auth/AB0scA-OZrxbi5_u56fl2h__bvNIUVySks5qyyq7gaJpZM4KTSBO .
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/TheKitty/Untz_Monome/issues/1#issuecomment-252831677 , or mute the thread https://github.com/notifications/unsubscribe- auth/AAZzuXXih9wVbfjduCNaCV-t7XyQYnMLks5qyzcpgaJpZM4KTSBO .
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/TheKitty/Untz_Monome/issues/1#issuecomment-252859901, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0scKO3Up5sVTMLlzO2LDwdkbE0J19Aks5qy1d3gaJpZM4KTSBO .
Hey! 1st off, thanks for writing an awesome bit of code to make the untz' play nice w/ the monome software in max -- great, readable code, clearly legible, a huge THANK YOU. It's been super frustrating digging through what works & what doesn't in the 8+ years of documentation around the monome project, so a huge thank you for that.
there's a couple ?'s in the code about the mext protocol (how to reply to some /sys commands, baud rate, etc). Is there any way i can help resolve those?
I'm trying to troubleshoot a 8x16 grid and seeing all sorts of glitchy behavior w/ the standard monome apps -- looks like garbage bytes gettings blitted out, the works. I'll update w/ a video of some of the standard apps -- and i'm wondering if they're related to some of those ?s or maybe the mext protocol changed, or what.
Thanks in advance for any help!