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

Hercules Inpulse 200 (update March 2020) #2542

Merged
merged 9 commits into from
Jun 12, 2020

Conversation

DJPhatso
Copy link
Contributor

Modified mapping files following the approval of the Inpulse 300

DJPhatso and others added 6 commits March 10, 2020 09:23
Initial release of MIDI configuration files for Hercules DJControl Inpulse 200
Minor corrections that eslint didn't catch.
@Holzhaus
Copy link
Member

Hey @DJPhatso, thanks for contributing yet another controller mapping. Can you please rebase on 2.2?

@Holzhaus
Copy link
Member

@DJPhatso DJPhatso changed the base branch from master to 2.2 March 11, 2020 12:15
@Holzhaus
Copy link
Member

Holzhaus commented Mar 12, 2020

Our pre-commit-pr job on Travis CI found some style issues:
https://travis-ci.org/github/mixxxdj/mixxx/jobs/660633844

Can copy and paste the diff from the build log into a new file names fix-issues.patch, the run git apply fix-issues.patch? That should resolve the issues.

Here's the diff:

diff --git a/res/controllers/Hercules-DJControl-Inpulse-200-script.js b/res/controllers/Hercules-DJControl-Inpulse-200-script.js
index fa12bac36..2b8a349d7 100644
--- a/res/controllers/Hercules-DJControl-Inpulse-200-script.js
+++ b/res/controllers/Hercules-DJControl-Inpulse-200-script.js
@@ -50,8 +50,8 @@ DJCi200.init = function() {
     DJCi200.scratchButtonState = true;
     // Scratch Action
     DJCi200.scratchAction = {
-    1: DJCi200.kScratchActionNone,
-    2: DJCi200.kScratchActionNone
+        1: DJCi200.kScratchActionNone,
+        2: DJCi200.kScratchActionNone
     };
 
     //Turn On Vinyl buttons LED(one for each deck).
@@ -61,11 +61,11 @@ DJCi200.init = function() {
     //Turn On Browser button LED
     midi.sendShortMsg(0x90, 0x04, 0x05);
 
-   //Softtakeover for Pitch fader
-   engine.softTakeover("[Channel1]", "rate", true);
-   engine.softTakeover("[Channel2]", "rate", true);
-   engine.softTakeoverIgnoreNextValue("[Channel1]", "rate");
-   engine.softTakeoverIgnoreNextValue("[Channel2]", "rate");
+    //Softtakeover for Pitch fader
+    engine.softTakeover("[Channel1]", "rate", true);
+    engine.softTakeover("[Channel2]", "rate", true);
+    engine.softTakeoverIgnoreNextValue("[Channel1]", "rate");
+    engine.softTakeoverIgnoreNextValue("[Channel2]", "rate");
 
     //Set effects Levels - Dry/Wet
     engine.setParameter("[EffectRack1_EffectUnit1_Effect1]", "meta", 0.6);
@@ -77,7 +77,7 @@ DJCi200.init = function() {
     engine.setParameter("[EffectRack1_EffectUnit1]", "mix", 1);
     engine.setParameter("[EffectRack1_EffectUnit2]", "mix", 1);
 
-	// Ask the controller to send all current knob/slider values over MIDI, which will update
+    // Ask the controller to send all current knob/slider values over MIDI, which will update
     // the corresponding GUI controls in MIXXX.
     midi.sendShortMsg(0xB0, 0x7F, 0x7F);
 };
diff --git a/res/controllers/Hercules_DJControl_Inpulse_200.midi.xml b/res/controllers/Hercules_DJControl_Inpulse_200.midi.xml
index 167611dd6..2c9b7634f 100644
--- a/res/controllers/Hercules_DJControl_Inpulse_200.midi.xml
+++ b/res/controllers/Hercules_DJControl_Inpulse_200.midi.xml
@@ -790,7 +790,7 @@
                     <normal />
                 </options>
             </control>
-            
+
             <!--Continuous Controllers (CC) - Faders/knobs -->
             <!-- CC's MIDI Channel 1 (0xB0 Standard mode)-->
             <!--Crossfader-->
@@ -1645,4 +1645,4 @@
             </output>
         </outputs>
     </controller>
-</MixxxMIDIPreset>
\ No newline at end of file
+</MixxxMIDIPreset>

@Holzhaus Holzhaus added this to the 2.2.4 milestone Mar 12, 2020
@DJPhatso
Copy link
Contributor Author

Can copy and paste the diff from the build log into a new file names fix-issues.patch, the run git apply fix-issues.patch? That should resolve the issues.

Let's see if I understand correctly:

  • I should create a new text file called fix-issues.patch, paste the build log into it and save it (in the root of my Mixxx folder i would guess?);

  • Once done, run the command git apply fix-issues.patch.

So I tried that, and I got 'error: corrupt patch at line 61'

@Holzhaus
Copy link
Member

Can copy and paste the diff from the build log into a new file names fix-issues.patch, the run git apply fix-issues.patch? That should resolve the issues.

Let's see if I understand correctly:

  • I should create a new text file called fix-issues.patch, paste the build log into it and save it (in the root of my Mixxx folder i would guess?);

Not the complete build log, just the diff that I copy-and-pasted from the build log to my comment above.

  • Once done, run the command git apply fix-issues.patch.

So I tried that, and I got 'error: corrupt patch at line 61'

You need to copy and paste the complete diff and not add, remove or modify any lines. It works fine for me.

After you've done that, you can delete the fix-issues.patch file and commit the changes.

@DJPhatso
Copy link
Contributor Author

Exactly what I had done. Created a new one just in case, tried again, same error
fix-issues.zip

@Holzhaus
Copy link
Member

Maybe your editor changed the formatting automatically or something like this. In that case download (not copy&paste) this one: https://gist.github.com/Holzhaus/d1c1c10f1b48c1b22961e420c568a67c

@DJPhatso
Copy link
Contributor Author

No better

error: patch failed: res/controllers/Hercules-DJControl-Inpulse-200-script.js:61
error: res/controllers/Hercules-DJControl-Inpulse-200-script.js: patch does not apply

@Holzhaus
Copy link
Member

This patch definitely works fine. Did you change your branch locally (i.e. made changed to the controller script files)? If you didn't commit them yet, you can check with git status.

@DJPhatso
Copy link
Contributor Author

Haven't made any changes since it was committed and status tells me that it is indeed up to date.

@Holzhaus
Copy link
Member

That is super strange. It works fine for me. Anyway, checkout out DJPhatso#6.

Hercules DJControl Inpulse 200: Fix some code stye issues
@Holzhaus
Copy link
Member

Ok, the code style issues seem to be fixed. Ignore the CI build fails - our CI for 2.2 does not work properly. I'll review soon.

Copy link
Member

@Holzhaus Holzhaus left a comment

Choose a reason for hiding this comment

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

@DJPhatso, thanks for contributing this mapping. It's really similar to the Inpulse 300 mapping that was merged a few days ago, so this should be fine. @Be-ing @Swiftb0y Do any of you want to take a look or shall I merge?

@Swiftb0y
Copy link
Member

I'll take a look.

- Corrected a bad assignment  to Effect Rack On/off
- Mapped FX On/Off to both standard and SHIFT mode for the FX pads (related to an upcoming update to the device that will change how the pads work ).
@uklotzde uklotzde modified the milestones: 2.2.4, 2.2.5 Jun 12, 2020
@uklotzde uklotzde modified the milestones: 2.2.5, 2.2.x Jun 12, 2020
Copy link
Member

@Holzhaus Holzhaus left a comment

Choose a reason for hiding this comment

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

LGTM, thank you! Sorry for the delay, I'll go ahead and merge now.

@Holzhaus Holzhaus merged commit c9ef8d8 into mixxxdj:2.2 Jun 12, 2020
@DJPhatso
Copy link
Contributor Author

Thanks Jan.

@uklotzde uklotzde modified the milestones: 2.2.5, 2.3.0 May 11, 2021
@Holzhaus
Copy link
Member

@DJPhatso I just noticed that this controller is lacking documentation in the manual (probably because this was originally merged for 2.2.5, before we added controller documentation in the manual). You could make a PR to the mixxxdj/manual to add it? Something similar to the documentation for the Pioneer DDJ-200 or the Roland DJ-505 would be great.

@DJPhatso
Copy link
Contributor Author

DJPhatso commented May 13, 2021 via email

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