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

feat(controllers): add new controller mapping for Numark NS6II #11075

Open
wants to merge 19 commits into
base: 2.4
Choose a base branch
from

Conversation

Swiftb0y
Copy link
Member

@Swiftb0y Swiftb0y commented Nov 17, 2022

Manual still TODO
manual PR

@Swiftb0y
Copy link
Member Author

tests are failing because of the EffectUnits. I guess I'll have to redo them when I find the time. Works locally so far.

@github-actions
Copy link

This PR is marked as stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the stale Stale issues that haven't been updated for a long time. label Feb 16, 2023
@github-actions github-actions bot removed the stale Stale issues that haven't been updated for a long time. label Jun 6, 2023
@Swiftb0y Swiftb0y force-pushed the numark-ns6ii branch 2 times, most recently from 7872f2b to fccd316 Compare June 22, 2023 22:46
@github-actions
Copy link

This PR is marked as stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the stale Stale issues that haven't been updated for a long time. label Sep 22, 2023
@Swiftb0y
Copy link
Member Author

Ah yes, good old stale. I have had and used this controller for about 5 years now, one day I'll get around to polishing the mapping enough for merge.

Still, a surface-level review in the meantime would be appreciated.

@github-actions github-actions bot removed the stale Stale issues that haven't been updated for a long time. label Sep 23, 2023
Copy link

This PR is marked as stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the stale Stale issues that haven't been updated for a long time. label Dec 22, 2023
@daschuer daschuer changed the base branch from 2.3 to 2.4 June 9, 2024 15:29
Copy link
Member

@acolombier acolombier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hard to review without the device to test. but it is looking good overall. Also I'm sure that if you've been using it this long, you probably had a chance to polish most of the small bug lying around :)

Some comment cruft here and there that might be worth removing or documenting if useful for alternate behaviours (note that if the latter, you might want to consider the controller settings).
Did you have a chance to prepare the manual for that?

@Swiftb0y
Copy link
Member Author

I'll try to give this another look and ping you when I think its ready. Thanks for the review.

@Swiftb0y
Copy link
Member Author

@acolombier please re-review ;)
I'm mostly satisfied with the mapping (there are a couple TODO's but I'm really not in the mood to implement those).
I'll focus on the manual page next.

@Swiftb0y Swiftb0y removed the stale Stale issues that haven't been updated for a long time. label Jul 17, 2024
@@ -1,4 +1,6 @@

type MidiInputHandler = (channel: number, control: number, value:number, status:number, group:string) => void;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't spot the place, where this type is defined in our API. Is this a mapping specific type, that doesn't belong to the API?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Swiftb0y Swiftb0y added this to the 2.4.2 milestone Aug 16, 2024
@Swiftb0y
Copy link
Member Author

friendly ping... ;)

Comment on lines +709 to +716
// grey could be an alternative as well as a backlight color.
off: NS6II.USE_BUTTON_BACKLIGHT ? NS6II.PAD_COLORS.RED.DIMMER : NS6II.PAD_COLORS.OFF,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could it be worth adding a dynamic setting for that?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I'll add that as a follow up, but I wanted to keep this branch targetted at 2.4

});
this.scratch = new components.Button({
midi: [0x90 + channelOffset, 0x07],
// shift: [0x90+channelOffset,0x46]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be removed as this is redundant with line 409/414?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

technically yes, but I would've preferred this to stay here instead of having it buried in the implementation.

this.parameterLeft = new components.Button({
midi: [0x90, 0x28],
unshift: function() {
// TODO change hotcue page
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this outstanding? Or should it be removed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nah, its technically outstanding, but I really didn't want to bother implementing that because components.HotcueButton is not setup for that.

this.parameterRight = new components.Button({
midi: [0x90, 0x29],
unshift: function() {
// TODO change hotcue page
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto

@daschuer daschuer marked this pull request as draft September 15, 2024 19:36
@daschuer daschuer removed this from the 2.4.2 milestone Sep 15, 2024
@Swiftb0y Swiftb0y force-pushed the numark-ns6ii branch 2 times, most recently from 88b88a0 to 38762b8 Compare November 15, 2024 14:24
@Swiftb0y Swiftb0y marked this pull request as ready for review November 15, 2024 14:24
@acolombier
Copy link
Member

acolombier commented Nov 17, 2024

I had a thorough look at that eslint failing, I really can't find what is wrong here. I reproduced to the exact everything the pipeline does (merge commit and container) and yet, everything is fine on my local. I'm running out of idea currently, but I'll try to think of something else.
Otherwise, since eslint is giving me a green light locally, I'd say we could ignore the CI failing and merge it, wdyt?
The build is a blocker tho IMO

@Swiftb0y
Copy link
Member Author

well the build failure is fortunately unrelated and fixed with #13904. I'll investigate whats wrong with pre-commit.

Otherwise the eslint stdout is only printed if eslint actually fails.
In the case of warnings, we don't want pre-commit to fail, but we
still want to bring attention to the users code that something is
suboptimal. In order for that to work the output still needs to be
shown even when the hook does not fail. Setting a hook to be
`verbose` is the only way to make that happen as far as I can tell.
@Swiftb0y
Copy link
Member Author

now depends on #13913

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

Successfully merging this pull request may close these issues.

4 participants