Code Monkey home page Code Monkey logo

fltouch's Introduction

fltouch

FL Studio MIDI scripts for the Behringer X-Touch + extender(s) (Mackie Control Universal) MIDI controllers, based on the official scripts by Image-Line.

Differences with the official scripts

  • Support for multiple extenders
  • Support for colored scribble strips
  • Improved knob resolution and acceleration
  • Improved jog wheel with automatic window focus
  • Jog wheel will seek by default
  • Auto channel selection when touching a fader
  • Make use of the full scribble strip width
  • Meter values are more accurate
  • The clip led works when the signal is clipping
  • Smoothing is disabled by default
  • Sliders now function in free control mode
  • Changing the tempo using the jog wheel now works
  • Added basic scrubbing functionality, hold shift for more accuracy
  • Name/Value button can now be used to rename tracks
  • Various bugfixes and improvements

More improvements later...

How to use

Installation

  1. This script uses the Mackie Control Universal (MCU) protocol. Your X-Touch and the extenders will need to be set to MCU mode. To do so,

    • Start with the device turned off
    • While holding down the SELECT button for channel 1, push the power switch
    • Rotate encoder 1 to set the mode to MC.
    • Rotate encoder 2 to select the interface to use (e.g. USB).
    • Pres the SELECT button for channel 1 to confirm settings.
    • The unit will now boot.
    • For more info, check out "Step 3: Getting started" in the official quick-start guide, p. 24.
  2. Download all files in this repository (Code -> Download ZIP). From the ZIP archive, copy all the files in the fltouch-main folder to your FL Studio Scripts folder, in a dedicated subfolder. Usually this would be:

  • Windows: %UserProfile%\Documents\Image-Line\Data\FL Studio\Settings\Hardware\fltouch
  • MacOS: ~/Image-Line/FL Studio/Settings/Hardware/fltouch
  1. In FL Studio's MIDI settings (Options -> Midi settings), you'll find your "X-Touch" and "X-Touch-Ext" controllers. Set your X-Touch's MIDI channel to 102 and the extenders to 103, 104, ... and change the controller type to "FLtouch X-Touch" or "FLtouch X-Touch Extender" (depending on if the device is an extender or not).

FL Studio Midi Settings Screen

If these instructions are unclear, you can find a more detailed guide by Zizzer Productions here.

Layout

You can print an overlay for this controller, courtesy of Bobby-Funk. The image must be printed 15.7956cm / 6.21875 inches wide in an A4 size.

271434055-cf50ff29-7763-49e1-a738-79fe292ccb69

Video

Using the Behringer X-Touch with FL Studio

fltouch's People

Contributors

bramdebouvere avatar casperlehmann avatar rtosman avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

fltouch's Issues

Script name needs to change to a unique name

Currently the script is using the same name as the MCU. We should give it a new name, so it definitely does not get overwritten by the new script auto update in the latest FL studio release.

The "Smooth" function creates a weird delay

By default the smooth function is enabled and it always seems to create a weird delay on the leds.
So far I have not noticed any upside when enabling smooth on the X-touch, so I will either remove it completely, or take the non-smooth as default mode.

xtouch script issues

hey, I've followed all of the steps on the github but there is no folder "fltouch" in my hardware holder.
I just created and named the folder, then populated it wit the filed from the zip folder.
'fltouch xtouch (user) showed up in controller type in fl settings, but when I selected it- the xtouch immediately disconnects showing blank screens..
I'd love this to work, as the color organization is a huge part of my workflow.
any help is appreciated.
(btw listened to your work on spotify, Bram, Dope!)

Enhancement - Update the "FREE" page to control plugins.

Suggestion / idea: taking the "FREE" page and making this work with some basic plugins (reverb, compression).

I tried manually linking the sliders and knobs in Fruity Reverb 2 to the controller and it worked... except that it was tied to that specific instance (the fruity reverb 2 thats on the track). if i change tracks and open another fruity reverb 2, it still just changes the values in the original / first instance of the plugin.

ideally we could use 16 faders, knobs and buttons to control a few common plugins. so the workflow would be to turn a plugin on or off on the "PLUGIN" page, then go to the FREE (INST on the controller) page, and tweak plugin settings for the selected track.

thoughts? is there a better way? maybe handle it all on the plugins page?

@bramdebouvere any thoughts on how to make this work?
i don't mind taking a stab if you could point me in the right direction as a starting point

Faders are resisting

Hello!
I've been using your script for my X-touch for a few months now. And it always worked. But, recently, I just bought a new MIDI controller... Since I started using it, the xtouch never worked normally again, even after resetting everything and removing the other device. I never changed any settings.

The problem is:
-The faders are resisting to my movement in every situation, even in the "free mode" impossible to use it then.

What I tried:
-Updating the xtouch firmware
-Trying in others DAWs -> works perfectly
-Trying the official Mackie control script from Image-Line -> Still the same problem
-Trying to delete the USB bus port in Windows settings and reinstall those
-Trying to change the UBS cable, and plugging it in different USB ports
-Fully re-install FL STUDIO with stock settings

I was thinking that maybe disabling the motors will change something... but I don't know how

I have no idea what is going on, or if it's your script or not. If you have any suggestion, or ideas, it would save my life!

Regards,
RAYES

Reprogram some of the buttons

Some of the labels on the buttons of the main controller totally do not match the features they execute.
We should attempt to make the functions execute what's displayed on the labels as much as possible.

A 1:1 will probably be hard, but we can reprogram some of the buttons and functions.

In the image below you will see the difference beetween the labels and the MCU mode in FL studio

afbeelding

Refactor scripts

The scrips that were provided by Image-Line are not very structured and need some refactoring.

Can't link to XTouch

I downloaded the zip, copied everything to D:\Libraries\Documents\Image-Line\Data\FL Studio\Settings\Hardware\fltouch
(I moved my libraries to a separate HDD since I have Windows on a SSD but with less capacity)

When I open FL studio it shows 4 new device types
FLTouch X-touch (user)
FLTouch X-touch (factory)
FLTouch X-touch Extender (user)
FLTouch X-touch Extender (factory)

xtouch 01

I'm trying both FLTouch X-touch (user) and (factory), set the MIDI channel to 102 and tried activating/deactivating the "Send master sync" button

image

After that, the XTouch doesn't respond. If I move a fader, it goes back to its original position and no button seems to work at all

If I go back to Mackie Control Universal, the XTouch works as expected

XTouch is in Mode = MC and IFC = USB
I'm using Windows 11

Not sure if the fact that FL Studio is installed in C: and all the user data is in D: is interfering

Scrub doesn't work as expected

Using the scrub button does not do anything scrub-like, but just zooms.

It should at least go trough the playlist slower than when you just use the Jog wheel, but a real scrub functionality would be best (but I don't know if this is possible in FL studio).

Coding Xtouch universal controler Faders to Link Properly

Hey. I'm sorry that I have to bug you with this request but i'm lacking in options. I'm using FL STUDIO. When I click the INST button at the top of the xtouch controller, it gives me the option of free knobs and faders to link to whatever parameter I choose. However, only the knobs seem to link correctly. When I try to link a Fader, the parameter just goes to 0%. Goes right to the bottom everytime. Can you write anything to fix this?

Language issue

Hello!

Thanks for the great work by creating this awesome script!
Having an issue displaying track names when they are named not in English.
For example, I name channel 14 a non-English name and when I switch the faders page from 1st to 2nd (to access channels 9 to 16), the fader page changes, but the names of all channels remain the same (from 1st to 8th).
Is there a way to add support of any other language but English?
If this is possible, please describe how to do it.
Big thanx in advance!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.