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

Changing mapping of faders meant a lot of moving connections in Max. #8

Open
rec opened this issue Apr 5, 2015 · 2 comments
Open
Assignees

Comments

@rec
Copy link
Owner

rec commented Apr 5, 2015

All those connections are a bad idea anyway. This needs more thought though, because everyone else who writes Max just drags stuff around a lot, there isn't a standard solution!

The Lemur phase will have to introduce some intermediate layer that will probably solve this issue, if we don't forget about it.

@rec rec added the nanolaser label Apr 5, 2015
@rec rec self-assigned this Apr 5, 2015
@bentoncbainbridge
Copy link

ok, but it still seems to me that I should be able to make a Lemur interface that exactly replicates MIDI values sent from the Korg Nano. I'm willing to try, I would just need to know the MIDI CC #s

@rec
Copy link
Owner Author

rec commented Apr 5, 2015

This bug is a sort of technical thing. Don't worry too much about it for
now.

We want to do better than the Nanokontroller on the Lemur. Let's see how
this next incarnation works...

On Sun, Apr 5, 2015 at 4:33 PM, Benton C Bainbridge <
[email protected]> wrote:

ok, but it still seems to me that I should be able to make a Lemur
interface that exactly replicates MIDI values sent from the Korg Nano. I'm
willing to try, I would just need to know the MIDI CC #s


Reply to this email directly or view it on GitHub
#8 (comment).

 /t

http://radio.swirly.com - art music radio 24/7 366/1000

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

No branches or pull requests

2 participants