IBOBGG wrote:T5 Results
LOOP SIZE ENCODER - is in constant off display, even when the loop is activated..
This was an attempt to do what you wanted. I tried but as it turns out Cross does not support LED out put from logic selection conditions.
Translation= Have to go back to displaying the loop size only when the loop is active.
IBOBGG wrote:LOOPING AND CUE POINTS -
I've loaded the same song into both Player A and B
Pads 1-7 are cue points = RED
Pad - 8 is a loop = BLUE (No flashing) good stuff.
Good, however let us get in the same terms for rest of our conversations. Based on the documentation the numbering system for the controller counts the pads left to right and bottom to top.
13 14 15 16
9 10 11 12
5 6 7 8
1 2 3 4
IBOBGG wrote:I've launched the app OVER 8 times and sometimes get different results for Player B (Player B is the problem).
Looking into the code for conflicts, so far all LED mapping for locators appears to be correct.
I will go through the pages. With pads 1-16 as numbers.
IBOBGG wrote:HOT CUE PAGE
PLAYER A -
OFF PADS = 9,10,11,12,13,14,15,16
RED PADS = 1,2,3,4,5,6,7 .
BLUE PAD = 8
Base on your numbering system that is correct.
IBOBGG wrote:PLAYER B -
OFF PADS = 9,10,11,12,13,14,15,16
RED PADS = 1,6 .
BLUE PAD = 0
Looking into this, so far nothing.
IBOBGG wrote:LOOP PAGE
PLAYER A -
OFF PADS = 1,2,3,4,5,6,7,8,11,15
RED PADS = 9,12,14
BLUE PADS =10,13,16
Keep in mind the numbering system I mention before.
The top 8 Pads control and display loop sizes
2 4 8 16
1 1/2 1/4 1/8
The bottom 8 pads are mapped for manual loop operation as follow
Loopin Loopout Loop on/off Loop double
AutoLoopselect - Autoloopselect + Reloop on/off Loop halve
Any button representing an initial action or an increase will be displayed red. So in your numbering system
pads
9 = Loopin = red
12 = Loop double =red
14 = Autoloop select + = red
That is the expected result.
Any button representing an decrease will be displayed blue. So in your numbering system
10 = Loop out = blue
13 = Autoloop select - = blue
16 = Loop halve = blue
That is the expected result.
IBOBGG wrote:PLAYER B -
OFF PADS = 1,2,3,4,5,6,7,8,11,13,14,15,16
RED PADS = 9,12
BLUE PADS = 10
Again the B side is mapped the same as the A side and the loop page is the only one that does not display cue points.
Now I can change the top 8 pads to display cue points just as the cue and sampler pages and the bottom 8 pads to display and control 8 selected loops.
IBOBGG wrote:SLICER PAGE
PLAYER A -
OFF PADS = 9,10,11,12,13,14,15,16
RED PADS = 1,2,3,4,5,6,7,
BLUE PADS = 8
The slicer page display the cue points in the top 8 and the activated sampler pad on the bottom 8. Based on the loaded track as you stated. red pads are displaying cue points, red is displayed
a loop as a locator point and the bottom 8 pads are off until a sample pad is pressed.
The idea in the Sampler and SLICER pages is to provide the cue points (locators) in the same page as the SLICER or sampler pads without having to change modes.
IBOBGG wrote:Also, in the T4 sampler page, the hot sample pads would all light up when launched = Pads 9,10,11,12,13,14,15,16 - Thats stopped working in T5 for Player A and B.
The previous configuration in T4 was too much of a power draw. What I can do is to have light up at a lower intensity when loaded and come up to full intensity when actively playing the pad.
Let me know your preferences.
I forgot to mention that Hercules Company saw our comment in this thread and are offering to ship a P32 to me so I can have the benefit of having the physical controller and map it really well.