This repository was archived by the owner on Jun 19, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 254
Midimap+ #1284
Open
nkymut
wants to merge
5
commits into
tidalcycles:main
Choose a base branch
from
nkymut:midimap+
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Midimap+ #1284
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
bc34818
allow midimaps to register arbitary controlnames
nkymut 260c6e0
Merge branch 'main' of https://github.com/tidalcycles/strudel into mi…
nkymut 84e3f12
Merge branch 'main' of https://github.com/tidalcycles/strudel into mi…
nkymut e075095
Add warning when midimap overrides existing Strudel API
nkymut 28eedae
docs: add tips for enabling MIDI in Chrome for local development
nkymut File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what if the control name exists already? then we shouldn't register it i think. when doing so, we might override it in a way that breaks it. for example, some controls are allowed to set multiple controls, like
cutoff:resonance:lpenv, which would probably break when callingregisterControl('cutoff'), as things likenote("g1").cutoff("200:8:4")wouldn't set resonance and lpenv anymoreThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's what I meant by namespace pollution.
I think an easier solution would be to add a prefix like
mm_to distinguish the names.Alternatively, it could just throw an error if
controlAlias.has(controlName)returns true, and prompt the user to choose a different control name.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not reuse existing names? one idea behind these midimaps was that you could easily play a non-midi pattern with your midi device without changing control names (e.g. lpf maps to your synths cutoff cc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, in that case how about registering a selective control function that checks whether
hap.value.midiexists, and then decides whether to use the original lpf or the midi-mapped lpf? Or is there a better way to tell if the current trigger is to MIDI, SuperDough, or else?