Mixvibes Dj Community old forum

In fam(Player)[0x1].BeatGridShirnkExpand (Integer)

I found couple of entries like this one in the listing. Please notice

BeatGridShirnkExpand should be
BeatGridShrinkExpand

I don't know if it is this way in the mapping utility but it is in the 1st posting for this thread.

Not being critical I just wanted to let someone know.

Thanks for pointing that out.
It amazes me how something so small can create such a huge headache. I wasted about 2hrs the other day trying to figure out why a led just wouldn't light up. Only to realize I had made a small typo in the alias. I wanted to kick myself!!

acemc wrote:Thanks for pointing that out.
It amazes me how something so small can create such a huge headache. I wasted about 2hrs the other day trying to figure out why a led just wouldn't light up. Only to realize I had made a small typo in the alias. I wanted to kick myself!!

Wellcome to the MIDI Mapping makers Mate You need to suffer to be good at it XD

FigDJ wrote:

In fam(Player)[0x1].BeatGridShirnkExpand (Integer)

I found couple of entries like this one in the listing. Please notice

BeatGridShirnkExpand should be
BeatGridShrinkExpand

I don't know if it is this way in the mapping utility but it is in the 1st posting for this thread.

Not being critical I just wanted to let someone know.

The typo was is in Cross, both aliases should work from 2.3.1, the erroneous one still being there only for backward compatibility

Can anyone please explain the differences between these 2 alias's.
DisplayCueOutput & CueStateOutput?

I'm not sure.

I know the CueStateOutput is the older one, which works fine. YOu can custom create lighting for your Cue states.

I belive DisplayCueOutput just follows the Cue state on the Screen of Cross.

...but correct me if I'm wrong.

That's CueDisplayOutput, and yes it follows the screen button state (no need to configure the blinking as with CueStateOutput).

no need to configure the blinking as with CueStateOutput

That's exactly what I was hoping. Thanks!!

Update - By using the "CueDisplayOut" I now (finally) have flashing cue led's that mimic the on screen state on my NS6.
I really do feel a document of some sort should be compiled explaining the functionality of the output commands. This is only valid if the MIDI output is gonna remain the same in future versions I guess. But until it changes / gets updated a basic explanation of the less obvious alias's & value's would be great. Eg: (Logic) value = true / false ; (Integer) value = numbers ; (Normal) value = ???? ; Delay A / B = ? ; InvertedPitchValue = ? etc....

OK this may be a little long winded but any help is greatly appreciated.

I wanted to individually select effects with a set of 8 pads. To that end I implemented the following code.

Code: Select all

 <mapping>
   <events>
    <MIDI type="Note" parameter="0x3a" modifiers="ML2" channel="0x1"/>
    </events>
    <controls>
      <control alias="fam(Fx)[0x1].SelectAndToggle"/>
     </controls>
     <preset name="Direct Integer Button">
         <parameters>
          <parameter object="action-0" key="integer" value="7"/>
          <parameter object="dispatch" key="interpretCCasNote" value="off"/>
         </parameters>
      </preset>
 </mapping>


The code allows me to auto select a specific FX and toggle the FX on.

To light up the corresponding pad i implemented the following
code

Code: Select all

<mapping>
 <control alias="fam(Fx)[0x1].Select" value="7"/>
   <MIDI type="Note" parameter="0x9" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0xb" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0xd" channel="0x1" value="127"/>
   <MIDI type="Note" parameter="0xf" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0x1" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0x3" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0x5" channel="0x1" value="0"/>
   <MIDI type="Note" parameter="0x7" channel="0x1" value="0"/>
</mapping>


This allows me to light up the correct pad and turn of the other ones off when the Fx select value of 7 is receiced.
Once I am done with the effect I hit the same pad once more and the effect is turned off.

My problem is that once I hit the pad a second time the effect is turning off but not the light.

I was trying to use code below to turn all 8 pads off when the FX on/off was not set. But it is not working. It almost seem like the fx onoff logic is set or not set correctly within Cross UI but not on the output flag when done using fam(Fx)[0x1].SelectAndToggle
Any ideas?

Code: Select all

<mapping>
  <control alias="fam(Fx)[0x1].OnOff" value="false"/>
    <MIDI type="Note" parameter="0x9" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0xb" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0xd" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0xf" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0x1" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0x3" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0x5" channel="0x1" value="0"/>
    <MIDI type="Note" parameter="0x7" channel="0x1" value="0"/>
</mapping>