Bitwig

tomsa · Post by **tomsa** » Tue Apr 21, 2015 7:46 am

webhamster wrote:When you put other scripts in that folder do they work?

As far as I understand the scripting language there shouldn't be any difference between OSX/Linux/Windows, but maybe there is some difference that I am not aware of.

Have any other people tested it? Would love to hear. Maybe that'll give a clue to the Linux version.

Yes, all of my other scripts work. I can successfully use Livid Base II, Livid Guitar Wing, Novation SL MkII, Faderport w/Mackie MCU script, Akai MPK Mini, Generic Keys, and Generic Keys +8 knobs. The only scripts that I have tried that haven't worked, other than yours for the faderport, are the Touch OSC and Liine Lemur scripts- but that is largely because I haven't managed to get any sort of USB/MIDI bridge working in Linux and there is no OSC support in Bitwig yet. Those last two simply have not been worth the trouble because everything else is working for me so well.

The only thing that I can think of that would cause any problems for me with your script in Linux would be a users/groups or file permissions issue. It also might be conflicting with the existing Mackie MCU script, since yours requires the Faderport to be in Mackie MCU mode as well. Thoughts?

ThomasHelzle · Post by **ThomasHelzle** » Tue Apr 21, 2015 7:13 pm

OSC4Bitwig exists and works great:
https://github.com/git-moss/OSC4Bitwig
Directly supports Lemur too:
https://github.com/Lucid-Network/Lemur4Bitwig-Template
It would be possible to OSCify the TouchOSC layout to make it work with OSC4Bitwig (I will probably not do it though since Lemur does so much more).

Don't know why the Faderport script doesn't work if it uses a unique GUID.
Send it to support maybe (if you didn't already)?

Cheers,

Tom

webhamster · Post by **webhamster** » Tue Apr 21, 2015 10:35 pm

I have uploaded it to Bitwig just now. When I hear from them I'll let you know.

Could you try the attached version. I've changed the GUID, maybe it does make a difference.

webhamster · Post by **webhamster** » Tue Apr 21, 2015 11:11 pm

I did just double check. The Faderport and Mackie MCU script load both at the same time for me.

webhamster · Post by **webhamster** » Sat Jun 20, 2015 6:17 pm

Zero interest from Bitwig in this controller (emailed them, even created a svn).
So download the Presonus Faderport driver here if you need it.

ThomasHelzle · Post by **ThomasHelzle** » Sat Jun 20, 2015 6:22 pm

Did you put it on Github and submit it here: http://www.bitwig.com/en/community/control_scripts.html ?
This should bring it into the Controller Library, but it's all done by hand and can take a while, especially now that the 1.2 Beta is out everybody will be _very_ busy...

Cheers,

Tom

webhamster · Post by **webhamster** » Sat Jun 20, 2015 6:36 pm

Yes did that back in April and emailed them.
After emailing them again I got a reply saying: 'as far as I know it will be checked and then listed in the controller section soon'.

ThomasHelzle · Post by **ThomasHelzle** » Sat Jun 20, 2015 7:09 pm

Now that sounds funny.
I can no longer help there but this is not the way it should be.

Cheers,

Tom

P.S. I wrote a mail to support about this and hope somebody at Bitwig will look into it sooner or later...

Liquinaut · Post by **Liquinaut** » Sun Jun 21, 2015 6:30 am

Thank you webhamster & Tom for your continued effort for integrating the Faderport Script into the Bitwig Controller Library. Much appreciated!

Cheers,

Paul

Bobby L'Avenir · Post by **Bobby L'Avenir** » Mon Jun 22, 2015 2:09 am

I didn't think the fader port was supported, does anyone know if I could get my frontier alpha track going with bitwig? Similar product to the fader port but it has a LCD screen, it's not great in mcu mode like most control surfaces out there. I can't get it to run under the generic midi control script, it sends midi but doesn't actually function and the screen is not displaying anything at all in that mode.

So anyway back to the faderport, can it access send levels on tracks as that seems to be broken even in control apps on the iPad like v-control?

Bobby L'Avenir · Post by **Bobby L'Avenir** » Mon Jun 22, 2015 9:50 pm

To webhamster & Tom many thanks for making this, i don't have a fader port but do have 2 Frontier Alpha Tracks (one with a faulty LCD) and this script works the basic functions of it in bitwig.

play
stop
ff & rewind kinda works as it jumps in bars on each press
fader
pan which is the same on all 3 touch sensitive knobs
loop
rec arm
solo

works very well but would there be any chance you could tweak this script to work the track select buttons which you currently have assigned to toggle the overdub switch on the left button and metronome on the right?

It would be so cool if you guys or someone else was able to go further as there's another 22 different switches on the alpha track if you can script the shift function too. either way though I'm very grateful, thanks a million

Liquinaut · Post by **Liquinaut** » Mon Jun 22, 2015 9:57 pm

Maybe you could also try the Mackie MCU Script. AFAIK the Faderport Script is based upon the Mackie MCU Script (webhamster please correct me if I'm wrong), and since the Mackie MCU offers plenties of additional functions, maybe some of them also apply to the Frontier Alpha Track? The Alpha Track does have a Mackie HUI Mode that can be enabled, right?

Worth a try, but since I don't own an AlphaTrack myself, please don't take any access for granted

Cheers,
Paul

Bobby L'Avenir · Post by **Bobby L'Avenir** » Mon Jun 22, 2015 10:35 pm

Liquinaut wrote:Maybe you could also try the Mackie MCU Script. AFAIK the Faderport Script is based upon the Mackie MCU Script (webhamster please correct me if I'm wrong), and since the Mackie MCU offers plenties of additional functions, maybe some of them also apply to the Frontier Alpha Track? The Alpha Track does have a Mackie HUI Mode that can be enabled, right?

Worth a try, but since I don't own an AlphaTrack myself, please don't take any access for granted

Cheers,
Paul

The MCU is pretty poor on the Alpha Track, it was designed for Ableton, the LCD shows the track names and the next track buttons work and even the send works, only the first send in bitwig anyway but trust me, it's messy.

Bobby L'Avenir · Post by **Bobby L'Avenir** » Tue Jun 23, 2015 12:03 am

OK so I don't know jack about scripting but I've managed to tweak the faderport script to show up as the Alpha Track, nudge through channels one by one with the correct buttons on the control surface and reassign the note editor, automation page and mixer to F1, F2 and F3 leaving F4 for the mixer if someone can help with that?

Alpha Track midi note on off is as follows;

pan button note on: 42
Send button note on: 41
eq button note on: 44
plugin button note on: 43
Auto button note on: 74
F1 button note on: 54
F2 button note on: 55
F3 button note on: 56
F4 button note on: 57
Flip button note on: 50
Shift button note on: 70
Touch sens knob 1 note on: 120
Touch sens knob 2 note on: 121
Touch sens knob 3 note on: 122
Touch sens knob 1 pushed note on: 32
Touch sens knob 2 pushed note on: 33
Touch sens knob 3 pushed note on: 34

I'll start a new thread on this in the scripting section too.

Cheers

webhamster · Post by **webhamster** » Wed Jun 24, 2015 6:50 am

I did use the MCU script to write the Faderport one, but ended up rewriting most of it. The faderport has a funny way of implementing the MCU and Bitwig scripting is still a bit limited so I had to work around that.
I do not use Bitwig anymore (will give it another try when 1.2 is out) so most likely I'll not be doing any updates.

Most likely for LCD support you'll have more luck using the MCU script.

Bitwig

KVR Audio

Support for Presonus Faderport?