loudsubz wrote:Thanks for all the hard work Ed. I loaded your mappings and started adding to them last night. Few questions and a couple comments.
My pleasure.
Do remember I only hit the high points, there is a LOT more work to be done.
loudsubz wrote:First, here is the layout of the controller for reference:
1. Comment
-I assume the Master and Booth knobs cannot be mapped. I tried reading any MIDI control from them and then looked online and it turns out they are directly connected to the sound card in the controller and don't send any MIDI output? I looked at a VDJ comment about mapping it and one of the guys said it couldn't be done, so I assume the same with CrossDJ.
As the Xponent as a built in 4 output sound card, the booth and master control the volume on one set of outputs, and the headphone volume control on the other. As was mentioned, it's 100% hardware control and not MIDI for those 3 knobs. However, the cue/mix is MIDI.
And I think I had it mapped.
loudsubz wrote:2. Question: Buttons 21 (X and -)
-I tried to map these buttons but when I press them, I see the screen behind the mapping screen flash green for a second like it is receiving a command, but nothing shows up in the available preset box like it didn't understand the command it received from the controller?
In Torq 2.0 these are used for deck switch, prior to that they were used for quick scratch. I haven't mapped these buttons to anything yet - the mapping is still in it's infancy so I only hit the base functionality so far.
loudsubz wrote:3. Question: Buttons 36 (buttons 1,2,3,4)
-In torq you have the option to set the loop length by bars. I see in Cross you can increase or decrease loop length but can you tell it exactly how many bars you want?
This was answered by support... but it's something I'm looking into.
loudsubz wrote:4. Question: Buttons 31 (control cue)
-I am trying to use buttons 1 to 5 as cue points in the program. I was able to use them properly and had 5 cue points tested, but I am having a hard time delecting the set cue points without having to use my mouse and clicking the X on the screen. It says I can press the shift key + the cue point I want to delete the cue point, but how do I map the shift key in Cross? I searched for the command shift and only saw something that mentioned Shift Logic etc but when I mapped it to one of those it still didn't work. The shift key is button 15 on the map.
I mapped in the cue points on my update (it wasn't in the original IIRC). The challenge is that within Torq you had a place to capture the MIDI values for shift - and they did some creative stuff behind the scenes that's not easy to find out.
The shift buttons send the same MIDI message but on different channels, which means they're different as far as most software is concerned. Programming them to respond the same way isn't difficult, but what it means is that you may have to double the number of programming statements to match each of the modifiers. Since I'm relatively new to Cross myself, I'm still learning the workflow but hope to implement much of this between now and this weekend. I'm asking questions and getting lots of help when I'm hung up on something.
Next is the LED's for where you are in the song, and then on to more stuff.
Like effects, filters, cue points, etc. Part of the challenge it going to be determining what to map where.
loudsubz wrote:Other than that I am really happy with the software. Very easy to use, the auto loop works amazing, no hiccups except for one small issue at the end, and I am not sure if I did something, but after mapping all my buttons I went to close down the preference screen and pressed a few buttons and noticed nothing was working anymore except the basics like play/pause, cue, fader etc. I checked my MIDI mappings and they were still good and setup so I am not sure why it stopped working all together. I will give it a go tonight and check again.
I still have to see if CrossDJ supports some of the same features as Torq so I can map all the buttons but so far so good.
It supports many of the actual performance items. So far the big one is MIDI Beat Clock, but not everyone uses it. Another is snapshots but there is a macro function that may work similarly. Still need to find out about beat markers and warping tracks on the fly or having the effects follow the tempo... but I'll get to it eventually.
Although the fact that Cross supports video is HUGE. Torq didn't (even though it was owned by Avid - and it's not like they know anything about video..
).
As for the problem you had, if you had an Xponent mapping and created a second one and selected it by accident, it can cause that to happen.
You can get my latest mapping in the other thread I have... and I'll be doing a lot more changes tonight to get this closer to being usable.
