Conversation
It's possible to send different light information when Shift is held. For now we just send the same lights either way.
| } | ||
|
|
||
| HercDJCompact.init = function(id) { | ||
| scratch = false; |
There was a problem hiding this comment.
Should this be an array to keep track of it for each deck?
There was a problem hiding this comment.
Nevermind, I see that this device has a single "Scratch" button for both decks. It'd be helpful to add a comment here about that.
|
Do you plan on documenting this now or when you finish the mapping? There's already a wiki page started for a different, unfinished mapping: http://mixxx.org/wiki/doku.php/hercules_djcontrol_compact |
| } | ||
| } | ||
|
|
||
| if(engine.getValue(input.group, "scratch2_enable")) { |
There was a problem hiding this comment.
IMO the code would be easier to understand if this was moved up above line 52. I wasn't clear what lines 54-56 did until I read this far.
|
Looks good so far other than the minor issues pointed out above. There's not much more to comment on without documentation. |
|
Before @sblaisot has to jump in to say it :P |
I was given this controller by hercules for the purpose of making an official mapping, so yes I'll be documenting it. As I stated this is just an initial commit. |
|
please add file removal from windows uninstaller EDIT : Damn it! @Be-ing has been faster than me ;) |
| "HercDJCompact.OnRecordingStatusChange"); | ||
|
|
||
| // Tell controller to send midi to update knob and slider positions. | ||
| midi.sendShortMsg(0xB0, 0x7F, 0x7F); |
There was a problem hiding this comment.
Cool! I didn't see anything about this in the P32 MIDI documentation, but it works on that too! :)
There was a problem hiding this comment.
yeah it's a great feature. (It was doc'ed in the pdf on hercules' site). I'm really impressed with the midi programming on this controller, a lot of convenience features.
There was a problem hiding this comment.
I tried this with my Electrix Tweaker just to see if it would work but it didn't. Is this a Hercules thing? I think I recall looking at one other mapping that had such a feature, but I don't remember what mapping it was or what MIDI signal was sent.
There was a problem hiding this comment.
my vestax VCI400 just does it on connect, for instance, no midi trigger required. It's certainly not any sort of standard, so I'd guess that someone at Hercules thought it up and they reuse firmwares on multiple devices.
|
notes addressed |
|
Hm, considering this controller lacks a high EQ knob, would it be helpful to (optionally?) map the mid EQ knob to the HPF (QuickEffect parameter3) or QuickEffect superknob? |
|
I am writing a framework for creating "controller preferences," which will allow this type of setting to be changed in the UI. For now I'll add a comment that users can remap the knob with the midi wizard (rather than adding javascript), or maybe even put some comments in the xml about how to do this. When controller prefs comes in, I'll make a proper set of preferences for the knob. It is a little silly that it's set to "mid" :/. |
Awesome!
Sounds good. |
| </options> | ||
| </control> | ||
| <control> | ||
| <group>[EqualizerRack1_[Channel2]_Effect1]</group> |
There was a problem hiding this comment.
Would it be better to use the description element for this? That shows up in the mapping GUI.
There was a problem hiding this comment.
the description tells them to edit the XML, but I don't think that's the place to go into this detail. This comment is right at the top of the file so if someone does get as far as editing the XML, they'll find it (I hope)
There was a problem hiding this comment.
Alright, fine to leave it as is then
|
lgty? |
| <name>Hercules DJControl Compact</name> | ||
| <author>Owen Williams</author> | ||
| <description>Controller mapping for Hercules DJControl Compact. Users | ||
| who want the labelled "mid" knob to adjust high eq instead may use the midi |
|
JSHint warnings: |
|
I'm guessing the beatlooproll_X_activate mappings are for loop mode with shift pressed. Is that correct? Could you document the mapping on http://mixxx.org/wiki/doku.php/hercules_djcontrol_compact ? I think 2x2 tables describing the pad functionality in each mode would be helpful. |
A bit off topic, but how do you intend to implement this? I think passing a QScriptValue containing all the options to the script's init function could work well. |
|
wiki will be updated after this is in. RJ and I have been collaborating on a design for controller preferences, it's similar to what you describe. Once it's settled I'll post the design doc to the mailing list. |
|
ping |
|
As I said before, there isn't much to comment on without having documentation to reference. I can't tell if it looks good unless I wen through the MIDI documentation for this device and compared it to the XML. |
|
you're not expected to go through every button in/out and confirm that it's correct, this review is mostly for the style of the javascript functions. I've gone through all the buttons and functions I've mapped and made sure the controller functions nicely. |
|
updated documentation. Most functions are the same as manual (linked on wiki), differences are noted. http://mixxx.org/wiki/doku.php/djcontrol_compact |
|
Thanks for documenting it. I added pictures of the device to the wiki from the other wiki page, reorganized the page, and made some edits. There is so little information to convey that I think referring users to Hercules' manual is more of an annoyance, so I put the little bit of information from there onto the wiki. Please confirm that it's all correct. I like the way you've mapped the pads in loop mode. That is more flexible than the way described in Hercules' manual. I think it would be a better use of the sampler buttons to map the left side to samplers 1-4 and right side to samplers 5-8. It doesn't look like you have mapped shift+play to anything. I find it useful to map this to After the changes in progress for the effects UI (see PRs #1062, #1063, #1068), I think the mapping for the effects pad mode should be reconsidered. I think enabling deck 1 for EffectUnit1 and deck 2 for EffectUnit 2 in the init function with each side toggling the effects within the EffectUnits would make sense. Shift + a pad could cycle to the next effect. |
|
There's a word or two missing in your edit of the jog wheel instructions: "Enable keylock on a deck by clicking the if you do not want the pitch to change when adjusting the tempo." I'll let you know when I've addressed the notes. |
|
Mixxx only has 4 samplers on startup, so specifying samplers 5-8 causes a warning to appear |
|
Do any of our skins support more than four samplers? It doesn't look like either Latenite nor Deere do |
Fix jog wheels while playing Change samplers, although those samplers don't exist
Create more by setting [Master],num_samplers to 8 in the script's init() function.
Yes, Deere does by flipping through the multiple pages of samplers available. It's clunky, but it's there. |
done |
|
LGTM 👍 |
I need to do a little testing but I think this is good enough for initial commit.
feel free to bikeshed the naming scheme