Statistics

249,687 members
126,737 posts
  • New
    EmotiveSigns
    Newcomer - Level 1
    2021-03-30

    Hi - 

    I have been using logic pro for years. For musical input I use a MK-425C keyboard which has worked perfectly. Recently I bought a x-touch and since adding that when I press a key on the keyboard strange behaviour occurs, such as it triggers a different layout, rather than playing the notes. 

    Can anyone help explain this problem and possibly help me fix it?

    Thanks in advance,

    Charles

    read more...
    0 58
    • EmotiveSigns
      NicJonesMT Hi Charles. Ideally it would be easier to help if I could see how you have both devices setup and configured in Logic.
      Could you please submit a tech support ticket (Click support above) and provide some screen shots of your setup?
      • Mar 30
  • New
    EmotiveSigns
    Newcomer - Level 1
    2021-03-30

    Hi

    I've recently got an X-touch which i'm loving. This maybe my misunderstanding but I'm assuming the modify buttons work the same as the keys on the keyboard. However when I press and hold the option key, and click on a track I would assume it would allow me to drag and copy that section to another track. However it seems only to grag and move instead. I've played about with all the buttons and they don't seem to behaviour in that way. 

    Should I be able to use these buttons instead of the keys on the keyboard. If so what am I doing wrong?

    Any help would be gratefully appreciated,

    Thanks in advance,

    Charles

    read more...
    0 55
  • New
    BenH
    Newcomer - Level 1
    2021-03-16

    Hi,

    Can the X-Touch select which side the X-Touch Extender is on?

    It seems by default to cascade to the right.  Can it be switched so that the Extender flows from the left side, so that track 1 is on the Extender, and Track 9 is on the X-Touch, and plug-in parameters flow similarly?

     

    Thanks

    Ben

    read more...
    0 58
    • BenH
      NicJonesMT Hi Ben.
      It is dependent on how you setup your control surfaces in your DAW.
      So for example if you are using Cubase, you need to set the Extender as the 1st device.

      Some DAW's also have a "Channel Offset" Option which you can use aswell, but this is DAW dependent.

      What I would recommend is contacting the DAW developer to see if they can assist you with any additional settings.
      • Mar 16
  • New
    RichardJones
    Newcomer - Level 1
    2021-03-11

    Hi folks,

    Just got my X-Touch and was using Tracktion 7.

    Adding the X-Touch as a control surface (Mackie Control Universal) in Tracktion 7:

    • In / Out markers on F3 & F4 keys - works
    • Touch fader track select - doesn't work

     

    Waveform 11 (Mackie Control Universal)

    • In / Out markers don't seem to work
    • Touch fader track select - works

     

    I was thinking of creating a brand new mapping but am having the following problems:

    1. Moving a fader doesn't register as a controller change (I have to touch it with a cloth to stop the 'touch' grabbing the control!)

    2. I can't get the job wheel to function properly. It jogs forward, but goes back home when I jog backwards.

    Anyone else using this same setup would be great to hear from youi!

    Thanks!

    Richard

    read more...
    0 57
    • RichardJones
      RichardJones Have solved one of the original problems, Waveform gets confused when the mouse is over the track and shows another bar line in addition to the one that's positioned by the jog wheel. Solution - move the mouse out of the track area ...
      • Mar 11
  • New
    bobbyval
    Newcomer - Level 1
    2021-03-08

    THis control surface had been working seamlessly with Presonus Studio One 5 on my Macbook Pro running Mac Os Mojave. I recently purchased a Mac Mini 2018, which came with Mac Os Big Sur already installed. I have since reconnected all of my audio and midi hardware to the Mac Mini and come to find that the Xtouch Compact is no longer responding in Studio One 5. Presonus states that the issue is with Behringer and that many third party developers are having a challenging time with Big Sur compatiblity. Has anyone else seen this issue with the Xtouch Compact and Mac Os Big Sur?

    read more...
    0 60
    • bobbyval
      PedroRodrigues Hi bobbyval, please consider that when it comes to implement any of our units on MacOS11 / Big Sur, consider that, at this moment none of our units is compatible and when interfaced with this OSX version will lead to issues. and my not work.
      However, USB audio/MIDI function of our products is fully USB 2.0 compliant and should keep working under CoreAudio as before.
      • Mar 9
    • bobbyval
      bobbyval I have an update to this thread and issue! It is not a Behringer Xtouch problem and Big Sur, Mac Mini, etc! It is a Presonus Studio One 5 and their support of Big Sur issue, even though they have continued to deny it! Here is how I have come to this conclusion. In an attempt to reproduce the non-responsive Xtouch Compact on my system, I took the liberty of downloading Cubase 11 (which I already have a license for ) and installed it on this computer. After a few clicks in the studio setup dialog, the Xtouch Compact came to life with all faders and lights active! I wasted so much time with Presonus and them telling me quite convincingly that it was Behringer's problem.
      • Mar 23
  • New
    chuckster101
    Contributor - Level 1
    2021-03-08

    Hi, 

    Is the X Touch controller compatible with Ipad (IOS) as I use Cubasis.

    BW

    Chuck 

    Somerset 

    0 76
    • chuckster101
      DavidKnighton Hi Chuck,
      I think the true question you're asking is, "is the X Touch compatible with iPad (iOS)"? The short answer is yes, but it gets a little complicated. The X Touch can output MIDI data to the iPad via a MIDI to Apple-connector-of-the-week cable. For example, you can use the MIDI to Lighting adapter here: https://www.iconnectivity.com/products/midi/iconnectmidi1. The same brand also has a MIDI to USB-C connector in an adjacent link. MIDI is a standard protocol, meaning it's the same language for any device or software. You will likely need to program Cubasis to recognize the incoming MIDI data, or as most folks will call it MAPPING the hardware to the software. For more information on this, I would suggest jumping on a Cubasis forum and see what the broader community has to offer. Check out this thread here: https://forum.audiob.us/discussion/37308/midi-learn-midi-assignment-cubasis-3
      • Mar 8
  • New
    FlipF
    Newcomer - Level 1
    2021-02-26

    My Wing was just returned from replacing the warranted malfunctioning touch screen, and now the headphone jacks built in on either side of the console are not working.  I pressed the Monitor Section 'View' and confirmed there is signal.  I also plugged the headphones directly into AUX OUT 7 & 8 which had sound.  I would appreciate any thoughts on what else to try.  

    Thanks

    read more...
    0 127
    • FlipF
      GaryHiggins Mon A (headphones) needs to be routed to aux7/8 and Mon A needs to be the focus..maybe it got changed somehow. I think B is for monitor speakers and C is both...
      • Feb 26
    • FlipF
      FlipF Mon A is routed to AUX OUT 7/8 (See photo). I did not change anything on my settings, and even tried reloading ‘snapshots’ in case something was just hung up somehow...
      • Feb 26
      • Behringer Wing built-in headphone jacks not working
        GaryHiggins Have you always had mon B on aux 1/2? How is your monitor set A, B or C? Mine does not have that for 1/2, and is on A. Curious if that might be it, sorry. Another thought is maybe initialize it, and check it (with all your scenes stored safely) Also what firmware?
        • Feb 26
      • Behringer Wing built-in headphone jacks not working
        FlipF First, thanks for continuing to throw out some ideas!
        • Feb 26
      • Behringer Wing built-in headphone jacks not working
        FlipF Yes, I use Aux 1/2 for studio monitors and I have the monitor set on A for headphones, but I also use B and A+B depending on what I’m doing. I’ve tried all of them.
        I tried to re-initialize it and nothing changed. I am using the latest firmware 1.10.1.
        .
        • Feb 26
      • Behringer Wing built-in headphone jacks not working
        GaryHiggins Wow...2 last ideas. Try unrouting aux 1/2. I kind of recall having an issue with using both and getting problems at one time, maybe it was a setting...or maybe I dreamt it. Worth a shot. Last but not least. If you want to post your snap, I will load it and see if I can still hear my phones...that would eliminate some odd setting in your setup. If mine works I would say maybe you need to send it out again....REAL BUMMER...hope not. I will look around my desk some more, maybe I see something else. BTW, you can attach the snap (I think) on your original post by using the edit button. The original poster supposedly can do this.
        • Feb 27
    • FlipF
      FlipF I already tried it with and without Aux 1/2 assigned but no change. I just did it again to make sure.
      Also, I tried to upload a snapshot but it said it’s an invalid file type.
      • Feb 27
    • FlipF
      FlipF I’ve tried it with and without the monitors assigned to Aux 1/2. It made no difference. I just tried it again just to be sure.

      I also tried to upload a snapshot, but it said it’s an invalid file type, or something like that. It won’t upload.

      I really appreciate you trying to sort this out. It’s very frustrating, and the lack of ability to reach Technical Support in a reasonable time frame (and only via email), is just making it all worse. It took just under a month to get the screen replaced, and I can’t afford that kind of downtime, let alone to do it again if it does indeed need to be shipped back. I keep hoping I’ve just done something dumb and it’s easily fixable…

      Thanks again!
      • Feb 27
    • FlipF
      FlipF Now, as I finished posting, and went back recording, the touchscreen FROZE!!! I had to turn the machine off and restart it to get it to work.
      • Feb 27
      • Behringer Wing built-in headphone jacks not working
        GaryHiggins Sorry, have you tried reloading that firmware again, or an earlier version? You can use Dropbox or similar, copy the link in your post. We do that here often. You have to attach from your original opening thread, can’t do it on later ones so I’ve heard. Dropbox links will work any time. .
        • Feb 27
  • New
    Robbinsegg1
    Newcomer - Level 1
    2021-02-19

    I am trying to find out a way to change the footswitch function to punch in/punch out.

    Behringer has a program that allows this for the regular X Touch, but it seems there isn't one for the X Touch One.

    I haven't found any documentation for this, can anyone help me?

    read more...
    0 154
    • Robbinsegg1
      WilliamR 1. The device ID for x-touch one is 0x41
      2. Make sure the x-touch one is in MIDI or CC mode, otherwise it will behave like a Mackie unit with emulation of the 8 fader blocks
      Protocol in MIDI/CC mode:
      X-Touch-one MIDI mode implementation:
      Buttons (standard MIDI mode):
      - Note on #0..34 (push: velocity 127, release: velocity 0)
      Buttons (MIDI CC mode):
      - CC #0..34 (push: value 127, release: value 0)
      Button Leds:
      - Note on #0..34 (velocity 0..63: off, velocity 64: flash, velocity
      65..127: on)
      - CC #0..34 (value 0..63: off, value 64: flash, value 65..127: on)
      Fader:
      - Control change 70 (receive and transmit)
      Fader Touch:
      - Note on #110 (touch: velocity 127, release: velocity 0)
      Encoder:
      - absolute mode: Control change 80 (value 0..127)
      - relative mode: Control change 80 (increment: value 65, decrement: value 1)
      Encoder Ring:
      - Control change 80 (value 0..127)
      Jog Wheel:
      - Control change 88 (turn CW: value 65, CCW: value 1)
      Meter Leds:
      - Control change 90 (value 0..127)
      Foot Switch:
      - Control change 64 (push: velocity 127, release: velocity 0)
      LCD:
      - sysex (hex) F0 00 20 32 41 4C 00 cc c1 .. c14 F7
        - cc: bits 0-2: backlight color (black, red, green, yellow, blue, magenta, cyan, white)
        - cc: bit 4: invert upper half of LCD
        - cc: bit 5: invert lower half of LCD
        - c1..c14: ascii characters (1..7: upper half, 8..14: lower half)
      Segment Displays:
      - sysex (hex) F0 00 20 32 41 37 s1 .. s12 d1 d2 F7
        - s1..s12: segment data (bit 0: segment a, .. bit 6: segment g)
        - d1: dots for displays 1..7 (bit 0: display 1, .. bit 6: display 7)
        - d2: dots for displays 8..12 (bit 0: display 8, .. bit 4: display 12)
      • Feb 19
    • Robbinsegg1
      Robbinsegg1 I thank you for replying. Sadly I’m not savvy on how to implement all of this info you’ve kindly supplied. The unit works as normal except for the footswitch, as far as I can tell. The way it behaves when the pedal is pressed is it goes into a rapid play stop, play stop, over and over. The only way to stop it is to unplug the pedal. I Logic Pro I tried to learn the pedal for record Toggle, but the same thing happens, just flashing repeated rapid record/stop instead.
      • Feb 19
  • New
    SpockAndStepR
    Newcomer - Level 1
    2021-01-29

    can someone send me the Controller addresses for the Behringer Odyssey? I've been trying to automate some parameters in my DAW and I haven't been able to find the controller addresses in the manual.

    0 52
    • SpockAndStepR
      DavidKnighton Hello Spock,
      I'm not certain you can automate parameters on the Odyssey. It's completely analog workflow, no digital controls. What exactly are you hoping to automate with this synth?
      • Jan 29
      • Behringer Odyssey Controller addresses
        SpockAndStepR the filter frequency. I was watching a tutorial on how to route midi from FL studio to my analog synthesizer, (it worked) and while I was watching it, it said that I could "control" any parameter of an analog synth by finding out the Controller addresses... if my initial post was worded kinda weird, here's a link to the video:
        https://youtu.be/xRRaeCw7P2Y?t=111
        • Jan 29
  • New
    danbaileyak
    Newcomer - Level 1
    2021-01-29

    Hello, I recently purchaed an X Touch One, and according to the instructions, I should be able to use a standard midi sustain pedal as a record-toggle footswitch with Logic Pro X. However, when I plug a pedal into the jack on the back of the unit and press the footswitch, the unit seems to get confused. It gets stuck in a glitchy recording loop inside Logic Pro, and the lights on the X Touch One go all haywire. The only remedy is to power off the unit and unplug the footswitch.

    I've tried using two different footswtiches, both standard 1/4" midi sustain pedals, and the unit exhibits the same behavoir, no matter which one is connected. Please note, I'm running the X Touch One firmware to the latest version (v.1.08) and using the X Touch One in the Logic configuration.

    Am I missing something? Is there anything specific I need to do inside Logic to properly set up the unit so it recognizes the record-toggle command doesn't get confused? Or do I have a defective unit.

    Thanks,

    Dan B.

    read more...
    0 305
    • danbaileyak
      PedroRodrigues Hi danbaileyak, I believe you have the unit on MC mode to operate with LOGIC have you tried to set up the unit in MIDI mode to control your pedal.
      If you are using the X-TOUCH ONE in a MIDI mode, select it in your DAW as a MIDI controller. Please confirm with your DAW’s MIDI Learn functions, and you will be able to map each button and feature of the X-TOUCH ONE to a function and control on your DAW.
      Please assign the unit to MIDI mode and please confirm that you have assigned the following message for your pedal as per below :
      MIDI Send CC
      Foot Switch: Control Change 64 (push: value 127, release: value 0)
      MIDI Send Note
      Foot Switch: Control Change 64 (push: value 127, release: value 0)
      I hope this helps
      • Jan 29
    • danbaileyak
      danbaileyak Thank you for getting back to me. I am currently using the X Touch One in LOGIC Mode. I prefer to use it this way, so that I don't have to reassign all of the buttons on the unit. By default, in Logic Mode, Pedal A is set to "Play or Stop," but as you saw in my video, this doesn't seem to work correctly. If I plug the footswitch into a different midi interface, I can get it to work just fine, so that's why I'm wondering if there's something wrong with my X Touch One, or if it simply doesn't work properly with the sustain pedal footswitch.
      • Jan 29
      • X Touch One Footswitch Problem
        PedroRodrigues Hi danbaileyak, form your description it seem that this is a matter that is related with your DAW MIDI implementation, as you stated the unit work with the Pedal work just not the way you wish to implement. I this case I would suggest to search for information on LOGIC support. Thank you
        • Feb 2
Go to page