Midi Controler with dot2

  • I work, some work, and some not. Can I assign to fader in APC Fader MASTER and XFade?
    Why note 125 in dot2, after the first use, (on my APC button stop), are still on? One press causes two changes, for example if the Go button is assigned to it, pressing changes to cue1 and releasing to cue2. Why does the play on APC button exit the router out, and play and rec midi out?

  • So, my file isn't 100% mapped. Some of the APC40 in that file still isn't actually mapped. So, that may be confusing. Plus some of the ones not mapped naturally work, but may be several of them are mapped to the same note, which is super confusing.



    I've done more mapping since I uploaded that file. I can try to share the new file today/tonight.


    In BOME, I tried to name the translators effectively so that you can see what is mapped. Take a look at them and see if the button you're trying to use is mapped.


    In that file, I think I had mapped:
    Clip Lanches - ALL
    Scene Launches - ALL
    Activators: maybe just 1-4 or so
    Faders 1-8+master
    Cross Fader, Play, Stop, Rec
    FS1 and FS2 on the back (near power button, but need an external switch to actuate)



    That may be all that is mapped. I can't remember where I was.
    Maybe Track Control knobs 1, 2 might be mapped.


    The incompleteness may be confusing about that file.

  • I work, some work, and some not. Can I assign to fader in APC Fader MASTER and XFade?
    Why note 125 in dot2, after the first use, (on my APC button stop), are still on? One press causes two changes, for example if the Go button is assigned to it, pressing changes to cue1 and releasing to cue2. Why does the play on APC button exit the router out, and play and rec midi out?

    I'm not sure I fully understand. I'll have to look at my file. Some of the buttons on the APC have an on+off for each push, others have just an on, then another push yields an off. BOME can change all of that to anything you want, but I have mapped them as they work on the APC. For example, the few activators that I've mapped are latching style in the APC, so they are on until you turn them off.


    As I am still just learning this as well and this is only for fun for me, I don't have hours available to commit to studying as much as I'd like, one confusing thing for me was the variable values in BOME. Initially, I just passed the value through the translation, but sometimes that didn't work. It was if the variable would stay 0 or something and it wouldn't cause any action. So, I just hard coded the variables to all be 127 and that seemed to fix my problem. I don't think this is 100% accurate way to translate, but it worked for me. As I mentioned, I wanted to learn dot2, not BOME. So, maybe some of the things I've done aren't perfect in BOME, but they work for me in dot2. I don't think this is causing your troubles, but it may.


    Edit:
    I think I recall some of the inputs staying on endlessly in dot2, but it didn't cause me problems. Let me see if I can confirm that and maybe find something in my file to fix it.

  • Hello Brian.
    For starters, great thanks for your work and for making it available. Respect.


    I do not criticize your work, but I only try to understand what, how, and why it works.


    And since I do not know which buttons you've assigned to which function, so I'm asking about their actions.


    I also asked if it is possible to map Master with dot2 and Xfade?


    And another question. How to connect dot2 with APC? I want to enter a command in the cue and turn on the led light in eg: clip launche.


    If I plug APC directly to dot2, I can do little about it. For example, by typing "MidiNote 53".


    But if I plug in a translator boom, nothing happens. I do not know how to use routing.


    Going back to the matter. I have a problem with the position of the "125" note in dot2 (as in the picture attached). This is the STOP button on APC (obviously translated by bome and I use your file). If I press and hold it, the button performs one action, and when I release it, it triggers the second action. Maybe the STOP button in APC works this way ... But without a translator, it works in a normal way, like PLAY and REC.
    However, I only ask ... and I learn.
    Thank you Brian, good job ...

  • Did you set BOME as your midi translator in dot2 onPC? Don't set it to use APC, set it to use BOME.


    Some keys have an output that will work from APC, but most don't. It may be that you've found one that works. To test, try the top right clip button, then the top, second button. Do they actuate the same input in dot2? If so, you haven't made dot2 use BOME and it is still using APC directly.


    Check out this vid from right about 4:00. He goes into how to connect a device thru BOME to dot2.

  • It is.... which is incorrect.
    So, looking at my translator file, the output of "Clip R1C1" is set to variable pp. That is different than all other outputs, and a mistake from my intentions.
    A good test for you is to change the variable value from pp to 127 in that translator file.
    See if you can do that.
    That should change the way it works and it should be on/off. All others seem to be correct in my current file.


    I'd suggest at least trying to make the change above so you learn a little about the translator, but I've attached my current file below. It's a bit more developed, but because it is done piece by piece, it could probably be in a little better order.
    I've changed the error above.


    For the activators, since they are momentary on/off but I used them as a SELECT 1 THRU 4 kind of command, I made them to be an "on" every touch. Confusing to explain, but makes sense in the way I use them. When I use this button to SELECT 1 THRU 4 and then apply another change, then selection the second actuator, which is SELECT 4 THRU 8, activator 1 is lit on the APC, but 1-4 is not selected anymore. I couldn't tell any way to guarantee that the APC actuator lights would mean that certain fixtures were selected. I just accepted that I'd have to hit it every time and ignore the light is on or not. If you have different plans and want on = on and off = off, just change the translator file's corresponding off translation to a "NOTE OFF" message type.


    Maybe we could share dot2 files well?

  • I find, where is trouble. XFadeStopOn, XFadeStopOff is 2 x NoteOn. I change and now it is work, as i want. 8o
    I wait now for my bome Pro key, i now have only trial. I already bought it, but I have not received it yet. So my work is very annoying because I forget that it turns off and works differently. How do I make a good test file, I will send you a show file from dot2 to see what I want to get, and what I do wrong.
    So far I managed to make a
    sequence on the first executor, where the first sequence illuminates
    the light in the launch clip, the first to the left at the top (CMD
    MidiNote 53), and the last one goes out (CMD MidiNote 53 Off). Unfortunately,
    it only works on the PC, by pressing the APC key, once it works, once
    it does not work, most often not, and do not know what it depends on. I will still try ...
    Regards.

  • You're right, you found another problem of mine! The XFaderStopOff push = on and release = on notes. I had this mapped to a CLEAR CMD. So, effectively I was doing CLEAR, CLEAR with one push and then it was stuck on. I corrected in my file.


    Thank you.


    My show file may be attached. I've never saved one to anywhere other than the native location. I'm not sure if 3D follows, etc.

  • Looks nice :)
    My midi work has been stuck in place for a while now, so I'm working on a console now. But soon I will return to the subject, I already have some idea of feedback to the lights in the controller, but I do not know yet whether it will work. ?(

  • Hello dear. I write to you because I have downloaded your files for bome's midi and I left several errors. how can I get it right. I could send the file. I want it to edit and occupy in AKAI APC MINI. Thank you from Chile